Hi everyone,
I'm working on prototyping a new platform utilizing the subject
technologies (ng 1.4, ngNewRouter and Webpack).
Here is a high level intent of the goals:
We have two entry points: Dashboard and Admin
I have my entry in my webpack.config.js as such:
entry: {
app: ['webpack/hot/dev-server', './app/app.js'],
dashboard: './app/components/dashboard/dashboard.js',
admin: './app/components/admin/admin.js',
vendors: ['angular', 'ngNewRouter']
}
My (abbreviated) file structure is:
/app
app.js
../components
../admin
../admin.html
../admin.js
../dashboard
../dashboard.html
../dashboard.js
/build
index.html
app.bundle.js
dashboard.bundle.js
admin.bundle.js
vendor.js
../components
../admin
../admin.html
../dashboard
../dashboard.html
When the webpack is rebuilt, there is a bundle file for the two entry
points, and I copy the html files from their components directory to the
build directory in the same location.
Now, when I load up the page, the controllers are loading properly using
the new $router, and the html files are being found in their correct
(build/) locations. The problem is, for some reason, nothing wants to be
injected into my <ng-viewport></ng-viewport>. The rendered HTML ends up
looking like:
<!-- ngViewport: undefined -->
Does anyone have any idea what may be causing this to happen...even though
the controller is loaded with the correct names (AdminController &
DashboardController) and the html files are found in their correct spot
with the correct names?
Thanks!
-Jason
--
You received this message because you are subscribed to the Google Groups
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.
