-
Firstly, thanks for this really useful package!
Despite not being [mentioned in the docs](https://docs.npmjs.com/cli/v7/using-npm/workspaces#defining-workspaces) NPM supports workspace wildcards, i…
-
### Self-service
- [ ] I'd be willing to implement a fix
### Describe the bug
When running binaries in a workspace, it's possible for `yarn` to **incorrectly** determine that the binary is availabl…
-
If you have a monorepo, and you have two workspaces `A` and `B`, you can import contracts from `A` in `B` doing:
```solidity
import "A/contracts/SomeContract.sol";
```
But you can't import the…
-
```
> node src/controllers/engine/generate.mjs
Generating storage context...
No valid data found at path: cache/doc_store.json starting new store.
No valid data found at path: cache/index_store.…
-
msr@4.0.0
https://github.com/qiwi/semantic-release-toolkit/runs/5289081231?check_suite_focus=true
npm ERR! code ENOWORKSPACES
npm ERR! This command does not support workspaces.
https://githu…
-
And add `npm >= 7` at [engines field](https://docs.npmjs.com/cli/v7/configuring-npm/package-json#engines)
Update lock file
Move to workspaces from lerna
-
## Motivation ("The Why")
Currently `npm deprecate` can only handle one package at a time, and only through a `@` syntax. Given the work towards providing better workspaces workflows, it's very lik…
-
## Motivation ("The Why")
Yarn already supports this option. It makes it possible to work with tooling that expects certain modules to be located in inside the same package that consumes them.
#…
-
**Describe the bug**
If pnpm_workspace.yaml is present for an npm-managed project, it will override the package.json["workspaces"] setting, which is not intuitive
**Pants version**
\>2.17
**OS…
tobni updated
3 months ago
-
This repository looks nice!
---
I recognized that in the main package.json one is advised to use `yarn` instead of `npm`.
Should this only be for developers of this repo or also for users of th…