@olehermanse/utils
v0.1.12
Published
Utility functions in js / ts
Readme
Common js / ts utilities for personal use
I use these across a few different projects;
- https://github.com/olehermanse/trpg
- https://github.com/olehermanse/tpg
- https://github.com/olehermanse/towers
Publishing new versions
Here are the steps to make a new version:
- Check that
package.jsonhas the correct version: https://github.com/olehermanse/utils/blob/main/package.json#L3- It should be the version you want to release.
- Change it if necessary, for example to bump major or minor version.
- Create a release in GitHub:
- Open https://github.com/olehermanse/utils/releases
- Draft a new release
- Put the version number in both tag (create a new tag) and name field
- Generate release notes
- Check that the release has been published on npm:
- https://www.npmjs.com/package/@olehermanse/utils
- This is done automatically by the GitHub Action after creating a release.
- Check that the version number has been bumped:
- https://github.com/olehermanse/utils/commits/main/
- The GitHub Action will automatically push a commit bumping the patch version.
- Manually bump minor or major version if you know that is what you'll release next:
- https://github.com/olehermanse/utils/blob/main/package.json#L3
Token for publishing to npmjs.com
One secret is needed for the publishing action to work - NPM_TOKEN.
After logging into npmjs.com it is generated here:
https://www.npmjs.com/settings/olehermanse/tokens
I use a granular token with access to only this repository, and expiration of ~1 year. This is entered into GH UI here:
https://github.com/olehermanse/utils/settings/secrets/actions
The token is not stored anywhere else and must be regenerated if expired or compromised.
