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
Empty ERROR
message
#238
Comments
Any progress on this? Seems like the only option is to revert to 0.4.9 |
Actually, the change seems to have been introduced in 0.5.6 |
Happening for me with nuxt 3.8.2 on a fresh install/setup |
Same for me? Any workaround for this? |
I figured out where the problem got introduced, but there's been no addressing of it thus far |
This line looks like it might be the root of the issue. 8dd4915#diff-7c457428fc11687ac503085166d754dc2dbdaa3df69069d3027272bda149ba5cR189 I found that while trawling through the diff between v0.5.5 and 0.5.6 vite-plugin-checker@0.5.5...vite-plugin-checker@0.5.6 |
@james-yeoman I'm seeing the same. Unsure why it would log if Checker.logger is empty, maybe an oversight? |
So the logger comes from Vite itself. I wonder why this plugin isn't receiving the logger from Vite... 8dd4915 |
Fixes fi3ework#238 It appears `config.logger` can be null or undefined, despite the typescript types for Vite specifying logger as required
Ok, so vite-plugin-checker is receiving the logger from vite, I'm just a dunce... The actual problem, is that There's currently no way of differentiating between an error, a warning, and a checker summary. This is beyond what I can justify spending time on during work, but hopefully my findings help someone who can spend more time on open source to fix this |
As a workaround, I've got a fork that I've added a bypass to in order to avoid erroring on an empty summary. It's not the cleanest, but it allows me to adopt the ESLint Flat Config without too much problem |
:/ I use yarn and so can't reference the fork since this plugin uses pnpm... guess I'm back to using yarn patches instead... |
Describe the bug
When
typescript check
option istrue
always getting this messageI tried to debug it and added log with
*** action
to themain.js
plugin source file.And since this action treaded as an Error on
line 182
we just added prefix ERROR.Reproduction
in vite config
Expected behavior
Action
{ type: 'console', payload: '\n[TypeScript] Found 0 errors. Watching for file changes.' }
should't be logged as an ErrorSystem Info
The text was updated successfully, but these errors were encountered: