-
Notifications
You must be signed in to change notification settings - Fork 201
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
Multiple Builds memory issue #3400
Comments
Please note that you are naming a default build (which I don't think includes compiling or minifying) and not selecting builds from |
This works for me, adjust the memory size as needed: |
You are correct when building with the --name I thought it would "look up" the build instructions, however it doesn't. I have ran polymer build with just one item in the builds list and it then builds correctly. It may be worth adding an option similar to --name to choose which build you want to save memory. Thanks for the suggestion this works with one item. It also completes the build process a bit faster as well. However with the three builds it fails to build. It seems that my only option is to use the --name option but add the build options as a work around. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed after being marked stale. If you're still facing this problem with the above solution, please comment and we'll reopen! |
My project is getting quite large and I have 3 builds say, production, development and localtest. If I use polymer build the build fails with memory heap error. However if I run
It works perfectly. When running effectively 3 builds at the same time it can exhaust the memory. I had expected the CLI to run build for each version behind the scenes and not require much more memory. I have also found that running the build command separately for each build required is quicker despite running it 3 times instead of once.
The text was updated successfully, but these errors were encountered: