> For AI agents: the complete documentation index is available at https://rslint.rs/llms.txt, the full documentation bundle is available at https://rslint.rs/llms-full.txt.

# no-extraneous-require

[Added in v0.9.3](https://github.com/web-infra-dev/rslint/releases/tag/v0.9.3)
## Configuration

| Preset                                 | Configured Value |
| -------------------------------------- | ---------------- |
| ✅ nodePlugin.configs.recommended       | `"error"`        |
| ✅ nodePlugin.configs.recommendedModule | `"error"`        |
| ✅ nodePlugin.configs.recommendedScript | `"error"`        |


```ts title=rslint.config.ts
import { defineConfig, nodePlugin } from '@rslint/core';

export default defineConfig([
  nodePlugin.configs.recommended,
  {
    rules: {
      'node/no-extraneous-require': 'error',
    },
  },
]);
```

Disallow loading installed packages that are not declared in `package.json`.

A transitive dependency can disappear when another dependency changes. Declare
the packages your code loads directly, even when they are already installed.

## Rule details

This rule checks `require()` and `require.resolve()`, including aliases,
destructured methods, optional calls, and access through Node's global object.
It reports the module argument when its constant value names an installed,
undeclared package. Local bindings that shadow `require` are ignored.

For example, if `declared` is a dependency and `transitive` is installed but
undeclared, these calls are incorrect:

```js
const value = require('transitive');
const filename = require.resolve('transitive');
const load = require;
load('transitive');
```

These calls are correct:

```js
const value = require('declared');
const fs = require('node:fs');
const local = require('./local.js');
```

The package's own name and all four dependency fields are accepted:
`dependencies`, `devDependencies`, `peerDependencies`, and
`optionalDependencies`. Workspace members also inherit those names from the
nearest matching ancestor workspace. Workspace arrays and the
`{ "packages": [...] }` form are supported, including negative patterns.

Missing packages, builtins, relative paths, and TypeScript `paths` aliases are
ignored. Resolution uses CommonJS export conditions. An `@types` dependency
alone does not permit loading its runtime package. Imports and TypeScript
`import value = require('package')` declarations are outside this rule.

Constant expressions such as concatenation and template literals are supported.
An identifier argument such as `require(packageName)` is not evaluated, even
when it has a constant initializer. The rule provides no fixes or suggestions.

## Options

```js
import { defineConfig, globals } from '@rslint/core';

export default defineConfig([
  {
    plugins: ['node'],
    languageOptions: { globals: globals.node },
    rules: {
      'node/no-extraneous-require': [
        'error',
        {
          allowModules: [],
          resolvePaths: [],
          tryExtensions: ['.js', '.json', '.node', '.mjs', '.cjs'],
          resolverConfig: { modules: ['node_modules'] },
        },
      ],
    },
  },
]);
```

- `allowModules`: package names accepted without a declaration. Scoped names
  are supported, and allowing a package also allows its subdirectories.
- `resolvePaths`: additional directories from which to resolve packages,
  relative to the working directory. The source file's directory is also used.
- `tryExtensions`: implicit file extensions. The JavaScript default is shown
  above. An empty array disables extension probing; explicit package entry
  points still resolve. TypeScript files also respect the nearest tsconfig's
  extension settings and the shared `typescriptExtensionMap` and `tsconfigPath`.
- `resolverConfig.modules`: a module directory string or an array of directories.
  The default is `['node_modules']`. Relative names are searched up the directory
  tree; absolute directories are also supported. An empty array disables lookup.
- `convertPath`: accepts the upstream object or array syntax. It has no effect
  on this rule in upstream v18.3.0 or in rslint.

These options can also be configured in `settings.node`. Rule options take
precedence, including explicitly empty arrays. Legacy `settings.n` is accepted
for compatibility and takes precedence over `settings.node` when both are set.

Supported `resolverConfig` properties are `modules`, `alias`, `fallback`, `fullySpecified`, `extensions`,
`extensionAlias`, `conditionNames`, `mainFields`, `mainFiles`, and `aliasFields`.

`resolverConfig.mainFields` selects package entry fields in order, for example
`['browser', 'module', 'main']`. `mainFiles` selects directory entry filenames,
such as `['api', 'index']`. `aliasFields: ['browser']` applies package mappings
including `false` to ignore a target. Field names can be nested arrays, such as
`[['build', 'main'], 'main']`. Empty entry lists disable that lookup.

`resolverConfig.fallback` redirects unresolved requests, for example
`{ fallback: { virtual: './shim.js' } }`. Existing targets take precedence.
`fullySpecified: true` disables extension and directory-entry guessing for
ordinary requests: `./helper.js` can resolve while `./helper` cannot. Package
entry points and alias redirects retain their normal lookup behavior.

## Differences from upstream

- `resolverConfig` options not listed above, including `symlinks`, are not supported.
- Overlapping object-form `alias` and `fallback` entries use alphabetical priority
  instead of declaration order. Use arrays to set priority.
- Package entry paths containing backslashes are unsupported on Linux and macOS.
  On Windows, relative paths containing backslashes can resolve in rslint but fail upstream.
- In `workspaces`, `{1..3}` expands numeric ranges in rslint; upstream matches
  `1..3` literally. Use `{1,2,3}` for consistent results.
- In `workspaces`, `[^a]` excludes `a` in rslint, while upstream can include it.
  Use `[!a]` to exclude `a` consistently.
- Disabled wildcard aliases only ignore matching modules; upstream may also ignore
  unrelated modules. Use exact alias names for consistent results.

## References

- [Upstream documentation](https://github.com/eslint-community/eslint-plugin-n/blob/v18.3.0/docs/rules/no-extraneous-require.md)
- [Upstream source](https://github.com/eslint-community/eslint-plugin-n/blob/v18.3.0/lib/rules/no-extraneous-require.js)
- [Shared settings](https://github.com/eslint-community/eslint-plugin-n/blob/v18.3.0/docs/shared-settings.md)