geldata / geldata/gel-examples
Next.js auth example: port number is hard-coded
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 69
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
Is it possible to make the port number dynamic? Links are failing for me because it happened to be brought up on 3001 instead of 3000. (Not a big deal for me as I can just bring it back up on 3000, but it might confuse a user trying to test it out.)
Contributor guide
No contributing guide indexed for this repository
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 in the Next.js auth example and locate where the port is hard-coded in the links. Verify the change by running the example on a non-default port such as 3001 and confirming that its links still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- authentication, web-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100