#nuxt3
Live, measured metrics for the hashtag #nuxt3 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #nuxt3
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 18:41 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 18:41 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 18:41 UTCEverything below is measured over the latest 35 public posts (spanning ~25976 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (27) · Russian (3) · French (2) · German (1) · Spanish (1)
Avg boosts / post: 0.2
Top of the latest posts
A small update on my blog about learning Nuxt 3: https://vernaillen.dev/blog/nuxt #nuxt #vue #nuxt3 #vue3
Analyze Memory Leaks in Your Nuxt App https://mokkapps.de/blog/analyze-memory-leaks-in-your-nuxt-app #nuxt #nuxtjs #nuxt3
I really like Nuxt 3, but not having a clear way to override the global $fetch is a deal breaker to me. In other words, you're bound plumb your way up to what you need. And that's what I hate from most Javascript frameworks. There is a lot
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/nuxt3