I'm a self-taught dev focused on websites and Python development.
My friends call me the "Data Genie".
When I get bored, I find tech to read about, write about and build things with.
I'm a self-taught dev focused on websites and Python development.
My friends call me the "Data Genie".
When I get bored, I find tech to read about, write about and build things with.
I'm a self-taught dev focused on websites and Python development.
My friends call me the "Data Genie".
When I get bored, I find tech to read about, write about and build things with.
I'm a self-taught dev focused on websites and Python development.
My friends call me the "Data Genie".
When I get bored, I find tech to read about, write about and build things with.
Thank you, interesting post!
But I think it is better to run the binary from node_modules like this:
Thanks for the tip. Npx is nice for scaffolding create apps but I didn't know it works for local packages.
According to this post I can just do a command without run.
blog.scottlogic.com/2018/04/05/npx...
Do you know if it respects the arguments?
Like if I wanted to run
Can I do that with npx? Like
Yes, you can)
Example:
run hexo version
run hexo version --debug
Thanks
Also my alias approach only works from the root. Does npx run from git root when run from anywhere?
I tried different options to learn how it works.
package.json located in /srv/projects/awesome-project/frontend/web/
gulp located in /srv/projects/awesome-project/frontend/web/node_modules/gulp/bin/
Run npx gulp --tasks
1) on /srv/projects/awesome-project/frontend/web/
2) on /srv/projects/awesome-project/frontend
Of course it doesn't work.
3) on /srv/projects/awesome-project/frontend/web/js
4) on /srv/projects/awesome-project/frontend/web/js/dist
Result - npx searches for the node_modules directory in the parent directories and tries to run the binary from there.
Neat