library dependencies not resolved when loading about angular-umd-dynamic-example

[lorenjerickson]

Update on this. I realized belatedly that just moving where the UMD bundles are physically located relative to the parent app doesn't change the fact that they're still loaded over http. So i get the same result (above) whether the modules live under the parent app's filesystem or if they're hosted somewhere else. So my issue is starting to sound more like #9.

The only think I can tell that is different about how I approached this is that my module library was not built with --prod because that option is not valid for library projects, only for application projects. Or more precisely, when that flag is passed the compiler looks for the standard environment config files which don't exist for a library project. What am I missing?

[foxtrot]

Hi,

I came across the same issue playing with this - My solution was to import the Angular module I needed in my library's module.ts as usual:

import {FormsModule} from '@angular/forms';

Doing just this will result in the 404 you mention, you must also add it to the Module loader service (module.service.ts):

import * as AngularRouter from '@angular/router';
import * as AngularForms from '@angular/forms';

...

        SystemJS.set('@angular/router', SystemJS.newModule(AngularRouter));
        SystemJS.set('@angular/forms', SystemJS.newModule(AngularForms));

Hope this helps you.