-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
Reduce webpack config rules #4147
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
Comments
I haven't come across a project where this caused any issues. If you think your issues are related to this config, please provide an actual reproduction. |
Hello! We get a lot of issues, so we currently close issues requiring feedback after 20 days of inactivity. It’s been at least 10 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. (A maintainer can also add the label Thanks for being a part of the Vue community! 💪💚️ |
Sorry @LinusBorg but for now i use nuxt.js for end my website. I go investigate more probably next month |
Hello! We get a lot of issues, so we currently close issues requiring feedback after 20 days of inactivity. It’s been at least 10 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. (A maintainer can also add the label Thanks for being a part of the Vue community! 💪💚️ |
Hey again! 😸️ It’s been 20 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Thanks again for being part of the Vue community! 💚️ |
Version
3.8.3
Environment info
Steps to reproduce
What is expected?
Don't have rules for stylus, less when use sass styles
What is actually happening?
The rules of webpack have usless rules like stylus, less if we use sass styles
I think is linked of an other problem, the build stuck for 30-40 seconds on step
40% building x/x modules ...
(this message end with filecore-js/library/fn/promise.js
on start and with component.vue
when i update component with more 100 lines)The text was updated successfully, but these errors were encountered: