Package Exports

pseudo-patch

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 (pseudo-patch) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

pseudo-patch

Edge case solve for CI/CD pipelines or lambdas/any prroject really that doesn't need to published to npm, but has some changelog formatting dependancies.

This tool assumes your projects CHANGELOG.md adheres to Semantic Versioning, in the keepachangelog format.

Install

install in your project

yarn add pseudo-patch

configure package.json:

{
  "scripts": {
    "pseudo-patch": "pseudo-patch"
  }
}

What it does

nothing more then increase the package.json. Works with version-changelog and similar changelog formatting solutions that rely on the package.json['version'] being already icremented.

 {
  "name": "your-project",
-  "version": "1.0.0",
+  "version": "1.0.1",
 }