-
Notifications
You must be signed in to change notification settings - Fork 445
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
ATTN: Status of this seed #457
Comments
Wonderful! Thank you for the great work. Soon I'll be reaching you out to discuss some improvements I've made on modularization and theming, which I'm using (and reusing) with success on my projects. -- luiz |
Can we use the seed in production environment? Is there a list of known issues? Is it being updated Regularly? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Everyone who comes upon this seed please read this first:
This seed was originally developed for the following reasons:
The parent angular-seed is built off SystemJS. At the time of it's first conception a lot was evolving in modern JavaScript development. Most importantly angular-cli has come to fruition over this time period as well as the amazing progressions of webpack as a build tool.
This seed will always attempt to mirror all the latest changes from Minko's seed which is rooted in SystemJS which will always make this seed rooted in SystemJS for at least the web build side of things at the moment.
Free free to use the seed if it suits your needs and/or improve upon it in ways you believe should be. I continue to monitor pull requests however have not been able to respond to issues lately. At the moment I plan to take some time in late Fall 2017 to bring a number of things up to date with this seed with latest versions of Angular/NativeScript/Electron and apologize to anyone who relies on this seed for more support as I have been busy on other things.
In meantime, I would encourage those who come upon this seed to evaluate several things:
❤️
The text was updated successfully, but these errors were encountered: