Skip to content

feat: setup questions with Gatekeeper rate limiting, release 1.1.0 - #2

Merged
SibilSoren merged 6 commits into
mainfrom
feat/wizard-gatekeeper
Nov 9, 2026
Merged

SibilSoren merged 6 commits into
mainfrom
feat/wizard-gatekeeper

Conversation

@SibilSoren

Copy link
Copy Markdown
Owner

Description

The interactive setup on main was never released, and its options didn't work: the Gatekeeper option generated code that didn't compile, and the Prisma option installed a Prisma version that crashes on Node 23 and later. This PR fixes the Gatekeeper option, drops Prisma for now, adds flags so every question can be answered from the command line, and adds tests so new options can't break the existing ones. It ends with the 1.1.0 release commit.

Type of Change

  • 🐛 Bug fix
  • ✨ New feature
  • 📝 Documentation update
  • 🔧 Refactor / chore
  • 💥 Breaking change

Changes Made

  • Gatekeeper: named import (there is no default export), window: '1m' instead of 60 (which meant 60 milliseconds), and gatekeeper ^2.0.0. It goes after request logging, so rate-limited requests are still logged.
  • --gatekeeper / --no-gatekeeper. --yes and CI now use the same default as the question: rate limiting on.
  • The project name is checked inside the prompt, instead of the CLI exiting after all the questions.
  • Prisma is removed for now. A database option (Drizzle first, then Prisma 7) will come as its own release.
  • Tests that scaffold real projects for every combination of options: no extras, Gatekeeper, pnpm, pnpm with Gatekeeper, an invalid name, and a folder that isn't empty. They check that the project without extras is exactly the template.
  • CI also builds and boots a project without Gatekeeper, and checks the rate limit headers are only there when it was chosen.
  • README and landing page no longer say "Zero prompts", and list the new flags.

Testing

  • I've tested the CLI tool locally (npx tsx src/index.ts test-project)

  • The generated project boots successfully (npm run dev)

  • The generated project's tests pass (npm test)

  • I've run npm run lint with no errors

  • The interactive setup was driven with expect, like a person typing. It rejected Bad Name in the prompt, accepted the corrected name, kept the Gatekeeper default and switched to pnpm with the arrow key.

  • A generated project with Gatekeeper allows 100 requests, then returns 429 with Retry-After and the X-RateLimit-* headers.

  • Every commit in this PR passes typecheck, tests and lint on its own.

Screenshots / Logs

101 requests to a generated project:
 100 404
   1 429
X-RateLimit-Limit: 100
X-RateLimit-Remaining: 0
Retry-After: 58

Checklist

  • My code follows the project's code style
  • I've updated documentation if needed
  • I've added an entry to CHANGELOG.md (if user-facing change)

The wizard's Gatekeeper option generated code that didn't compile (a
default import; gatekeeper only has a named export), set `window: 60`,
which is 60 milliseconds, and installed ^1.0.0.

- Named import, `window: '1m'` and ^2.0.0, added after request logging
- Throw if the app.ts template stops matching instead of skipping silently
- --gatekeeper/--no-gatekeeper skip the question; --yes now includes it,
  the same default as the wizard
- Validate the project name inside the prompt instead of exiting after
It installed Prisma 5, which crashes on Node 23 and later, and ran prisma init after the project was committed. A database option with Drizzle and Prisma 7 will come as its own feature.
Creates real projects without installing for each option and combination, and checks the files. A new option now can't quietly change what the others generate.
Checks the rate limit headers are there only when Gatekeeper was chosen, so the project without extras keeps working as features are added.
@SibilSoren
SibilSoren merged commit c8417bb into main Nov 9, 2026
14 checks passed
@SibilSoren
SibilSoren deleted the feat/wizard-gatekeeper branch November 9, 2026 08:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant