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
transpile next code with estree-util-build-jsx
estree-util-build-jsx
const a = () => ( <> <div>text</div> <div> text </div> <div> text{" "} </div> </> )
const a = () => React.createElement( React.Fragment, null, React.createElement("div", null, "text"), React.createElement("div", null, "text"), React.createElement("div", null, "text", " ") );
const a = () => React.createElement( React.Fragment, null, React.createElement("div", null, "text"), React.createElement("div", null, " text"), React.createElement("div", null, " text", " ") );
typescript, babel, swc work as expected, but this project adds extra leading spaces
The text was updated successfully, but these errors were encountered:
Why should this project do things differently than babel, esbuild, typescript, swc?
Sorry, something went wrong.
Babel and typescript don't add spaces in this case (don't have exp with esbuild and swc)
check the repl
EDIT:
swc trims leading spaces too.
1a8b9d3
No branches or pull requests
Uh oh!
There was an error while loading. Please reload this page.
Steps to reproduce
transpile next code with
estree-util-build-jsx
Expected behavior
Actual behavior
typescript, babel, swc work as expected, but this project adds extra leading spaces
The text was updated successfully, but these errors were encountered: