stealjs / cache-bust

A cache busting extension for StealJS

StealJS

StealJS is an awesome front-end module loader that makes writing large applications easy. Learn more at stealjs.com.

This repository houses the source for the website.

Contributing

If you’d like to have your Steal plugin added under the Ecosystems section on the website, please add an issue and we can discuss it.

If you want to work on the website, first clone it:

git clone https://github.com/stealjs/stealjs.git

Then install the dependencies:

npm install

Then generate the documentation:

npm run document

License

Steal, StealTools, and all sub-projects are licensed under the MIT License.

cache-bust's Issues

wont work in production

as worte in http://forums.donejs.com/t/problems-getting-stealjs-cache-bust-to-work/514/4
steal-cache-bust can (today) not work in production.

in production steal-cache-bust is bundled into the index.js file and steal therefore cant be load the index.js file with the cache-bust extension because it dont know that cache-busting is enabled.

for any future files, steal will load these files with a version number

@matthewp
my thoughts:
either we integrate steal-cache-buster into core and enable it by setting the steal config
or
we add (in steal 1.0) the fetch hook into the steal.production.js that we copied into the dist folder and remove cache-buster from being bundled

update loader.env to use window-production

Newer versions of steal use window-production instead of production.

Default cache version enhancement

When obtaining the cache version:

var cacheVersion = loader.cacheVersion || Math.random();

That Math.random() will not be guaranteed to be unique. However, new Date().getTime() would do the trick.

Not a big deal though as typically one should specify the version.

Come to think of it... the cache busting should be applied when not in production as well. In a previous project we added the date to the urls for development builds to always force a reload. Would this perhaps be an option? So use the above suggestion when either no cache version is set or when not in production.

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

API

System.cacheVersion

This is the key that is changed (usually by your server-side scripting language) when you need to bust the cache.

System.cacheKey

If for some reason you want to configure what is used as the querystring key when fetching.

Questions

1. Should this be production only?
2. This will bust the cache for all modules, is there a better way to only bust it for files that have changed?