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

Run yarn lint or npm run lint to lint all files

Detection after usage of optional chaining

Pretty sweet! Let's ignore test files and the playground, I guess

Looks like we also need to ignore lexical-devtools

Looks like we also need to ignore lexical-devtools

Done 🚀

@shanpriyan Hi. I'm having some kind of problem with this eslint rule today.

I've just synced my Lexical fork so I can update my local copy. However, I can't complete the commit with all the changes because ESLint is causing Husky to die on this plugin.

Specifically:

1. Husky reports:

ESLint couldn't find the plugin "eslint-plugin-lexical".

(Despite this, I do see all the code you added to Lexical via this PR in my local copy.)

2. Then ESLint says:

ESLint: 7.32.0

ESLint couldn't find the plugin "eslint-plugin-lexical".

(The package "eslint-plugin-lexical" was not found when loaded as a Node module from the directory "/Users/james/Desktop/code/lexical".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

    npm install eslint-plugin-lexical@latest --save-dev
...

3. Finally, when taking ESLint's advice to do a npm install ..., I get the following error:

npm ERR! Cannot convert undefined or null to object

Do you have any advice on how to fix this? Is it possible that you added a file system reference to your "npm registry list", a la https://stackoverflow.com/a/41200925 ? If so, what would I need to add?

I can't even seem to remove the rule, as, each time I do, Husky seems to "magically" reinsert it.

I'm definitely missing something here. Any thoughts that could help?

@shanpriyan Hi. I'm having some kind of problem with this eslint rule today.

...

Ha! I asked for help in the Eslint Discord and the recommendation seems to have worked right quick:

npm link ./eslint-plugin

Looks like this solves the problem. I'm cautiously optimistic!