You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The initial load of a web app can be sped up by preloading all javascript chunks it needs using <link> tags. This could be done with the esbuild JS or Go API like it is done with Rollup, where each output chunk has imports and dynamicImports keys specifying paths to the corresponding output files. Rollup's CLI doesn't currently support outputting this information, but perhaps esbuild could optionally emit a manifest file with metadata on all emitted entrypoints, chunks, and assets.
Below is a link to the relevant Rollup docs section:
Thanks for logging this. I agree that this would be good to do.
There actually already is a way to emit a metadata file (the --metafile flag) but it probably doesn't yet output all of the information it needs to for code splitting.
The initial load of a web app can be sped up by preloading all javascript chunks it needs using
<link>
tags. This could be done with the esbuild JS or Go API like it is done with Rollup, where each output chunk hasimports
anddynamicImports
keys specifying paths to the corresponding output files. Rollup's CLI doesn't currently support outputting this information, but perhaps esbuild could optionally emit a manifest file with metadata on all emitted entrypoints, chunks, and assets.Below is a link to the relevant Rollup docs section:
http://rollupjs.org/guide/en/#rolluprollup
The text was updated successfully, but these errors were encountered: