Repository navigation
Tags
Tags
feat!: modernize template — pnpm, ESM, ESLint, knip, typecheck, cover… …age, format-check (#166) * feat!: modernize template — pnpm, ESM, ESLint, knip, typecheck, coverage, format-check Ports the modernization pattern from freckle/npm-package-template#178. - yarn -> pnpm, Node pinned via .nvmrc - ESM (`"type": "module"`), `.js` extensions on relative imports - jest -> vitest, coverage gated at 70% (currently 100%) - adds ESLint, knip, typecheck (covers test files), format-check - modernizes tsconfig.json (ES2023, NodeNext, stricter checks) - adds `files: ["dist"]` to package.json - drops @semantic-release/exec's dist rebuild; CI uses freckle/check-git-clean-action@v1 instead - replaces the local check-git-clean.sh with the shared action BREAKING CHANGE: @freckle/maybe is now ESM-only. `require('@freckle/maybe')` works on Node 22.12+ via require(esm) but not on older Node or under CJS-only bundlers. Contributors also need pnpm instead of yarn. * chore: pin .nvmrc to major only Node minor/patch drift across independent, decoupled packages doesn't matter the way pnpm/TS pins do — Renovate keeps each repo current regardless. * chore: CODEOWNERS frontenders -> team-student-activities * chore: author -> Renaissance Learning Inc
chore: stop committing package.json and dist back to main (#163) The @semantic-release/git push to main is blocked by the `main` ruleset ("Changes must be made through a pull request"), so every releasing run since #154 has failed with GH013. npm packages have no need to commit back: @semantic-release/npm publishes the bumped version from the working tree, and CI's check-git-clean already guarantees the committed dist matches the build. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>