You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
extensionAlias: {// Make webpack try the .tsx and .tsx extensions in case the import// doesn't match a .js file. This is necessary to get TS and ESM to work// together.// cf. https://github.com/webpack/webpack/issues/13252#issuecomment-1170215575".js": [".js",".ts",".tsx"],},
What does the proposed API of configuration look like?
What problem does this feature solve?
I already added details in another closed issue but the gist of it is:
.js
because that's what Node's resolution algorithm expects.js
to.ts(x)
to support this strategy as wellWith Webpack I could have (inspired by this comment webpack/webpack#13252 (comment)):
What does the proposed API of configuration look like?
Just match the Webpack configuration: https://webpack.js.org/configuration/resolve/#resolveextensionalias
The text was updated successfully, but these errors were encountered: