Update steal to the latest version 🚀 #18
Conversation
Version 1.3.1 just got published. |
Version 1.3.2 just got published. |
Version 1.4.0 just got published. |
Version 1.4.1 just got published.Update to this version instead 🚀 Release Notes1.4.11.4.1 contains a couple of bug fixes. BugsCommitsThe new version differs by 5 commits .
See the full diff. |
Version 1.4.2 just got published.Update to this version instead 🚀 CommitsThe new version differs by 37 commits .
There are 37 commits in total. See the full diff. |
Version 1.4.6 just got published.Update to this version instead 🚀 CommitsThe new version differs by 17 commits .
There are 17 commits in total. See the full diff. |
Version 1.5.0 just got published.Update to this version instead 🚀 Release Notes1.5.0This is a minor release of steal that adds the new FeatureshomeAliasSteal 1.0 added the tilde operator that allows you to reference your project's root/home folder using the import "~/components/tabs"; The {
"steal": {
"homeAlias": "@"
}
}import "@/components/tabs"; The steal-sans-promisesNow that it is 2017 more and more browsers support In Steal 2.0 it is likely that no polyfill will be included (or might be included optionally), but in the meantime the steal-sans-promises.js and steal-sans-promises.production.js scripts have been added to steal. Use them in exactly the same manner that you use steal.js today: <script src="./node_modules/steal/steal-sans-promises.js"></script> Note that when building with steal-tools the steal.production.js script is copied into your dest folder. This is the normal version of steal which does include the Promise polyfill. There is an open issue to provide a way to use steal-sans-promises.production.js instead (and ditto for using bundleSteal). In the meantime you can use steal-sans-promises from node_modules like so: <script src="./node_modules/steal/steal-sans-promises.production.js" main="app/main"></script> IssuesCommitsThe new version differs by 11 commits0.
false See the full diff |
Version 1.5.1 just got published.Update to this version instead 🚀 Release Notes1.5.1This is a bug fix release that fixes an issue with Zombie 5.x. Zombie no longer supports the attribute.nodeName property. This release fixes this by using attribute.name instead. Fixed #1177 |
Version 1.5.2 just got published.Update to this version instead 🚀 Release Notesv1.5.2Improved progressive loading guide for #1188 CommitsThe new version differs by 5 commits0.
false See the full diff |
Version 1.5.3 just got published.Update to this version instead 🚀 Release Notes1.5.3This is a bug fix release, which fixes an issue when using live-reload with steal-clone. Also includes some minor documentation improvements to the Babel docs and progressive loading guide. IssuesCommitsThe new version differs by 29 commits.
There are 29 commits in total. See the full diff |
Version 1.5.4 just got published.Update to this version instead 🚀 Release Notes1.5.4This is a bug-fix release that fixes usage in IE9. Issues |
Version 1.5.5-pre.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 6 commits.
See the full diff |
Version 1.5.5 just got published.Update to this version instead 🚀 Release Notesv1.5.5Patches
|
Version 1.5.6 just got published.Update to this version instead 🚀 Release Notes1.5.6PatchesCommitsThe new version differs by 8 commits.
See the full diff |
Update to this version instead 🚀 Release Notes for 2.1.6This fixes a bug with using steal-clone in a tree-shaken context. |
Update to this version instead 🚀 Release Notes for 2.1.7Fixes a bug when treeshaking a large app with multiple bundles. |
Update to this version instead 🚀 Release Notes for 2.1.9This is a bug fix release, fixing an issue with tree-shaking modules with non-ES module parents. Issues |
Update to this version instead 🚀 Release Notes for 2.1.10This fixes a false positive JSON parse warning in production when a JSON module is loaded from another bundle. |
Update to this version instead 🚀 Release Notes for 2.1.12This is a patch release, which adds names to all of the extension functions to make them easier to debug. |
Update to this version instead 🚀 Release Notes for 2.1.13Fixes an issue where a module loading a dependency by its exact npm module name might load the wrong package version and error out. |
Update to this version instead 🚀 CommitsThe new version differs by 7 commits.
See the full diff |
Update to this version instead 🚀 Release Notes for Introduce forceES5 flag to skip ES2015 transpilation{
"steal": {
"forceES5": false // defaults to true
}
}when set to false, Steal.js does not include the ES2015 preset. This is useful when the target browser supports all of the syntax/features transpiled by the ES2015 preset. CommitsThe new version differs by 6 commits.
See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 5 commits.
See the full diff |
|
|
Version 1.3.0 of steal just got published.
The version 1.3.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of steal.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴