RequireJs makes dependency management on the client mostly better. Once it’s setup, it’s nice. Getting the patterns of your paths to work correctly can be difficult to setup, depending on the constraints of your system. Making the same paths work in a prod, test, and build environment can be even more adventuresome. In my case, there were a few extra hoops. My scenario might not fully match yours, but perhaps you can apply this solution to your own needs.
Prod: Loading Modules From a Different Server
Recently, we built a portal. It contains a bunch of widgets that are served from domains different from the host page. The portal requested these widget js files via RequireJs.
Because the widgets live on other domains, those widgets’ subdependencies needed a path that would be relative to that other widget domain and not the portal domain. In order to accomplish this, widget dependencies were specified in this way:
1 2 3
.js extension tells RequireJs to load the dependency as a URL. The
./ makes the URL relative to the widget domain.
Test: RequireJs Paths in Testacular
When you go to test your modules in a test environment, you may not want to load your modules as URLs. Such was the case for me, running Testacular, where the source code is requested into the context of the test server already.
In prod, I needed the
.js extension. But, in test I didn’t want to load modules from URLs. So, I need to make the test environment ignore the extension. The solution? Override the regular expression that checks for the extension in my test runner to be something that was never matched:
This allows RequireJs to load the module by module name.
RequireJs Adds Double .js Extension
It’s getting better in the test environment, but we still haven’t totally appeased RequireJs. It turns out that when it loads a module by name, it still has to convert that name to a path.
Given my constraints (widgets from another domain on a portal), my name actually includes a
.js extension. This isn’t usually the case. RequireJs doesn’t test for this again (remember, we overrode the regex that did), so it just adds a
.js extension on the end, creating two:
But there is one final way to trick it out: Add a ‘?’ to the name. This rule was meant to apply to URLs that represented dynamic scripts (and would thus take query strings) as opposed to static js files. That’s not why we’ll add it, but it will help us nonetheless.
So now your module dependencies will look like this:
1 2 3
And in your test environment they will load, and you will be happy. Until…
Build: Module Names for Optimization
When you go to optimize your RequireJs modules you’ll again need RequireJs to load your modules by module name instead of url. If you don’t, you’ll get nice messages like:
1 2 3 4 5 6
You may cry a little, but we’re almost there. Remember, your module dependency paths worked just fine in prod. You only changed them to accommodate the test environment. So, it’s time to change them back when you optimize your module into one file for production use.
r.js configuration in
app.build.js includes an function called
onBuildRead()’. Call it to transform the code as it goes out the door for optimization. We want to strip out the ‘?’ question marks from our dependency arrays. Stripping out all ‘?’s might be a bit too dangerous. So, let’s make a benign adjustment that will help us identify exactly what we’re trying to strip out and replace our ‘?’ string in our dependency paths with ‘?test’, finally:
1 2 3
1 2 3
“Shut off all the garbage smashers on the detention level!”
Take a deep breath. That was a little much to make all that work. You have made your RequireJs paths happy in 3 contexts:
- In production, where modules are served from domains different from the host page and must be loaded by URL.
- In test, where your modules must be loaded by module name.
- In the optimization build, where modules must be loaded by module name.
I fill like I’ve tricked out RequireJs a bit to make this work. How could we adjust the solution to be more straightforward?