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
Description:
It would be great if the open option in development mode (nuxt dev -o) could support opening a custom URL or path in the browser. Currently, it always opens the root path (/). This enhancement would provide greater flexibility and improve developer experience, especially when working with environments that use a reverse proxy (e.g., Nginx).
Use Case:
When developing under a reverse proxy setup, the default root path might not be the desired entry point. For example, developers may need to test a specific subpath that maps to a proxied service. Allowing a custom URL or path to be passed to the open option would save time and streamline the development workflow.
Proposed Solution:
Add support for a custom URL parameter to the open option. For example:
nuxt dev -o /custom-path
# or
nuxt dev -o http://custom-domain.com/custom-path
Benefits:
Improved development experience (UX) in environments with reverse proxy setups.
Increased flexibility for testing specific subpaths or URLs during development.
Looking forward to your consideration of this feature. Thank you! 😊
Additional information
Would you be willing to help implement this feature?
The text was updated successfully, but these errors were encountered:
Describe the feature
Description:
It would be great if the open option in development mode (nuxt dev -o) could support opening a custom URL or path in the browser. Currently, it always opens the root path (/). This enhancement would provide greater flexibility and improve developer experience, especially when working with environments that use a reverse proxy (e.g., Nginx).
Use Case:
When developing under a reverse proxy setup, the default root path might not be the desired entry point. For example, developers may need to test a specific subpath that maps to a proxied service. Allowing a custom URL or path to be passed to the open option would save time and streamline the development workflow.
Proposed Solution:
Add support for a custom URL parameter to the open option. For example:
nuxt dev -o /custom-path # or nuxt dev -o http://custom-domain.com/custom-path
Benefits:
Improved development experience (UX) in environments with reverse proxy setups.
Increased flexibility for testing specific subpaths or URLs during development.
Looking forward to your consideration of this feature. Thank you! 😊
Additional information
The text was updated successfully, but these errors were encountered: