#no-missing-import

#Configuration

import { defineConfig, nodePlugin } from '@rslint/core';

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

Disallow imports and re-exports whose modules cannot be found.

The rule checks static import, export ... from, and dynamic import() with literal arguments. It checks installed packages and their exports maps as well as local files. Declaring a dependency in package.json does not make an uninstalled package available.

#Examples

Incorrect:

import missing from './missing.js';
export { value } from 'missing-package';
const module = import('./missing.js');

Correct, when existing.js and installed-package exist:

import existing from './existing.js';
export { value } from 'installed-package';
import fs from 'node:fs';

Relative directory imports such as import './directory' are reported even when the directory contains index.js or a package entry point. Import that file explicitly. Bare package imports can use package entry points.

Runtime imports of Node builtins, data: URLs, and HTTP or HTTPS URLs are accepted. Expressions such as import(variable) and template literals are outside this rule's checks. The rule provides no fixes or suggestions.

#Options

import { defineConfig } from '@rslint/core';

export default defineConfig([
  {
    plugins: ['node'],
    rules: {
      'node/no-missing-import': [
        'error',
        {
          allowModules: ['electron'],
          resolvePaths: [],
          ignoreTypeImport: false,
        },
      ],
    },
  },
]);

• allowModules: package roots to accept without resolving them, including scoped packages and virtual: modules. Allowing a package also allows its internal paths, such as electron/main. The default is an empty list.
• resolvePaths: additional base directories, searched before the importing file's directory. Relative entries use the working directory, or settings.cwd when configured. The default is an empty list.
• tryExtensions: extensions to try for extensionless imports. The default is ['.js', '.json', '.node', '.mjs', '.cjs']. An empty list disables extension guessing; explicit filenames can still resolve.
• resolverConfig.modules: a module directory string or array, such as 'node_modules' or ['custom_modules', 'node_modules']. The default is ['node_modules']. Relative names are searched up the directory tree; absolute directories are also accepted. An empty array disables package lookup without disabling relative file imports.
• ignoreTypeImport: skips whole import type declarations when true. The default is false. Type re-exports and individual type specifiers in a value import are still checked, matching upstream.
• typescriptExtensionMap: overrides TypeScript extension substitution. Accepts [sourceExtension, emittedExtension] pairs, or preserve, react, react-jsx, react-jsxdev, and react-native. An empty array disables substitution.
• tsconfigPath: selects a TypeScript config for extension substitution. The nearest tsconfig.json supplies the default mapping and path aliases. Relative values use the working directory, independently of settings.cwd. An explicit extension map takes precedence over tsconfigPath.

Except for ignoreTypeImport, these options can also be supplied through settings.node. Rule options take precedence over shared settings. Legacy settings.n is accepted with the same precedence as upstream. Explicit empty lists override shared lists.

In TypeScript files, the default mapping substitutes .ts for .js, .mts for .mjs, .cts for .cjs, and .tsx for .jsx in preserve mode or .js in React modes. With allowImportingTsExtensions, the default extension list also includes .ts, .mts, and .cts, and emitted extensions are not substituted. Type-only imports also activate the types export condition.

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.
• Error messages for malformed package.json files and invalid imports mappings may differ.
• Module names containing \uD800 may show � in diagnostics.
• Disabled wildcard aliases only ignore matching modules; upstream may also ignore unrelated modules. Use exact alias names for consistent results.

#References

• Upstream documentation
• Upstream source
• Shared settings