Package Exports

patch-version

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (patch-version) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

patch-version

Patch git tag version to package.json before publish to npm.

Usage

Install patch-version from npm.
Stick your package.json to one version. My suggestion is 0.0.1, as this package does.
Add patch-version command to deployment hook in your CI configuration file.
When you want to publish a new version to npm, create a tag with a valid semver, push it to trigger CI build and deployment. The tag version will be patched to package.json before publish to npm.

Supported CI

Travis
GitLab
AppVeyor

Example

Here is the example configuration in .travis.yml for Travis CI:

before_deploy:
  - ./node_modules/.bin/patch-version

deploy:
  provider: npm
  email: "my@email"
  api_key:
    secure: "secure-key"

License

MIT License.