A simple tool that can merge the
devDependency dependency types for npm/yarn
package.jsons or bower
bower.jsons into a single
bower.json object (and optionally file). To properly support frontend scenarios, this tool also merges
resolutions, and ignores unnecessary field recommendations for private npm/yarn packages. Perfect for projects like UserFrosting where plugins (Sprinkles) provide virtually all functionality.
NOTE: While non-semver values are supported, they will act as an override and emit a warning (even if logging is disabled). This override behavior only applies to 'incoming' values. This behavior does not match npm, yarn or bower.
NOTE: This is currently an offline tool, and as such conflicts further down the dependency chain are not evaluated. There is however a duplicate dependency detection tool for yarn to allow the creation of workarounds in the meantime (see docs/api
NOTE: Any dependencies with a path specified as the version will not be adjusted, even if an output location is specified.
npm i -D @userfrosting/merge-package-dependencies
To merge multiple
package.json's into a single object, and save to a specified location...
;let result = mergePackages;
Generally speaking, all releases should first traverse through
rc (release candidate) to catch missed bugs and gather feedback as appropriate. Aside from this however, there are a few steps that MUST always be done.
- Make sure
CHANGELOG.mdis up to date.
- Update version via
npm version 3.0.0or
npm version patch.
- Create release on GitHub from tag made by