Log inSign up
Log inSign up
Hugo
4,102 posts
Hugo profile banner
@hugorcd

Hugo

@hugorcd
Software Engineer at @vercel ▲ Working on nuxt.com Ambassador @raycast Building evlog.dev & shelve.cloud
French / London
hugorcd.com
Joined February 2018
544 Following
4,310 Followers
1 Subscription
RepliesRepliesRepostsRepostsMediaMediaArticlesArticles

Log in or sign up for X

See what’s happening and join the conversation

Continue with phone
or
Log in with username or email
Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
  • Pinned
    @hugorcd
    Hugo
    @hugorcd
    Jul 8, 2025
    What an incredible day! So thrilled to share this. Couldn't be prouder of the entire team. Joining forces with @vercel is a massive step that will bring so much to the framework. I'm incredibly excited for this new chapter! Let's go! 🔥
    @vercel
    Vercel
    @vercel
    Jul 8, 2025
    NuxtLabs, creators of Nuxt and Nitro, are joining Vercel. Same license, roadmap, and open governance, but now in a joint mission to build the best web.
    00:00
    8
  • @hugorcd
    Hugo
    @hugorcd
    9h
    evlog this week: - The GitHub Action is on the Marketplace. Add `uses: evloghq/action@latest` and every PR gets an observability score compared with main. If a change leaves a route with less logging, it's flagged on that line of the diff. - The CLI no longer needs its own
    evlog — Digging through logs is not observability. It's hope.
    From evlog.dev
  • @hugorcd
    Hugo
    @hugorcd
    15h
    Claude Max now gives you up to $200 of API credit every month. Put the key in Bring Your Own Key on @vercel AI Gateway once, and every @eve agent you ship runs on it. You get logs, budgets and ZDR without any extra setup, and switching models is just a string change.
    A dark interface displays a list of AI projects with their status indicators, featuring options for logs, budgets, and API keys.
    3
  • @hugorcd
    Hugo
    @hugorcd
    Oct 8
    We made Nuxt’s error page clearer, with @danielcroe
    Before and after the same Nuxt development error. Nuxt 4.5.2 gives the generic heading ‘An error has occurred’; the current my-bad renderer in Nuxt 4.6 puts ‘Cannot read properties of undefined (reading name)’ first, followed by the failing expression. Notes explain the clearer starting point and expanding callers or component ancestry when needed.
    Two views of the same failing frame. Original TypeScript points to shared/directory.ts:8:20; compiled JavaScript points to 4:18. Annotations explain how the highlight and caret locate the expression, source maps connect generated code to TypeScript, file actions open the editor, and copy location shares the precise position. Editor links retain the original source target.
    Application callers, optional framework frames and component ancestry in the current Nuxt development error renderer. Notes explain tracing the call that supplied the arguments, hiding library internals while following application code, preserving frame order, revealing framework detail for library debugging, and opening a captured component source file. Execution and UI hierarchy answer different questions.
    The Copy error split button and its menu. The primary action copies the diagnosis and source for an issue. Named menu choices offer Markdown, a prompt giving an agent the task and error context, or structured JSON for scripts and tools. All formats use the same report. Purple annotations explain each format’s purpose without covering the controls.
    Nuxt
    3
  • @hugorcd
    Hugo
    @hugorcd
    Oct 8
    True!!! But for the moment, at least, I am convinced that DX = AX, and that's a big part of why I think frameworks still matter. An agent usually starts a new thread with almost no memory. A dev landing on your docs for the first time is in the same spot. Both need the same
    @posva
    Eduardo.𝚟𝚞𝚎
    @posva
    Oct 8
    As coding radically changes, I still think Frameworks play their role of abstractions: they get you where you want faster and with less bugs But as a Framework author, you just don't optimize for the same things anymore, e.g. API design was exclusively meant for humans and now
    4
Edit with