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
I've wanted to add notification to the end of some of my build paths and have run into issues where I'm using parallelshell for watching. That is, the same set of commands ( build:scripts, build:templates, etc. ) are called by two paths, either a npm run build or npm run watch.
In the case of the former, the build script simply calls npm run build:scripts && npm run build:templates.
In the case of the latter, there are nodemon's watching a directory that call the corresponding script ( build:scripts, build:templates, etc. ) as things become available.
If I put a call to notify in, say, build:templates, it works fine if I call it directly ( either npm run build or npm run build:templates ). However, if it is called inside parallelshell it fails ( npm run watch -> nodemon ).
You can try it out for yourself by using this simple package:
I've wanted to add notification to the end of some of my build paths and have run into issues where I'm using
parallelshell
for watching. That is, the same set of commands ( build:scripts, build:templates, etc. ) are called by two paths, either anpm run build
ornpm run watch
.In the case of the former, the
build
script simply callsnpm run build:scripts && npm run build:templates
.In the case of the latter, there are
nodemon
's watching a directory that call the corresponding script ( build:scripts, build:templates, etc. ) as things become available.If I put a call to
notify
in, say,build:templates
, it works fine if I call it directly ( eithernpm run build
ornpm run build:templates
). However, if it is called insideparallelshell
it fails (npm run watch
-> nodemon ).You can try it out for yourself by using this simple package:
The text was updated successfully, but these errors were encountered: