Too many templates generate confusion

[bluesurfer]

I am relatively new to Vue and the npm world. I have played with Vue for a while and fell in love with it. Now, I want to make the next step: starting a medium-to-large scale project (meaning that I have to communicate with an API backend).

I read the docs section about starting a new project and I reach this repository. I begin looking at the four template and choose the webpackone, then I discover that it is not very maintained (packages outdated) and got disappointed. After that I take a look at other templates on Github:

• Vuepack
• vue.js-starter-template

Now I discover vuex and found this other project structure which is said to be best suited for large project (wasn't it also the webpack one best suited?). It becomes all quite confusing. There are too many ways to start a project and each one claims to be the best.

It would be great if there exists one, well maintained and officially recognized project structure.

[egoist]

What else disappointed you besides the outdated webpack dependencies in the webpack template? (technically webpack 1 is not outdated and not everyone likes webpack 2 for now)

Now I discover vuex and found this other project structure which is said to be best suited for large project (wasn't it also the webpack one best suited?). It becomes all quite confusing. There are too many ways to start a project and each one claims to be the best. ... There are too many ways to start a project and each one claims to be the best.

After a little research, I found none of these templates and examples are said to be the best one by themselves, can you point it out?

[yyx990803]

What makes you think the official webpack template is not well maintained? If there are specific problem you ran into, please open issue in the template's own repo. It is intended to be the one, well maintained and officially recognized template. However, the templates are focused on build toolchains, not project structure - i.e. it doesn't mandate how you structure your source code, so it's orthogonal to what Vuex outlined in its docs. We intentionally stayed away from an overly opinionated source code structure before best practices are consolidated in the community.

[bluesurfer]

@egoist

"best" is not the correct term let's say suggested.

@yyx990803

What makes you think the official webpack template is not well maintained?

No problem at all. Mostly because webpacktemplate uses webpack 1, webpack-simple uses webpack 2 and in the webpack site I read:

webpack v1 is deprecated. We encourage all developers to upgrade to webpack 2.

I tend to follow best practices (from my Python experience) but unfortunately, as you said, the best practices here are not yet consolidated. I am struggling to find the best way to start whereas in Python the path is more clear. I need a guide to move around this new messy Javascript world :D and if you say:

It is intended to be the one, well maintained and officially recognized template. However, the templates are focused on build toolchains, not project structure

I will start right from there and begin installing the stuff I need (bootstrap, vue-routers and axios for the API communication).

[yyx990803]

v1 to v2 upgrade is planned for the webpack template and will happen soon (webpack 2 was officially out only two weeks ago).

[LinusBorg]

update: the template is now using webpack2 since a week ago or so.