server-side error: HTMLSelectElement is not defined #2233
Comments
|
Bug reports must include a live demo of the problem. Per our contributing guidelines, please create a reduced test case (you can use our preconfigured Plunker), and report back with:
|
|
This setup is very complicated. There is no reduced test case. I can make a public repo that others can try the newer version to see it. The problem is that its part of Server Side Rendering and it being compiled with a package manager to reproduce. I could dig further in, but I will just wait till others see the issue with other similar systems if a repo is not good enough. |
|
So you're only getting that error server side? |
|
It really just needs a |
|
Definitely that would fix the error. Just wanted to make sure I didn't need to come up with a new way to do the |
caseyjhol
changed the title
|
@caseyjhol I am not 100% sure if that is the case (where its not yet available), but sounds like the case. Let me know when I can update and test again. If you need more help, I should have time in a week to dig deeper. I do like this project and have been using it for a long time. |
|
Released in v1.13.9! |
|
Thanks for trying, now I get another error (Just updating this one package) and still breaks everything. I will dig deeper soon, still works 100% with version 1.13.5. Big deadline then I will be happy to make a PR |
|
@MarcGodard What error are you getting now? |
|
@caseyjhol unfortunately the error isn't descriptive. It would require some deep probing.
However, the older version still works 100%. |
|
@MarcGodard For what it's worth, this polyfill will be removed in v1.14.0, so if you're still having problems hopefully that will fix it. |
I have been getting this error since 1.13.6:
error: HTMLSelectElement is not definedI have no idea why, or how, but I use a type of webpack and server side rendering. So I assume in one of those the error is created (if no one else is getting this issue).
The text was updated successfully, but these errors were encountered: