eb-disable-npm
Advanced tools
Comparing version 1.0.0 to 1.0.1
{ | ||
"name": "eb-disable-npm", | ||
"version": "1.0.0", | ||
"version": "1.0.1", | ||
"description": "Disables npm in Elastic Beanstalk environments.", | ||
@@ -29,4 +29,4 @@ "scripts": { | ||
"dependencies": { | ||
"install-files": "^1.0.0" | ||
"install-files": "^1.1.5" | ||
} | ||
} |
@@ -11,4 +11,4 @@ # eb-disable-npm | ||
along with our application source from our CI server. What makes this possible is | ||
that it already installs the modules for the purposes of running our tests, and | ||
uses the same architecture as Elastic Beanstalk's EC2 instances. | ||
that the CI server already installs the modules for the purposes of running our | ||
tests, and uses the same CPU architecture as Elastic Beanstalk's EC2 instances. | ||
@@ -20,3 +20,3 @@ This package has been tested against Elastic Beanstalk platform versions | ||
1. `npm install eb-fix-npm --save-dev` (see [here](https://github.com/mixmaxhq/install-files/blob/master/README.md#installation) for why `--save-dev`) | ||
1. `npm install eb-disable-npm --save-dev` (see [here](https://github.com/mixmaxhq/install-files/blob/master/README.md#installation) for why `--save-dev`) | ||
2. Commit the `.ebextensions` file it creates. | ||
@@ -23,0 +23,0 @@ |
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
5659
2
Updatedinstall-files@^1.1.5