Add importEntrypoint to CunkExtractor and don’t load stats with require. about loadable-components HOT 9 CLOSED

Fixed

from loadable-components.

is it technically different?
This will blow up a little with transpilation/cjs so what about moving responsibility to the end user

const App = extractor.importEntrypiont(await import('test entrypoint'))
//                                     ^ everything under user control

from loadable-components.

Yeah that seems better.

from loadable-components.

const App = await extractor.importEntrypiont(‘test entrypoint', (entry) => import(entry)))

Maybe?

from loadable-components.

That will not be statically analyzeable. Not sure if there's a need, it's not analyzable right now, but why you might need such indirection?
Lets apply occam's razor here and cut what we don't have a good reason for.

from loadable-components.

Also a typo in the example (piont).

from loadable-components.

const App = await import(extractor.getEntrypointPath(‘testentrypoint'))

Is better perhaps.

from loadable-components.

requireEntrypoint seems to require all script assets up front, so should it import all too?

from loadable-components.

In the pull i added you can now do

const extractor = ChunkExtractor({ statsfile: 'loadable-stats.json', entrypoints: ['main'] })
await Promise.all(extractor.getAllScriptAssetsPaths().map(asset=>import(asset)))
const App = await import(extractor.getEntrypointPath('main'))

from loadable-components.