Avoid using wildcard imports JS-C1003
Anti-pattern
Minor
a year ago
—
2 years old
Explicitly import the specific method needed
1/* eslint-disable turbo/no-undeclared-env-vars */
2import express, { Request } from 'express';
3import cors from 'cors';
4import * as dotenv from 'dotenv'; 5
6import { ExpressPeerServer } from 'peer';
7Explicitly import the specific method needed
1import { createRequestHandler } from '@remix-run/vercel';
2import * as build from '@remix-run/dev/server-build';3
4export default createRequestHandler({ build, mode: process.env.NODE_ENV });
Description
Wildcard imports are easier to write, but make it harder to pick out the specific functions or objects from a dependency that are used in a file.
import * from 'module';
// there is no clear way to tell if
// `someFunction` has been imported
// from 'module'.
someFunction();
Therefore, it is recommended to explicit imports wherever possible.
NOTE: Some libraries do not expose themselves as ESModules. In cases like these, it is recommended to use a skipcq comment to suppress this issue.
Bad Practice
import * as axios from 'axios'
import * as Sentry from '@sentry/node'
try {
const result = await axios.get();
// ...
} catch (err) {
Sentry.captureException(err);
}
Recommended
import axios from 'axios'
// skipcq: JS-C1003 - sentry does not expose itself as an ES Module.
import * as Sentry from '@sentry/node'
try {
const result = await axios.get();
// ...
} catch (err) {
Sentry.captureException(err);
}