
Security News
Crates.io Users Targeted by Phishing Emails
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
The chronological versioner.
$ npm i chronver
@chronver/regex
is an evergreen module. 🌲 This module requires an Active LTS Node version (v12.0.0+).
import chronver from "chronver";
new chronver({ increment: "change", version: "2030.04.03" }).version;
// ^ Returns 2030.04.03.1
new chronver({ increment: "year", version: "2030.04.03" }).version;
// ^ Returns 2031.04.03
new chronver({ increment: "month", version: "2030.04.03" }).version;
// ^ Returns 2030.05.03
new chronver({ increment: "day", version: "2030.04.03" }).version;
// ^ Returns 2030.04.04
new chronver({ coerce: "2030.4.3" }).version;
// ^ Returns 2030.04.03
new chronver().version;
// ^ Returns the current date in ChronVer format
// Here is how a full response looks
ChronVer {
change: 0,
day: 3,
month: 4,
raw: "2030.04.03",
version: "2030.04.03",
year: 2030
}
{
"scripts": {
"increment": "chronver --increment package"
}
}
This allows you to run npm run increment
and have your package.json
version incremented to ChronVer's spec. However if you want to have this happen automatically when committing to a repo, employ husky like so:
{
"husky": {
"hooks": {
"pre-commit": "npm run increment && git add -A :/"
}
}
}
ChronVer must be instantiated with the new
keyword.
Type: string
(optional)
coerce
will attempt to format it into a ChronVer object.Type: string
(optional)
version
parameter.change
: increments supplied version
...version by one.day
: increments supplied version
year by one.month
: increments supplied version
year by one.year
: increments supplied version
year by one.version
parameter is not supplied along with an increment
option:Type: string
| CVType
(optional)
parse
will test the validity of it and return a formatted ChronVer object.parse
. __
/ /
____/ / _______ _____ __________
/ __/ _ \/ __/ _ \/ _ | |/ / -_/ __/
\__/_//_/_/ \___/_//_|___/\__/_/
A JavaScript implementation of the https://chronver.org specification
Copyright © netop://ウエハ (Paul Anthony Webb)
Usage: chronver [options] <version>
Prints valid ChronVer versions
Options:
-c --coerce
Coerce a string into ChronVer if possible, silently fail otherwise.
-? -h --help
Show this help message.
-i --inc --increment [<level>]
Increment a version by the specified level. Level can be one of: year,
month, day, or change. Default level is "change".
Only one version may be specified.
The version returned will always default to the present. However,
supplied versions with a future date will remain in the future.
ex. Passing "1970.04.03 -i month" to ChronVer will return the present
date but passing "3027.04.03 -i month" will return "3027.05.03".
--init --initialize
Creates a ChronVer string, defaulting to the present.
ChronVer exits upon failure.
Examples:
$ chronver --initialize
$ chronver --increment month 2030.03.03
$ chronver --increment package
You will need to first download this repo, cd
into it, and npm i
before proceeding further.
# Run all tests, sequentially
$ npm test
# Test dependencies for latest versions
$ npm run test:dependencies
# Lint "bin" and "lib" directories
$ npm run test:typescript
# Run this module through its paces
# PLEASE run this so I can feel my time writing and troubleshooting these tests were worth it
$ npm run test:assert
MIT © netop://ウエハ
FAQs
The chronologic versioner
We found that chronver demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
Product
Socket now lets you customize pull request alert headers, helping security teams share clear guidance right in PRs to speed reviews and reduce back-and-forth.
Product
Socket's Rust support is moving to Beta: all users can scan Cargo projects and generate SBOMs, including Cargo.toml-only crates, with Rust-aware supply chain checks.