Skip to content

Development: 'import/order' ESLint rule conflicts with Typescript import sorter #310

@0DarkPhoenix

Description

@0DarkPhoenix

Describe the bug

When saving the index file of a tool which contains the import { translate as t } from '@/plugins/i18n.plugin'; import line, it gives an error caused by the 'import/order' ESLint rule where it states that the import line above should appear below a different import statement.

However, when manually changing the order of this import statement or saving the file in general, it still jumps to a different position causing the ESLint error to appear again. This happens because it first gets sorted by ESLint, and later sorted again by the TSC (TypeScript Compiler).

I suggest disabling the import/order rule in .eslintrc.cjs, so it doesn't keep conflicting with the import sorting done by the TSC. I had a similar situation in my own projects while using Biome as a formatter and linter where the import sorting of Biome would conflict with the import sorting of the Typescript compiler, where the solution was to disable the import sorting of Biome because it is handled just as good by Typescript.

2026-02-01-20-09-08.mp4

What happened?

A bug happened!

System information

IT-Tools dev environment in Visual Studio Code

Where did you encounter the bug?

Public app (sharevb-it-tools.vercel.app)

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions