Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
ripple: HTMLElement is not defined on SSR
See original GitHub issueHello,
With the changeover to TS in v0.8.0, the following line went from being scoped within a function to not:
const MATCHES = util.getMatchesProperty(HTMLElement.prototype);
In SSR React apps, this will result in an HTMLElement is not defined error, because it’s not evaluated in a browser where HTMLElement would exist.
The following line, when added just before the line above, resolves the issue locally:
const HTMLElement = typeof HTMLElement === 'undefined' ? function () {} : HTMLElement;
However, I’m not sure this is an appropriate solution outside of my use case. If this addition would suffice, I can submit a PR for it. Let me know! Thanks! 😄
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
sweet! ya don’t worry too much about exploring how RMWC tests SSR. I will be looking into…eventually. I need to meet with the team to see where it fits into 2019.
closing as #592 was merged. Thanks again!