@KevinVanCott Yeah will try to show something concrete. Sent a discord message also just now
English
Scott
346 posts
@sprusr I agree that type-inference is a good thing, but you'd have to PR a working example of what you're trying to suggest. I don't know how it would get better.
English
As soon as I move TanStack Table V9 to beta and promise more stability, I figure out ways to make the TypeScript experience so much better, but it could require breaking changes...
Who would like to never need declaration merging ever again for TableMeta or ColumnMeta? Per-table metas too?
English
@KevinVanCott But regarding inferred types, I again point to query where the default is for types to be inferred. I personally think that makes for an excellent developer experience and would love to see a similar setup for table.
English
@KevinVanCott Inferring the type doesn’t mean allowing anything, the table config as a whole still has its type constraints. But true that even if inferred for the table itself you would probably still need to explicitly define it in other places with the current setup 🤔
English
@KevinVanCott From previous post it sounded like there could be things which conceptually could be at either level. But maybe my thoughts on this are not yet well formed 😅
But point I’d most like to make here: meta should be inferred like how data is, without manually defining its type.
English
@sprusr You can use both helpers. They're at different levels.
They're also noop wrapper functions pretty much. They only exist as typescript helpers.
English
@KevinVanCott Looking within tanstack ecosystem, I really like how query solves this with queryOptions. Saw there’s now tableOptions but feels like that and tableFeatures are kinda stepping on each other for reusability. Many generics not necessarily bad if there are many things to configure.
English
I'm actually considering moving all rowModels and Fns to features too. The reason is that we can gain type-safety from the TFeatures generic without having to introduce a half-dozen new generics to get all of this to work. I think it fits. Anything that has to do with code construction or allowed types comes from `features`
English
@KevinVanCott Oh cool yeah I see the PR, nice one. Ergonomics feel a bit weird to me to configure the type with features but meta is not a feature. Would prefer if type of meta could be inferred from what’s passed to table. But this certainly works + is great improvement.
English
@sprusr I've just added it, and it's not a breaking change. But I'm looking at more changes to make also make the filterFns, sortFns, and row models in general more automatically type-safe, and that requires re-arranging some table options again. Builds on this idea.
English
@KevinVanCott That type param also needs adding to basically everything else I suppose, and that gets complex. But I feel that meta should behave in a similar way as data, in terms of types. Inferred from what’s passed to useTable for example.
English
@KevinVanCott I had imagined it would work with an additional (optional) type param for useTable, but almost certainly I’m missing some of the complexity to why it’s not that straightforward!
English
So I picked a great day yesterday to make my first contribution to TanStack Router 😅
TANSTACK@tan_stack
SECURITY ADVISORY — TanStack npm packages A supply-chain compromise affecting 42 @tanstack/* packages (84 versions total) was published to npm earlier today at approximately 19:20 and 19:26 UTC. Two malicious versions per package. Status: ACTIVE — packages are deprecated, npm security engaged, publish path being shut down. Severity: HIGH — payload exfiltrates AWS, GCP, Kubernetes, and Vault credentials, GitHub tokens, .npmrc contents, and SSH keys. If you installed any @tanstack/* package between 19:20 and 19:30 UTC today, treat the host as potentially compromised: • Rotate cloud, GitHub, and SSH credentials immediately • Audit cloud audit logs for the last several hours • Pin to a prior known-good version and reinstall from a clean lockfile Detection — the malicious manifest contains: "optionalDependencies": { "@tanstack/setup": "github:tanstack/router#79ac49ee..." } Any version with this entry is compromised. The payload is delivered via a git-resolved optionalDependency whose prepare script runs router_init.js (~2.3 MB, smuggled into each tarball at the package root). Unpublish is blocked by npm policy for most affected packages due to existing third-party dependents. All 84 versions are being deprecated with a SECURITY warning, and npm security has been engaged to pull tarballs at the registry level. Full technical breakdown, complete package and version list, and rolling status updates: github.com/TanStack/route… Credit to the security researcher for responsible disclosure.
English
@sprusr nice.
I'd love this for bigger maps, like countries or worlds. RPG stuff.
right now i use azgaar.github.io/Fantasy-Map-Ge…
English
I started this as a fun project, but the more I’m working on it the more it feels like something serious, legit good alternative for 90% of web map use cases
Scott@sprusr
Been building a vector map rendering library from scratch. It’s called mewmap and it’s powered by SVG tech built-in to browsers. That allows for pretty small bundle size
English
I put together some vector tiles from the new data (for using on web/mobile apps) and a style to go with them gist.github.com/sprusr/ab2adfe…
Tom Patterson@MtnMapper
We are pleased to announce the release of updated Natural Earth v6 transportation data, including roads, railroads, and ferries. A big thank you to Zhaoxu Sui for preparing it. shadedrelief.com/ne-draft/
English
Can try it out at spru.sr/mewmap but beware it still has a bit of jank in Safari/iOS to figure out
English