The kickass in-browser assets (JS/CSS/Text) loader with the support of localStorage caching and progress tracking. The Loada is here to give you control over assets loading order, parallelism, cache expiration and actual code evaluation.
Use it to:
The Loada is available through Bower as
If you are in the Ruby environment with
sprockets around – use
gem 'loada' and
#= require 'loada'.
Alternatively you can download minified version. But you should not. Seriously. Use package managers. Please.
The Loada splits your dependencies into sets. Each set is an instance of The Loada. Each set is an atomic cache part: if the number of cached assets changes – unused caches get busted on the next run keeping your localStorage space usage low. You can i.e. have main set, the core of application, and templates that will be treated and cached separately.
Create a set to start:
loader = Loadaset'dependencies' # name of the set defaults to `*` if omitted.
To load an asset with the default options run
loaderrequire url: '/assets/application.css'
To load several assets one after another (they depend on each other?) run
loaderrequire url: '/assets/jquery.js'url: '/assets/application.js'
And to load an external library that shouldn't be cached at localStorage (but has to be kept at the browser cache) run
loaderrequire url: ''localStorage: false
According to our requires, the assets will be loaded in the following groups (:
And now that we have our dependencies specified, load'em!
loaderload# During downloading you will get this callback called from time to time: # ...# And this one will run as soon as all assets are around: -> # ...
The Loada will try to make progress ticks as often as possible. There are some things you should keep in mind to sort it out though:
sizeto the asset options to specify download size. This is the most efficient scenario so if you have a chance to count size programmatically – do that.
HEADquery for every asset with unknown size expecting server to return
So in the worst case when The Loada was not able to find sizes from any source, you will get percentage split to the number of loading assets. In the best case, when all sizes are known, ticks will happen every 100ms and will be pretty detailed.
Important note: The Loada WILL NOT make separate
HEAD queries unless you pass
progress callback. So if you don't need the progress tracking feature – you are not hitting the overhead. In the case when you passed
progress in and still want to avoid
HEAD queries (resulting into "per-library" percentage), pass
0 as the
size value to every asset.
set = Loadaset 'name'prefix: 'foobar'localStorage: false
Important note: The Loada is only able to work with JS when localStorage mode is disabled.
setrequireurl: '/assets/application.js'key: 'app'type: 'js'revision: 1expires: 5cache: truerequire: truesize: 0
text(The Loada tries to parse URL to get extension if omitted)
falsein to turn localStorage caching off for this particular asset
Gets raw asset source by its key
source = setget 'app'
Manually triggers expiration check for current storage
Busts all cache of the current set
Loada is an extraction from Joosy core.
It is free software, and may be redistributed under the terms of MIT license.