New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: #7986
Comments
You can see an example of this for This affects those using Subsequently is it possible just to add those to the |
Ugh, sorry about that. We didn't realise that the internal modules were used directly. Let's see how we can fix it (happy to review a PR) but my first thought is: perhaps we should create an API for this use case? |
@OrKoN an API or a dedicated export would be appreciated, thanks! We're seeing the same issue with WebdriverIO (and other frameworks that rely on it, like Serenity/JS), which relies on Puppeteer to run local tests. Here are the Perhaps they could be added to |
Change of plans: we are going to revert the change and re-land it later in a backwards-compatible way. |
closing as solved in 13.3.1. Thanks for the quick turnaround |
Bug description
Steps to reproduce the problem:
puppeteer-core
./lib/cjs/puppeteer/revisions
Puppeteer version
13.3.0
Node.js version
14.19.0
npm version
6.14.19
What operating system are you seeing the problem on?
Linux, macOS
Relevant log output
The text was updated successfully, but these errors were encountered: