npm
export new RELEASE_TYPES constant
This will help library consumers better integrate semver into their apps.
Possible usecases of consuming this constant:
- Automatically show a dropdown of available release types that conform to the semver spec
- Validate user inputs where a release type is expected
I am happy to add this to the docs if this idea is approved by the maintainers.
Coverage remained the same at 100.0% when pulling 6bc60b71583d53529d5e16eec0b7c13e961c5360 on charlex:patch-1 into 9f5f615165b3a0b906467f1edeebb0f5de379a9e on npm:master.
Coverage remained the same at 100.0% when pulling 6bc60b71583d53529d5e16eec0b7c13e961c5360 on charlex:patch-1 into 9f5f615165b3a0b906467f1edeebb0f5de379a9e on npm:master.
Yes, please add to the docs, and add at least a basic test. (Just verify it exists and is what you expect; I realize it's kinda silly for such a trivial feature, but it prevents us from accidentally breaking it in the future and not noticing.)
@isaacs I added a section in the README, but it looks like this project as undergone a big change in its structure, and I'm not able to resolve the conflicts right now.
