New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explain the webpack setup #31
Comments
I'm using |
I removed everything except angular2/angular2
|
I nonetheless do not understand the reason you are including angular2/angular2. Your entry point is your app script. It imports angular2/angular2 using import statement. Unless I am missing something, if you are including angular2/angular2 this way, your script does not even pick it up, i.e. dead weight.
|
When webpack generates the file it chunks modules together so I'm forcing Angular to remain in one file for the browser to cache. |
Thats because you are using the plugin. This kinda defeats the purpose of the latter plugin, esp. on a small app.
|
In the webpack.config.js you have "angular2" entry.
I do not understand whats the purpose of bundling together the following dependencies:
into a separate script, if you require these using ES6 imports in the script itself, when you use them, e.g. https://github.com/angular-class/angular2-webpack-starter/blob/master/src/app/bootstrap.ts#L4. The end result is that you have multiple declarations of "angular2/*" and those declared as the "angular2" webpack entry are never used.
What are you using './src/common/BrowserDomAdapter' for?
The text was updated successfully, but these errors were encountered: