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
I'm trying to configure my OIDC provider to redirect back to vite running locally, and while localhost works fine, 127.0.0.1 is now advertised in the console as the link to click on.
Why was this changed? According to the history the title of the #8543 it looks like it should show the opposite. It should at least be configurable..
Reproduction
Create a new vite app, run npm run dev, in console it shows "local: http://127.0.0.1..."
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
The first case is when localhost is used. Node.js under v17 reorders the result of DNS-resolved address by default. When accessing localhost, browsers use DNS to resolve the address and that address might differ from the address which Vite is listening. Vite prints the resolved address when it differs.
You can set dns.setDefaultResultOrder('verbatim') to disable the reordering behavior. Vite will then print the address as localhost.
I suggest upgrading your Node.js version or manually setting dns.setDefaultResultOrder('verbatim') in the Vite config.
Otherwise, the possibility remains that another server can also listen on localhost:5050 and hijack the connections from Vite.
Describe the bug
I'm trying to configure my OIDC provider to redirect back to vite running locally, and while localhost works fine, 127.0.0.1 is now advertised in the console as the link to click on.
Why was this changed? According to the history the title of the #8543 it looks like it should show the opposite. It should at least be configurable..
Reproduction
Create a new vite app, run
npm run dev
, in console it shows "local: http://127.0.0.1..."System Info
Used Package Manager
npm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: