dynamic import at top level fails

[s7dhansh]

A)

async function main() {
	const [
		React,
		{hydrate},
	] = await Promise.all([
		import('react'),
		import('react-dom'),
	]);

	hydrate(<div>asdfasdf</div>, document.getElementById('root'));
}

main();

fails with an error:

Uncaught ReferenceError: exports is not defined
    at 0.js:1
(anonymous) @ 0.js:1
app.js:817 Uncaught (in promise) Error: Loading chunk 0 failed.

If I remove the Promises, it works:
B)

import React from 'react';
import {hydrate} from 'react-dom';
hydrate(<div>asdfasdf</div>, document.getElementById('root'));

Ironically enough, if I replace (B) with (A) now (while meteor is running), the app starts working. It fails again when I restart meteor. Can someone guide me on fixing/debugging this?

[abecks]

I don't believe Meteor's dynamic import functionality will currently work with this package. Some more work is likely required. You might be better off using webpack's code splitting functionality.

[s7dhansh]

How do I do that?
Webpack's code splitting with dynamic imports also uses the same syntax, right? Should I remove dynamic-import from meteor packages?

[abecks]

To be honest I'm not sure, as I haven't used it before. If you have any luck, please let me know.

…

On Tue, Apr 2, 2019 at 10:30 AM Sudhanshu ***@***.***> wrote: How do I do that? Webpack's code splitting with dynamic imports also uses the same syntax, right? Should I remove dynamic-import from meteor packages? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#64 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB-PgQwxB9aWlO-nf-mn-IEpFIzgJmKwks5vc5O3gaJpZM4cXwWi> .

[ardatan]

@s7dhansh @abecks Meteor-Webpack supports dynamic imports by serving chunks as assets;

meteor-webpack/atmosphere-packages/webpack/plugin.js

Line 129 in 1f67967

targetFile.addAsset({

I think there is a problem in dev-middleware package about calculation of output files.
68898dc#diff-8f10efed2c00dab752c268b55cfd62a1
The problem may be related to this commit, on each compilation the assets to be served must be recalculated.

[s7dhansh]

@ardatan sorry I have very limited understanding of what you are saying. Can you let me know a fix that I can try?