postinstall-build - npm Package Compare versions

Comparing version 4.0.0 to 4.1.0

index.js

		@@ -137,2 +137,10 @@ var fs = require('fs')
		throw new Error('A build artifact must be supplied to postinstall-build.')
		} else if (!flags.silent && /^(npm\|yarn) /.test(buildArtifact)) {
		console.warn(
		"postinstall-build:\n '" + buildArtifact + "' is being passed as the " +
		'build artifact, not the build command.\n If your build artifact is ' +
		"a file or folder named '" + buildArtifact + "', you may ignore\n " +
		'this warning. Otherwise, you probably meant to pass this as the build ' +
		'command\n instead, and must supply a build artifact.\n'
		)
		}
		@@ -139,0 +147,0 @@

package.json

		{
		"name": "postinstall-build",
		"version": "4.0.0",
		"version": "4.1.0",
		"description": "Helper for conditionally building your npm package on postinstall in order to support git installs.",
		@@ -5,0 +5,0 @@ "repository": {

README.md

		@@ -67,4 +67,8 @@ [![Travis Status](https://travis-ci.org/exogen/postinstall-build.svg)](https://travis-ci.org/exogen/postinstall-build)
		will be generated by the build command. If the file already exists, the build
		command won’t be run. If you want to always build (not recommended), just pass a
		bogus file path.
		command won’t be run. The build artifact should almost certainly be included
		in the published npm package, so that normal installs from the npm registry don’t
		trigger a build (you can build in the `prepublish` hook, for example). If you want
		to always build, you may pass a bogus file path, but this is not recommended
		(if you’re always going to build, just make your `devDependencies` real
		`dependencies` instead of using `postinstall-build`).

		@@ -180,3 +184,3 @@ Note that if your `command` contains arguments (and thus has spaces), you should

		I recommend using npm 3 or better, except for npm 4.1.x–4.4.x.
		I recommend using npm 3 or better, except for npm 4.1.x–4.5.x.

		@@ -191,3 +195,3 @@ There are several distinct bugs in npm itself that you may encounter when using

		The `prune` command is broken in npm 4.1.x–4.4.x, and is unable to correctly
		The `prune` command is broken in npm 4.1.x–4.5.x, and is unable to correctly
		prune `devDependencies`. Thus, when `postinstall-build` is finishing up, it
		@@ -194,0 +198,0 @@ leaves behind extraneous packages. (See issues [#15727](https://github.com/npm/npm/issues/15727),

New alerts