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
deno task is slowly becoming my go-to way of running package.json#scripts, even in Node.js projects, because I don't need to worry whether my dependencies are all installed or if I first have to run npm install.
It works for basic scripts, but it breaks in the case of a script calling another one through npm run (if you want an example, try running deno task build-loose and deno task build in https://github.com/tc39/proposal-defer-import-eval/). It would be great if it worked in that case, and I can think of three ways to do so:
blindly replace npm run with deno task in the executed command
alias npm to some intermediate program, that dispatches npm run to deno task and everything else unchanged to the real npm
create a .bin folder in the node_modules folder that Deno generates, so that the real npm is able to find the scripts it needs to run
The text was updated successfully, but these errors were encountered:
deno task
is slowly becoming my go-to way of runningpackage.json#scripts
, even in Node.js projects, because I don't need to worry whether my dependencies are all installed or if I first have to runnpm install
.It works for basic scripts, but it breaks in the case of a script calling another one through
npm run
(if you want an example, try runningdeno task build-loose
anddeno task build
in https://github.com/tc39/proposal-defer-import-eval/). It would be great if it worked in that case, and I can think of three ways to do so:npm run
withdeno task
in the executed commandnpm
to some intermediate program, that dispatchesnpm run
todeno task
and everything else unchanged to the realnpm
.bin
folder in thenode_modules
folder that Deno generates, so that the real npm is able to find the scripts it needs to runThe text was updated successfully, but these errors were encountered: