Are nextjs's dynamic imports more performant than an array of components?

Title may sound dumb, but I can’t use variables w/ the dynamic variables.

const t = './page'
dynamic(import(t))

Fails but dynamic(import('./page')) works.

That’s fine I guess - I’m currently circumventing this by having all of my templates in an array and using some logic to figure out which template to use by its key value.

However, it looks like I could maybe do this with the modules{} object that dynamic takes. Would it be more performant or would it ultimately be the same thing?

[tweeres04]

The TC39 proposal mentions passing a variable or template string literals in order to not only lazy load, but also pick which module to load at runtime based on some context. An example from the proposal is import(`./language-packs/${navigator.language}.js\`)

Will this ever be supported by next.js? I am hoping to achieve something like dynamic(import('./blog/${post-slug}`)), saving each of my blog posts as react components.

Either way, the documentation suggests the tc39 import spec is supported, which it only partially supports. I think some clarification on that would clear things up for some.

[Haraldson]

No official statements on this yet?