-
-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Stopped working with yarn
#196
Stopped working with yarn
#196
Comments
It's due to the glob pattern. Yarn is expanding the glob and not sending it to
See also: #200 |
@TreTuna It's been a while since I posted this, so I cannot truly confirm what you're saying. But judging from my original comments, that wouldn't explain why Also, the issue you're pointing at is related to |
The error is very similar to mine, except that I'm getting it with $ npm --version
7.8.0
$ npm run build:cat
> coreutils@0.0.0 build:cat
> cd src/uu/cat && wasm-pack build && npx pkg2wef
# ...executes successfully
$ npx npm-run-all build:cat
Watching /home/snejugal/projects/wubix-crates/coreutils and all sub-directories not excluded by your .gitignore. Will not monitor dotfiles.
Found & ignored ./node_modules ; is listed in .gitignore
Starting: build:cat
node:internal/modules/cjs/loader:928
throw err;
^
Error: Cannot find module '/home/snejugal/projects/wubix-crates/coreutils/build:cat'
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:925:15)
at Function.Module._load (node:internal/modules/cjs/loader:769:27)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:76:12)
at node:internal/main/run_main_module:17:47 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}
^C # note: it doesn't exit but stuck in some infinite loop wasting CPU time
$ npx npm-run-all --version
v4.1.5
$ npm i -g npm@6
removed 58 packages, changed 11 packages, and audited 436 packages in 6s
3 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
$ npm --version
6.14.12
$ npx npm-run-all build:cat
> coreutils@0.0.0 build:cat /home/snejugal/projects/wubix-crates/coreutils
> cd src/uu/cat && wasm-pack build && npx pkg2wef
# ...executes successfully as well
$ npx npm-run-all --version
v4.1.5 FWIW, the repo is public: https://gitlab.com/wubix-crates/coreutils (note that if you try to execute |
I ran into this issue with Yarn Classic (v1) and the workaround was to downgrade from npm v7 to npm v6:
|
@petermikitsh worked for me too, any idea why the downgrade is even a solution though? |
change from
to
|
In yarn v3, `run-p 'bundle:*'` must be quoted. See: mysticatea/npm-run-all#196 (comment)
In yarn v3, `run-p 'bundle:*'` must be quoted. See: mysticatea/npm-run-all#196 (comment)
In yarn v3, `run-p 'bundle:*'` must be quoted. See: mysticatea/npm-run-all#196 (comment)
While having the following scripts on
package.json
:running
npm run build
works fine and does exactly what is expected. Usingyarn
, however, fails with a bunch of exceptions.Interestingly, this only seems to happen if scripts include
run-s
,run-p
ornpm-run-all
calls. For instance, running simplyyarn clean
(which invokesrimraf
) works, but runningyarn run-s clean
fails with the same exception shown above.Using:
The text was updated successfully, but these errors were encountered: