We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
I'm not sure if this is a bug, but seems like a change in behavior from 5 to 6
In 5.x, using React, I could resolve a .tsx or .jsx file with:
.tsx
.jsx
import Foo from "components/foo"
In 6.0, with the default configuration and preset-react, I can't do that, I have to do the import as
preset-react
import Foo from "components/foo.tsx"
Can't tell if this is my error, or a deliberate change of some kind.
Thanks.
The text was updated successfully, but these errors were encountered:
Have you tried
// development.js OR base.js // ... webpackConfig.resolve.extensions.push('.tsx') // ...
Sorry, something went wrong.
@noelrappin Could you try from master? This PR was recently merged and should address your issue #2862
No branches or pull requests
I'm not sure if this is a bug, but seems like a change in behavior from 5 to 6
In 5.x, using React, I could resolve a
.tsx
or.jsx
file with:import Foo from "components/foo"
In 6.0, with the default configuration and
preset-react
, I can't do that, I have to do the import asimport Foo from "components/foo.tsx"
Can't tell if this is my error, or a deliberate change of some kind.
Thanks.
The text was updated successfully, but these errors were encountered: