Now the tab completion, for myApp mind you, will be enabled in all new terminal windows (so start a new one to try it).If you're developing on Windows, we recommend that you use vsts-npm-auth to fetch the credentials and inject them into your %USERPROFILE%\.npmrc. Instead of creating a separate file, like we did above, we can send it to ~/.bashrc which is a file that is run as you start a new terminal window.
#Npm config set reset how to#
I’m not good enough in Linuxy things to know how to do that. Until you load it into the current shell.
#Npm config set reset code#
For example npm completion > myAppTabCompletion.sh will create a file called myAppTabCompletion.sh with the necessary code to get tab-completion to work.īut it doesn’t work. sh file that enables the tab completion for the package.json in the current directory. It’s a little bit weird I think but here’s how it works.Ĭalling npm completion will create a.
You can enable tab-completion in npm for all commands and even the scripts in the package.json too. That in itself can be useful as documentation. Just giving the command npm run will list all scripts in your package.json. This can prove very useful as a setting to tweak in your build server for example. We can simply turn logging up or down by going npm run deploy:prod -ddd or npm run deploy:prod -s. " deploy:prod " : " npm run test & npm run version:patch & npm run push & npm run launch " , So for our mega-build-script-calling-into-other-scripts thing we built before: What I found interesting is that this is passed on to npm scripts. For example -s turns logging more or less off ( -d is more logging, and -ddd is silly logging, try it!), that can be useful to tweak. s to silence it downĪny parameter you pass to npm at the command prompt is used for that entire command. There’s some small things with the npm command that is easily missed and that can prove useful. There’s a number of different ways to do this, of course. That describes one way to get watching and reloading of browsers. Well… you can read about this in the section above on running in parallel. Pretty nice, and yet another option to use. If something changes on the client, our browser(s), will be reloaded. Meaning that we something changes on the server nodemon will restart the server for us. Here we start our node server and a live reload functionality for our browser at the same time. This can be accomplished, also using normal “linux” commands, with the & switch or what you call it. We will see later, under Watching, we will have the need to start more than one thing simultaneous, running tasks in parallel. Now all of that is packed into the build-js command. That file is then passed to the uglifyjs (you front-end guys and your names) that minifies the file and puts it into the static/bundle.js. The output of the browserify command is a bundled file with all the code from all the required modules into one file (the -t reactify is simply packing up. " build-js " : " browserify -t reactify app/js/main.js | uglifyjs -mc > static/bundle.js "īy using the | you can take the result of one task and pass it on to the next. I also “borrowed” from this post an example where you want to send the output from one task into the next one. There’s more options just using normal command line functionality: Piping result into the next command In the last post I used & to call task one after another. If you liked this post I know you will love the course! Thank you for reading this
I’ve written two posts on npm scripting with package.json and during the course of these post I’ve picked up some tricks that I didn’t really use in the posts.
0 kommentar(er)
