One core difference that annoyed me in early use was figuring out that a define might never be called. As long as there is only one define per file, it will register that module as available under that filename. However, define modules are only loaded once a require function asks for each of them. Define: … Read more
Answered by James Burke on RequireJS Github Issue’s page: Issue #447: Multiple Base URLs ยท jrburke/requirejs. Turns out to be quite simple if data-main is the only entry point to your scripts(comments for more info), I solved my particular problem with the following: My app’s index.html: <script src=”http://framework.jpillora.com/js/lib/require.js” data-main=”http://framework.jpillora.com/js/framework” > </script> has the requirejs entry … Read more
I was just looking for this myself, the require global has a “defined” method on it which takes a module name and returns true or false. // returns true require.defined(“my/awesome/defined/module”); // returns false require.defined(“not/yet/loaded”);
An AMD optimiser has the scope to optimise more than the number of files to be downloaded, it can also optimise the number of modules loaded in memory. For example, if you have 10 modules and can optimise them to 1 file, then you have saved yourself 9 downloads. If Page1 uses all 10 modules … Read more
The reason your test isn’t running is because src/utils.js is not a valid Node.js library. According to the RequireJS documentation, in order to co-exist with Node.js and the CommonJS require standard, you need to add a bit of boilerplate to the top of your src/utils.js file so RequireJS’s define function is loaded. However, since RequireJS … Read more
This is what the requirejs documentation says on the topic of named modules: These are normally generated by the optimization tool. You can explicitly name modules yourself, but it makes the modules less portable — if you move the file to another directory you will need to change the name. It is normally best to … Read more
You can do this at the top of your file (instead of import): /// <amd-dependency path=”just/referencingthis/forpackaging” />
Here your TypeScript has compiled happily, to code that will work in a requireJS environment (technically, an AMD environment). That means it generates output that assumes that define/require etc all already exist. The overall answer is that you need to include RequireJS before you depend on your compiled code. Notably the error suggests you’ve made … Read more
jQuery 1.7 registers itself as an AMD module by the name of ‘jquery’, so you need to create a mapping for ‘jquery’ using the paths config: requirejs.config({ paths: { ‘jquery’ : ‘https://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min’ } }); require([‘jquery’], function($) { //$ points to jQuery }); Note however that RequireJS loads modules asynchronously and out of order, so if … Read more
According to the docs that error is thrown if “Script was part of a shim config that specified a global string property that can be checked for loading, and that check failed.” To fix this you need to add exports value in the shim config so that RequireJS can check whether the script was succesfully … Read more