fix: change isTSX option to opt-in

[wattanx]

🔗 Linked issue

Fixes: #1063

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

If you add isTSX, you cannot use angle-bracket syntax.
We would like to change it to opt-in as it would be inconvenient for users who do not use tsx.

(If it were possible to replace esbuild, I would replace it.)

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[wattanx]

It can also be resolved at #1065.
I will open this if the migration to esbuild does not work.

[rchl]

Shouldn't we stick to simple fixes like this one instead of migrating the whole build to esbuild? The latter sounds risky and I'm not sure if adding more work to Nuxt 2 which is in maintenance mode makes sense.

[rchl]

Is it possible to enable this plugin per webpack rule so that we can target the one without isTSX for typescript files and one with isTSX for jsx/tsx?

Though maybe vue files would still be problematic since those don't explicitly state whether they are using tsx or not. But then the opt-in could be for vue files only rather than global.

[wattanx]

Shouldn't we stick to simple fixes like this one instead of migrating the whole build to esbuild?

Yes, I agree.
I am planning to introduce the migration to esbuild to reduce the differences with Nuxt 3.
(Nuxt Bridge is an upward compatible library)