oh gosh this may or may not be that simple, haha. normal package resolutions are done this way: (lib/resolve.js):

pnpm install lodash@^4.0.0
> GET https://registry.npmjs.org/lodash/^4.0.0
> get `dist.tarball` and `dist.shasum` from its response

but scoped resolutions must be done this way:

pnpm install @rstacruz/tap-spec@^4.0.0
> GET https://registry.npmjs.org/@rstacruz%40tap-spec
> get `versions` from its response
> find the version that matches `^4.0.0` using `semver.maxSatisfies()`
> get `versions.{version}.dist.tarball` and `versions.{version}.dist.shasum` from it

they should also be stored in the store without a / to maintain the "flatness" of .store. This is because symlinks in node_modules inside it assume the store is at ../../. So that'd be:

node_modules/.store/@rstacruz--tap-spec@4.0.0  # ✓ ok
node_modules/.store/@rstacruz/tap-spec@4.0.0   # ✗ bad

Apart from this, there might be some symlinking voodoo that may come out of symlinking node_modules/.store/@rstacruz--tap-spec@4.0.0 -> @rstacruz/tap-spec, but I haven't given that part enough thought just yet.

Uh oh!

Uh oh!

Implementing scoped modules #9

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions