Look up the file that an `import()` statement will resolve to, possibly relative to a given parentURL
Gatsby plugin to set Webpack to resolve import root
resolve @import statements in stylesheets
Resolve @import statements in scss and scss.liquid
TypeDoc plugin to resolve import target and inject import code block
NPM module to resolve import module extension for Deno
Provides Rollup plugins that resolve import specifiers defined in `package.json` that link other NPM packages.
Gatsby plugin to set Webpack to resolve import root
This is a Sass [importer](https://sass-lang.com/documentation/js-api/interfaces/importer/) for Yarn PnP projects that want to resolve `@import` or `@use` statements from packages external to the current one.
tsconfig-paths/register : this package is used to resolve import using tsconfig alias path
A TypeScript transformer for use with ttypescript that will resolve import target during transpile.
Resolve import with type css as Constructable Stylesheets
Resolves @import statements in CSS
tsconfig-paths/register : this package is used to resolve import using tsconfig alias path
Resolve import paths for named dependencies
Compose CSS from SASS files using Node's algorithm to resolve `@import` statements. Plus more goodness.
Resolve things like Node.js — ponyfill for `import.meta.resolve`
A SWC plugin to resolve import extensions. (e.g. `import 'foo'` -> `import 'foo.js'`)
Resolve import specifiers against import maps.
Module resolution utilities based on Node.js upstream implementation.
Import a module like with `require()` but from a given path
A fork of `import-meta-resolve` with commonjs + ESM support at the same time, AKA dual package.
Node default behavior import resolution plugin for eslint-plugin-import.
Resolve package.json exports & imports maps
AI Plugin Manager — consumer CLI (install, validate, doctor, link)
AI Plugin Manager — author CLI (init, pack, publish, yank, login)
Core library for AIPM — manifest parser, resolver, store, lockfile
Engine API schema source-of-truth for AIPM (canonical Rust types + build-time generated tables)
Bundle assets with webpack, resolve and compile opal ruby files and import them in the bundle, without sprockets or the webpacker gem (but can be used with both of them too). Comes with a installer for rails and other frameworks.
PGroonga 2.0 has been released with 2 years development since PGroonga 1.0.0. PGroonga 1.0.0 just provides fast full text search with all languages support. It's important because it's a lacked feature in PostgreSQL. PGroonga 2.0 provides more useful features to implement rich full text search system with PostgreSQL. This session shows how to implement rich full text search system with PostgreSQL! This talk describes about PGroonga that resolves these problems.
This gem resolves basically two problems. --- 1. MySQL for strings(VARCHAR(255)) by default has limit 255 characters. And when developer left this attribute without any length validation, then it's possible to face with situation when user unintentionally or intentionally will pass in text field more characters. So, then, probably you will get 500... --- 2. PostgreSQL. The maximum number of characters for variable unlimited length types (text, varchar) is undefined. There is a limit of size in bytes for all string types: In any case, the longest possible character string that can be stored is about 1 GB. And when developer left this attribute without any length validation, then it's possible to face with situation when user unintentionally or intentionally will try to full up your database with lots of GB of 'important' info. --- Both of this cases, I guess, are not very pleasant. This gem adds default length validation for all string attributes. Except those which are already vlidated in standart rails way.
GraphQL interface over WCC::Contentful store
Contentful API wrapper library exposing an ActiveRecord-like interface
No description provided.
No description provided.