Interest | Match | Feed
and also having to depend on an lsp other than tsserver to correctly resolve deps is annoying, especially when you aren't building exclusively for deno
and also having to depend on an lsp other than tsserver to correctly resolve deps is annoying, especially when you aren't building exclusively for deno
この文章は、VSCodeの動作を軽くし、メモリ使用量を削減するための設定と最適化方法を解説しています。主なポイントは以下の通りです。
1. 拡張機能の見直しと管理:不要な拡張機能を無効化し、必要なものだけを有効にすることでパフォーマンス向上。拡張機能の起動時間を確認し、原因を特定できる。
2. ファイル監視の最適化:不要なディレクトリを監視対象から除外し、エクスプローラーや検索の負荷を軽減。
3. TypeScriptの最適化:tsconfig.jsonで不要な解析を除外し、tsserverのログや自動型取得を無効化して負荷を減らす。 (1/2)
この文章は、VSCodeの動作を軽くし、メモリ使用量を削減するための設定と最適化方法を解説しています。主なポイントは以下の通りです。
1. 拡張機能の見直しと管理:不要な拡張機能を無効化し、必要なものだけを有効にすることでパフォーマンス向上。拡張機能の起動時間を確認し、原因を特定できる。
2. ファイル監視の最適化:不要なディレクトリを監視対象から除外し、エクスプローラーや検索の負荷を軽減。
3. TypeScriptの最適化:tsconfig.jsonで不要な解析を除外し、tsserverのログや自動型取得を無効化して負荷を減らす。 (1/2)
Interest | Match | Feed
Interest | Match | Feed
File: src/testRunner/unittests/tsserver/session.ts:567
handle(msg: ts.server.protocol.Message): void
SVG: dark, light
File: src/testRunner/unittests/tsserver/session.ts:567
handle(msg: ts.server.protocol.Message): void
SVG: dark, light
My understanding is that the 4GB limit is inherent becuase the pointers have been limited to roughly old-school 32-bit values.
My understanding is that the 4GB limit is inherent becuase the pointers have been limited to roughly old-school 32-bit values.
I know a lot of people force VS Code to use node to run, say, tsserver to avoid pointer compression memory limits.
tsserver may not be long for this world but it's kinda spooky if every Node process will end up limited to 4GB...?
I know a lot of people force VS Code to use node to run, say, tsserver to avoid pointer compression memory limits.
tsserver may not be long for this world but it's kinda spooky if every Node process will end up limited to 4GB...?
すでにあるやつが雑多だから、作り直しじゃなくて新しく作って技術ブログにしようかな
すでにあるやつが雑多だから、作り直しじゃなくて新しく作って技術ブログにしようかな
This goes for all the major ones I touched, including NPM and TS/tsserver
I got more community value out of Orogene, which was a tiny niche project.
It’s good to note how much Rust provides for tooling
This goes for all the major ones I touched, including NPM and TS/tsserver
I got more community value out of Orogene, which was a tiny niche project.
It’s good to note how much Rust provides for tooling
this shit is literally in a public PR to tsserver
this shit is literally in a public PR to tsserver
all this stuff existed before language servers were a thing (so uses tsserver directly for example)
all this stuff existed before language servers were a thing (so uses tsserver directly for example)
lyra.horse/blog/2025/08...
What about React ? Is this allowed ?
Despite the ts warning, it looks like it works. Property 'cool-thing' does not exist on type 'JSX.IntrinsicElements'. (tsserver 2339).
I use next-yak to use proper HTML in my Next app.
lyra.horse/blog/2025/08...
What about React ? Is this allowed ?
Despite the ts warning, it looks like it works. Property 'cool-thing' does not exist on type 'JSX.IntrinsicElements'. (tsserver 2339).
I use next-yak to use proper HTML in my Next app.
2️⃣ridiculous tsserver perf
3️⃣insanely fast runtime validation
4️⃣great documentation
5️⃣power features (generics and HKTs)
6️⃣deep introspectability
7️⃣serializable definitions
8️⃣human-readable errors
9️⃣universal composability
🔟easy to learn
Choose 10.
2️⃣ridiculous tsserver perf
3️⃣insanely fast runtime validation
4️⃣great documentation
5️⃣power features (generics and HKTs)
6️⃣deep introspectability
7️⃣serializable definitions
8️⃣human-readable errors
9️⃣universal composability
🔟easy to learn
Choose 10.
That said I don't mind having the config.
That said I don't mind having the config.
Interest | Match | Feed
Interest | Match | Feed