New import()
In compliance with the upcoming es6 proposal-dynamic-import and Typescript 2.4 dynamic imports we added this functionality.
With the new import()
support you can do the following:
- import json
- import CSS
- import ANY other extension (give strings)
- import javascript file (+commonjs)
- import split bundles (WITHOUT "magical" comments)
And it works on server and in browser!
Example:
import("./main.css")
await import("./external.js")
await import("./config.json")
// bundle name "about"
await import("about")
// bundle name "about"
// automatically mapped to bundle "about" (no comments required)
await import("./components/about/AboutComponent")
And yes, it works with Quantum and has a nice test coverage
Check this out
npm install
node fuse dist
Browser target
Browser
target for the Vanilla API got a major improvement. It handles it not just for the entry points, but also across an entire module. It will display a warning and notify users about possible problems if the latter is not set.

Quantum improvements
Quantum has a massive upgrade too.
- ContainedAPI for publishing a single bundle to CDN or NPM
- Lego-API has been improved. It contains so much more features and adjusts to your needs automatically.
- Improved stability and compatibility with Windows OS.
- Generating manifest files
- Various improvements and bug fixes (lots of them)
Require Statement Hoisting
It will be possible to enable hoisting with Quantum. Many repetitive require statements gets hoisted when built with Quantum
Promise polyfills with Quantum
Quantum has polyfills
property that accepts a list of desired polyfills to be included
QuantumPlugin({
polyfills : ["Promise"]
})
Tree shaking upgrade
Quantum now evaluates process.env.NODE_ENV
if statements! And removes unused files!

Various contributing
Thanks a million for everyone who contributed to this awesome release.
You can find closed issue in the milestone
Source code(tar.gz)
Source code(zip)