This will be MUCH faster than shelling out to npm.
Note that the proposed libraries for publish/pack will significantly increase the dependency tree of beachball due to pulling in a significant number of the npm CLI's dependencies... that's unfortunate from an installation standpoint, and worth considering alternatives maybe? Or those dependencies could be bundled to minimize bulk?
An advantage of moving away from CLI-based publish is that it would get rid of the horrible platform-specific spawn workarounds from #1211...
Related links:
- show/view core logic using
pacote (which downloads all fields of the manifest regardless of args) -- went with simpler npm-registry-fetch instead for now
This will be MUCH faster than shelling out to npm.
libnpmpublishlibnpmpacknpm-registry-fetch,see Fetch packages from registry directly, not with npm CLI #1114temporarily reverted in Temporarily revert npm-registry-fetch usage #1145--see Re-enablenpm-registry-fetch#1143Note that the proposed libraries for publish/pack will significantly increase the dependency tree of beachball due to pulling in a significant number of the npm CLI's dependencies... that's unfortunate from an installation standpoint, and worth considering alternatives maybe? Or those dependencies could be bundled to minimize bulk?
An advantage of moving away from CLI-based
publishis that it would get rid of the horrible platform-specific spawn workarounds from #1211...Related links:
pacote(which downloads all fields of the manifest regardless of args) -- went with simplernpm-registry-fetchinstead for now