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
module.exports={scripts: {build: 'eleventy --input src --output dst',develop: '$npm_package_scripts_build --serve',test: 'echo "Error: no test specified" && exit 1'}};
The command executed:
nps develop
The output:
nps is executing `develop` : $npm_package_scripts_build --serve/bin/sh: --serve: command not foundThe script called "develop" which runs "$npm_package_scripts_build --serve" failed with exit code 127 https://github.com/sezna/nps/blob/master/other/ERRORS_AND_WARNINGS.md#failed-with-exit-code
Problem description:
npm allows templating in values from package.json; a script like $npm_package_scripts_build --serve would be expanded out to eleventy --input src --output dst --serve (given a build script of eleventy --input src --output dst). As nps init blows away the existing scripts, even if this variable were templated in it would not be valid.
Suggested solution:
Perhaps it could be enough to throw on init if one of these variables are found, since automatic conversion is not necessarily what you want. For instance, you could have a script like this:
{
"scripts": {
"version": "echo Current version: v$npm_package_version"
}
}
Capturing the version as a static value into your package-scripts.js on nps init is not equivalent here. 🙂
The text was updated successfully, but these errors were encountered:
nps
version: 5.10.0node
version: 12.16.1npm
version: 6.13.4Scripts file (or at least the relevant bits):
The command executed:
nps develop
The output:
Problem description:
npm
allows templating in values frompackage.json
; a script like$npm_package_scripts_build --serve
would be expanded out toeleventy --input src --output dst --serve
(given abuild
script ofeleventy --input src --output dst
). Asnps init
blows away the existing scripts, even if this variable were templated in it would not be valid.Suggested solution:
Perhaps it could be enough to throw on
init
if one of these variables are found, since automatic conversion is not necessarily what you want. For instance, you could have a script like this:Capturing the version as a static value into your
package-scripts.js
onnps init
is not equivalent here. 🙂The text was updated successfully, but these errors were encountered: