https://github.com/iansu/npm-linked-install-repro
https://github.com/iansu/npm-linked-install-repro
Last synced: about 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/iansu/npm-linked-install-repro
- Owner: iansu
- Created: 2023-02-02T22:12:07.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2023-02-02T22:25:20.000Z (over 2 years ago)
- Last Synced: 2025-01-26T06:44:52.187Z (4 months ago)
- Language: JavaScript
- Size: 1.95 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# npm-linked-install-repro
When using `install-strategy=linked` the package namespace is being dropped from workspace packages which causes imports to fail
I have two packages in a workspace in this repo:
- `@iansu/package-a`
- `@iansu/package-b`
`@iansu/package-b` has a dependency on `@iansu/package-a`
When no install strategy is specified this is what the root `node_modules` directory looks like:
```txt
❯ tree node_modules
node_modules
└── @iansu
├── package-a -> ../../packages/package-a
└── package-b -> ../../packages/package-b
3 directories, 0 files
```
In this case nothing is installed in `package-b`'s `node_modules` directory
When `install-strategy=linked` is specific this is what the root `node_modules` directory looks like:
```txt
❯ tree node_modules
node_modules
├── package-a -> ../packages/package-a
└── package-b -> ../packages/package-b
2 directories, 0 files
```
Additionally this is what `package-b`'s `node_modules directory looks like:
```txt
❯ tree packages/package-b/node_modules
packages/package-b/node_modules
└── package-a -> ../../package-a
1 directory, 0 files
```
When I try to import from `@iansu/package-a` I get an error because neither `node_modules/@iansu/package-a` or `packages/package-b/node_modules/@iansu/package-a` exist