fix: drop development for precompile JSX transform #179
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, this transform doesn't really have a
development
behavior really. Exposing this in the transform options is therefore confusing.What we did when
development: true
is that we imported fromjsx-dev-runtime
and calledjsxDEV
instead ofjsx
, but that has been more or less regarded as a design flaw of the jsx runtime proposal. These days everyone just aliasesjsx-dev-runtime
andjsx-runtime
to the exact same file and aliasesjsxDEV
tojsx
. The only difference between those functions is thatjsxDEV
receives more parameters about call location. Everyone just treats that as optional arguments tojsx
these days.For all those reasons it's best if we drop the
development
option of the precompile transform.