[bug?]import {jsx} from 'react/jsx-runtime' would throw error in package with type: module

[indooorsman]

e.g.:
I bundle a lib package with latest esbuild(format: esm, target: chrome100 & "type":"module" in package.json), which export a react component, by default the output would be something like:

import { jsx } from 'react/jsx-runtime';
....

then if some project used my lib but bundle with webpack, the error would happen:

in my opinion, if my package set type to module explicitly, esbuild should add .js to the import path:

import { jsx } from 'react/jsx-runtime.js';
....

[evanw]

This is documented here: https://esbuild.github.io/api/#jsx-import-source

The /jsx-runtime and /jsx-dev-runtime subpaths are hard-coded by design and cannot be changed.

This is deliberate behavior.

in my opinion, if my package set type to module explicitly, esbuild should add .js to the import path:

import { jsx } from 'react/jsx-runtime.js';

They tried doing what you suggested, and then they reverted it because it was a bad idea: babel/babel#12210. Closing this issue as esbuild is working as intended. Your bug report is a problem with React, not with esbuild, and this problem was fixed in React 18: facebook/react#20235 (comment).

[indooorsman]

This is documented here: https://esbuild.github.io/api/#jsx-import-source

The /jsx-runtime and /jsx-dev-runtime subpaths are hard-coded by design and cannot be changed.

This is deliberate behavior.

in my opinion, if my package set type to module explicitly, esbuild should add .js to the import path:

import { jsx } from 'react/jsx-runtime.js';

They tried doing what you suggested, and then they reverted it because it was a bad idea: babel/babel#12210. Closing this issue as esbuild is working as intended. Your bug report is a problem with React, not with esbuild, and this problem was fixed in React 18: facebook/react#20235 (comment).

Got it, thanks