1.11.5

This is a patch release, fixing an issue where stealTools.export()ed modules were throwing when run within Node.js

1.11.4

This patch release fixes an issue with the special //!steal-remove-{start|end} comments.

If there was a space after the ! the code would not be removed, e.g:

//! steal-remove-start
doOnlyDuringDevelopmentStuff()
//! steal-remove-end

It should work now.

🎉

1.11.2

This path release fixes a couple of issues:

a) modules having incorrectly normalized dependencies due to the usage of a single normalizeMap reference for all bundles introduced in steal-tools1.11.1 #939

b) the BuildOptions page on the steal-tools documentation, used stealTools.build in the usage section of target when the option is only available for stealTools.optimize. #941

🐛 🐛 🐦

1.11.1

This patch release fixes a couple of issues with the slim loader:

a) Plugins (like steal-css) were only used on statically imported modules; dynamically loaded modules might need plugins to be loaded first, too. #934

b) Shared bundles were only loaded for entry point bundles, but some dynamically loaded bundles might also need shared bundles to be loaded first. #936

💥 🚀

1.11.0

Allow plugins to force inclusion of the slim dynamic loader

steal-tools analyses the dependency graph and makes it so the slim loader is able to progressively load bundle when it detects there are multiple bundles written out.

It is possible that even with a single bundle, during runtime modules like done-autorender try to (dynamically) load modules in the main bundle.

This feature release allows plugin to set up a flag and "force" the dynamic loading features on the slim loader.

1.10.2

This fixes a problem with optimized builds when user code dynamically loads a module bundled in the main bundle.

The slim loader will now flag the main bundle as already loaded, e.g:

var loadedBundles = { 6: LOADED };

The loader checks loadedBundles before trying to append a script tag when loading bundles in the browser, flagging the main bundle as loaded prevents the loader to throw.

1.10.1

This fixes a problem with using live-reload in Chrome 63. Chrome 63 doesn't close websocket's socket correctly, causing a socket error on the server. This change makes it so that we handle that situation cleanly.

Pull Requests

• #913 Handle errors from uncleaned disconnected connections

1.10.0

This is a minor release, now making it so that development code is not removed from dev bundles.

Previously code like:

//!steal-remove-start
console.warn("This is a dev warning!");
//!steal-remove-end

Would be removed in dev bundles. In production builds this is what you want, but in development bundles you want the same experience as developing with just the raw source code.

1.9.3

This patch release pins down prettier to 1.8.2; 1.9.0 shipped with a bug that breaks stealTools.build

1.9.2

This release removes the guides from this repository, moving them to stealjs/stealjs instead.