So it does look like the TypeScript language server has a limit of 4MB source size where it disables type checking (and actually shows an erroneous error stating that exports that exist in the file do not exist) for files that are imported but not open in the current workspace/session.

Still not sure if this is documented anywhere or not (haven’t been able to find it, if it is).

99.99999% of the time, unless you’re doing niche stuff like I am, you won’t run into this.

Workaround: should you have such a large file, e.g., with a large generated object, try and refactor to split it up into multiple files and rejoin it a separate file. The actual object size/memory usage isn’t the issue, it’s the file size.

https://github.com/typescript-language-server/typescript-language-server/issues/951#issuecomment-2786000876

@LibreKitsune I still consider this a hostile act and a blatant violation of their previous #settlement that forced them into #publishing said #IPv4 #ranges...

• In fact had they not actively worked against that previously and it only raised my attention when I saw errors re: said ranges.

I'm considering to build a #workaround on #GitHub to just use a #cookie and some #compute to do it, but if I had cash to spare I'd sue them into removing #ClownFlare and allowing me to scrape the list directly...

• I'm very close to just sending them an #invoice for the personnel hours wasted on that bs and billing them regularly for the expense of manually checking the difference between those (@ minimum of 60:15 billable minutes)...

Otherwise I do expect regulators to actually go after #OpenAI and force them to undo the #Cloudflare-based #Enshittification, since it's neither feasible nor reasonable to claim "#DDoS-#Protection" for a 48 Bytes (!!!) file...

• Every #WAF / #WebApplicationFirewall I know would not get triggered even if I were to query it once per hour (which I now do just to annoy them or rather ClownFlare!...

Just found out that another workaround may be granting Accessibility Permissions to the launcher. I'm testing that now.

この問題、ひとまずの回避方法を見つけたかも知れない。
⌘（Command）キーを含む一部のキーボードショートカットが重複して実行されてしまう場合があるみたいだけど、ショートカットに ⌘ を含まなければ発生しない気がする。
よく使う ⌘ を含むキーボードショートカットは ⌘ を Control キーに変えたショートカットを設定することで重複実行を回避できるかも（とりあえず、タブを閉じるショートカットに Control + W も追加してみて試してみている

Aha! Workaround: using the mobile phone as a USB tethered Ethernet adapter. Slow, but the driver works out of the box. Now loading/attempting to build a suitable driver. #workaround

My bad, I accidentally ran npm config set registry http:// registry.npmjs.org --global instead of *https* while troubleshooting.

All good now :)

@marcpalmer I use #Hue, but for most rooms I’ve created a scene called “standard”, and when I want reset from different brightness or colour changes I just enable that scene #workaround