Config source dir

[ieshan]

What problem does this feature solve?

There should be option in vue.config.js to change the 'src' dir to something else.

What does the proposed API look like?

module.exports = {
sourceDir: "client"
};

[Pymous]

You can, just create a vue.config.js file, and configure it like that :

  lintOnSave: true,
  configureWebpack: {
    output: {
      path: __dirname + '/dist/client'
    },
    resolve: {
      alias: {
        '@': __dirname + '/src/client'
      }
    },
    entry: {
      app: './src/client/main.js'
    }
  }
}```

[cj]

@Pymous I agree with @ieshan, it would be nice just to set the sourceDir, or how poi does it by just specifying the entry file https://poi.js.org/options.html#entry

[Pymous]

It is possible, look at the snippet 😀

But I agree that it could be made more clear somewhere in the doc !

[cj]

@Pymous I know it's possible using vue.config.js, I just think it should be made an option as other cli's like nuxt, poi etc... do 😄

[cj]

@Pymous you also have to add these to your config https://github.com/vuejs/vue-cli/blob/dev/packages/%40vue/cli-plugin-eslint/index.js#L9 https://github.com/vuejs/vue-cli/blob/dev/packages/%40vue/cli-plugin-typescript/lib/tslint.js#L78 https://github.com/vuejs/vue-cli/blob/dev/packages/%40vue/cli-plugin-typescript/index.js#L23. So it's not just as simple as your snippet above. Making these use a variable and allowing you to just set sourceDir would be a nice addition IMO.

[yyx990803]

There will not be a first-class option for this because we prefer all Vue CLI projects to have a consistent, standard directory structure. Using a different directory name is only a matter of personal taste, so if you insist on changing that, you are on your own.

[azjezz]

i had the same problem, i'm only using vue for front-end with zend expressive ( php ) on the back end, all modern php projects use the src/ directory to point to the source directory and public/ to the public directory, so i was looking for a way to change to source directory to assets/ and the output directory to public/assets, i ended up using @Pymous method. but i think it would be better if vue had an option to change the source directory like @ieshan mentioned.

[brhx]

@yyx990803 I would like to kindly request that you reconsider your position.

One of the core tenants of Vue CLI 3 is that you can go an incredibly long way without having to eject.

Many people build Vue projects as subcomponents of other, larger projects. Usually these are servers of many different languages and frameworks; often at least partially responsible for serving the generated dist directory (something that you can configure, as there has been a clearly recognised need to change the output of build files).

The src directory may also be used by these frameworks and languages for different purposes. For any particular project, it may make sense that the client uses src for their serverside code, and wish to rename their src to client to better distinguish these, for example.

This lack of configurability feels weird and inconsistent. src works well as a default but it doesn't seem take into account the scope of which Vue projects often exist: not as standalone projects but as a smaller part of larger projects. Creating an entirely new subdirectory within an existing project for a Vue project and then also having an src and dist and new package.json and every other required file again is an unwieldy solution to these problems.

[onyijne]

@sam3d just spoke my mind, after going through several docs on the internet on how to rename src folder to client.
I use Onsen-UI, Vue with Yii framework and I have configured the project to share a single package.json file, (as I configured Yii to use npm for assets management instead of Yii's built-in assets management), but could not tell Vue where to get its source code from, @yyx990803 kindly reconsider your stand.

[brhx]

I've started work on a package that attempts to emulate the desired native behaviour as closely as possible.

$ vue add source-dir

// vue.config.js
module.exports = {
    pluginOptions: {
        sourceDir: "client"
    }
}

https://github.com/sam3d/vue-source-dir

This should be a first-class option though, and I would rather this was treated as a stopgap implementation as opposed to a long-term solution.