Can't get Jasmine 4 to support .jsx files

[EvHaus]

Can't get Jasmine 4 to support .jsx files

[sgravrock]

Done.

But I also think Jasmine can probably handle this transparently, by falling back to require() when it gets that particular error code. The drawback I see is that it'd lead to more confusing errors if someone tries to use ES module syntax in a JSX file without transpiling, but hopefully that's a rare scenario.

[sgravrock]

Well, it didn't take long at all to get the answer to "do we still need the jsLoader setting, and why?". One of the ways in which dynamic import isn't quite a drop-in replacement for require is that it only accepts paths that use a small predefined list of extensions, which doesn't include .jsx.

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 jsLoader": "require" to your jasmine.json file.

[EvHaus]

@sgravrock Darn, that sucks. I can confirm that jsLoader: "require" fixes the problem.

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 .jsx info will be relevant to them there.

[EvHaus]

Thanks! Going to close this issue as this addresses my initial issue.

[ch1c0t]

Thanks to you both for handling this issue promptly. It resolved the same issue for .coffee files in coffeelib.

[sgravrock]

I've also just released 4.0.1, which handles this situation without the need for a configuration change.

[EvHaus]

Confirmed. With 4.0.1 jsx files work without jsLoader: "require". Thanks!