Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

.env.example

Open
  • Is something wrong?
#16 0 comments 0 reactions 0 assignees View on GitHub

@suryacagur is already working on this.

Since Oct 8, 2026.

  • #22 by @suryacagur — open

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
javascript, nextjs
Domain
developer-experience

Research direction

Open .env.example and compare its Appwrite variables with the three values listed in the issue. Add the missing project-name entry, then verify the example includes all three required variables with the same formatting.

Written by the indexing model from the issue text.

Description

documentation
💭 Description

.env.example has missing field

NEXT_PUBLIC_APPWRITE_PROJECT_NAME =

Connect your platform in the Console gives the following values

NEXT_PUBLIC_APPWRITE_PROJECT_ID = 
NEXT_PUBLIC_APPWRITE_PROJECT_NAME =
NEXT_PUBLIC_APPWRITE_ENDPOINT =

But the .env.example in this repository only have

NEXT_PUBLIC_APPWRITE_PROJECT_ID= 
NEXT_PUBLIC_APPWRITE_ENDPOINT=
👀 Have you spent some time to check if this issue has been raised before?
  • I checked and didn't find similar issue
🏢 Have you read the Code of Conduct?
Dominant language
JavaScript
Stars
12
Forks
49
Avg merge
24m
Merged PRs (30d)
4

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from appwrite/starter-for-nextjs

All issues in appwrite/starter-for-nextjs

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.