We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I wasn't sure which repo this issue belonged to, I discovered it while adding prember to a new app.
If I add a css import to a ts/js file eg
application/route.ts
import '../style/styles.css';
Webpack attempts to use insertStyleElement to inject the css to the page, but this uses document.createElement so the page fails to render under fastboot and prember cannot successfully build the page https://github.com/webpack-contrib/style-loader/blob/43bede4415c5ccb4680d558725e0066f715aa175/src/runtime/insertStyleElement.js
insertStyleElement
document.createElement
style-loader in general makes use of document quite liberally. What would need to happen to support this?
style-loader
document
The text was updated successfully, but these errors were encountered:
This is being worked on here
embroider-build/embroider#1049
and here
embroider-build/embroider#1146
Sorry, something went wrong.
Thanks @ef4 I'll close this issue
No branches or pull requests
I wasn't sure which repo this issue belonged to, I discovered it while adding prember to a new app.
If I add a css import to a ts/js file eg
application/route.ts
Webpack attempts to use
insertStyleElement
to inject the css to the page, but this usesdocument.createElement
so the page fails to render under fastboot and prember cannot successfully build the pagehttps://github.com/webpack-contrib/style-loader/blob/43bede4415c5ccb4680d558725e0066f715aa175/src/runtime/insertStyleElement.js
style-loader
in general makes use ofdocument
quite liberally. What would need to happen to support this?The text was updated successfully, but these errors were encountered: