You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today UI5WC cannot be run inside Node.js because it relies on browser-specific objects like window and browser-specific APIs like fetch. For purposes of testing (via Jest, for example) or potentially server-side rendering, it would be nice to be able to use UI5WC inside Node.js instead of a browser.
Proposed Solution
I'm not exactly sure what an exact solution would look like, but presumably it would need to internally use alternatives for browser-specific objects and APIs where possible, if such objects/APIs are found to not be available at runtime.
Priority
Low
Medium
High
Very High
The text was updated successfully, but these errors were encountered:
With this change the web components use shim for node/ssr environment and available since version 1.22. The web components will no longer fail if imported within Node. However it's only the first step, there are plans to work on complete SSR solution, described in this GitHub issue. We will post update in the issue for timelines and decisions made.
Feature Request Description
Today UI5WC cannot be run inside Node.js because it relies on browser-specific objects like window and browser-specific APIs like fetch. For purposes of testing (via Jest, for example) or potentially server-side rendering, it would be nice to be able to use UI5WC inside Node.js instead of a browser.
Proposed Solution
I'm not exactly sure what an exact solution would look like, but presumably it would need to internally use alternatives for browser-specific objects and APIs where possible, if such objects/APIs are found to not be available at runtime.
Priority
The text was updated successfully, but these errors were encountered: