If Node reports Cannot find module 'puppeteer-core/internal/...', first distinguish that internal-path error from a missing puppeteer-core package. The documented causes for the internal-path form include an old Node.js version and a custom module resolver such as jest-resolve. Check the full error, the project where the script runs, and the Node and resolver versions before changing dependencies. If the error names only puppeteer-core, start by verifying that the package is installed in that project.
Identify which module Node cannot resolve
Read the entire error message, including the quoted module name and the first lines of the stack trace. These two messages point to different failure layers:
| Error form | What it indicates | First check |
|---|---|---|
Cannot find module 'puppeteer-core' |
Node cannot find the package entry point from the script’s execution context. | Is puppeteer-core installed and declared in the package or workspace running the script? |
Cannot find module 'puppeteer-core/internal/...' |
The top-level package may be present, but a particular internal path cannot be resolved. Puppeteer’s troubleshooting guide lists old Node.js and custom resolvers as possible causes. | Check Node.js and any test runner, bundler, or custom resolver involved in the stack. |
| A browser executable or launch error after import | JavaScript found the package; failure occurred later, while connecting to or launching a browser. | Check how the browser is supplied and the launch or connection settings. |
The internal-path wording is specifically covered in Puppeteer’s official troubleshooting documentation. An error mentioning the package name alone is not enough to conclude that this documented internal resolver issue is occurring.
Fix a missing top-level package
Run package-manager checks from the project or workspace that executes the script, not from an unrelated parent directory. In a monorepo, a dependency installed in one workspace is not necessarily available to a script in another. Use the package manager already selected by the project and preserve its lockfile.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Check and install with npm
npm ls puppeteer-core
npm install puppeteer-coreIf the project already declares the dependency and you are restoring its locked installation, use the project’s normal clean-install workflow instead of changing versions unnecessarily:
npm ciCheck and install with pnpm or Yarn
pnpm why puppeteer-core
pnpm add puppeteer-coreyarn why puppeteer-core
yarn add puppeteer-coreUse the add command only if the package is genuinely absent from the executing project. If it is declared already, first restore dependencies with the project’s usual install command. A workspace may require adding the dependency specifically to the package that imports it; follow that repository’s workspace conventions rather than installing it globally.
Check the import and project module format
For Node.js use of the core library, Puppeteer’s installation guide demonstrates this package import:
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
import puppeteer from 'puppeteer-core';Import the published package name, puppeteer-core, rather than reaching into an undocumented internal path in application code. Internal paths are implementation details; code that imports them can become sensitive to package or resolver changes.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsIf the package is installed but the import still fails, inspect the project’s module format and the exact installed Puppeteer release. The official changelog records a move to ESM-only packages and raised Node.js minimums. An upgrade can therefore expose incompatibility between the installed release, runtime, project module format, or a bundler/test resolver. Do not copy an old CommonJS workaround or pin an arbitrary version without first confirming which release the project expects.
Useful checks from the project directory include:
node --version
npm ls puppeteer-coreFor pnpm or Yarn, use the corresponding dependency inspection command above. In a workspace, also confirm that the script is launched from the intended package and that its dependency manifest lists the package there.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
For an internal-path error, check Node and the resolver
Puppeteer’s troubleshooting guidance names Node.js versions below 14 and custom resolvers such as jest-resolve as possible causes of Cannot find module 'puppeteer-core/internal/...'. For a custom-resolver case, it says upgrading the resolver or its parent package, such as Jest, usually works.
Separately, the current Puppeteer system requirements page lists Node.js 22.12 or later; that page displayed version 25.12.0 when checked on September 29, 2026. These statements answer different questions: “below 14” is a condition mentioned on the troubleshooting page for this particular error, not the current general supported minimum. Check the requirements for the Puppeteer version actually installed because the documentation and compatibility requirements can change.
- Record the runtime from
node --versionin the same environment that runs the failing script. A local shell, CI job, container, and production host can use different Node versions. - Inspect the stack trace for a test runner or custom resolver. If the failure occurs only under Jest or another resolver-based tool, compare the resolver and its parent package versions with the project’s current Puppeteer release.
- Update the outdated resolver or parent package when the stack points to one, using the project’s normal dependency-update process. Review the lockfile diff and run the relevant tests; do not assume that reinstalling Puppeteer alone will fix an incompatible resolver.
- Check the installed Puppeteer release’s system requirements and the project’s module format before changing the Node version or package version.
If this began immediately after upgrading Puppeteer, treat the version change as useful diagnostic evidence. Check the installed version, runtime, module format, and resolver or bundler compatibility together. A package-manager reinstall can reproduce the same incompatible combination if the manifest and lockfile still select it.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Choose the right Puppeteer package for browser ownership
puppeteer and puppeteer-core serve different setup expectations. Choose based on who manages the browser, not as a blind fix for a module-resolution error.
| Package | Browser setup | When it fits |
|---|---|---|
puppeteer |
Provides the end-user package’s defaults and automatically downloads a browser. | The project wants Puppeteer’s standard local setup and browser-download workflow. |
puppeteer-core |
Does not download Chrome during installation and has no assumed browser defaults. | The project manages a local browser itself or connects to a remote browser. Supply the relevant executable path or connection details. |
Switching packages changes browser management; it is not a general-purpose way to repair an unresolved internal module. If the top-level import works but launch later reports a missing executable, that is a browser-setup issue rather than Node failing to resolve puppeteer-core.
Do not use Puppeteer configuration to repair this import
Puppeteer’s configuration guide states that configuration files and environment variables are ignored by puppeteer-core. Those settings therefore will not make Node resolve a missing package or internal path. For core, configure the browser through the options and connection details used by your code instead of expecting the full Puppeteer package’s configuration workflow to apply.
Recommended Free Tools
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Troubleshoot by symptom
puppeteer-coreitself is missing: Install or restore the dependency in the package that runs the script. Verify the import spelling and workspace location.- Only an
internal/...path is missing: Check the runtime and whether Jest or another custom resolver appears in the stack. For an outdated resolver, upgrade it or its parent package where appropriate. - The import succeeds, but launch cannot find Chrome: Supply a managed browser executable or connection details, or choose
puppeteerif its automatic browser download and defaults fit the project. - The failure appeared after an upgrade: Compare installed release, Node version, module format, resolver, and lockfile changes. Avoid changing several of these at once; make a focused update so the cause remains identifiable.
- It works locally but fails in CI or a container: Compare the Node version and installed dependencies in the failing environment with the successful one. Ensure dependency installation runs for the workspace that executes the script.
- You changed Puppeteer configuration but nothing changed: Configuration files and environment variables are ignored by
puppeteer-core; configure browser launch or connection options directly.
Or skip the browser setup
If your goal is simply to capture a website screenshot rather than to run Puppeteer code in your application, ScreenshotNeo provides a screenshot API. One GET request returns a PNG, JPEG, WebP, or PDF; see the ScreenshotNeo API documentation for request options.
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 before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and the response identifies page verdict and billing status in headers. It also offers an MCP server with take_screenshot, get_page_info, and capture_pdf tools for AI agents. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. This is an alternative for obtaining captures, not a repair for an application that needs to import Puppeteer.
Sign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.
Frequently Asked Questions
Should I delete node_modules to fix this error?
Not as the first step. Confirm the dependency declaration, execution workspace, runtime, and resolver involved; restore dependencies using the project’s package manager if the installation is actually incomplete.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Does this error prove Puppeteer itself is broken?
No. The missing package, an unresolved internal subpath, and a browser-launch failure are distinct layers. The full module name and stack trace help identify which one failed.
Quick Recap
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.
