New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VS Code warning about soon-to-be-dropped code action #724
Comments
Hi @philsherry! Sorry for the delay on this. This is the first time we've seen this issue. Could you provide some additional information:
|
Took me a few days to get back to this, but:
In the time it's taken for us both to respond, this is no longer happening. However… stderr: |
Oops! Something went wrong! :(
ESLint: 9.0.0
Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@eslint/js' imported from eslint.config.js I’ve since tried updating to ESLint 9 and Trunk doesn’t seem to like it. So, maybe the issue has been fixed by an updated VS Code, or maybe it’s Trunk’s inability to handle the ESLint 9 config? Could be either. Or both. Or neither. 😄 Is there anything specific that is required to switch from ESLint 8 -> 9? I assume you've given it a good going over to check. Edit: I had a look at the suggested config for it and it doesn’t look to be covered here. I see only legacy config file names in the array—not the newer, flat config style. They’re already up to |
Hi! Glad the original issue is no longer a problem. As for Eslint9, we are aware of the new eslint flat config changes and haven't finalized our approach for upgrading our existing users. With that being said, we just landed some temporary migration guidelines if you want to start using ESlint9. Please let us know if you encounter any issues with that override. We plan to have a more OOTB approach for Eslint9, but it's likely a few weeks out from being released, so you should use the override in the meantime |
Quick fixes have stopped working for me.
Now I just get stuck on “Checking for quick fixes...” and the following warning in the Extension Host console:
The text was updated successfully, but these errors were encountered: