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

Nessuno ha ancora preso questa issue.

### Has this bug been raised before?

- [x] 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_

Inizia con dev/setup.js, invocato da npm run setup, e riproduci il comportamento con npm ci seguito da npm run setup. Traccia il motivo per cui apre solo la porta localhost indicata, quindi verifica che setup crei il file .env documentato e termini correttamente.

Scritto dal modello di indicizzazione a partire dal testo della issue.