Illuminated Chair

Implement source switch for SPA

Asynchronous loading of JS and CSS depending on the environment

A while ago I wrote a Single Page Application (SPA) with jQuery and and decided to use some useful plugins to avoid reinventing the wheel. To keep the delivered sources small, I used the bundler Gulp, to pack all JS plugins in a single file and another one for my custom JS code. I used the same procedure with the CSS files.

The SPA contained only a single HTML file in which all bundeled sources and needed HTML template blocks were included, in order to load most of the stuff while starting the app, when the users sees a GMail-like loading screen.

But the whole thing had one disadvantage: Debugging for example in Chrome Dev Tool is not a joy, if the code is packed with Gulp Concat and Gulp Uglify. It would be much more convenient, if the source loading can be done depending on the environment.

First step was to replace the SCRIPT and LINK tags in die index.html with a dynamic loading approach using JavaScript.

Dynamic JS loading

For some custom code it was necessary to load the plugins previously, because of dependencies.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
function addScriptAsync(url) {
return new Promise(function(resolve, reject) {

var script = document.createElement("script");
script.type = "text/javascript";
script.src = url;

script.addEventListener("load", function() {
resolve(script);
}, false);

script.addEventListener("error", function() {
reject(script);
}, false);

document.getElementsByTagName('head')[0].appendChild(script);
});
}

By returning a Promise, the calling code is able to wait for a dependent source to load:

1
2
3
addScriptAsync("Build/vendor.min.js").then(function() {
addScriptAsync("Build/custom.min.js");
});

Dynamic CSS loading

Loading CSS is pretty straightforward and includes an id as parameter, in order to be able to access the style afterwards, for example when tehh user is chanhing the SPA’s theme:

1
2
3
4
5
6
7
8
9
10
function addStylesheet(url, id) {

var stylesheet = document.createElement('link');
stylesheet.rel = 'stylesheet';
stylesheet.type = 'text/css';
stylesheet.href = url;

if (id) { stylesheet.setAttribute("id", id); }
document.getElementsByTagName('head')[0].appendChild(stylesheet);
}
1
2
addStylesheet("Build/vendor.css");
addStylesheet("Build/custom.css");

Consider the environment

Now everything was set up to implement a switch, depending on whether the SPA was started locally or in production.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
var _DEV = (window.location.hostname.indexOf("localhost") !== -1);

addStylesheet("Build/vendor.css");
if (_DEV) {
addStylesheet("Libraries/styles.css");
addStylesheet("Libraries/helpers.css");
...
} else {
addStylesheet("Build/custom.css");
}

addScriptAsync("Build/vendor.min.js").then(function() {
if (_DEV) {
addScriptAsync("Libraries/prototypes.js")
.then(function() { return addScriptAsync("Libraries/tools.js"); })
.then(function() { return addScriptAsync("Libraries/app.js"); })
...
} else {
return addScriptAsync("Build/custom.min.js");
}
})

You can interact with this article (applause, criticism, whatever) by mention it in one of your posts, which will be shown here as a Webmention ... or you leave a good old comment with your GitHub account.

In case your blog software can't send Webmentions, you can use this form:

Webmentions

No Webmentions yet...

Comments

Related