```javascript import timeResolve from 'time-resolve'
resolve like require.resolve() on behalf of files asynchronously and synchronously
A fork of `import-meta-resolve` with commonjs + ESM support at the same time, AKA dual package.
Offers a async require.resolve function. It's highly configurable.
Uses export conditions to return environment information in a way that works with major bundlers and runtimes.
Parse, Resolve, and Dereference JSON Schema $ref pointers
Resolve a URI relative to an optional base URI
Resolve things like Node.js — ponyfill for `import.meta.resolve`
The fastest and smallest JavaScript polygon triangulation library for your WebGL apps
TypeScript definitions for resolve
Internationalized calendar, date, and time manipulation utilities
micromark utility to resolve subtokens
Resolve the path of a module like `require.resolve()` but from a given path
Resolve package.json exports & imports maps
Parse, Resolve, and Dereference JSON Schema $ref pointers
Resolve a directory that is either local, global or in the user's home directory.
Caching DNS resolve
Locate and bundle third-party dependencies in node_modules
react hooks library
Resolve the path of a module like `require.resolve()` but from the current working directory
Resolve nested CSS selectors
Missing ECMAScript module utils for Node.js
Module resolution utilities based on Node.js upstream implementation.
Babel plugin for resolving Vue types.
TZip can resolve United States ZIP codes into the appropriate Rails time zone identifier. This makes it easier to setup your rails app, or change time zones based on user input.
ConfigManager can load properties from YAML or Java style property files. Properties can have references to other properties that are resolved at run-time. Inspired, in part by Apache's configuration API.
Something with the combination of Rails 3.1, Mysql2 0.3.x, Capybara, Selenium/Webkit/etc causes Mysql to raise exceptions where the connection is waiting on a result. This gem provides an auto-retry capability with the Mysql2Adapter to retry any query execution up to 5 times. This is a a temporary solution until the real issue with the above libraries/frameworks are resolved. This should NOT be used in production.
Xelor was built for systems that require random bytes for processes faster than one second. Because normal random generation is based off of time as a seed, if there exists multiple calls towards SecureRandom or Rand within one second, the same number will be produced. This can be resolved on unix or linux based systems by making a system call to read /dev/urandom.
The gem in development is part of a suite of Developer Productivity Software that is strategically designed to enhance efficiency and productivity during the Software Development Life Cycle (SDLC). It mainly addresses the limitations and blockades encountered due to Cross-Origin Resource Sharing (CORS) policies that often hinder smooth interaction between the frontend and backend components when hosted on different domains.
Server-side Ruby port of Alap, the expression parser that turns curated link queries (.coffee + :time:7d:) into resolved link results. Ships the parser, URL sanitization, SSRF guard, regex validation, and config validation — same surface as the TypeScript, Go, Python, PHP, Java, and Rust ports.
This is an experimental branch that implements a connection pool of Net::HTTP objects instead of a connection/thread. C/T is fine if you're only using your http threads to make connections but if you use them in child threads then I suspect you will have a thread memory leak. Also, I want to see if I get less connection resets if the most recently used connection is always returned. Also added a :force_retry option that if set to true will retry POST requests as well as idempotent requests. This branch is currently incompatible with the master branch in the following ways: * It doesn't allow you to recreate the Net::HTTP::Persistent object on the fly. This is possible in the master version since all the data is kept in thread local storage. For this version, you should probably create a class instance of the object and use that in your instance methods. * It uses a hash in the initialize method. This was easier for me as I use a HashWithIndifferentAccess created from a YAML file to define my options. This should probably be modified to check the arguments to achieve backwards compatibility. * The method shutdown is unimplemented as I wasn't sure how I should implement it and I don't need it as I do a graceful shutdown from nginx to finish up my connections. For connection issues, I completely recreate a new Net::HTTP instance. I was running into an issue which I suspect is a JRuby bug where an SSL connection that times out would leave the ssl context in a frozen state which would then make that connection unusable so each time that thread handled a connection a 500 error with the exception "TypeError: can't modify frozen". I think Joseph West's fork resolves this issue but I'm paranoid so I recreate the object. Compatibility with the master version could probably be achieved by creating a Strategy wrapper class for GenePool and a separate strategy class with the connection/thread implementation.
Contentful API wrapper library exposing an ActiveRecord-like interface
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.