-
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
polymer-bundler v3.1.1 fails to inline script with empty getter function #775
Comments
cc @azakus @usergenic. This was discovered at https://chromium-review.googlesource.com/c/chromium/src/+/1309223 by @rbp314. |
Interesting... i wonder if our JS parser in the analyzer broke trying to read it with empty body and/or if this is an issue with latest package versions. Thanks for the heads up @freshp86 - I'll add a regression test for this case and see where it leads. |
Note Bundler is now part of https://github.com/Polymer/tools so I'll transfer this issue over there. |
@usergenic Issue with dead code removal? Just a thought. Seen lots of those floating around babel repos lately for some reason. |
@moderndeveloperllc makes a lot of sense assuming the dead-code removal occurs prior to bundling. Verifying... |
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! |
bug.html file
bug.js file
Polymer bundler command (version 3.1.1)
The command above returns the contents of the original HTML file without inlining the JS file. The contents of the manifest indicate that something went wrong.
Apparently polymer-bundler failed to find the JS file, which seems very odd.
If
get foo() {}
is changed to have some contents, likeThe problem no longer happens, and the script is inlined as expected.
The text was updated successfully, but these errors were encountered: