Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
semver
-
The curious case of semver
Yeah, but it talks about the semver package, which is related and why it caused performance issues
-
Release NPM Package With Automatic Versioning
This release script increments the version number of the package and publishes the package to the NPM registry (or other registry). To correctly increment the version number, npm's semver package automatically finds the next version number according to the specified level minor (major/minor/patch).
-
Symbols in package.json
In a later post, I shall be sharing some actual examples using node-semver, which is the tool that npm uses to parse these Semantic Versioning Complaint dependencies version.
-
npm-registry-firewall
{ "server": { "host": "localhost", // Defaults to 127.0.0.1 "port": 3000, // 8080 by default "secure": { // Optional. If declared serves via https "cert": "ssl/cert.pem", "key": "ssl/key.pem" }, "base": "/", // Optional. Defaults to '/' "healthcheck": "/health", // Optional. Defaults to '/healthcheck'. Pass null to disable "keepAliveTimeout": 15000, // Optional. Defaults 61000 "headersTimeout": 20000, // Optional. Defaults 62000 "requestTimeout": 10000 // Optional. Defaults 30000 }, "firewall": { "registry": "https://registry.npmmirror.com", // Remote registry "entrypoint": "https://r.qiwi.com/npm", // Optional. Defaults to `${server.secure ? 'https' : 'http'}://${server.host}:${server.port}${route.base}` "base": "/", // Optional. Defaults to '/' "rules": [ { "policy": "allow", "org": "@qiwi" }, { "policy": "allow", "name": ["@babel/*", "@jest/*", "lodash"] // string[] or "comma,separated,list". * works as .+ in regexp }, { "policy": "deny", "name": "colors", "version": ">= v1.4.0" // Any semver range: https://github.com/npm/node-semver#ranges }, { "policy": "deny", "license": "dbad" // Comma-separated license types or string[] }, { "policy": "allow", "username": ["sindresorhus", "isaacs"] // Trusted npm authors. }, { "policy": "allow", "name": "d", // `allow` is upper, so it protects `< 1.0.0`-ranged versions that might be omitted on next steps "version": "< 1.0.0" }, { "policy": "deny", // Checks pkg version publish date against the range "dateRange": ["2010-01-01T00:00:00.000Z", "2025-01-01T00:00:00.000Z"] }, { "policy": "allow", "age": 5 // Check the package version is older than 5 days. Like quarantine } ] } }
-
Package.json File explained!!!
Note: ~ and ^ you see in the dependency versions are notations for version ranges defined in semver as it follows semantic versioning.
-
SemVer - 0.x.x
To prevent potential breaking changes, when you do a minor update of a dependency, NPM treats versions a bit different:
-
One-stop shop for working with semantic versions in your GitHub Actions workflows
Yeah, it's basically a wapper around semver package, so the outputs may look familiar to you. But if you need more in your workflows — feel free to open an issue with a feature you’re missing.
project
-
Introducing selfh.st/releases, a Collection of RSS Release Feeds for Self-Hosted Software
How is this better than https://github.com/OWNER/PROJECT/releases.atom? Since all the linked projects are from github anyway?
-
Issues creating a pre-commit hook from a Cobra based CLI
- repo: https://github.com/owner/project rev: 1.0.0 hooks: - id: project args: - "--tests=a,b,c" - "--path=."
- Everything about package.json
-
What's the general pattern for testing-developing crates downloaded from Github?
[dependencies] projname = { git = "https://github.com/owner/project.git" }
-
hooks you must know about package. Json
“homepage”: “https://github.com/owner/project#readme",
-
Package.json File explained!!!
"bugs":{ "url" : "https://github.com/owner/project/issues", "email" : "[email protected]" }
What are some alternatives?
husky - Git hooks made easy 🐶 woof!
metaverse - The Metaverse virtual reality. The final outcome of all virtual worlds, augmented reality, and the Internet.
dotenv - Loads environment variables from .env for nodejs projects.
fcc_file_metadata_microservice - Free Code Camp File Metadata Microservice
Electron - :electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
stingoftheviper - Share configuration between spf13/cobra and spf13/viper
os-locale - Get the system locale
cli - the package manager for JavaScript
opencv - OpenCV Bindings for node.js
caniuse - Raw browser/feature support data from caniuse.com
hypernova - A service for server-side rendering your JavaScript views
browserslist - 🦔 Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-preset-env