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 am installing laravel breeze package . during installation this error happen "error when starting dev server:
TypeError: Invalid URL
at new URL (node:internal/url:775:36)
at getAdditionalAllowedHosts (file:///C:/Users/User/Desktop/Laravel/eloquent/node_modules/vite/dist/node/chunks/dep-BdTvomPN.js:37687:29)
at resolveConfig (file:///C:/Users/User/Desktop/Laravel/eloquent/node_modules/vite/dist/node/chunks/dep-BdTvomPN.js:53812:29)
at async _createServer (file:///C:/Users/User/Desktop/Laravel/eloquent/node_modules/vite/dist/node/chunks/dep-BdTvomPN.js:43695:18)
at async CAC. (file:///C:/Users/User/Desktop/Laravel/eloquent/node_modules/vite/dist/node/cli.js:746:20)" . and it also happen in when run npm run dev .
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.
Describe the bug
i am installing laravel breeze package . during installation this error happen "error when starting dev server:
TypeError: Invalid URL
at new URL (node:internal/url:775:36)
at getAdditionalAllowedHosts (file:///C:/Users/User/Desktop/Laravel/eloquent/node_modules/vite/dist/node/chunks/dep-BdTvomPN.js:37687:29)
at resolveConfig (file:///C:/Users/User/Desktop/Laravel/eloquent/node_modules/vite/dist/node/chunks/dep-BdTvomPN.js:53812:29)
at async _createServer (file:///C:/Users/User/Desktop/Laravel/eloquent/node_modules/vite/dist/node/chunks/dep-BdTvomPN.js:43695:18)
at async CAC. (file:///C:/Users/User/Desktop/Laravel/eloquent/node_modules/vite/dist/node/cli.js:746:20)" . and it also happen in when run npm run dev .
Reproduction
l
Steps to reproduce
npm run dev
System Info
Used Package Manager
npm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: