Replies: 3 comments 5 replies
-
I've started having the same problem too (it changed without upgrading anything which was a bit alarming). As a workaround I have this in my server: {
port: 5000,
proxy: {
"/api": {
target: "http://localhost:3000",
changeOrigin: true,
secure: false,
},
},
}, And then run |
Beta Was this translation helpful? Give feedback.
3 replies
-
I have the same problem. This should be an issue instead of a discussion. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Although I can't explain why, following config solve the issue for me. {
"scripts": {
"dev": "vite --port $PORT",
}
}
{
"devCommand": "npm run dev"
} |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
If I use the default config and default development command (
vite
) and runvercel dev
:it starts both on different ports
changing the command to
npm run dev
and the following package.json, starts both on port 3000 and serverless functions work, but the vite/vue app itself doesn't:Beta Was this translation helpful? Give feedback.
All reactions