speculate - npm Package Compare versions

Comparing version 2.0.0-alpha.4 to 2.0.0-alpha.6

lib/spec.js

@@ -51,3 +51,4 @@ 'use strict';
       license: pkg.license,
-      prune: getValueFromSpec(pkg.spec, 'prune', true)
+      prune: getValueFromSpec(pkg.spec, 'prune', true),
+      rebuild: getValueFromSpec(pkg.spec, 'rebuild', true)
     },
@@ -54,0 +55,0 @@ getExecutableFiles(pkg),

package.json

 {
   "name": "speculate",
-  "version": "2.0.0-alpha.4",
+  "version": "2.0.0-alpha.6",
   "description": "Automatically generates an RPM Spec file for your Node.js project",
@@ -5,0 +5,0 @@ "main": "index.js",

README.md

@@ -85,2 +85,12 @@ # speculate
 
+If for some reason you do not want to rebuild your native modules, you can explicity tell speculate not to rebuild by adding the following to your `package.json`:
+
+```json
+{
+  "spec": {
+    "rebuild": false
+  }
+}
+```
+
 A typical speculate build looks like this:
@@ -87,0 +97,0 @@

test/spec.js

@@ -32,2 +32,10 @@ 'use strict';
 
+  it('removes the rebuild step when specified', () => {
+    const pkg = require('./fixtures/my-cool-api-no-rebuild');
+    const expected = loadFixture('my-cool-api-no-rebuild.spec');
+    const spec = createSpecFile(pkg);
+
+    assert.equal(spec, expected);
+  });
+
   it('sets the release number when specified', () => {
@@ -34,0 +42,0 @@ const releaseNumber = 7;

New alerts

New author

Supply chain risk

A 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

Improved metrics

Total package byte prevSize

58181

increased by3.17%

Number of package files

58

increased by3.57%

Lines of code

959

increased by2.24%

Number of lines in readme file

342

increased by3.01%

Worsened metrics

Number of medium supply chain risk alerts

1

increased byInfinity%

No dependency changes