I would like to use lazy loading but I can not understand why it does not work, it gives me error "Cannot find module".
This is my environment:
- Angular 5.2.1
- .NET Core 2
- Webpack 3.10.0
- angular-router-loader 0.8.2
- @angular/cli 1.6.5
I tried different path in loadChildren always without success, i also temporarily disabled all the guards and the children routing. What did I do wrong?
FOLDERS
ClientApp
app
components
users
users-routing.module.ts
users.module.ts
app-routing.module.ts
app.module.shared.ts
app-routing.module.ts
const appRoutes: Routes = [
{
path: 'users',
loadChildren: './components/users/users.module#UsersModule'/* ,
canLoad: [AuthGuard] */
},
{
path: '',
redirectTo: '/login',
pathMatch: 'full'
},
{
path: '**',
redirectTo: '/login'
}
];
@NgModule({
imports: [
RouterModule.forRoot(
appRoutes,
{ enableTracing: false }
)
],
exports: [
RouterModule
],
providers: [
CanDeactivateGuard
]
})
export class AppRoutingModule { }
users-routing.module.ts
const usersRoutes: Routes = [
{
path: '',
component: UsersComponent/* ,
//canActivate: [AuthGuard],
children: [
{
path: 'detail',
canActivateChild: [AuthGuard],
children: [
{
path: ':id',
component: UserViewComponent
},
{
path: 'edit/:id',
component: UserFormComponent,
canDeactivate: [CanDeactivateGuard],
resolve: {
user: UsersResolver
}
},
{
path: '',
component: UserFormComponent,
canDeactivate: [CanDeactivateGuard]
}
]
},
{
path: '',
component: UsersListComponent
}
] */
}
];
@NgModule({
imports: [
RouterModule.forChild(
usersRoutes
)
],
exports: [
RouterModule
]
})
export class UsersRoutingModule { }
users.module.ts
@NgModule({
imports: [
CommonModule,
FormsModule,
UsersRoutingModule,
RouterModule
],
declarations: [
UsersComponent,
UserFormComponent,
UsersListComponent,
UserViewComponent
],
providers: [
UsersResolver,
RouterModule
]
})
export class UsersModule { }
webpack.config.js
const path = require('path');
const webpack = require('webpack');
const merge = require('webpack-merge');
const AngularCompilerPlugin = require('@ngtools/webpack').AngularCompilerPlugin;
const CheckerPlugin = require('awesome-typescript-loader').CheckerPlugin;
module.exports = (env) => {
// Configuration in common to both client-side and server-side bundles
const isDevBuild = !(env && env.prod);
const sharedConfig = {
stats: {
modules: false
},
context: __dirname,
resolve: {
extensions: ['.js', '.ts']
},
output: {
filename: '[name].js',
publicPath: 'dist/' // Webpack dev middleware, if enabled, handles requests for this URL prefix
},
module: {
rules: [{
test: /\.ts$/,
include: /ClientApp/,
use: isDevBuild ? ['awesome-typescript-loader?silent=true', 'angular2-template-loader'] : '@ngtools/webpack'
},
{
test: /\.html$/,
use: 'html-loader?minimize=false'
},
{
test: /\.css$/,
use: ['to-string-loader', isDevBuild ? 'css-loader' : 'css-loader?minimize']
},
{
test: /\.(png|jpg|jpeg|gif|svg)$/,
use: 'url-loader?limit=25000'
}
],
loaders: [
{
test: /\.ts$/,
loaders: [
'awesome-typescript-loader'
]
},
{
test: /\.(ts|js)$/,
loaders: [
'angular-router-loader'
]
}
]
},
plugins: [new CheckerPlugin()]
};
// Configuration for client-side bundle suitable for running in browsers
const clientBundleOutputDir = './wwwroot/dist';
const clientBundleConfig = merge(sharedConfig, {
entry: {
'main-client': './ClientApp/boot.browser.ts'
},
output: {
path: path.join(__dirname, clientBundleOutputDir)
},
plugins: [
new webpack.DllReferencePlugin({
context: __dirname,
manifest: require('./wwwroot/dist/vendor-manifest.json')
})
].concat(isDevBuild ? [
// Plugins that apply in development builds only
new webpack.SourceMapDevToolPlugin({
filename: '[file].map', // Remove this line if you prefer inline source maps
moduleFilenameTemplate: path.relative(clientBundleOutputDir, '[resourcePath]') // Point sourcemap entries to the original file locations on disk
})
] : [
// Plugins that apply in production builds only
new webpack.optimize.UglifyJsPlugin(),
new AngularCompilerPlugin({
tsConfigPath: './tsconfig.json',
entryModule: path.join(__dirname, 'ClientApp/app/app.module.browser#AppModule'),
exclude: ['./**/*.server.ts']
})
])
});
// Configuration for server-side (prerendering) bundle suitable for running in Node
const serverBundleConfig = merge(sharedConfig, {
resolve: {
mainFields: ['main']
},
entry: {
'main-server': './ClientApp/boot.server.ts'
},
plugins: [
new webpack.DllReferencePlugin({
context: __dirname,
manifest: require('./ClientApp/dist/vendor-manifest.json'),
sourceType: 'commonjs2',
name: './vendor'
})
].concat(isDevBuild ? [] : [
// Plugins that apply in production builds only
new AngularCompilerPlugin({
tsConfigPath: './tsconfig.json',
entryModule: path.join(__dirname, 'ClientApp/app/app.module.server#AppModule'),
exclude: ['./**/*.browser.ts']
})
]),
output: {
libraryTarget: 'commonjs',
path: path.join(__dirname, './ClientApp/dist')
},
target: 'node',
devtool: 'inline-source-map'
});
return [clientBundleConfig, serverBundleConfig];
};
tsconfig.json
{
"compilerOptions": {
"module": "es2015",
"moduleResolution": "node",
"target": "es5",
"sourceMap": true,
"experimentalDecorators": true,
"emitDecoratorMetadata": true,
"skipDefaultLibCheck": true,
"skipLibCheck": true, // Workaround for https://github.com/angular/angular/issues/17863. Remove this if you upgrade to a fixed version of Angular.
"strict": true,
"lib": [ "es6", "dom" ],
"types": [ "webpack-env" ],
"typeRoots": [
"node_modules/@types"
]
},
"exclude": [ "bin", "node_modules" ],
"atom": { "rewriteTsconfig": false }
}
ERROR MESSAGE
Unhandled Promise rejection: Cannot find module './ClientApp/app/components/users/users.module'. ; Zone: angular ; Task: Promise.then ; Value: Error: Cannot find module './ClientApp/app/components/users/users.module'. at vendor.js?v=AdjSBPSITyauSY4VQBBoZmJ6NdWqor7MEuHgdi2Dgko:34015 at ZoneDelegate.invoke (vendor.js?v=AdjSBPSITyauSY4VQBBoZmJ6NdWqor7MEuHgdi2Dgko:117428) at Object.onInvoke (vendor.js?v=AdjSBPSITyauSY4VQBBoZmJ6NdWqor7MEuHgdi2Dgko:5604) at ZoneDelegate.invoke (vendor.js?v=AdjSBPSITyauSY4VQBBoZmJ6NdWqor7MEuHgdi2Dgko:117427) at Zone.run (vendor.js?v=AdjSBPSITyauSY4VQBBoZmJ6NdWqor7MEuHgdi2Dgko:117178) at vendor.js?v=AdjSBPSITyauSY4VQBBoZmJ6NdWqor7MEuHgdi2Dgko:117898 at ZoneDelegate.invokeTask (vendor.js?v=AdjSBPSITyauSY4VQBBoZmJ6NdWqor7MEuHgdi2Dgko:117461) at Object.onInvokeTask (vendor.js?v=AdjSBPSITyauSY4VQBBoZmJ6NdWqor7MEuHgdi2Dgko:5595) at ZoneDelegate.invokeTask (vendor.js?v=AdjSBPSITyauSY4VQBBoZmJ6NdWqor7MEuHgdi2Dgko:117460) at Zone.runTask (vendor.js?v=AdjSBPSITyauSY4VQBBoZmJ6NdWqor7MEuHgdi2Dgko:117228) Error: Cannot find module './ClientApp/app/components/users/users.module'. at http://localhost:5000/dist/vendor.js?v=AdjSBPSITyauSY4VQBBoZmJ6NdWqor7MEuHgdi2Dgko:34015:9 ... [truncated]
EDIT
link to stackblitz for testing
In root module's route configuration, use loadChildren with a relative path to the lazy loaded angular module. The string is delimited with a # where the right side of split is the lazy loaded module's class name. I have added ./ as prefix to the loadChildren string.
It is true? Some developers suggest to use loadChildren: () => PromotionsModule. But apparently this is not a solution and it is only a dirty workaround. Additionally, it will cause proud build fail. According to #10981, it seems like there is a bug when using Angular Lazy Load Module.
A common error when lazy-loading modules is importing common modules in multiple places within an application. Test for this condition by first generating the module using the Angular CLI and including the --route route-name parameter, where route-name is the name of your module.
In situations where you wish to load a module conditionally or on demand, you can use a dynamic import instead. It is the primary tool which is also a basic building block for all the angular applications. You need to run the following command to install the latest version of Angular CLI:
I have found two solutions (via the OP by edit):
Reference to the module, after it has already been resolved with an import statement:
import { UsersModule } from './components/users/users.module';
then referencing this way:
{
path: 'users',
loadChildren: () => UsersModule,
canLoad: [AuthGuard]
}
I have added ng-router-loader
to the application (npm install ng-router-loader --save-dev
) and I set up Webpack like this:
rules: [{
test: /\.ts$/,
include: /ClientApp/,
//use: isDevBuild ? ['awesome-typescript-loader?silent=true', 'angular2-template-loader'] : '@ngtools/webpack'
use: isDevBuild ? [{ loader: 'ng-router-loader' }, 'awesome-typescript-loader?silent=true', 'angular2-template-loader'] : '@ngtools/webpack'
},
{
test: /\.html$/,
use: 'html-loader?minimize=false'
},
{
test: /\.css$/,
use: ['to-string-loader', isDevBuild ? 'css-loader' : 'css-loader?minimize']
},
{
test: /\.(png|jpg|jpeg|gif|svg)$/,
use: 'url-loader?limit=25000'
}
],
then referencing the module by path:
{
path: 'users',
loadChildren: './components/users/users.module#UsersModule',
canLoad: [AuthGuard]
}
Supposing this is AppModule that handles lazyloading and the features of your system are of the same tree as it is:
routes: Routes = [
{
path: 'files-pannel',
loadChildren: () => import('./module-folder/module-name.module').then(m => m.ModuleName)
}
];
You can use like this:
const rootRoutes: Routes = [
{ path: 'your-path', loadChildren: () => UsersModule }
];
The currently accepted answer, which proposes to exchange the value of loadChildren from a string to a function, removes the possibility of AOT compilation when doing a production build.
What worked for me, was 1) use absolute paths 2) Add the lazy loaded modules as a string array in angular.json under projects > 'projectname' > architect > build > options > lazyModules. The paths should be the same as defined under loadChildren.
So, in your case, I think this should work in your routing module:
loadChildren: 'app/components/users/users.module#UsersModule'
And in angular.json, add this at the location specified above:
lazyModules: ["app/components/users/users.module"]
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With