-
We have a similar error with the use of ``catalog:``` to reference node modules versions.
 of pkg work for you?
5.15.0
### What version of Node.js are you using?
20.18.0
### What operating system are you using?
…
-
### My Environment
| Dependency | Version |
| --------------------------- | -------- |
| Node.JS version | v20.12.2 |
| react-color-palette version | v7.3.0 |
…
-
## Affected Packages
@changesets/cli
## Problem
I have a monorepo (using Turbo) that I'm using PNPM with. I've recently restructured where my packages physically live and what they are called…
-
## Proposal
For applications which leverage multiple server-side applications (or) are tending towards a microservice approach, we can try to support `yarn workspaces` and `pnpm workspaces` which l…
-
Currently Deno supports `workspace:*` specifiers in `package.json`, but tools like pnpm also support
`workspace:^`, `workspace:~` and others.
See https://pnpm.io/workspaces#publishing-workspace-pa…
-
### 💡 Feature Request: Nested Deno Workspaces
**Description**
Add support for nested workspace configuration in Deno projects to better organize code by domains and subdomains, similar to how pnpm…
-
I was creating a new package in a monorepo by copying an existing one. I forgot to change the name and ended up with two workspaces having identical names. `pnpm install` did not complain, `manypkg` d…
-
### Describe the bug
*I initialy though this was a case of https://github.com/vitejs/vite/issues/11468#issuecomment-2073871487, but it seems it is something else, so I am opening another issue.*
…
-
### Issue
Aider gets stuck on /map. My repo only has 424 files, but when I attempt to talk with LLM or run /map it gets stuck processing. Tested with multiple model with same behavior. Uninstalled an…