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
Cache is corrupted when run module with 'nuxt-build-optimisations' module #103
Comments
Hey @sondh0127 Thanks for the issue and reproduction repo. I followed your instructions and could replicate the bug. I'm not too familiar with how the hardsource plugin works internally, but I'm guessing it's failing because the pitcher is removed as part of the compilation. Will need to do a proper investigation. It seems that these "ERROR"s are fine to ignore though. If you want to avoid it you'll need to disable the hardsource plugin either by changing your profile to buildOptimisations: {
features: {
hardSourcePlugin: false
}
} |
Thank you @harlan-zw for the quick response. With hardsource disabled, the error is gone. But I also hope the module will work with hardsource plugin. It seems fast to me. Hardsource enabled startime reduced 29 seconds to 10 seconds. P/S: I will also try 'nuxt-vite' again, but it caused a lot of problems last time. |
Yup will try find a fix for it |
Hey @sondh0127. Have found the issue with this and have pushed a release - 1.2.1 which solves it. Let me know if you have any further issues :) |
Describe the bug
Cache is corrupted when run module with 'nuxt-build-optimisations'. This force build-optimisation re-create the cache.
To Reproduce
Steps to reproduce the behavior:
https://github.com/sondh0127/nuxt-windi-optimize
yarn dev
yarn dev
Expected behavior
Windi module will work well with module (nuxt-build-optimisations)
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
The text was updated successfully, but these errors were encountered: