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
When there are other file types/loaders used, an attempt is made to process them as valid input for stylex leading to a compilation failure
example if the index.html file has a different extension for template compilation.
ERROR in Error: Child compilation failed:
Module parse failed: Unexpected token (1:0)
File was processed with these loaders:
* ../../node_modules/.pnpm/html-webpack-plugin@5.6.0_webpack@5.91.0/node_modules/html-webpack-plugin/lib/loader.js
* ../../node_modules/.pnpm/unplugin@1.10.1/node_modules/unplugin/dist/webpack/loaders/transform.js
You may need an additional loader to handle the result of these loaders.
> <!DOCTYPE html>
| <html lang="en">
|
The text was updated successfully, but these errors were encountered:
deepjoy
pushed a commit
to deepjoy/unplugin-stylex
that referenced
this issue
May 18, 2024
I've been runnning into this with more and more extensions since bundlers deal with fonts, images, svg, xml, json and numerous other extension. Could we flip to a model that only validExts are processed by this plugin.
Maybe something like
'''
[ ".js", ".cjs", ".mjs", ".ts", ".jsx", ".tsx"]
'''
By default.
When there are other file types/loaders used, an attempt is made to process them as valid input for stylex leading to a compilation failure
example if the index.html file has a different extension for template compilation.
The text was updated successfully, but these errors were encountered: