Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Breaking changes planned after the 1.0 release? #336
our team started 4 weeks ago working on a new reactjs application based on your starterkit and we really appreciate the work you've done to make our lifes easier.
What is your plan after the 1.0 release regarding breaking changes for existing applications?
Thanks for your feedback.
@GerritWanderer so that's an interesting question, and as much as I love semver I'm not sure what
Right this moment I don't have any major plans beyond project cleanup and finding a fix for the vendor hash (which seems to be a general webpack problem, not something unique to this project). Probably when Webpack 2 drops we'll try to switch to that, but I have absolutely no idea what the ETA is on that. The most important thing right now is just maintaining dependencies.
So, per your question, I've had a few ideas but nothing great to be honest. The point of the project is to give you a starting-off point rather than a long-lived framework since teams are very likely to make changes to the build process. One idea I've had is to create a system that will automatically pull in the latest build-specific code (
Since I'm clearly not much help on this, I'd like to pose the question back to you: what could we do to make your life easier? How is the configuration working out for you? What common problems do you encounter? The more perspectives we get into the design of this project the better it will be and, hopefully, easier it will be for teams such as yours to keep it up to date.
That’s what I’ve been doing, personally. Although I do pull to a branch initially and only merge back to my own master when it’s working.
On 22 Dec 2015, at 19:43, Alex Bachuk firstname.lastname@example.org wrote: