What's the importance of script loaders like RequireJS etc if we are anyway minifying and concatenating JS files in production?

In other words, do you care about script loaders? Are they useful?

With HTTP2 they might be more useful - with HTTP2 you can keep them as separate files instead of concatenating them into one giant JS file, you can load only the files you need to load and speed up startup time. With HTTP2 you will have a single connection through which everything is loaded instead of opening many connections to load files.

Yes we like script loaders, wether we are bundling or not. They help us to keep our projects neat and organised for one thing, and force us to be modular with componenet scripting, they also help us to keep things correctly/safely scoped, out of the box.

Care to elaborate on that? Do you use script loaders in production as well?

Hi Mark, I personally like require.js, and yes we bundle this with R.js through gulp in production code, using configs that can help us to manually make exclusions from the bundling. For instance; if we only have an 'accordion' section on a single page in the site, we would load that in when we detect it is needed (perhaps when we detect a certain dom object) - but if we had an accordion on each page of the site it makes sense for the accordion js file to be bundeled.

Thread

What's the importance of script loaders like RequireJS etc if we are anyway minifying and concatenating JS files in production?

Responses(2)

Recent threads

Search Hashnode

What's the importance of script loaders like RequireJS etc if we are anyway minifying and concatenating JS files in production?

Responses(2)

Recent threads