You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to run web-test-runner inside of a monorepo and I get this error:
$ npm test -w packages/memory
> fsx-memory@0.4.0 test
> web-test-runner --node-resolve tests/*.js
node:internal/modules/cjs/loader:452
throw err;
^
Error: Cannot find module 'C:\Users\nzaka\projects\humanwhocodes\fsx\packages\web\node_modules\proxy-agent\dist\index.js'. Please verify that the package.json has a valid "main" entry
at tryPackage (node:internal/modules/cjs/loader:444:19)
at Module._findPath (node:internal/modules/cjs/loader:715:18)
at Module._resolveFilename (node:internal/modules/cjs/loader:1130:27)
at Module._load (node:internal/modules/cjs/loader:985:27)
at Module.require (node:internal/modules/cjs/loader:1235:19)
at require (node:internal/modules/helpers:176:18)
at Object.<anonymous> (C:\Users\nzaka\projects\humanwhocodes\fsx\packages\web\node_modules\@puppeteer\browsers\lib\cjs\httpUtil.js:46:23)
at Module._compile (node:internal/modules/cjs/loader:1376:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
at Module.load (node:internal/modules/cjs/loader:1207:32) {
code: 'MODULE_NOT_FOUND',
path: 'C:\\Users\\nzaka\\projects\\humanwhocodes\\fsx\\packages\\web\\node_modules\\proxy-agent\\package.json',
requestPath: 'proxy-agent'
}
Node.js v20.11.0
npm ERR! Lifecycle script `test` failed with error:
npm ERR! Error: command failed
npm ERR! in workspace: fsx-web@0.4.0
npm ERR! at location: C:\Users\nzaka\projects\humanwhocodes\fsx\packages\web
I'm trying to run web-test-runner inside of a monorepo and I get this error:
Some other details about the project:
package.json
"type": "module"Environment Info
@web/test-runner
v0.18.0Reproduction steps
npm install
cd packages/memory
npm i @web/test-runner
package.json
to be "web-test-runner tests/*.js --node-resolve"npm test
The text was updated successfully, but these errors were encountered: