Aurelia Dynamic Compose + Webpack = Module ID Not Found

Last updated: April 7, 2017

If you’re using the latest and greatest Webpack plugin for Aurelia, there is a possibility if you use the <compose> element to dynamically render UI you will run into an issue where Webpack doesn’t know about the dynamic imports.

Specifically, I am talking about usage of <compose> that might look like the following:

<template>
    <compose view-model="./views/view-${viewTemplateName}"></compose>
</template>

This is due to the fact, they can’t be resolved beforehand and put into the bundle. Fortunately, there is an easy fix for all of this.

Newly introduced into the Webpack plugin, is support for PLATFORM.moduleName(file) which tells Webpack where to find files in Aurelia. We can use this to tell Webpack about our dynamic files.

At the top of each dynamic file, simply add the following:

import {PLATFORM} from "aurelia-framework";

PLATFORM.moduleName("./my-dynamic-view");

export class MyDynamicView {

}

Using moduleName helps Aurelia and Webpack see your dynamic files: that’s all you need to do.

Purchase Aurelia for Real World Applications over at Leanpub now

Liked it? Take a second to support Dwayne on Patreon!
 

Dwayne

 

2 thoughts on “Aurelia Dynamic Compose + Webpack = Module ID Not Found

Leave a Reply

Your email address will not be published. Required fields are marked *