-
Notifications
You must be signed in to change notification settings - Fork 145
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
Can't get Jasmine 4 to support .jsx files #188
Comments
Well, it didn't take long at all to get the answer to "do we still need the I'm not sure how best to reconcile the conflict between providing good support for ES modules and supporting nonstandard (but very common) file extensions. But as a quick fix you can get around the problem by adding |
@sgravrock Darn, that sucks. I can confirm that Thanks for updating the docs in 1e133d6. Can I suggest updating the React documentation page here as well? Given that most React users will be following that guide I think the |
Done. But I also think Jasmine can probably handle this transparently, by falling back to |
Thanks! Going to close this issue as this addresses my initial issue. |
Thanks to you both for handling this issue promptly. It resolved the same issue for |
I've also just released 4.0.1, which handles this situation without the need for a configuration change. |
Confirmed. With 4.0.1 |
Are you creating an issue in the correct repository?
I hope so. Only the core
jasmine
dependency is used to reproduce this.Expected Behavior
Spec files with the
.jsx
extension should be loadable byjasmine@4
when used withbabel
.Current Behavior
Trying to load a
.jsx
file throws:Possible Solution
Not sure. This wasn't a problem in
jasmine@3.99
, so maybe the new ESM changes injasmine@4
are causing it?Suite that reproduces the behavior (for bugs)
https://stackblitz.com/edit/node-pmddnq?file=README.md
Context
Makes v4 somewhat un-useable for React projects.
Your Environment
The text was updated successfully, but these errors were encountered: