Resolve version of an installed module.
Plugin for git-json-resolver that applies semver-based merge strategies (max, min, secure, override) to resolve version conflicts in package.json and similar files.
resolve like require.resolve() on behalf of files asynchronously and synchronously
Resolve the path of a module like `require.resolve()` but from a given path
Resolve a directory that is either local, global or in the user's home directory.
Resolve the path of a module like `require.resolve()` but from the current working directory
Offers a async require.resolve function. It's highly configurable.
Resolve things like Node.js — ponyfill for `import.meta.resolve`
Resolve a relative path against a root path with validation
resolve which handles browser field support in package.json
Resolve URL pathnames using JavaScript
Locate and bundle third-party dependencies in node_modules
Resolve nested CSS selectors
Missing ECMAScript module utils for Node.js
A better path.resolve() that normalizes paths on Windows
Module resolution utilities based on Node.js upstream implementation.
Resolve a URI relative to an optional base URI
Read a protobuf schema from the disk, parse it and resolve all imports
Convert a dependency path into a filepath
Resolve an options object based on configuration.
Node default behavior import resolution plugin for eslint-plugin-import.
TypeScript definitions for resolve
Plugin for git-json-resolver that applies semver-based merge strategies (max, min, secure, override) to resolve version conflicts in package.json and similar files.
micromark utility to resolve subtokens
Resolves urls to the canonical version. It does this by following redirects in the headers or body of the destination url.
Resolves a breaking change in CanCanCan version 1.13.0 and above when using it with DraperDecorator
Play a history game
Tools used by Puppet to parse, validate, and compare Semantic Versions and Version Ranges and to query and resolve module dependencies.
Resolves the Puppet Modules in a Puppetfile with a full dependency graph, including Puppet version checks.
A custom git merge driver that auto-resolves the most common conflict in Rails schema files (db/schema.rb and, with the data_migrate gem, db/data_schema.rb): the define(version: N) line that gets bumped on every migration. Keeps the higher version on conflict and falls back to a normal merge conflict for any other diverging content.
The premise of this gem is that consumers of your API need versioning and different shapes of your resources. Without proper thought into versioning and shaping, your codebase can quickly resolve into a redundant and confusing state. This gem tries to solve that problem by allowing the API owner to use simple conventions -- Accept headers and ActiveModelSerializer namespacing -- to achieve controller reuse by controllers delegating resource versioning and shaping to the serializer level.
Resolves foreign keys, enums, booleans and custom transformations from PaperTrail::Version into structured, UI-ready hashes.
Service directory is the single place to register, browse, and resolve application services. Note that google-cloud-service_directory-v1beta1 is a version-specific client library. For most uses, we recommend installing the main client library google-cloud-service_directory instead. See the readme for more details.
Service Directory is the single place to register, browse, and resolve application services. Note that google-cloud-service_directory-v1 is a version-specific client library. For most uses, we recommend installing the main client library google-cloud-service_directory instead. See the readme for more details.
The premise of this gem is that consumers of your API need versioning and different shapes of your resources. Without proper thought into versioning and shaping, your codebase can quickly resolve into a redundant and confusing state. This gem tries to solve that problem by allowing the API owner to use simple conventions -- Accept headers and ActiveModelSerializer namespacing -- to achieve controller reuse by controllers delegating resource versioning and shaping to the serializer level.
The premise of this gem is that consumers of your API need versioning and different shapes of your resources. Without proper thought into versioning and shaping, your codebase can quickly resolve into a redundant and confusing state. This gem tries to solve that problem by allowing the API owner to use simple conventions -- Accept headers and ActiveModelSerializer namespacing -- to achieve controller reuse by controllers delegating resource versioning and shaping to the serializer level.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.