-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Error in 2.30.0 - ERROR in Template execution failed: TypeError: Cannot read property 'Symbol(Symbol.iterator)' of undefined #753
Comments
Hi @billneff79 I don't believe there is a breaking change in the new version, here's the diff if you can spot anything: 2cc10df...09a96f5 Would you mind posting your webpack config? Also can you double check it's working on 2.29.0 |
I verified that it is purely the switch from 2.29.0 to 2.30.0 that is causing it by doing the following:
We have a pretty complicated webpack config. I'll see if I can get it up here. |
@billneff79 a git repository would be even more awesome, that way I can check which commit introduced the issue :) |
Same issue with us as well. Started happening today. We have a starter app created via preact-cli. |
Thank you @exp10r3r, I managed to reproduce the issue |
I may be the common denominator there, let me know if either of the templates are doing something incorrect: https://github.com/developit/preact-cli/blob/master/src/resources/template.html |
@developit It might be caused by this line: https://github.com/developit/preact-cli/blob/master/src/resources/template.html#L13, but I don't believe there is anything wrong with it I will add some tests later to prevent this kind of changes to land in the future |
@mastilver thank you for the quick response! Much appreciated. |
Thanks for your quick feedback I merged #754 and released 2.30.1 |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
After upgrading from 2.29.0 to 2.30.0 this morning, we are seeing this error in our build. This does not occur in 2.29.0. Was there supposed to be a breaking change in 2.30.0?
The text was updated successfully, but these errors were encountered: