Closed Markus-Ende closed 10 months ago
got that problems too, and memory footprint about 7+ gb when use angular 16 instead of 15 (4-4.7gb for my project). Can't wait properly working browser-esbuild
update: did the full delete node_modules and cache, refresh package-lock cycle. It seems to work now (with NX_NON_NATIVE_HASHER still set). I'll keep it open for now, and try a bit longer, but the memory crash did not occur again (still 16.0.3).
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. If we missed this issue please reply to keep it active. Thanks for being a part of the Nx community! 🙏
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.
Current Behavior
JavaScript heap out of memory
Expected Behavior
should serve happily like in the previous version :)
GitHub Repo
No response
Steps to Reproduce
unfortunately I can't create a repro repo and it happens in a closed source project
Nx Report
Failure Logs
Additional Information