Updating to latest version of starter

[isaacplmann]

• I'm submitting a ... [ ] bug report [ ] feature request [x] question about the decisions made in the repository

What is the workflow for getting the latest build configuration from the starter and applying it over the top of a library that's using an older version of the starter?

If there's an easy process for doing that, I'm all in on this starter.

[shlomiassaf]

Generally speaking, this starter does not change much.

But, since there is a big difference between the 2 operations (building an app vs library) there are some changes.

Mainly, the application is not in the root of src but in src/demo, this requires some changes, though minimal.

Unit testing, e2e, etc left untouched.

The best approach is to compare and use some GUI tool to assign changes.

That said, there is no common history between 2 repos, this means that while most changes will be quick and easy, changes in the application (demo) will require more work since the paths are not aligned.

I just compared the config folder between the two, the changes are minimal, most of them are just the change of the app from src to src/demo.

[isaacplmann]

Sorry, I don't think I explained myself well. Let's say these things happen:

1. I start using angular-library-starter to develop my-awesome-library.
2. At some point later angular-library-starter adds a super awesome feature that I want to use in my library

Is there an easy way to update my-awesome-library to the latest version of angular-library-starter without over-writing my own code? Do I need to manually copy and paste all the changes over?

[joshwiens]

@isaacplmann - Something that may be useful here. In @webpack-contrib we created https://github.com/webpack-contrib/webpack-defaults to maintain our boilerplate. The same approach could be applied here to handle managing all the boilerplate.

We update defaults as needed & then run npm run wepback-defaults to update all of our loaders & plugins.