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

docs: add a pnpm path to the first-feature tutorial

Closed Beginner friendly
#26 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@sudo0m is already working on this.

Since Oct 11, 2026.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

The change belongs in docs/getting-started.md, where the first-production-feature tutorial shows only the npm command. Read that section to see how the npm command is presented, then confirm the pnpm form by running create-jst@latest with pnpm. Done means the pnpm command sits beside the npm one, npm stays the default, the tutorial order is unchanged, the commands were verified, and the documentation link check passes.

Written by the indexing model from the issue text.

Description

documentation good first issue help wanted

Scope

The first-production-feature tutorial currently starts with the npm command only. Add an equivalent pnpm command without duplicating the remainder of the guide.

Acceptance criteria

  • Show the supported pnpm command beside the existing npm command in docs/getting-started.md.
  • Keep npm as the default path and preserve the current tutorial order.
  • Verify every new command against create-jst@latest.
  • Run the documentation link check.
  • Do not change package-manager support or generated project defaults.

Why this is bounded

This is a documentation-only contribution with one source file, an executable verification step, and no architecture decision.

Dominant language
JavaScript
Stars
1
Forks
0
Avg merge
1d 3h
Merged PRs (30d)
11

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 jst-stack/jst

All issues in jst-stack/jst

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.