semver
patch-package
semver | patch-package | |
---|---|---|
7 | 65 | |
4,962 | 9,975 | |
0.6% | - | |
7.0 | 6.3 | |
6 days ago | 20 days ago | |
JavaScript | TypeScript | |
ISC License | MIT License |
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.
patch-package
-
Finding Stars and Affirmations in the Sky with Three.js for Ayra Starr
In order to allow users to use their device as a controller to adjust the position of the camera and find stars, I use the depreciated DeviceOrientationControls by patching it back into Three. In order for DeviceOrientationControls to function, we need access the user to grant access to their device's orientation. I attempt to gain access to this, alongside their camera, during a previous step of the UX using a custom composable I wrote for this purpose. You can see that permission step in the mockup video above. Once this permission is granted, we can initialize our DeviceOrienationControls with a single line.
-
TypeScript NPM Packages Done Right
If you use Yarn, there’s the `yarn patch` command [1], which lets you maintain patches for your dependencies. Even though I try to upstream patches wherever possible, sometimes you just want to apply a quick patch and move on, especially if the dependency is poorly maintained or even worse, deeply nested in your dependency hierarchy. I use `yarn patch` regularly, it’s one of the main reasons why I moved to Yarn in the first place.
If you’re not using Yarn, there seems to be a similar thing on npm, `patch-package`. [2] I never had to use that though.
[1]: https://yarnpkg.com/cli/patch
[2]: https://www.npmjs.com/package/patch-package
- Fix broken node modules instantly
-
How to ignore an error , that happens in a node modules library ?
You can use patch-package to edit the part of the library.
- Jest not recommended to be used in Node.js due to instanceOf operator issues
-
Getting kinda stuck with a build error, any help much appreciated
patch-package
-
Credentials Leak with Knex
NPM doesn't have a patch command, but you can use patch-package to achieve the same result.
-
Why react native is so shit
If there's issue ticket discussing it and someone can fix it, ask for patch file and use patch-package to patch it
- Eas local build, how skip npm install
-
Invariant Violation: ViewPropTypes has been removed from React Native. Migrate to ViewPropTypes exported from 'deprecated-react-native-prop-types'.
You can try this (I highly recommend you to use the Patch Package library to track changes on any external library that you are using. (https://www.npmjs.com/package/patch-package)
What are some alternatives?
husky - Git hooks made easy 🐶 woof!
dotenv - Loads environment variables from .env for nodejs projects.
node-pre-gyp - Node.js tool for easy binary deployment of C++ addons
Electron - :electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
vite - Next generation frontend tooling. It's fast!
os-locale - Get the system locale
vercel - Develop. Preview. Ship.
opencv - OpenCV Bindings for node.js
Faker.js - What really happened with Aaron Swartz?
hypernova - A service for server-side rendering your JavaScript views
basic-ftp - FTP client for Node.js, supports FTPS over TLS, passive mode over IPv6, async/await, and Typescript.