Load node modules according to tsconfig paths, in run-time or via API.
Get the first path that exists on disk of multiple paths
Get paths for storing things like data, config, cache, etc
Load modules according to tsconfig paths in webpack.
Vite resolver for TypeScript compilerOptions.paths
Enforces module path case sensitivity in Webpack
Determine (XDG-compatible) paths for storing application files (cache, config, data, etc)
Convert Windows backslash paths to slash paths
Determine common OS/platform paths (home, temp, ...)
Tests whether one path is inside another path
UnRS Resolver Node API
ZLayer Plugin Development Kit for TypeScript
very fast object redaction
Extends `minimatch.match()` with support for multiple patterns
Universal filesystem path utils
walk paths fast and efficiently
Ergonomic TypeScript SDK for ZLayer. Wraps the auto-generated OpenAPI client (@zlayer/api-client) with convenience methods and a Unix-socket-aware fetch.
Runs (webpack) loaders
Get the paths of edge browser easily
Moving a file to different folder, could result in changing all imports statement in that file. This will not happen is the import paths are absolute. The eslint rule helps enforcing having absolute import paths. Support eslint --fix to automatically chan
Access to __filename and __dirname within ECMAScript modules
Transforms module resolution paths using TypeScript path mapping and/or custom paths
No description provided.
Easily get the CWD (current working directory) of a project based on package.json, optionally starting from a given path. (node.js/javascript util)