Run the project you want to test in and see your changes!.In the directory of the project that you want to test your NPM package, just run an npm install with the path to your.You can then copy the name of that newly created file. tgz and print the name of the generated file in your console. tgz file at the directory’s root with a structure like this. This will ensure that what would get included in a usual publish process will be what you package up to install locally. Run your build command from the directory of your application that gets published as an NPM package.How do you test changes to one of these NPM packages locally without having to publish and then install in the project you’d like to test in? Do you have to publish any change you want to test? Luckily, it’s very easy to work with NPM packages locally thanks to a couple of handy features!

This has been a boon for us, but it also came with its own challenges. Over the last year, we have transitioned some of our infrastructure at RIMdev into several NPM packages that we can use across various projects. Working with NPM packages locally can feel a little bit overwhelming at first.

Npm update package