Dan Vanderkam 🦋

It's here! 🎉 The 2nd edition of Effective TypeScript is now available in all formats. The bird on the cover is the same, but the content is throughly revised and expanded to reflect how TS is used in 2024. Get your copy today! @OReillyMedia amzn.to/3UjPrsK

Great article from @ollie about my long-running quest to find the highest-scoring Boggle board. I love the visuals! ft.com/content/0ab64c…

writing typescript for the first time in 6 years, and i think im enjoying it? new additions like type predicates inference make for a much nicer devex found a very cool article too documenting the development process of this feature from @danvdk effectivetypescript.com/2024/04/16/inf…

@StatisticsFTW @bradzacher Thanks! Curious how it works for you. Right now I think it’s heat for reading code, but for writing you quickly run into github.com/danvk/any-xray…. I think I know how to fix this.

@bradzacher @danvdk 🙌🙌🙌 excellent work sir 🙌🙌🙌

I'd love a VSCode extension that highlighted any variable that TypeScript thinks has type any

@AndaristRake It's interesting that it seems to do two passes here. Is that unique to constructors?

@danvdk Yep, I believe this is exactly what’s happening - without rechecking all of the internals involved here. Good read! :) I stumbled upon this when investigating this fix: github.com/microsoft/Type…

I still find surprising type behaviors in TypeScript. This one makes sense but I had to think about it for a moment to understand how it can be explained: #code/GYVwdgxgLglg9mABMMAKAlIg3gKEYgGwFMpEBnKEYYAbj0RmEVQFkBDKACwDoAnNsABM4AWwyZc+fBSpMAvIgBEwOHEV18AX0RECZItnrTK1RAoAsAJhqIA9LcRwA1vU30ZphYoBGbXupw3HAgCNjIyRABhPUNjWTp6CAQKXhBoOF4MWKlGZnYuPgFhMXQJIykuGDJuD3klFTUNKW1dfWypRErq2rNEKxt7HV5eDPKgjq6akzqfPwCtQJwgA" target="_blank" rel="nofollow noopener">typescriptlang.org/play/?ts=5.7.0…

Just published a big update to my "X-Ray Glasses for any types" VS Code extension: marketplace.visualstudio.com/items?itemName… It uses the built-in TypeScript server now, which makes it faster and more likely to work with your project. Give it a try! It found some anys in vscode and tsc itself!

Just started reading the 2nd edition of this book 🎉 I can’t recommend it enough! The first version made me an entire new dev.

@adokce Try any-xray 0.1.1, I lowered the VS Code requirement.

For a weekend project, I wrote a VS Code extension: X-Ray Vision for any types. The scary thing about "any" is that it can appear in surprising place and silently spread. No more! This was frustrating, rewarding, and hopefully useful. Give it a try! marketplace.visualstudio.com/items?itemName…

@IgorKrupenja Try installing 0.1.1, which lowers the VS Code requirement.

@IgorKrupenja Sure. I can’t imagine I’m using any remotely recent APIs, this was just the default.

@jjalan There are always unexpected any types that come from @types packages. For example, #L135" target="_blank" rel="nofollow noopener">github.com/DefinitelyType… or #L449" target="_blank" rel="nofollow noopener">github.com/DefinitelyType…

@danvdk Love it. Curious, have you run into any unexpected patterns while testing it?

@deanylev Thanks, I’ll take a look. It’s almost certainly not finding the lib.d.ts files for your project, so it can’t get types for callbacks like forEach.

@danvdk Here's an equivalent 😄 github.com/deanylev/any-x…

@_baxuz At the moment, high. But maybe this suggestion will lower it: x.com/acutmore/statu…

@acutmore @JoshuaKGoldberg I was not, but I’ll give this a try! Thanks!🙏 This would also solve lots of issues around understanding everyone’s TS configuration.

@danvdk @JoshuaKGoldberg I suspect you're already aware and this wouldn't work but just in case there is this: #L10" target="_blank" rel="nofollow noopener">github.com/orta/vscode-tw… Command for getting type info from the existing tsserver.

@stevebeauge unknown is much safer than any, since you’ll get a type error if you try to do much of anything with it.

@danvdk would it make sense to also detect unknowns ? I've some weird bugs when using zod's passthrought, and "seeing" unknown may prevent it.

@mazrikbeats There’s no-unsafe-assignment and friends. My goal here was to make the anys visible, not necessarily errors. typescript-eslint.io/rules/no-unsaf…

@danvdk Hmm doesn’t eslint do that with a rule ?

@ihorvorotnov @BenJ_Ayc0 @WebStormIDE noImplicitAny is a TS thing, not an IDE thing. It’s different than this. This will also help you find any types that come from library type definitions (like JSON.parse).

@BenJ_Ayc0 @danvdk As a @WebStormIDE user I rely on “no-implicit-any” eslint rule which does essentially the same thing

@deanylev Can you share your project? There’s a real diversity in how everyone has TS configured, I’m not surprised it’s failing on some setups.

@danvdk Hmm it seems to randomly highlight a bunch of non-any vars for me in my Bun + ElysiaJS project, while not highlighting an actually any var :/

@JoshuaKGoldberg Thanks! I just wish there were a way to do it without running my own copy of the language service…

@danvdk OH this is a really good idea!!