vue.config.js (devServer) not used in npm run serve

Question

I'm trying to set up a reverse proxy on the development server for my VUE js webapp to get around the CORS issue that I was getting when I was trying to use my flask HTTP APIs with the vue js webapp.

I did this by creating a vue.config.js file in the root of the project directory:

module.exports = {
  devServer: {
    proxy: 'http://localhost:5001/'
  }
}

when I run npm run serve, and try to use a REST API defined on port 5001 - I don't see the request going to port 5001, it uses the same port as the web app.

And there are no useful logs being written to stdout either to help me debug this.

Has anyone come across this issue before ?

Usually you want to proxy only the API requests, so usually the config looks like proxy: { '/api': { target: 'http://remote_api.com:5001/', changeOrigin: true } } — IVO GELOV
– IVO GELOV, Commented Jun 21, 2020 at 15:16
@IVOGELOV I do realize that. I was just trying to get the simplest config change working. But it seems like the config file is just not being picked up by vue-cli-service — user12246781
– user12246781, Commented Jun 21, 2020 at 15:51
You can confirm if the file is not picked up by intentionally making a syntax error in the file. — IVO GELOV
– IVO GELOV, Commented Jun 22, 2020 at 6:51

neelmeg · Accepted Answer · 2021-10-28 08:34:57Z

0

I had a similar issue and found that the port was already in use by another application and hence it was not going to the correct port. Once i shutdown the other app, it started working as expected.

answered Oct 28, 2021 at 8:34

neelmeg

2,5056 gold badges34 silver badges47 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

vue.config.js (devServer) not used in npm run serve

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related