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]: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined #8362
Labels
Comments
Line 6 of constants.js actually contains the following:
|
compat.js exports the |
OrKoN
added a commit
that referenced
this issue
May 18, 2022
Running only tsc-cjs does not seem sufficient for rebuilding the project after the compat layer for ESM was introduced. Let's run `tsc` instead although it's somewhat slower. Issues: #8362
OrKoN
added a commit
that referenced
this issue
May 18, 2022
Running only tsc-cjs does not seem sufficient for rebuilding the project after the compat layer for ESM was introduced. Let's run `tsc` instead although it's somewhat slower. Issues: #8362
OrKoN
added a commit
that referenced
this issue
May 18, 2022
Running only tsc-cjs does not seem sufficient for rebuilding the project after the compat layer for ESM was introduced. Let's run `tsc` instead although it's somewhat slower. Issues: #8362
OrKoN
added a commit
that referenced
this issue
May 19, 2022
Running only tsc-cjs does not seem sufficient for rebuilding the project after the compat layer for ESM was introduced. Let's run `tsc` instead although it's somewhat slower. Issues: #8362
OrKoN
added a commit
that referenced
this issue
May 19, 2022
Running only tsc-cjs does not seem sufficient for rebuilding the project after the compat layer for ESM was introduced. Let's run `tsc` instead although it's somewhat slower. Issues: #8362
OrKoN
added a commit
that referenced
this issue
May 19, 2022
Running only tsc-cjs does not seem sufficient for rebuilding the project after the compat layer for ESM was introduced. Let's run `tsc` instead although it's somewhat slower. Issues: #8362
Thanks for the detailed report! I think this should be fixed now. |
This was referenced May 30, 2022
This was referenced May 30, 2022
This was referenced May 30, 2022
This was referenced Jun 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
This is a problem that I can currently see locally when trying to run the Puppeteer unit tests with the latest upstream revision. Once it failed it always fails even for installing Puppeteer. The only workaround is to manually remove the
lib/
folder with generated code.Steps to reproduce the problem:
npm install
=> successnpm run funit
=> successnpm install
=> successnpm run funit
=> failurenpm install
=> failure@OrKoN maybe these steps help to analyze the problem. At least for me these always reproduce it.
Puppeteer version
14.1.0-post
Node.js version
v17.9.0
npm version
v8.5.5
What operating system are you seeing the problem on?
macOS
Relevant log output
The text was updated successfully, but these errors were encountered: