-
## Motivation ("The Why")
We are moving from a non-workspace repository to using the workspaces feature. Previously we had two workspaces like `workspace-a/package-lock.json` and `workspace-b/packa…
-
-
The are several "plugins" that are developed over this project, for example, `iv-spectrum`, `thermal-resistance`, among others.
Every change in this repo is strongly related to these dependencies, an…
-
### Describe the bug
Running `lb-eslint` command from a package in npm workspaces environment throws following error:
Full Command: `lb-eslint --report-unused-disable-directives .`
```
Error…
-
I have a "real" monorepo with multiple workspaces under a single root repository (**_not_** a multi-root workspace). This extension doesn't support multiple function apps in a true, single-root monore…
-
We tried implementing pleb for publishing our packages, and we saw that in our structure, which is not a flat `packages` structure, `pleb` fails locating the packages.
steps to reproduce:
```sh
…
-
### What is the problem this feature would solve?
Support for config in `package.json`. https://docs.npmjs.com/cli/v9/configuring-npm/package-json#config
When adding in `package.json`:
```
{
…
-
I am a contributor to a project that has a complex architecture. There is a a job runner whose jobs make calls to third-party APIs through a collection of specialized plugins. The plugins are in tur…
-
GitLab has some support in https://github.com/npm/cli/pull/6375
https://gist.github.com/wlynch/42e89527d51bc72a61279f0c7f3be1cd
-
### Describe the bug
Using yarn PnP with workspaces causes swc to emit
```
ERROR failed to read input source map: failed to parse inline source map url
src.js.map
Caused by:
relati…