You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When uncompressing a file, pacm should follow symlinks (only if that are inside the package) and write out the file. This is needed for nodejs which has the following:
This is actually more difficult than I first thought for node / npm. The node executable is a single binary so that is fine, but the npm and npx executables are javascript scripts, which rely on files from the included packages javascript files:
$ grep "require" ~/src/bin/npm
var unsupported = require('../lib/utils/unsupported.js')
var log = require('npmlog')
var npm = require('../lib/npm.js')
var npmconf = require('../lib/config/core.js')
var errorHandler = require('../lib/utils/error-handler.js')
var nopt = require('nopt')
const pkg = require('../package.json')
let notifier = require('update-notifier')({pkg})
const isCI = require('ci-info').isCI
const color = require('ansicolors')
It might be time to look at extracting the code related to a package, have created a new issue for that #7.
When uncompressing a file, pacm should follow symlinks (only if that are inside the package) and write out the file. This is needed for
nodejs
which has the following:So currently, only
node
is written to disk, the others are ignored. Butnpm
andnpx
should both be written to disk (rather than symlinked).The text was updated successfully, but these errors were encountered: