Results for "require.resolve"

Expose require.resolve as executable. `$ resolve request` returns /path/to/node_modules/request/index.js

resolve like require.resolve() on behalf of files asynchronously and synchronously

```js module.exports = { transform: { '.(ts|tsx|js|jsx)$': require.resolve('ts-jest'), '.(svg)$': require.resolve('@ssen/jest-transform/transform/svg'), '.(html|ejs|txt|md)$': require.resolve( '@ssen/jest-transform/transform/text',

empty module for require.resolve

For parcel v2, this is a fallback resolver that uses require.resolve

Module to fallback the Node.js require and require.resolve function

``` const eslint = require("klopov-eslint")("eslint/lib/cli.js"); const eslintrc = require.resolve("klopov-eslint/.eslintrc.json"); ```

The core of Expo Modules architecture

Bring node's require.resolve pattern to Lua.

Call require pretending your are at another directory

It will collect dependencies (package names) by analyze `import`, `import()`, `require()` and `require.resolve()` of JS and TS source codes of a directory.

resolve like require.resolve() on behalf of files asynchronously and synchronously

Transforms require module paths that have a prefix referring to the project root. Also works on `require.resolve`.

A helper function to resolve a module name or path in relation to the specified context and require it.

Resolve a package entry point to a file path (like require.resolve/import.meta.resolve) OR a file path to a package entry point

Offline search component for Docusaurus V3

module: { rules: [ { test: require.resolve('./src/index.js'), use: 'imports-loader?thiss=>window,$=jquery' }, { test: require.resolve('./src/globals.js'), use: 'exports-loader?file,parse

launch a web worker at runtime that can require() in the browser with webpack

Offers a wrapper for require.resolve function. Supporting configurable NodeJS sugar exports

Get information on local packages.