-
using Default devcontainer https://github.com/dotnet/dotnet/blob/main/.devcontainer/devcontainer.json and executing `./build.sh`, I consistently hit the following error once build starts for aspnetcor…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### This issue exists in the latest npm version
- [X] I am using the latest npm
### Current Behavior
We have a m…
-
#### [1] Run `` in all of my workspaces (parent → child).
With Wireit, you can already just do `npm run build -ws` to run a given script in all workspaces, which is the standard npm workspaces appr…
-
we have this internal dependency where the sample-cookout package depends on the client package.
right now there's a `file:` dependency entry in sample-cookout. this isn't well supported, and it ma…
-
### What version of Bun is running?
1.0.0+822a00c4d508b54f650933a73ca5f4a3af9a7983
### What platform is your computer?
Linux 5.15.0-1041-azure x86_64 x86_64
### What steps can reproduce the bug?
…
-
Workspaces support is now implemented in npm.
So, having workspaces in package.json should not force yarn anymore.
Lockfile should take precedence.
Thanks
-
I don't know exactly when but `npm` started to embrace workspaces as such. Because of that `node_modules` is in root repo and not in individual packages. `npm i` doesn't install `node_modules` in sequ…
-
`npx husky init` is generating this invalid pre-commit script:
`npm`
See bin.js:
`w('.husky/pre-commit', p.env.npm_config_user_agent?.split('/')[0] ?? 'npm' + ' test\n')`
So possible values …
-
Lerna has caused several issues with bugs and security vulnerabilities. We should therefore move to NPM Workspaces.
-
https://github.com/npm/cli/issues/3637
NPM > v7.20.2 does not work with workspaces. You cannot install deps from your monorepo, within your monorepo.
NPM CLI will always try to install from the …