LWC compiler errors on `.jsx`/`.tsx` files about lwc HOT 6 CLOSED

Sure, I would recommend reading CONTRIBUTING.md.

from lwc.

Alternatively, we could have @lwc/rollup-plugin just not route .jsx/.tsx files to @lwc/compiler, since @lwc/compiler doesn't need to compile them anyway. (They cannot possibly be LWC components.)

from lwc.

hey @nolanlawson ,
I have tried fixing it by just checking the file extensions and returning early if file extensions are either .jsx/.tsx. I am not sure whether it'll introduce a breaking changes or not. Can you please verify?

from lwc.

Hi @SaurabhMulay999 thanks for the contribution! However, this fix needs to be made inside of @lwc/compiler, not @lwc/rollup-plugin. The Rollup plugin uses the @lwc/compiler under the hood, but there are other consumers of the compiler (e.g. Webpack, LWR).

As mentioned above, I think the simplest fix would be to add the extensions here. It is not ideal, since .jsx/.tsx files are unlikely to need LWC component transformations, and it will assume that someone has set up a tool earlier in the processing pipeline to convert these files into JS, but it seems like the most expedient solution to me.

from lwc.

Thanks @nolanlawson for the details. I'll try what you have suggested. Is there any open doc maintained to get idea of whole project? It would be helpful.

from lwc.

Fixed by #4164

from lwc.