a special purpose fast memoizing way to resolve a node modules package.json
Resolve a path by walking parent directories.
Parses every stack trace into a nicely formatted array of hashes.
Layer and resolve configuration from YAML, JSON, or `.env` templates: merge multiple sources, interpolate literals (environment, built-in functions, AWS Parameter Store / Secrets Manager), write resolved files, and read values from the CLI or Node.js.
Helper library for module federation
Universal module importer for Node.js
Essential initialization for every JavaScript process
[](https://www.npmjs.com/package/@loaderkit/resolve) [](https://github.com/braidnetworks/loaderkit/blob/main/LICENSE) [](https://www.npmjs.com/package/contentful-resolve-response) [](https://github.com/c
Resolves a given package if it is installed locally, then tries to resolve it from global registry, using battle-tested [global-modules][] package. Better approach than internal `require.resolve`, so you can trust. You just get absolute filepath to some p
Library that resolves AWS Cloudformation templates with exact values
YAML 1.2 parser and serializer
Issues mentioned in `README` should be solved by other approaches: - `.addEventListener()` is blazing fast and is not a real performance issue - to solve issues with ordering in case when regular DOM event propogation is not available consider to use thi
Parse, Resolve, and Dereference JSON Schema $ref pointers
React Freeze
An algorithm for resolving imports in Sass
Webpack loader that resolves relative paths in url() statements based on the original source file