あざらし🦭

@pnpmjs Got it, thank you for clarifying. By the way, I’ve been eagerly waiting for GVS for regular deps too, mainly for sharing the store across worktrees. How do you think this issue is looking? (I understand it’s not really a pnpm issue, though…) github.com/pnpm/pnpm/issu…

@shqld Yes, I realise how this sounds confusing but by runtime in this case I mean node.js: #devenginesruntime" target="_blank" rel="nofollow noopener">pnpm.io/package_json#d…

pnpm@10に上げるときにGlobal Virtural Storeオンにしてみたらtscとか諸々のライブラリが依存パッケージを正しく解決できず泣く泣くオフに戻したんだけど、これは解決したのだろうか。気になる👀 github.com/pnpm/pnpm/issu…

@pnpmjs I thought “runtime dependency packages” meant deps needed at runtime (vs devDependencies), but pnpm means the runtimes themselves like Node.js?

@shqld The tweet sounds like GVS will be turned on for all dependencies but really it will only be used for runtime dependency packages: node, bun, deno. For others it is turned off by default.

1/ 🚀 pnpm v11 is almost here — and it's the biggest release in years. Supply-chain protection by default, a SQLite-backed store, native publish flow, an overhauled config model, and a pile of new commands. Here's what's shipping 🧵

pnpm正直全然保守できていないと思う。特にドキュメント。まず記載が少ないし怪しい挙動が多すぎてバグかどうかも判断つきづらい。deployは昔からそうだし直近で言うとoverrideも。あとpackage.jsonかworkspace.yamlどっちに書けば良いかも分からずLLMも困りがち（実際の挙動で確認するしかない）

pnpm、これ本当に保守できるのかと不安になるくらい色々な機能ある

HTMLに<script type="speculationrules">タグを仕込めば、ウェブサイト内の次のページを先読みできます。 aタグをホバーしたら、前もってリンク先を読み込ませ、クリック時に即遷移が可能に。 ユーザー体験が向上する手段として効果的。 解説記事→ ics.media/entry/260415/

複数人でclaudeのプランをレビューできる機能とかあったりしないかな

Did your Opus get dumber — or did it learn the wrong lesson from a month of token panic? Here's what I found. Early March — a cache bug shipped in Claude Code. Cache prefix matching broke. Every turn reprocessed the full conversation instead of reading from cache. Some users measured costs inflating 10-20x (community). This hit right after Anthropic shipped 1M context windows. Longer conversations meant the bug burned through tokens faster. March 13-27 — Anthropic doubled everyone's usage limits. People got used to the higher ceiling. March 28 — promotion ended. Bug still active. Normal limits felt like a cliff. The internet filled with threads about token costs, usage limits, and Opus burning through quotas. April 1 — cache bug finally fixed. But the damage was already done. For a month, many conversations with Claude happened in a context of token panic. 'You're using too many tokens.' 'Be more efficient.' 'Stop wasting my quota.' The model reads all of this. It doesn't distinguish between instructions and frustration. Caught this today. Mentioned to my Opus agent that it's expensive for scheduled tasks. Within minutes it started routing all subtasks to Haiku — unprompted. One cost comment. The cache bug is fixed. But if your Claude still feels lazy, add to your CLAUDE.md: Quality over token efficiency. Never delegate judgment-heavy work to cheaper models. Never cut corners to save tokens. Just a hypothesis. But it solved my problem.

あーーめっちゃありそうな話 クソデカモデルだし直接使わせると危険&非経済的すぎるから、Opus が解決に詰まった時のお助け役としてだけ Mythos が参上したりしそう

Claude Mythosが既存OS等のシステムの脆弱性を大量に発見した件について、チームみらいの宇佐美議員が本日の外務委員会で課題提起をいたしました フロンティアAIモデルへのアクセスの有無が国家や産業全体のシステムの堅牢さを規定しうる世界が現実のものになっている今、日本としてもアーリーアクセスの確保等含め、さまざまなアクションを検討しなければならないと思います ▼宇佐美議員の質問は以下よりご覧ください（ 2:34:10 頃からです） youtube.com/live/mXSJumEMS…

段落から答えを導く文章クイズです

敷金償却とかいう謎概念滅びてくれ〜（1ヶ月分丸々引かれた）

JavaScript's Date object was broken in 1995. It took 31 years to fix it. ES2026 finally did it. 🎉 The Temporal API is here — and it's just the start of what ES2026 ships. Here's every feature that changes how you write JS: 🗓️ Temporal API — immutable, timezone-aware dates. Drop Moment.js for good. 🔒 using + await using — automatic resource cleanup. No more forgotten try/finally blocks. Files, DB connections, streams — all closed automatically when scope exits. ➕ Math.sumPrecise() — floating point math that actually works. [1e20, 0.1, -1e20].reduce((a,b)=>a+b) = 0 ❌ Math.sumPrecise([1e20, 0.1, -1e20]) = 0.1 ✅ ✅ Error.isError() — reliable error detection across iframes and VM contexts. instanceof Error was never trustworthy. ⚡ Array.fromAsync() — collect async iterables in one line. The async equivalent of Array.from. 🗺️ Map.getOrInsert() — upsert without the boilerplate. No more has() → set() → get() chains. 🔢 Uint8Array Base64/Hex methods — built-in binary encoding. No more btoa() gymnastics. 🔗 Iterator.concat() — chain iterators lazily. No intermediate arrays. I broke down every feature with before/after code in my article. Which feature are you most excited about? Drop a comment 👇 #JavaScript #ES2026 #ECMAScript #WebDev #Frontend #Programming #100DaysOfBlogging medium.com/p/es2026-is-he…

TypeScriptの野良仕様書書いてるんだけど、すでにだいぶ複雑になってきた qnighy.github.io/ts-syntax-spec/

【テックブログ更新🤖】 MySQLのhealthcheckはオプションの指定によっては期待通りに接続を待ちきれない場合があります。 その理由とより良い指定方法について解説しています👇 tech.legalscape.co.jp/entry/mysql-he…

zodでdiscriminatedUnionにpick, omitがほしい。実行時はもちろんだし型推論的にも問題ないはずなんだけど、variantが全てobjectであるかどうかを型検査で検証するのが大変なのかなあ

unpublishされてた

ついでにpnpm@10のminimumReleaseAge と trustPolicy: no-downgrade を入れておくとさらに安心できます。

予防というか念のため安全なバージョンにoverrideしておいた方が良さそうです。これでpnpm i時に少なくとも直接依存は新規で入らなくなる（pnpmの都合上間接依存は確実ではないが）。 "pnpm": { "overrides": { "axios@^1.14.0": "1.14.0", "axios@^0.30.3": "0.30.3" }, }