You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For years, I've used an Envoy Proxy during development of Vue/Webpack apps, but the Vue/Vite combination has been complicated when specifying an app base. I've tried all the possible vite.config possibilities except for the ones that work. BTW, the issue concerns dev/debug, and not building/deployment.
The local Envoy Proxy setup simulates the external production environment providing various service routing & gRPC features. So Vite's proxy features wouldn't suffice.
Without an app base, looping through Envoy works well. But with a base path in the URL, I found the following:
either the initial request redirects indefinitely (base set to app base)
or, the html header is delivered and stuffed with absolute paths to things such as /@vite/client and /src/main.ts (base set to ./)
As I have a work-around (i.e., no app base), going forward isn't a problem. However, if it were necessary to run multiple Vite apps through the proxy, header-based routing would likely be necessary.
Anyway, I opened this up for discussion should anyone else be working with a production proxy during development.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
For years, I've used an Envoy Proxy during development of Vue/Webpack apps, but the Vue/Vite combination has been complicated when specifying an app base. I've tried all the possible vite.config possibilities except for the ones that work. BTW, the issue concerns dev/debug, and not building/deployment.
The local Envoy Proxy setup simulates the external production environment providing various service routing & gRPC features. So Vite's proxy features wouldn't suffice.
Without an app base, looping through Envoy works well. But with a base path in the URL, I found the following:
./
)As I have a work-around (i.e., no app base), going forward isn't a problem. However, if it were necessary to run multiple Vite apps through the proxy, header-based routing would likely be necessary.
Anyway, I opened this up for discussion should anyone else be working with a production proxy during development.
Beta Was this translation helpful? Give feedback.
All reactions