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
# ./packages/FormRuntime/package-scripts.ymlscripts:
dev:
description: Local Development Modescript: >- npx parcel devlint: >- npx eslint ./test: >- npx jestwatch:
description: run in the amazingly intelligent Jest watch modescript: >- jest --watchbuild:
prod:
script: >- parcel build
The command executed:
yarn nps formruntime lint
or
npx nps formruntime lint
The output:
> yarn nps formruntime lintyarn run v1.22.5
$ C:\Storage\Projects\Forms\node_modules\.bin\nps formruntime lintnps is executing `formruntime` : npx nps --config=./packages/FormRuntime/package-scripts.yml --Usage: nps.js [options] <script>...Commands: nps.js init automatically migrate from npm scripts to nps nps.js completion generate completion scriptOptions: --config, -c Config file to use (defaults to nearest package-scripts.yml or package-scripts.js) [default: "C:\Storage\Projects\Forms\package-scripts.yml"] --silent, -s Silent nps output [boolean] [default: false] --log-level, -l The log level to use [choices: "error", "warn", "info", "debug"] [default: "info"] --prefix, -p Prefix for each script name --require, -r Module to preload --scripts Log command text for script [boolean] [default: true] --help-style, -y Choose the level of detail displayed by the help command [choices: "all", "scripts", "basic"] [default: "all"] -v, --version Show version number [boolean]Examples: nps.js test build Runs the `test` script then the `build` script nps.js "test --cover" "build --prod" Runs the `test` script and forwards the "--cover" flag then the `build` script and forwards the "--prod" flagAvailable scripts (camel or kebab case accepted)dev - Local Development Mode - npx parcel devlint - npx eslint ./test - npx jestwatch - run in the amazingly intelligent Jest watch mode - jest --watchbuild.prod - parcel buildScripts must resolve to strings. There is no script that can be resolved from "lint" https://github.com/sezna/nps/blob/master/other/ERRORS_AND_WARNINGS.md#missing-script error Command failed with exit code 1.info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Problem description:
want to split up monorepo tasks among their relevant areas
> npx npsUsage: nps.js [options] <script>...Commands: nps.js init automatically migrate from npm scripts to nps nps.js completion generate completion scriptOptions: --config, -c Config file to use (defaults to nearest package-scripts.yml or package-scripts.js) [default: "C:\Storage\Projects\Forms\package-scripts.js"] --silent, -s Silent nps output [boolean] [default: false] --log-level, -l The log level to use [choices: "error", "warn", "info", "debug"] [default: "info"] --prefix, -p Prefix for each script name --require, -r Module to preload --scripts Log command text for script [boolean] [default: true] --help-style, -y Choose the level of detail displayed by the help command [choices: "all", "scripts", "basic"] [default: "all"] -v, --version Show version number [boolean]Examples: nps.js test build Runs the `test` script then the `build` script nps.js "test --cover" "build --prod" Runs the `test` script and forwards the "--cover" flag then the `build` script and forwards the "--prod" flagAvailable scripts (camel or kebab case accepted)formruntime.dev - Local Development Mode - npx parcel devformruntime.lint - npx eslint ./formruntime.test - npx jestformruntime.watch - run in the amazingly intelligent Jest watch mode - jest --watchformruntime.build.prod - parcel build
The text was updated successfully, but these errors were encountered:
nps
version:node
version:npm
version:Scripts file (or at least the relevant bits):
The command executed:
yarn nps formruntime lint
or
npx nps formruntime lint
The output:
Problem description:
want to split up monorepo tasks among their relevant areas
Suggested solution:
I actually came up with this wrapper:
lets me have these yaml files:
output becomes:
The text was updated successfully, but these errors were encountered: