I had node installed on my computer before installing Kitten. When I would run kitten-npm, it would use the previously-installed node instead of kitten-node.
This changes kitten-npm from a simple symlink into a simple bash script that makes sure to prepend the KITTEN_RUNTIME_BINARIES_PATH to the PATH env variable before calling kitten-npm so that the version of node installed by kitten is always used when kitten-npm is called.
This is basically replicating the functionality that already exists here:
Lines 267 to 281 in 8c4e473
export function npm (command, modulePath) {
const env = Object.assign(process.env, {NODE_OPTIONS: ''})
env.PATH = `${paths.KITTEN_RUNTIME_BIN_DIRECTORY}:${env.PATH}`
try {
childProcess.execSync(`${kittenNpm}${command}`, {
encoding: 'utf-8',
env,
cwd: modulePath
})
return true
} catch (error) {
console.error(`npm ${command} failed on path ${modulePath}`, error)
return false
}
}
I had `node` installed on my computer before installing Kitten. When I would run `kitten-npm`, it would use the previously-installed `node` instead of `kitten-node`.
This changes `kitten-npm` from a simple symlink into a simple bash script that makes sure to prepend the KITTEN_RUNTIME_BINARIES_PATH to the PATH env variable before calling `kitten-npm` so that the version of `node` installed by kitten is always used when `kitten-npm` is called.
This is basically replicating the functionality that already exists here: https://codeberg.org/kitten/app/src/commit/8c4e473c4cf63c8b732773bc246287eae89ec998/src/Utils.js#L267-L281