-
Notifications
You must be signed in to change notification settings - Fork 278
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
Slow performance with yarn serve and yarn build after Enso 4.4.0 #352
Comments
Not saying this is from 4.4.0 code changes - it might be from yarn + windows and triggered not because of recent changes. In the same time I'm trying: https://stackoverflow.com/questions/40566222/yarn-5x-slower-on-windows
|
Oh... this ain't looking good. Can be from AV: |
Hi @robbykrlos, We're only using linux & mac so we don't have any helpful input for W... other than switch it:) |
Ok, good. Will close this one. Will return with updates in case we find a solution for windows - may be useful for somebody with the same issue. |
Some updates on this issue : after some days, I had to clean-up node_modules, because of some corrupted files, and some weird errors, and using: Clean-up yarn cache: Delete all node_modules inner folders. Use "Fast delete": Install RimRaf: Install again all node_modules:
Build and Serve are now working normally 👍 |
This is a question.
Prerequisites
(enso is made of many specialized packages: https://github.com/laravel-enso)
Description
Not sure how you guys run your environments and what OS you are using, but we noticed a slower performance in yarn build and yarn serve - especially in yarn serve with the new Enso 4.4.0 on Windows 10 Pro machines.
This makes it much more slower to observe changes in page when any line change will trigger a ~100 seconds rebuild, mostly hanging on 40%:
I've noticed some Vue files had some local styles defined, and thought by removing them will help - but was no significant performance change (at least for one correction).
If you have some ideas we're glad to have a starting point of investigation
The text was updated successfully, but these errors were encountered: