Repository navigation
chore: weekly dependency update (2026-09-26) - #8
Merged
Merged
Conversation
Bump pnpm packageManager to 12.6.0 and update workspace deps via `pnpm update --latest -r`. Notable bumps: - next 16.3.5 -> 16.3.6 - eslint-config-next 16.3.5 -> 16.3.6 - @types/node 26.4.1 -> 26.6.3 - csv-parse 7.0.2 -> 7.0.3 - fs-extra 11.4.0 -> 11.4.1 - prettier 3.9.6 -> 3.9.9 eslint capped back to 9.39.5 (latest 9.x) instead of the resolved 10.11.0: eslint-plugin-react@7.37.5 (pulled in transitively via eslint-config-next) throws `TypeError: contextOrFilename.getFilename is not a function` under eslint 10, which is an eslint-plugin-react/eslint-config-next support gap, not an app bug. Verified: `pnpm lint` and `pnpm build` pass cleanly; `pnpm dev` smoke test confirmed the `/` redirect resolves to the article page with real content (200). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018cQGMQEWosyap8seKE16Be
This was referenced Sep 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Weekly automated dependency update. Ran
corepack use pnpm@latestthenpnpm update --latest -r.Bumped:
pnpmpackageManager: 12.4.1 -> 12.6.0@types/node: 26.4.1 -> 26.6.3csv-parse: 7.0.2 -> 7.0.3fs-extra: 11.4.0 -> 11.4.1prettier: 3.9.6 -> 3.9.9Capped back down:
eslintresolved to 10.11.0 bypnpm update --latest, but I capped it back to 9.39.5 (the latest 9.x release) inpackage.json. Reason:eslint-plugin-react@7.37.5(pulled in transitively througheslint-config-next, which is pinned to next's version) throwsTypeError: contextOrFilename.getFilename is not a functionunder eslint 10 — this is aneslint-plugin-react/eslint-config-nextsupport gap for eslint 10, not an app bug. All other deps in this repo (react, next, typescript aliases, d3, tailwind, etc.) were already at their latest versions before this update and had no newer release this cycle.Checks
pnpm lint— pass (clean, after the eslint cap above; failed with thegetFilenameTypeError before capping)pnpm build— pass (Turbopack build + TypeScript check vianext build, no errors)pnpm devsmoke test — pass. Port 3000 was occupied so it bound 3001;curlshowed/returning a 307 redirect and the destination article slug (/adaptation-and-adoption-analyzing-gpu-trends-among-pc-gamers-during-covid-19-and-crypto-craze) returning 200 with real rendered content (verified via page<title>). No stack traces or warnings in dev startup logs beyond the expecteduseTypeScriptCliexperimental notice (see below). Note:next devauto-generatedAGENTS.md/CLAUDE.mdscaffold files (a new Next 16 dev-server feature) — these were removed before committing since they're unrelated to this update.What I fixed and why it was safe
eslintto 9.39.5 as described above — purely a version-compat gap in a linked plugin, no source changes needed, and it's the newest release still compatible with the currenteslint-config-next/eslint-plugin-reactchain.useTypeScriptCliworkaround — obsolescence checknext.config.tscurrently setsexperimental.useTypeScriptCli: falsewith a comment explaining that the aliasedtypescriptpackage (@typescript/typescript6) only shipslib/typescript.js, not atscbinary Next's CLI type-checker could invoke.This update lands the repo on next@16.3.6, which (per two sibling repos in this update batch, "thursday" and "blog") adds a
/^tsc\d+$/bin-name fallback torunTypeScriptCli.js. I verified this directly in this repo:node_modules/next/dist/lib/typescript/runTypeScriptCli.jsat 16.3.6 does contain the fallback:Object.entries(packageJson.bin ?? {}).find(([name]) => /^tsc\d+$/.test(name)).@typescript/typescript6@6.0.2's ownpackage.jsondeclares"bin": { "tsc6": "./bin/tsc6" }, which matches that regex.useTypeScriptCli: truelocally, ranrm -rf .next && pnpm build, and it compiled and type-checked successfully with no⨯ useTypeScriptCliwarning (vs. the warning that appears with the flag off). I then reverted the config change before committing —next.config.tsis unchanged in this PR.Conclusion: the workaround now looks safe to remove (i.e.
useTypeScriptClicould be flipped totrueor the override dropped entirely to take Next's new default). I did not make that change here per instructions — flagging it for a maintainer to decide, since it's a config/behavior change outside the scope of a routine dependency bump.GitHub Actions pins (CI.yml)
Checked live tags for all four pinned actions:
actions/checkout@v7— latest major tag, currently at v7.0.1. No change needed.actions/setup-node@v7— latest major tag, currently at v7.0.0. No change needed.pnpm/action-setup@v6— latest major tag (no v7 exists), currently at v6.1.0. No change needed.actions/cache@v6(used twice) — latest major tag, currently at v6.1.0. No change needed.All four are already tracking their latest available major version tag (which auto-resolves to the newest minor/patch), matching what sibling repos found this week. No CI.yml changes made.
Dockerfile
FROM node:lts-alpineis an intentional floating tag — left alone.corepack enable && corepack installpicks up the bumped packageManager pin automatically. No other hardcoded/pinned versions found in the Dockerfile.Needs review
useTypeScriptCliworkaround removal (see above) — empirically verified safe, but left as a follow-up decision rather than bundled into this dependency-update PR.eslintversion cap (9.39.5 instead of resolved 10.11.0) — should be revisited onceeslint-plugin-react(oreslint-config-next) ships eslint 10 support.pnpm peers checkreportsreact-popper@2.3.0wantingreact/react-dom^16.8.0 || ^17 || ^18while the repo runs React 19.3.0. This predates this update (react/react-dom versions unchanged) and wasn't touched.🤖 Generated with Claude Code
https://claude.ai/code/session_018cQGMQEWosyap8seKE16Be
Generated by Claude Code