[BUG]: npm run setup does not create .env file, stops after opening localhost port

[sirconfy]

Has this bug been raised before?

• I have checked "open" AND "closed" issues and this is not a duplicate

Description

When running npm run setup, the script doesn’t generate the .env file as expected. Instead, it stops after opening a localhost port (e.g., http://localhost:54043).

Steps to Reproduce

1. Clone the repo:
   git clone https://github.com/jargonsdev/jargons.dev.git cd jargons.dev npm ci
2. Run setup:
   npm run setup
3. Observe that the script outputs:
   `> jargons.dev@1.0.0 setup

node dev/setup.js

Open http://localhost:54043
4. No .env` file is generated.

Expected Behavior

The .env file should be created automatically after running npm run setup, as described in the documentation.

Actual Behavior

The setup script hangs and only opens a localhost port. No .env file is created.

Environment

1. OS: macOS (e.g., macOS 14.x Sonoma)
2. Machine: MacBook Pro
3. Node.js: v22.14.0
4. npm: 10.9.2

Screenshots

npm run setup

npm start

Output

Do you want to work on this issue?

No

If "yes" to above, please explain how you would technically implement this

No response

[babblebey]

Did you follow this exact steps as seen in the screencast??

screen-capture.15.webm

The Steps

• Run npm run setup
• Open the page created for you in the script result in the browser (in my case it was http://localhost:62470 - you have to be logged in to github)
• That should redirect you to a page to create a Github App using a set manifest
• append your name to the preset App name and create the App
• That is when your env gets set with the details retrieved from the App creation session.
• You can then follow the next step.

[sirconfy]

Yes. I still tried again

…

On Sat, Oct 4, 2025 at 2:52 PM Olabode Lawal-Shittabey < ***@***.***> wrote: *babblebey* left a comment (jargonsdev/jargons.dev#233) <#233 (comment)> Did you follow this exact steps as seen in the screencast?? https://github.com/user-attachments/assets/20329758-e6b9-45d8-858c-aaf32ebc3a8a — Reply to this email directly, view it on GitHub <#233 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALXCJ2H5KBSXYHON2XAVWYD3V7GILAVCNFSM6AAAAACII474F6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNRYGI3TKNJXG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[babblebey]

Still need some more context, I am currently working on #234 with the intention of making the steps even clearer and more user friendly too... This bothers me though.

Could you kindly record your screen as your run the script again... or if you could provide more context by answering the questions...

• Were you able to create a GitHub App, when you were redirected to the github page
• After creation, were you redirected back to the page with next steps??
• What was the returned response in your terminal when you returned from the github app creation.... expected returned is an app object that should show metadata of the app (icluding some sensitive info too though)

🤔

[Nabilhassan12345]

Hi — I’m Nabil (first-time contributor for hacktoberfest). I’d like to work on this issue and will open a small PR that:
adds safer logging to the setup flow,
writes .env when GitHub App data is received, and
writes a .env.example fallback if values are incomplete.
I’ll attach a short screencast of the local setup flow when I test. Please let me know if you prefer a docs-only change instead.

[babblebey]

Hi @Nabilhassan12345, its good to have you here 😁

The understanding is that this doesn't work as it should on macOS, @sirconfy here confirm he was able to gotten thisto work after moving to windows - #62 (comment); I can confirm it works on my windows machine and some other contributors' too.

Here's what would be valuable contribution to start with....

• See if you can reproduce this error on a macOS by running the npm run setup on a macOS - this kinda depends on whether you're running on macOS
• Try running this script on windows (if you're on windows) to confirm it works as intended

If we figure this really is an issue related to macOS, then we have to fix... but we can only do that after we finish up on the following pull requests that touches on that part of the system...

• refactor(dev/setup): implement improved contributor onboarding UI #234
• fix: contribution flow of the jargons editor #236

Feel free to report your findings here on this issue 😉