proposal-dynamic-import VS proposal-object-rest-spread

Something like dynamic import() could do the trick, but that ends up chunking your build rather than omitting what you don't need/want.

I've looked at the official proposal (https://github.com/tc39/proposal-dynamic-import) and it seems possible to do something like this:

Support for modern JavaScript features like async/await, rest/spread, dynamic imports right out of the box which make the developer's life easier.

You can just use the javascript import() syntax if you want to dynamically import a simple javascript module. next/dynamic just adds some extra stuff on top of that to make React components work without having to handle the promise yourself..

I located first usages of "spread operator" in January 2009, and also in the language in the TC39 proposal itself - even though MND has changed the name of the content from "Operator" to "Syntax" https://github.com/tc39/proposal-object-rest-spread

According to TC39, object spread initializer is a syntactic sugar on top of Object.assign. So the next logical step is to see how the Object.assign should work, as instructed by the ECMAscript spec.

Support for modern JavaScript features like async/await, rest/spread, dynamic imports right out of the box which make the developer's life easier.