-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Typescript + React: Unexpected token: "(" #3446
Comments
I think you either need a Unless you're already using one of those, this might not be a bug in Parcel itself. |
Have the same issue, but I'm using lerna monorepo with yarn workspaces. And issue occurs when I import with namespace like Also TS with React. |
@chrisands Do you have |
@embeddedt yes, I do have |
@embeddedt I created repository example with issue |
Our team is build a package and are receive the exact same error in the exact same spot. |
Curiously, in Parcel
|
For some reason, #2486 hasn't got ported to v2. I've basically applied the same fix locally and now the error is:
It made me change Now, the error is:
|
I've managed to reduce the example app to just
and then exits with status=1 |
Could you share that example code? |
Any luck on this issue? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. |
🐛 bug report
Using a .pug file as the entry point, I'm including a script file which is a .tsx file and yet the React part of it seems to be failing.
🎛 Configuration (.babelrc, package.json, cli command)
I do not have a .babelrc file - do I need one and why?
My configuration is a bit...complex, basically I'm creating a package that I can use as a dependency that renders react components within the main package in a harness page. If I get chance I'll create a simpler repo with the issue though.
🤔 Expected Behavior
Parcel should transpile the TypeScript and React TSX into javascript.
😯 Current Behavior
I'm getting an error:
💻 Code Sample
Will add asap
🌍 Your Environment
The text was updated successfully, but these errors were encountered: