-
Notifications
You must be signed in to change notification settings - Fork 372
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
Trying to import effect
results in parse issue.
#1484
Comments
I am generally going to ask for reproductions. Doesn't matter how trivial it is. It saves a good chunk of time. And when triaging happens how much time estimate to look into an issue comes into consideration. That being said looking at the error maybe it's related to The oddest part is this is a parser issue in TypeScript of all things. I can tell from the error this is coming from SolidStart so it might even be other bundling transform considerations, not even the JSX transform. |
O yea sorry! I was kind of in a hurry when creating the issue 😅, so I wasn't really able to create a repro repo. Sorry! I'll update the issue first thing tomorrow to link to a reproduction repository. |
I have created a minimal reproductive repository using SolidStart and have linked it to the issue description. Sorry again, and I hope this helps! |
Thanks I might move this to Start now because I'm not sure what piece in the pipeline is causing this. |
adding:
to the |
Describe the bug
When trying to import the effect library (see: https://effect.website) babel seems to complain, as babel is used in the effect pipeline as well, and the code is valid, it seems odd that solid.js seems to be failing.
The error is:
Your Example Website or App
https://github.com/indietyp/solid-js-regressions/tree/effect-dependency (branch: effect-dependency)
Steps to Reproduce the Bug or Issue
Simply
import { Iterable, pipe } from "effect";
in a solid start repo should work.Expected behavior
I can compile
Screenshots or Videos
No response
Platform
Additional context
The text was updated successfully, but these errors were encountered: