-
Notifications
You must be signed in to change notification settings - Fork 18
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
Are you using angular-webpack-starter? Please comment here! #15
Comments
I use it for an internal big projet, mostly because it's an aot-ready starter; i added some loaders & rules (sass, pug, json, txt) and removed dashboard that had memory leaks... thank you 😍 |
I am using this and it was a great help to get all this built out. The one issue/complaint I have though is that when I do npm start sometimes node crashes but I get no indication of the issue. I have to do a clean and build:dll and sometimes that fixes it and sometimes it does not. I basically just have to play around to get npm start to launch things again. It is pretty frustrating. Seems to happen most when you add/remove a package or change your components structure around. |
@antonybudianto7 just came across this wonderful project from angular2 starter page. You rock!! I have three questions: 1) How is this project different than angular2 starter? What I understood is angular2 starter uses gulp as oppose to this one does webpack + ang cli compilation. Any other difference? Which one you recommend? 2) I setup and compiled project fine but unable to browse site. It didn't launch and get 404 on localhost:8080. Any ideas? 3) I dont know how but this link also came up https://github.com/AngularClass/angular2-webpack-starter. Is this same project or you involved? Thank you so much. |
@ManishJainGitHubUser
|
@GenZodd , sorry for late reply. |
Hi everyone ✋
I would like to know who are using angular-webpack-starter and how you use it.
It'd be great if you can post your project/company logo too
Please share your experiences below!
Thank you ❤️
The text was updated successfully, but these errors were encountered: