Found unnecessarily complex import statement JS-C1001
Anti-pattern
Minor
a month ago
—
2 months old
Useless path segments for "../", should be ".."
1import type { Mina } from "@palladxyz/mina-core"
2import type { Address, Chain } from "viem"
3
4import type { Provider } from "../" 5
6export interface TokenIdMap {
7 [alias: string]: stringUseless path segments for "./", should be "."
2import type { NetworkName } from "@palladxyz/vault"
3import { MinaProvider } from "@palladxyz/web-provider"
4import { serializeError } from "serialize-error"
5import type { Handler } from "./" 6
7export const palladSidePanel: Handler = async ({ sender }) => {
8 await chrome.sidePanel.open({
Description
Unnecessarily complex import statements can be simplified. Complex imports usually result in confusing code. This usually happens as a result of refactoring.
For the following project structure
├── root.config.js
├── .deepsource.toml
└── calculator
├── index.js
├── calc.js
└── config.js
└── utils
└── pofyfills.js
└── index.js
Bad Practice
// <!-- calcuator/index.js -->
import utils from './utils/index.js' // unnecessary to mentioned `index.js` at the end. NodeJS always resolves using index.js
import config from './../root.config.js' // unnecessary to add the `./`/
import polyfills from './utils//polyfills.js' // unnecessary to add the extra `/` before `polyfills.js`
import { processUtils } from './utils/' // unnecessary to add the extra `/` after `./utils`
Recommended
// <!-- calcuator/index.js -->
import utils from './utils'
import config from '../root.config.js' // unnecessary to add the `./`/
import polyfills from './utils/polyfills.js' // unnecessary to add the extra `/` before `polyfills.js`
import { processUtils } from './utils' // unnecessary to add the extra `/` after `./utils`