refactor: add Vite compatibility when lazy loading

[farnabaz]

Using the module with Nuxt Vite does not lazy load languages on client site because of limitations of dynamic import.

This PR will expand dynamic import into a switch case to remove variables inside import name and automatically detects build target and change the srcDir alias

@pi0 What do you think about this?

[rchl]

I'm fine with it although I would love if there wouldn't have to be a special case checking for the presence of nuxt-vite. Do you have some links that explain that @fs{dir} syntax?

[farnabaz]

I would love if there wouldn't have to be a special case checking for the presence of nuxt-vite

I asked pooya to check it, I wanted to make sure about checking vite environment here (He may have better idea):

/* <% const _srcDir = (isDev && (nuxtOptions.buildModules || []).includes('nuxt-vite')) ? '/@fs' + srcDir : '~' %> */

Do you have some links that explain that @fs{dir} syntax?

It is the second reason why I keep this drafted and asked Pooya. @fs is not documented and I found it in Vite internals.

[farnabaz]

My bad, your refactor is great :) I was addressing isDev && (nuxtOptions.buildModules || []).includes('nuxt-vite'))

[rchl]

Ideally, Vite would also support the ~ alias since it's used in many places. I'm surprised if it doesn't.

(sorry, I've removed my earlier comment as I've realized that you meant something else)

[pi0]

@farnabaz @rchl At least at this stage, we should not depend on any vite-specific feature like checking it's existence from buildModules or @fs/ requests.

Ideally, Vite would also support the ~ alias since it's used in many places

Actually it should do since we are providing resolve.alias option for ~ (otherwise it is a bug in either vite or nuxt-vite)

Let me check PR locally :)

[rchl]

Thanks to both of you for your work on that.

[pi0]

This could be done in a simpler approach by mapping to file and use a Set 😃

[pi0]

Needs to tested but looks good to me now

[rchl]

LGTM too. I've tested it in one of my projects that uses lazy loading and of course tests pass also.

[rchl]

Haven't tested with Vite though so I can wait until someone does that.

[pi0]

Haven't tested with Vite though so I can wait until someone does that.

There is no pressure on vite. Since everything is super experimental know so i don't want to make chaos in community for vite support. These PRs generally improved runtime quality with esm support.