

The momentum on a lot of the “popular node.js package but for Deno” packages died well before they added npm: specifiers and more support for node builtins. Aside from a few notable outliers, denoland is full of stuff that hasn’t been updated in 4+ years.
What I like about deno is that I can do everything with web standards, then fill the gaps for server-side needs with the node standard lib. Web standards have come a long way for server code thanks to web workers, but there are still some missing pieces. The deno experience is way better with web standard libraries and jsr, so my hope is the momentum will continue to head in that direction such that the npm: and node: imports just become nice-to-have capabilities for niche uses.
Chances are they are doing something similar to URL shortening where a reference to the destination and the tracking info is either hashed into the URL directly or stored elsewhere behind whatever ID is in the URL.
Unshortening tools can fetch the actual URL (with any tracking params) in a private context.
I have no idea if anything exists on iOS, but on Android there are tools like URL Check which replace your default browser and let you un-short or otherwise manipulate URLs before opening in a browser or sharing.