A resolver for eslint-plugin-import that provides Meteor-specific import resolution in ESLint. Version 0.4.0 is the latest stable release, last updated in 2018. It handles '/' root imports, enforces client/server folder import restrictions, and resolves 'meteor/' package imports with limitations. Unlike generic resolvers, it uses the project's .meteor folder to resolve paths and checks .meteor/versions and .meteor/packages for package existence. Provides configurable extensions, paths, and moduleDirectory. Works with eslint-plugin-import >=1.4.0.
npm install eslint-import-resolver-meteorVerified import paths — ran on the pinned version, not inferred.
Configures ESLint to use Meteor resolver with custom extensions, enabling import/no-unresolved rule.
Use the resolver for basic linting, but be aware of false positives. For accurate resolution, consider using Meteor's built-in linting tools.
Include '.js' in the extensions array if you want it alongside others.
Consider using eslint-import-resolver-typescript or writing a custom resolver for modern ESLint.
Disable the import/no-restricted-paths rule if false positives occur, or adjust folder structure.
Ensure the project has a .meteor folder in a parent directory, or set the root manually via settings.
Ensure you have run 'meteor add meteor' or check that .meteor/versions exists. The resolver may produce false positives.
Verify that the file exists at PROJECT_ROOT/imports/foo, where PROJECT_ROOT is the directory containing .meteor.
Run: npm install --save-dev eslint-plugin-import eslint-import-resolver-meteor