Epic: npm exec spec issues
#403
Labels
Comments
ruyadorno
added a commit
to ruyadorno/cli
that referenced
this issue
Mar 30, 2022
Fixes the proper path location to use when targetting specific workspaces. Makes it so that libnpmexec is always reading from the Arborist actual tree instead of reading `node_modules` from the file system when retrieving local package data. Fixes: npm#3520 Relates to: npm#4619 Relates to: npm/statusboard#403
ruyadorno
added a commit
to ruyadorno/cli
that referenced
this issue
Mar 30, 2022
Fixes the proper path location to use when targetting specific workspaces. Makes it so that libnpmexec is always reading from the Arborist actual tree instead of reading `node_modules` from the file system when retrieving local package data. Fixes: npm#3520 Relates to: npm#4619 Relates to: npm/statusboard#403
ruyadorno
added a commit
to ruyadorno/cli
that referenced
this issue
Mar 31, 2022
Fixes the proper path location to use when targetting specific workspaces. Makes it so that libnpmexec is always reading from the Arborist actual tree instead of reading `node_modules` from the file system when retrieving local package data. Fixes: npm#3520 Relates to: npm#4619 Relates to: npm/statusboard#403
ruyadorno
added a commit
to ruyadorno/cli
that referenced
this issue
Mar 31, 2022
Fixes the proper path location to use when targetting specific workspaces. Makes it so that libnpmexec is always reading from the Arborist actual tree instead of reading `node_modules` from the file system when retrieving local package data. Fixes: npm#3520 Relates to: npm#4619 Relates to: npm/statusboard#403
ruyadorno
added a commit
to ruyadorno/cli
that referenced
this issue
Apr 11, 2022
Fixes the proper path location to use when targetting specific workspaces. Fixes: npm#3520 Relates to: npm/statusboard#403
ruyadorno
added a commit
to ruyadorno/cli
that referenced
this issue
Apr 19, 2022
Fixes the proper path location to use when targetting specific workspaces. Fixes: npm#3520 Relates to: npm/statusboard#403
ruyadorno
added a commit
to ruyadorno/cli
that referenced
this issue
Apr 19, 2022
Refactor / clean up of the logic around reading installed packages. Fixes reading packages from mixed sources (one being from the local installed tree and the other from the registry using pacote.manifest). Makes it so that libnpmexec is always reading from the Arborist actual tree instead of reading `node_modules` from the file system when retrieving local package data. Fixes: npm#3668 Relates to: npm#4643 Relates to: npm#4619 Relates to: npm/statusboard#403
lukekarrys
pushed a commit
to npm/cli
that referenced
this issue
Apr 19, 2022
Refactor / clean up of the logic around reading installed packages. Fixes reading packages from mixed sources (one being from the local installed tree and the other from the registry using pacote.manifest). Makes it so that libnpmexec is always reading from the Arborist actual tree instead of reading `node_modules` from the file system when retrieving local package data. Fixes: #3668 Relates to: #4643 Relates to: #4619 Relates to: npm/statusboard#403
lukekarrys
pushed a commit
to npm/cli
that referenced
this issue
Apr 19, 2022
Fixes the proper path location to use when targetting specific workspaces. Fixes: #3520 Relates to: npm/statusboard#403
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Epic
This is an issue to track the
npm exec / npx / npm init@specissues I've found. I'm not sure if they are all the same issue or just related, but a fix should likely address all of them.npm init <package>doesn't use newer version if existing version is semver-major incompatible cli#3444npx node-gyp@versionruns the copy of node-gyp bundled with npm instead cli#3058The text was updated successfully, but these errors were encountered: