Hard Coded HOST and PORT (nux-bridge
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 285
- Forks
- 33
- Avg merge
- 22h 38m
- Merged PRs (30d)
- 3
Description
Describe the feature
I would like to be able (like in nuxt 2) define in nuxt.config.js, the default port for the app, without using .env file or environnement variables
I have already see/search in issues, none of them explain how to set it without .environnements variables
in my team, we have 2 nuxt project, one running on default port, another at port 3333 we cannot run both without set a .env or use environnements variables
Additional information
- Would you be willing to help implement this feature?
- Could this feature be implemented as a module?
Final checks
- Read the contribution guide.
- Check existing discussions and issues.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how Nuxt Bridge currently determines the app's host and port, then inspect how nuxt.config.js is loaded alongside .env and environment variables. Done means a project can define a default port such as 3333 in nuxt.config.js without those external settings, while retaining the existing default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxtjs, typescript
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100