Is it possible to run any post processing script after installing NPM module automatically.
I have a case where, I can install some specific NPM modules in my node.js project. After installation of NPM module, I need to update some places in project automatically.
Is it doable?
Yes. Add a postinstall script to your package.json as described in the npm documentation
Related
I have a Node.js project which has several dependencies.
I created the package.json file (npm init)
and try to install all the relevant packages
(npm install all) or (npm install)
with npm install I'm getting the following result:
npm notice created a lockfile as package-lock.json. You should commit this file.
but
when I'm trying to run, I'm getting error that a package is missing (i.e express and I need to install it manually)
Is there a way (command) to install at once (with one command) all the relevant packages and dependencies ? (instead of install each of the package manually) ?
Update 1:
I think I found the solution to your problem, you can use this npm module for auto installing your dependencies.
Install
npm install -g auto-install
Usage
Run auto-install in the directory you are working in.
So npm is simple!
you can add a single package using npm install package-name
or
you can install all using npm install, this will read your package.json file and install all the packages which are in there
Additionally you can do this:
npm install package1 package2 package to install multiple packages.
If a required dependency is not installed, just install it once manually using npm's --save argument and it will automatically add that dependency to your package.json.
For instance, if you are missing the express dependency, just run:
npm install --save express
That will install the dependency in your node_modules folder and also automatically update your package.json file to include express. On subsequent installs on different machines, you'll now only need to run npm install and the express package will be added automatically.
Update with a little more context: In Node your package.json file defines all dependencies that are required for your project. However, these dependencies are not automatically generated for you. npm init will create a boilerplate package.json, but it will not fill that package.json with any dependencies.
You need to define the dependencies yourself, which you can do one of two ways:
Manually add lines to your package.json's dependencies section
Use npm install --save <package name> to have npm install a package and automatically save that package as a dependency in your package.json file
If you aren't familiar with package.json files, I'd recommend sticking to approach number 2 so that npm handles editing that file for you.
Once you have a package.json with all of the dependencies you need, then when you pull down your project onto new machines you will be able to automatically install all dependencies at once using a simple npm install command. You can test this on your own machine by deleting the node_modules folder and running npm install, then trying to run your project. If it runs fine then you successfully added all dependencies to your package.json. If it complains about a missing package then add that package with npm install --save <package>
I am integrating firebase cloud functions with my app's workflow. I needed to install a package so I did npm install --save #sendgrid/mail. The installation was a success but I can't see the dependency either in node_modules folder or the package.json file. What do I do?
One way to add the package would be to do the reverse. Add #sendgrid/mail to your package.json with the version you want, and then run npm install.
I using npm a few years. But I still don't know when npm install devDependencie and when don't install?
In npm docs, npm install --production don't install devDependencies.
But in my testing, I init a package, add eslint to dependencies, run npm install --production, the eslint's devDependencies still installed? I don't know why?
I want a table to specify when to install or when to skip.
devDependencies are dependencies that you only use during local development, including running local tests and running local build tools. eslint is a devDependency because you only use it for local code linting.
dependencies are for dependencies required for your final deliverable project to run. Your project might be an npm module, or a node program, or a bundled Javascript file. If you use Webpack to build your Javascript, but don't include Webpack's source code in your final output, then webpack is a devDependency.
This is especially important when publishing an npm node module so that the consumers of your package don't download other packages that are never used.
Following this question, NPM dependencies can be installed using:
$ npm install --ignore-scripts
Is there a way to mark that a dependency should be installed without running scripts in package.json?
This is because, when I run npm install --ignore-scripts, the dependency is added to package.json. As a result, other users will install the package while running scripts, however I want this certain package to never run scripts.
I could be wrong but I believe its: npm install -ignore-script package-name#version
I'm able to build contextify 0.1.1 using node-gyp on Windows, but I don't know how to get npm to recognize/use this version when resolving other modules' dependencies. 'npm install' fails with the same (expected) 'node-waf was unexpected at this time.' error, despite having a build version of contextify in the local directory.
Put simply: how do I tell npm to use a module I've built myself, instead of trying to download/build its own?
npm install installs modules into the current directory's node_modules directory. So instead of using npm install at all, just move/copy the contextify module that you built yourself to node_modules/contextify. Unfortunately you will have to do this for any module that depends on contextify.
Hope that helps!