Included in all copies or substantial portions of the Software.

The above copyright notice and this permission notice shall be

Software is furnished to do so, subject to the following Restriction, including without limitation the rights to use,Ĭopy, modify, merge, publish, distribute, sublicense, and/or sellĬopies of the Software, and to permit persons to whom the Obtaining a copy of this software and associated documentationįiles (the 'Software'), to deal in the Software without Permission is hereby granted, free of charge, to any person Support: if you find any problems with this module, email / tweet / License: MIT - do anything with the code, but don't blame me if it does not work. Do Not Let NPM Cache Snowball on CI blog post.For big projects where installing the dependencies takes a long time, and cache restores are faster, useRollingCache will provide a performance improvement. This is the recommended setup for small projects. The rule of thumb is this: if re-installing your dependencies doesn't take very long, you can avoid superfluous cache restores by keeping useRollingCache off. Instead of letting the cache grow forever, this action resets it every month by including the current month in the cache key. To get better cache hit rates without the cache size snowballing, you can turn on this action's useRollingCache option, which will allow old caches to be re-used when your dependencies change, at the expense of some snowballing. See this post for more details on this issue. This is the default cache key strategy to avoid unbounded growth of the cache, as if you don't expire the cache, it will continue being added to. If you change any dependencies, there will be a cache miss. Each workflow uses this action to install dependenciesīy default, this action will cache dependencies using an exacty hashs of the lock file (like package-lock.json, npm-shrinkwrap.json or yarn.lock). all environment inputs are done inside the action, so they can be stubbed and controlled during tests.Using Mocha and Sinon.js following the guide How to set up Mocha with Sinon.js. Tip: environment variable ACTIONS_STEP_DEBUG enables debug messages from this action itself, try it first. You can see verbose messages from GitHub Actions by setting the following secrets (from Debugging Actions Guide) ACTIONS_RUNNER_DEBUG: true Const = require ( 'npm-install' ) await npmInstallAction ( ) Debugging

Npm install from github version