Noel Calonia

@iAli22 sorry for the laaaateeee response, I didn't though, my last resort is to not include a pre-render from it to avoid the headache.

@bpolaszek sorry for the laaaateeee response, I didn't though, my last resort is to not include a pre-render from it to avoid the headache. but @bpolaszek @iAli22 try to replace...

I tried to solve this issue via latest version of Nuxt 3; to import all components of tw-elements via plugins(like we've used to do in nuxt 2 on most 3rd...

@Trochonovitz hello, thank you for your response. Can you able to provide some sample/s on initialization of the said codeblock via JavaScript? It would be a great guide to those...

@iprzybysz hi, do you have an idea about this issue? Thanks

> @noelc10 try our integration tutorial: it should answer to all of you questions. :) https://tw-elements.com/docs/standard/integrations/nuxt-integration/ @Trochonovitz I already follow those tutorials and resolve the routing issue on my end....

@manniL hey man, glad that you notice this issue, I'm a big follower on your YouTube videos 🙌 (P.S.: I'm rooting on you on this issue 🥺) My bad for...

@melasculla I resolve my issue by fixing the i18n config on nuxt.config.ts file: ```javascript i18n: { strategy: 'no_prefix', locales: [ { code: 'kr', language: 'kr-KR', name: 'Korean', file: 'kr-KR.js' },...

@BobbieGoede will try to create a reproduction, I'll post when able. Thanks.

@melasculla probably related to tailwind or vite that makes the # causing the issue. Did you have a workaround on resolving this one on your end? maybe try to remove...