Justinas Delinda

For simple cases sure you can use v-if but what should be shown in v-else part, sorry your data was not loaded, but navigation was a success? You can kinda...

Vue supports jsx when lang attribute set as such `lang=jsx` without it, parser error is thrown, [see](https://play.vuejs.org/#__PROD__eNp9kTFPwzAQhf+KdRNIVTLAVKWVAHWAARAwerGSI7g4tmWfQ6Qq/52zo5YOqEsUv++98zv5AHfeV2NCWENDOHijCLfSCtF0etw2df5K29RnjI+xDdqTiEjJC6Nsv5FAUQLT1tlIQolNmSDqEsiiM1gZ11+p6zxvmcAQVpxk/qn7ah+d5SKHfL+E1g1eGwwvnjTnJaxFIZkpY9zPU9EoJFwd9fYL2+9/9H2csibhNWDEMKKEEyMVeqQF796fceL/Exxclwy7L8A35N1S7rjY7pPtuPaZr7R9HLwLpG3/EXcToY3HpXLR7JyLXwK/xsOF1f/q3lS3JSftDPMv8TSW/Q==) Should we also enable it based on attribute?

The problem enabling jsx on every vue file would that valid TS code like `const fn = () => {}` would no longer be parsed correctly.

Sorry if I am wrong, doesn't this PR changes behavior that `lang='ts'` is being parsed as `tsx` and `lang=js` as `jsx`?

Launched `vite --profile` and it seems loadConfigFile is called over and over. Not sure of that is intended but I see bunch of Jiti's calls under it too.

I managed to solve this issue by using rollup manual chinks option: ```ts build: { rollupOptions: { output: { manualChunks: (id) => { // Merge all css into a single...

Currently that lint rule fails for me, hence this issue report. I think I was bit wrong `this` should not be declared on `defineExtensionMessaging` but on `sendMessage` instead https://github.com/aklinker1/webext-core/blob/ce0ad0d78de9feff2c91a239cd42294d989e6819/packages/messaging/src/generic.ts#L40-L59 Not...

@SaadBazaz are you interested looking into this?

I added reproduction https://github.com/minht11/tauri-TaskDialogIndirect-issue. I am using [moon](https://moonrepo.dev/moon) task runner to install additional cargo things, but that shouldn't be needed if you have them.

Still an issue on latest RC.