[CI] Feature: Add a fixer for the no-imports-from-self lint

[etrepum]

Description

When an invalid import is generated (usually by vscode heuristics) we generally know what the import should be so we might as well provide a fixer at the same time.

Test plan

Before

Get a lint error when circularly importing a module

After

Also get a lint error, but make it fixable by replacing the package name with ., e.g. in

packages/lexical/src/LexicalNodeState.ts

import {NODE_STATE_KEY} from 'lexical';

Error: Exported module 'lexical' should not import from itself. Use a relative import instead.
Suggestion: Rename import 'lexical' to '.' (lexical/no-imports-from-self)

An also correct fix (and what is actually in that particular module right now) would be to do the import directly from the module that defines it:

import {NODE_STATE_KEY} from './LexicalConstants';

But given the toolchains we use either should work and produce the same build artifact. Worst case the user then gets a different error and they can track down which file actually exports that name.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
lexical	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 4, 2025 6:25am
lexical-playground	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 4, 2025 6:25am