-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Continuing support for this project? #1684
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
Comments
This repo may not continue. if so, it should be called angular4-webpack-starter... |
It should be called angular-webpack-starter |
I am looking to fork/maintain this repo, but haven't quite gotten a response. I've posted my concerns and updates I've done to the stack over here awhile back: |
@admosity, yours was one of the comments which inspired this issue :) |
@AngularClass are busy making classes.. for angular |
I will update this repo this weekend |
I'm redoing everything and changing the repo name |
Thank you for the issue. Please follow issue #1686 for updates |
I see this question being asked in the comments of a few other issues, so perhaps it's useful to track it separately.
What is the status of this project? Are there plans to continue supporting it? There are quite a few PRs and issues which are not receiving attention and it seems like the project is falling behind. Is there intention to maintain this more actively in the future?
The work done here has been immensely valuable to us, and it is greatly appreciated, but it would be helpful to know where it's headed. I have a build system and a few projects based off of this. As Angular and Webpack quickly move forward, I think a lot of people in the same boat are getting to the point where we need to decide to continue using and contributing to this project or move to something more active.
Any feedback you could provide to help us understand the future state of things would be appreciated.
The text was updated successfully, but these errors were encountered: