How to disable console log `hmr update`
See original GitHub issueIs your feature request related to a problem? Please describe.
I’m always frustrated when vite print a lot of logs on HMR, I tried both logLevel: silent
and logLevel: error
, none of them remove hmr update /path-to-file
. Am i missing something?
export default defineConfig({
plugins: [reactRefresh()],
dedupe: ['react', 'react-dom'],
logLevel: 'silent',
});
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Nuxt - How can I remove the [HMR] logs from the console
One of few approaches I have found is to clear the console. On reload. However, this approach does not fit my needs and...
Read more >How can I remove the [HMR] logs from the console? : r/Nuxt
Right Click on console entry -> hide messages from...
Read more >hot-module-replacement | Meteor API Docs
Disable updating this module or its dependencies with HMR. Hot code push will be used instead. Can not be overridden by calling module.hot.accept...
Read more >Hot Module Replacement - SurviveJS
Hot Module Replacement (HMR) builds on top of the WDS. ... Webpack has to provide hot updates to the server and can be...
Read more >HMR API - Vite
For handling HMR update in plugins, see handleHotUpdate. ... when SyntaxError happened console.log('updated: count is now ', newModule.count) } }) }.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Use negated console filters:
This issue has been locked since it has been closed for more than 14 days.
If you have found a concrete bug or regression related to it, please open a new bug report with a reproduction against the latest Vite version. If you have any other comments you should join the chat at Vite Land or create a new discussion.