-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
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
.tsx
support broken since v0.9.0
#189
Comments
.tsx
support broken since 9.0.0
.tsx
support broken since v0.9.0
@jrson83 , the |
@zoeyzhao19 Itested this with |
I think we can also directly add tsx loader to defaults in inline plugin :) |
That would be great. Or at least add a hint to the docs. I searched through issues, changelogs, PR's and also googled how to make unbuild work with |
I submitted a PR that add jsx/tsx loader to defaults in inline plugin to fix this issue: #198 |
Environment
Reproduction
https://github.com/jrson83/unbuild-broken-tsx
unbuild-broken-tsx
0.9.0
is broken when using.tsx
0.8.11
is working when using.tsx
0.9.0
is working when using.tsx
Usage
Install and run build on broken 0.9.0 example:
git clone https://github.com/jrson83/unbuild-broken-tsx.git cd unbuild-broken-tsx npm install npm run build
Install and run build on working 0.8.11 example:
git clone -b unbuild@0.8.11 https://github.com/jrson83/unbuild-broken-tsx.git cd unbuild-broken-tsx npm install npm run build
Install and run build on fixed 0.9.0 example:
git clone -b unbuild@0.9.0-fix https://github.com/jrson83/unbuild-broken-tsx.git cd unbuild-broken-tsx npm install npm run build
Describe the bug
When running build on a
.tsx
file, unbuild throws an errorSyntaxError: Unexpected token
.Additional context
compare/v0.8.11...v0.9.0
Update on possible fix
Update
build.config.ts
:Logs
The text was updated successfully, but these errors were encountered: