JSX automatic transform development incorrect

[kitsonk]

Describe the bug

When attempting to transform JSX, with the setting development to true, swc does not properly transpile like Babel or TypeScript.

It provides something like this:

import { jsx as _jsx, Fragment as _Fragment } from "react/jsx-runtime";
function App() {
    return(/*#__PURE__*/ _jsx("div", {
        __source: {
            fileName: "https://deno.land/x/mod.tsx",
            lineNumber: 4
        },
        __self: this,
        children: /*#__PURE__*/ _jsx(_Fragment, {
        })
    }));
}

Input code

function App() {
  return (
    <div><></></div>
  );
}

Using a JSX pass with the options like this:

let options = swc_ecma_transforms_react::react::Options {
  runtime: Some(swc_ecma_transforms_react::react::Runtime::Automatic),
  development: true,
  import_source: "react".to_string(),
  ..Default::default()
};

Expected behavior

This is what Babel outputs with development plugin:

var _jsxFileName = "/repl.tsx";
import { Fragment as _Fragment } from "react/jsx-dev-runtime";
import { jsxDEV as _jsxDEV } from "react/jsx-dev-runtime";
export function App() {
  return /*#__PURE__*/_jsxDEV("div", {
    children: /*#__PURE__*/_jsxDEV(_Fragment, {}, void 0, false)
  }, void 0, false, {
    fileName: _jsxFileName,
    lineNumber: 3,
    columnNumber: 5
  }, this);
}

And this is what is output by the TypeScript emitter:

import { Fragment as _Fragment, jsxDEV as _jsxDEV } from "react/jsx-dev-runtime";
const _jsxFileName = "file:///input.tsx";
export function App() {
    return (_jsxDEV("div", { children: _jsxDEV(_Fragment, {}, void 0, false, { fileName: _jsxFileName, lineNumber: 3, columnNumber: 10 }, this) }, void 0, false, { fileName: _jsxFileName, lineNumber: 2, columnNumber: 11 }, this));
}

As you can see in both cases, they are using the jsxDEV import from the jsx-dev-runtime module, not the jsx import from the jsx-runtime module.

Version

swc_ecma_transforms_react 0.53.0

[swc-bot]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.