fstream-npm
fstream-npm copied to clipboard
npm
fstream class for creating npm packages
Packages which have a `files` property in their `package.json` file and want to publish a dependency-frozen package with [npm-shrinkwrap](https://www.npmjs.org/doc/cli/npm-shrinkwrap.html) need to explicitly state that `npm-shrinkwrap.json` file is to be included...
Previously, files were treated as negated-negated ignores. This made it fairly tricky to control whether files or .npmignore took priority when deciding whether a file should be included. With this...
Fixes https://github.com/npm/npm/issues/10243, refs https://github.com/npm/read-package-json/pull/52 Currently, `*.gyp` files are all renamed to `binding.gyp` if a `package.json` file exists in the same directory (potentially clobbering each other if multiple `*.gyp` files exist)....
Do not rename multiple *.gyp files to binding.gyp . As a side-effect, no .gyp files will be renamed if binding.gyp is present. Fix: https://github.com/npm/npm/issues/8411
Fixes: https://github.com/npm/npm/issues/8510
This makes it so we keep track of which files from the files array have actually had any matches. npm will then be able to warn about them as needed....
This will prevent issues like https://github.com/substack/node-browserify/issues/1687, where a user has a 'files' list, or .npmignore file, and inadvertently tries to exclude their browserify/webpack entry point.
When publishing npm packages under a single-character folder in root directory, `fstream-npm` generates malformed tarball package without the "package" directory in package.tgz. Check out https://github.com/npm/fstream-npm/blob/master/fstream-npm.js#L355 When publishing a package under...
It seems that due to following approach: ``` // we don't want empty directories to show up in package // tarballs. // don't emit entry events for dirs, but still...
