-
Notifications
You must be signed in to change notification settings - Fork 293
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
Using source map doubles memory usage #596
Comments
I did a test, replaced the custom source map require in index.js with regular require('source-map-support') |
Using
|
I tried to use nodejs native integration --enable-source-maps instead, and it seems to work better. |
Now that |
yes native source map seems fine, but the key is to split index.js into chunks otherwise the sourcemap would get super big and take a ton of memory when loaded |
The purpose of ncc is to bundle chunks of js into a single file. So splitting doesn't make sense, you could just avoid using ncc and keep the original files. |
I disagree with that, having index.js automatically split into 10 chunks and required in main index.js would serve the same purpose as currently but would fix the issues with source maps. |
Running app after compiling with -s option uses ~ 320MB on start, while without the flag it's 150-200MB.
Running pure typescript compiled version, even with require('source-map-support'), does not have this problem
The text was updated successfully, but these errors were encountered: