chore(eslint): optimize imports

[LitoMore]

Changes

• Add sort-imports
• Add import/order
• Add import/no-duplicates
• Add @typescript-eslint/consistent-type-imports

I moved all unassigned imports (CSS/Less/MP3) to the bottom for a better visual.

When to disable it?

And I am using eslint-disable-next-line import/order to allow our unassigned sibling CSS/Less imports after those imports from package. Just to avoid some style override issues. Here is an example:

import 'videojs/example.css';
// eslint-disable-next-line import/order
import './style.less';

I don't want to take too much effort on pathGroups. Using eslint-disable-next-line import/order is easilier.

Tips

Use the split diff view for better visual.

Plan

I'm going to enable ESLint for all workspaces and root files in another PR.

[BlackHole1]

Wow. Thank you for the PR! This is something I've always wanted to do! 🤩

Please wait a moment, I need to test this RP locally

[BlackHole1]

@LitoMore Can you resolve the conflict?

[LitoMore]

@BlackHole1 Conflict has been resolved.

Please hold on other PRs until this one get merged.

[crimx]

How about eslint-plugin-simple-import-sort which keeps the order of side-effect imports.

[LitoMore]

@crimx You can create another PR and try to replace them (based on this PR). I'm not going to take too much effort into it.

[BlackHole1]

I will be responsible for the revision of this PR as @LitoMore does not have the extra time to do it

[LitoMore]

We can merge. Then change to eslint-plugin-simple-import-sort.

[BlackHole1]

Hey @LitoMore 👋
The other day, I communicated with @crimx about this PR.
Currently this PR cannot be merged immediately as this PR automatically modifies the order in which some style files are introduced, which may result in style errors.
So to be on the safe side, we should address this issue in the current PR rather than opening a new one to address it.🙇

[LitoMore]

OK. Closing in favor of the new one.