Separating boilerplate from starter

[moltar]

trafficstars

I think having examples of how the TypeScript can be used (components and store) is great. But the problem comes when instantiating a new project - need to remove all the defaults.

I think it would be better to have a completely empty starter and then a separate repo with the example implementation.

What do you think?

[daveberning]

I'm hesitant to do this. I personally like to see something working as I start a new project; almost solidifying best practices of the template. Do you find that it's a lot to remove when starting a new project?

[moltar]

I'm hesitant to do this. I personally like to see something working as I start a new project;

Yup same.

Do you find that it's a lot to remove when starting a new project?

Yes, I do. There are many files scattered around in not obvious places. E.g. style sheets in assets, components, pages. Need to remember them all.

Maybe a solution could be to have a manifest of these files, and then have a removal npm script that uses rimraf (cross platform) to remove the files?

E.g. something like:

npm run remove-boilerplate