Add `eject` information to README/add `eject` functionality

[soanvig]

What problem does this feature solve?

The new vue-cli 3.x.x lacks eject option (either only in README or in whole project). The README mentions:

At the same time, it still offers the flexibility to tweak the config of each tool without the need for ejecting.

Projects created by Vue CLI allows you to configure almost every aspect of the tooling without ever needing to eject.

But no such command exist, or no such command is mentioned in README.

What does the proposed API look like?

yarn eject -> yarn run eject

• confirmation, that this is unrevesable action.

It should then immediately fallback whole project directory into standard Vue/Webpack project directory known from vue-cli 2.x.x

[soanvig]

It would at least follow Vue.js philosophy of being customizable (which is guaranteed by vue-cli actually), and elastic (which is not guaranteed now, since it requires yarn, which would be dispensable after actual ejecting).

[yyx990803]

The whole point is... It doesn't exist because you don't need to. This is by design.

[soanvig]

Because of your experience, I believe you, that it's good decision.
Personally I cannot come with some use case (having in mind how vue-cli treats configuration files).

At the first place I was confounded by the statement, that vue-cli requires yarn, but now I relealised, that it was Contributing section.

[asadsahi]

@yyx990803 if eject isn't available, then how to achieve the project model of https://github.com/vuejs/vue-hackernews-2.0 i.e implement SSR if someone have to or to use node as backend? From backend I mean running node server and use webpack-dev-middleware for client asset compilation. This allows to run project with one command and controlling it that way.

Or it isn't possible with vue cli based template?

[Akryum]

@asadsahi A SSR plugin will be added at some point.

[asadsahi]

@Akryum I am guessing in current version of cli, its webpack-dev-server, but with SSR plugin are you planning to use node as a server and static assets being compiled using webpack-dev-middleware?

[njleonzhang]

@yyx990803 can you consider to support the eject? The tool is cool, and the configuration through vue.config.js is also cool, but working without webpack config(souce code) makes me scared, especially if I encounter some weird issue.

[AliasT]

@vue/cli have the vue.config.js configureWebpack, but it is more friendly with adding, not modifying. just as @vue/cli indicates:

You will need to familiarize yourself with webpack-chain's API and read some source code in order to understand how to leverage the full power of this option...