Also agree, with each release I get an "Eureka effect" that now I can solve the type issue I strugled couple months ago trying to create to just make some highly used function safer/easier to use for the developers.
Example the new satisfies and some upcomign "as const" features to generics I'm looking forward to
Actually liked that it lacked a minimap. Got a better sense of scale. After going trough most of the tunnels and getting stuck and kings chamber there, couldn't crawl back, I zomemed out and was shocked by the scale of the tunnels.
Right now only pain-point with npm is that "npm link" can't be forced to install peer dependencies so I'm unable to easily test typesscript built libraries within other projects.
I'm currently having a similar issue where the query planner refuses to use the indexes on a search query (was fine for w hile, but one day it just started de-optimizing itself). Instead just does a seq-scan. Instead of the execution taking ~40ms with indexes the query planner thinks that the seq scan of ~1.5s is better...
Re-indexes the db and run analyze the table. It gets better for max 30min then PG de-optimizes itself again.
I'm kinda stuck on it, any ideas what can I do to resolve it?
Example the new satisfies and some upcomign "as const" features to generics I'm looking forward to