kibana/packages/kbn-eslint-import-resolver-kibana/import_resolver_kibana.js
Spencer 0b03166d2d
[eslint] unify resolver configs (#19102)
* [eslint] unify resolver configs

Our eslint resolver settings currently rely on the fact that we define
our resolver with a string globally, and an object in the overrides.
This causes the override value to completely override/replace the global
setting, which is desired, but when the global setting is converted to
an object they are merged, causing both resolvers to run.

This is a problem because some dependencies in the UI side of things
will resolve with the node resolver, but will resolve incorrectly
because they are intended to use some webpack specific override.

While trying to add TypeScript I needed to pass argument to the node
resolver which uncovered this issue. The change here moves us away from
using the node resolver directly and instead uses the kibana resolver
with `forceNode: true` set when linting server code and `forceNode:
false` when resolving imports that will be handled by webpack.

* [import-resolver] use object spread operator
2018-05-16 10:45:41 -07:00

107 lines
3.2 KiB
JavaScript
Executable file

const { join, dirname, extname } = require('path');
const webpackResolver = require('eslint-import-resolver-webpack');
const nodeResolver = require('eslint-import-resolver-node');
const {
getKibanaPath,
getProjectRoot,
getWebpackConfig,
isFile,
isProbablyWebpackShim,
getIsPathRequest,
resolveWebpackAlias,
} = require('./lib');
// cache context, it shouldn't change
let context;
function initContext(file, config) {
if (context) {
return context;
}
const projectRoot = getProjectRoot(file, config);
const kibanaPath = getKibanaPath(config, projectRoot);
const webpackConfig = getWebpackConfig(kibanaPath, projectRoot, config);
const aliasEntries = Object.entries(webpackConfig.resolve.alias || {});
context = {
webpackConfig,
aliasEntries,
};
return context;
}
function tryNodeResolver(importRequest, file, config) {
return nodeResolver.resolve(importRequest, file, {
...config,
extensions: ['.js', '.json'],
isFile,
});
}
exports.resolve = function resolveKibanaPath(importRequest, file, config) {
config = config || {};
if (config.forceNode) {
return tryNodeResolver(importRequest, file, config);
}
// these modules are simulated by webpack, so there is no
// path to resolve to and no reason to do any more work
if (importRequest.startsWith('uiExports/')) {
return {
found: true,
path: null,
};
}
const { webpackConfig, aliasEntries } = initContext(file, config);
let isPathRequest = getIsPathRequest(importRequest);
// if the importRequest is not a path we might be able to map it to a path
// by comparing it to the webpack aliases. If we can convert it to a path
// without actually invoking the webpack resolver we can save a lot of time
if (!isPathRequest) {
const resolvedAlias = resolveWebpackAlias(importRequest, aliasEntries);
if (resolvedAlias) {
importRequest = resolvedAlias;
isPathRequest = true;
}
}
// if the importRequest is a path, and it has a file extension, then
// we just resolve it. This is most helpful with relative imports for
// .css and .html files because those don't work with the node resolver
// and we can resolve them much quicker than webpack
if (isPathRequest && extname(importRequest)) {
const abs = join(dirname(file), importRequest);
if (isFile(abs)) {
return {
found: true,
path: abs,
};
}
}
// only use the node resolver if the importRequest is a path, or is
// a module request but not one that's probably a webpackShim. This
// prevents false positives as webpackShims are likely to be resolved
// to the node_modules directory by the node resolver, but we want
// them to resolve to the actual shim
if (isPathRequest || !isProbablyWebpackShim(importRequest, file)) {
const nodeResult = tryNodeResolver(importRequest, file, config);
if (nodeResult && nodeResult.found) {
return nodeResult;
}
}
return webpackResolver.resolve(importRequest, file, {
config: webpackConfig,
});
};
// use version 2 of the resolver interface, https://github.com/benmosher/eslint-plugin-import/blob/master/resolvers/README.md#interfaceversion--number
exports.interfaceVersion = 2;