Changelog for Template-NEXT: Version 0.3.2

In this changelog, we'll cover the additions and refinements in v0.3.2 that make scaffolding more predictable for teams while keeping an opt-in path to bleeding-edge packages.

Version 0.3.2 - What's New

1) Next.js 16 baseline (pinned)

Scaffolding now defaults to Next.js 16 for stability and predictable installs. Use --latest to override pins when you want the newest compatible releases.

2) Runtime Node guard (Node ≥ 20.9.0)

The CLI checks your Node version on start and exits with a clear message if it's below 20.9.0, aligning with Next 16 requirements.

3) Reveal pins with `versions`

Quickly audit the pinned package set used by default:

Terminal

npx @edward-hyde/template-next versions

This prints the pinned versions for Next.js, Prettier, and Prettier-Tailwind.

4) UX & publish polish

Clearer progress and help text, normalized package metadata, and small copy tweaks.

Usage Examples

Terminal

# Standard (pinned Next 16)
npx @edward-hyde/template-next my-app

# Initialize in the current directory
npx @edward-hyde/template-next .

# Use latest instead of pins
npx @edward-hyde/template-next my-app --latest

# Inspect pinned versions
npx @edward-hyde/template-next versions

Current Pin Set (0.3.2)

Package	Pinned Version	Reason
`next`	`16`	Predictable scaffolding aligned with Next 16
`prettier`	`^3.5.0`	Minor updates for bug fixes; stable formatter
`prettier-plugin-tailwindcss`	`^0.6.0`	Compatible with Prettier 3; Tailwind class sorting

System Requirements

Node.js ≥ 20.9.0
npm (or pnpm) installed

If you're below the required Node version, the CLI will exit with a helpful message.

Summary

Template-NEXT 0.3.2 brings a stable default with Next.js 16, a Node 20.9+ guard for clarity, a convenient versions command to surface pins, plus light UX polish. If you want the absolute latest packages, you can still opt in with --latest.

With 0.3.2, Template-NEXT aims to be boring-reliable by default and flexible on demand. Spin up a project with the pinned Next 16 stack, or opt in to the bleeding edge with --latest. If something feels rough, open an issue or PR—your feedback directly shapes the next release. Happy coding!