[GH-ISSUE #83] how to create brand new project #24

New issue

Closed

opened 2026-05-06 12:36:35 +02:00 by BreizhHardware · 1 comment

BreizhHardware commented

2026-05-06 12:36:35 +02:00

Owner

Originally created by @junaid-ali-ruk on GitHub (Feb 26, 2026).
Original GitHub issue: https://github.com/cloudflare/vinext/issues/83

how to create brand new project

Originally created by @junaid-ali-ruk on GitHub (Feb 26, 2026). Original GitHub issue: https://github.com/cloudflare/vinext/issues/83 how to create brand new project

BreizhHardware closed this issue

2026-05-06 12:36:35 +02:00

BreizhHardware commented

2026-05-06 12:36:35 +02:00

Author

Owner

@mhs003 commented on GitHub (Feb 26, 2026):

There may be other ways, but this is what I did and it worked fine.

Create a new NextJs project

npm create next-app@latest

Cd into the project directory and install vinext package.

npm i vinext

Initialize vinext (read more)

npx vinext init

Replace next with vinext in the scripts section of your packages.json:

{
  "scripts": {
    "dev": "vinext dev",
    "build": "vinext build",
    "start": "vinext start"
  }
}

You are now ready to go.

(optionally you may remove the next package if it is no longer required.)

@mhs003 commented on GitHub (Feb 26, 2026): **There may be other ways, but this is what I did and it worked fine.** 1. Create a new NextJs project ```bash npm create next-app@latest ``` 2. Cd into the project directory and install `vinext` package. ```bash npm i vinext ``` 3. Initialize `vinext` [(read more)](https://github.com/cloudflare/vinext?tab=readme-ov-file#migrating-an-existing-nextjs-project) ```bash npx vinext init ``` 4. Replace `next` with `vinext` in the `scripts` section of your `packages.json`: ```json { "scripts": { "dev": "vinext dev", "build": "vinext build", "start": "vinext start" } } ``` **You are now ready to go.** (optionally you may remove the `next` package if it is no longer required.)

BreizhHardware referenced this issue

2026-05-06 12:38:52 +02:00

[PR #46] [CLOSED] feat(cli): load .env files with Next.js precedence #266

BreizhHardware referenced this issue

2026-05-06 12:38:59 +02:00

[PR #70] [MERGED] fix(dotenv): load .env files with Next.js precedence #288