Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →TS2307 means TypeScript cannot resolve the module named in the import; it does not identify one universal LangChain fix. Start with the quoted module specifier in the full diagnostic. If it names a LangChain loader path, verify that path against the installed @langchain/community version. If it names puppeteer, check that dependency in the workspace running the typecheck. Then make sure TypeScript’s module-resolution mode matches whether the project runs on Node.js or uses a bundler.
Read the full diagnostic before changing packages
Copy the entire error, especially the name inside quotation marks. TypeScript’s documentation uses “Cannot find module ‘./settings.json’ or its corresponding type declarations” as an example for JSON imports; it is not a LangChain-specific diagnosis. The same TS2307 code can point to different missing modules, so the specifier—not just the code—determines what to inspect.
As an Amazon Associate I earn from qualifying purchases.
@langchain/community/...: check the loader subpath and exports for the installed community package.puppeteer: check whether Puppeteer is installed and visible to the importing workspace.puppeteer-core/internal/...: investigate Puppeteer’s Node-version or custom-resolver guidance; this is a separate issue from the LangChain loader path.
For the official TypeScript explanation of module resolution, see TypeScript’s module reference. For its JSON-import example, see resolveJsonModule.
Check the loader import against your installed LangChain version
LangChain’s current JavaScript reference documents PuppeteerWebBaseLoader in its web Puppeteer document-loader API area. Its load() method returns LangChain Document objects. The reference search result showed version 1.1.27 as latest at crawl time; use the documentation matching the version actually installed rather than assuming an older tutorial’s path still applies. See the LangChain Puppeteer loader reference and document loader index.
#1 Best Overall
As a version-specific example, the published @langchain/community 1.1.4 declaration at puppeteer.d.ts imports Document and loader interfaces from @langchain/core, and browser types and functions from puppeteer. It declares PuppeteerWebBaseLoader methods including scrape(), load(), screenshot() and imports(). That verifies the declaration for 1.1.4 only; inspect the release you have installed before copying a subpath or assuming exports are identical.
Verify what the application actually installed
- Check the dependency versions in the package that runs the TypeScript check, not only the monorepo root or a sibling app.
- Confirm
@langchain/communityis installed in that workspace and that its package entry point contains the requested loader export or subpath. - If the error names
puppeteer, confirm that package is installed and resolvable from the importing workspace. The community 1.1.4 declaration imports its types directly. - When multiple LangChain packages are in use, follow the package installation guidance and keep a common
@langchain/coreversion aligned. See LangChain’s package and installation guidance.
Match TypeScript resolution to the project host
TypeScript’s moduleResolution setting controls how import specifiers are found. Its current guidance distinguishes modern Node modes such as node16 and nodenext from bundler, which is intended for bundler-hosted projects. Choose the mode that corresponds to how this application resolves modules at runtime; changing it reflexively can trade one error for another.
Rank #2
| Project host | Resolution direction | Check |
|---|---|---|
| Modern Node.js | Use the modern Node resolution mode appropriate to the project, such as node16 or nodenext. |
Ensure the configured module mode and package metadata agree with how Node executes the application. |
| Bundler | Consider bundler resolution for a bundler-hosted project. |
This mode supports package exports while allowing extensionless relative imports. |
See TypeScript’s module-resolution guidance for the rules around package subpaths and exports. A subpath that works in one resolution mode or package release may be absent or blocked in another.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Do not paper over a dependency path with paths
TypeScript warns that paths can override package metadata such as exports. A mapping may make an import typecheck while leaving the runtime or bundler unable to resolve the same specifier. Prefer correcting the import, dependency installation, package version, or host-appropriate resolution configuration; use a path mapping only when the runtime resolution is deliberately made consistent too.
Separate type resolution from launching a browser
If TS2307 is gone but Puppeteer cannot find or start a browser, that is a later runtime failure, not the missing TypeScript import. Puppeteer notes that some package managers block install scripts; if a browser download is needed, its troubleshooting guide offers npx puppeteer browsers install. Consult Puppeteer troubleshooting for installation and operating-system dependency issues.
If the full error names puppeteer-core/internal/..., Puppeteer identifies Node versions below 14 or a custom resolver such as jest-resolve as possible causes in that specific case, and points to supported Node versions or updating the resolver. Do not treat that internal-module error as evidence that the LangChain loader subpath is missing.
Distinguish TS2307 from a package export mismatch
A framework build can fail because a class is not exported even when a module is found; that is not the same diagnosis as TS2307. LangChain.js issue #8441, opened July 1, 2025, describes BaseDocumentLoader export errors involving filesystem loaders in a reported setup with @langchain/community 0.3.47, @langchain/core 0.3.61, langchain 0.3.29, Node 22.12.0 and Next.js 15.3.4. It is a version-specific report, not a general TS2307 fix. Compare your installed versions and inspect the specific package entry point if your error is an export complaint. See LangChain.js issue #8441.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchUse a screenshot API if your actual goal is capturing a page
If you need the page image or PDF rather than LangChain’s browser-backed document loading, ScreenshotNeo is a separate website screenshot API and MCP server. It can return PNG, JPEG, WebP or PDF; it does not resolve a TS2307 in your LangChain project.
Best Value
- Used Book in Good Condition
Or skip the browser setup
One GET request can capture a URL without configuring Puppeteer locally. See the ScreenshotNeo API documentation for request options.
Quick Recap
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups and chat widgets before capture; each step can be turned off. Bot checks/CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, with response headers identifying the page verdict and billing status. Its MCP server offers take_screenshot, get_page_info and capture_pdf for Claude, Cursor and other MCP clients. The free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
