2026-06-22のJS: TypeScript 7.0 RC、Babel 8.0.0、React Router v8#1383
Conversation
Co-authored-by: azu <azu@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
JSer.info #774(2026-06-22公開分)の日本語記事を追加し、2026年6月の主要なJavaScriptエコシステムのリリース/変更点をまとめるPRです。
Changes:
- 新規記事
_i18n/ja/_posts/2026/2026-06-22-774draft.mdを追加(TypeScript 7.0 RC / Babel 8.0.0 / React Router v8 など) - ヘッドライン/アーティクル/サイト/ツール各セクションに関連トピックを追記(npm v12、pnpm、MDN MCP server、WASI 0.3、Biome v2.5 など)
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| --- | ||
| title: "2026-06-22のJS: TypeScript 7.0 RC、Babel 8.0.0、React Router v8" | ||
| author: "azu" |
| @@ -0,0 +1,243 @@ | |||
| --- | |||
There was a problem hiding this comment.
🟡 Non-descriptive filename produces incorrect permalink URL
The file is named 2026-06-22-774draft.md with the slug "774draft". Per _config.yml:36, the permalink pattern is /:year/:month/:day/:title/, so this will generate the URL /2026/06/22/774draft/. All other posts in the repository use descriptive content-based slugs (e.g., 2026-06-07-pnpm11.5-node.js26.3.0-cloudflare-void0.md). If merged as-is, this creates a non-descriptive permanent URL that breaks the established naming convention. The repository also has a test/filename-checker.js that runs as part of CI which may additionally flag this.
Prompt for agents
The filename 2026-06-22-774draft.md should be renamed to follow the repository convention of using descriptive content-based slugs. Based on the post title mentioning TypeScript 7.0 RC, Babel 8.0.0, and React Router v8, the file should be renamed to something like 2026-06-22-typescript-7.0-rc-babel-8.0.0-react-router-v8.md. This affects the permalink URL generated by Jekyll via the /:year/:month/:day/:title/ pattern in _config.yml.
Was this helpful? React with 👍 or 👎 to provide feedback.
| <p class="jser-tags jser-tag-icon"><span class="jser-tag">pnpm</span> <span class="jser-tag">ReleaseNote</span></p> | ||
|
|
||
| pnpm 11.7リリース。 | ||
| 読み取り専用ファイルシステム上のストアに対応する`frozenStore`設定、同一レジストリURL配下でのスコープ別認証トークンの指定に対応。 |
There was a problem hiding this comment.
🚩 Potential doubled の particle in line 112 across compound particle
Line 112 contains 同一レジストリURL配下でのスコープ別認証トークンの指定に対応. The morphological analyzer may parse "での" as で + の, giving two の particles in one clause ("での" and "トークンの"). However, similar patterns exist in other passing posts (e.g., compound particles like "への", "での" are common in this blog), so this likely won't be flagged. Worth verifying if textlint CI passes.
Was this helpful? React with 👍 or 👎 to provide feedback.
Summary
Add a new JSer.info article covering major JavaScript ecosystem releases from June 2026, including TypeScript 7.0 RC, Babel 8.0.0, and React Router v8.
Changes
_i18n/ja/_posts/2026/2026-06-22-774draft.mdwith comprehensive coverage of:--checkers,--builders,--singleThreaded), default value changes, and removed optionsloose/spectoassumptions, polyfill handling changesNotable Details
https://claude.ai/code/session_01UwdMW4jrJ4xKbV4MnaHyJ2