The **resolve** package reproduces Node.js’s `require.resolve()` algorithm, letting you determine the exact file path of a module both asynchronously and synchronously (with optional customization of search rules, extensions, core‑module handling, exports‑field resolution, etc.). It’s aimed at developers building bundlers, loaders, or tooling that needs to mimic Node’s module resolution behavior outside of the runtime.
Total donated
Undistributed
Share with your subscribers:
Recipients
How the donated funds are distributed
Support the dependencies of substack/node-resolve
A simple cache for a few of the JS Error constructors.
Is this specifier a node.js core module?
Node.js path.parse() ponyfill
Determine if the current node version supports the `--preserve-symlinks` flag.
My shareable eslint config
An ES5 spec-compliant `Array.prototype.map` shim/polyfill/replacement that works as far down as ES3.
copy-dir
Validate or fix code that doesn't adhere to EditorConfig settings or infer settings from existing code.
Detect if we were run as a result of `npm publish`
Recursively mkdir, like `mkdir -p`
fs.rename but works across devices. same as the unix utility 'mv'
Command line tool for creating or updating a .npmignore file based on .gitignore.
An Object.keys replacement, in case Object.keys is not available. From https://github.com/es-shims/es5-shim
A deep deletion module for node (like `rm -rf`)
Ensure that when you `npm publish`, the "latest" tag is only set for the truly latest version.
The semantic version parser used by npm.
tap-producing test harness for node and browsers
Temporary file and directory creator
Support the repos that depend on this repository
Top contributors
Recent events
Kivach works on the Obyte network, and therefore you can track all donations.
No events yet
