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.
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 🤔
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.
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.
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.
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.
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!
Yes please! I started looking into contributing this but hadn’t managed to find the time/effort. Big quality of life improvement for projects with multiple tables. At first thought should also be possible to add without breaking declaration merging 🙏
Thankfully I missed the compromise window, but even if I had been working during it I think pnpm v11 new defaults would have saved my ass!
So I picked a great day yesterday to make my first contribution to TanStack Router 😅
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/router/i…
Credit to the security researcher for responsible disclosure.
Focus of my project is more about displaying/exporting to SVG a map from data of the real world, rather than making the map itself. Azgaar’s fantasy map generator is a really great thing :)
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
Doing a talk next week at HelsinkiJS meetup about maps on the web. Bit of history, bit of future. Hopefully interesting and entertaining!
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/ab2ad…
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/
After that something I’m excited to explore is server-side rendering + possible lightweight isomorphic React wrapper ⚡️
I have a small roadmap in the GitHub readme, but next focuses are:
- Symbols (text and icons)
- Rendering from geojson (custom markers)
- Bunch of work to support full Maplibre/Mapbox style spec
Now with raster (satellite) layers working in mewmap 🌍 I think I could probably ship a raster-only version in just a few kb bundle size 🤔
Can try it out at spru.sr/mewmap but beware it still has a bit of jank in Safari/iOS to figure out