Installation
fetch and ReadableStream are used internally). For full JavaScript-rendered portfolio scraping you will also want a browser peer dependency:
Canonical integration pattern
The most common production pattern combinescreateProvider, scrapePortfolio, and parseResume. Always call provider.cleanup() in a finally block so browser processes are never left dangling.
Neither
scrapePortfolio nor parseResume ever throws. Any failure is captured in result.error so a try/finally around cleanup() is sufficient — you do not need a catch block for the resolution functions themselves.Export reference
All public exports are grouped below. Click any category to jump to the dedicated reference page.Classifier
Portfolio Scraper
Resume Parser
Disambiguator
Browser providers
Types
API pages
Classifier
classifyInput, parseRepoUrl, parseGitLink, extractGitUrlsFromText, isGitProviderUrl, and GIT_HOSTSPortfolio Scraper
scrapePortfolio and extractLinksFromHtmlResume Parser
parseResume — dual-method PDF extraction with unpdfDisambiguator
resolveOwnerAndCategorize and dedupeProfilesByUsernamecreateProvider
Browser provider factory, all three provider classes, and the
BrowserProvider interfaceTypes
Complete TypeScript type reference for every exported interface and union type