@JNYBGR — silencing npm's noise with four lines
Adblock for NPM 😂
npm set fund false npm set audit false export DISABLE_OPENCOLLECTIVE=1 export ADBLOCK=1
Suddenly output is super clean
That's genuinely useful — npm set fund false and npm set audit false are persistent config changes (written to ~/.npmrc), while the two env vars kill the opencollective banners that some packages still inject at install time. I've had fund false in my config for years but didn't know about ADBLOCK=1. Adding that to my dotfiles now.
@vercel — AI provider integrations, now in Marketplace
Introducing AI Integrations on Vercel.
◆ @perplexity_ai ◆ @replicate ◆ @pinecone ◆ @modal_labs ◆ @fal_ai_data ◆ @lmnt_com ◆ @togethercompute ◆ @elevenlabs ◆ @anyscalecompute
Smart move — if you're already deploying on Vercel, adding an AI provider through their Marketplace means credentials flow into your environment automatically and billing is consolidated. The list covers inference (Together, Anyscale), image/audio generation (Replicate, fal.ai, LMNT, ElevenLabs), vector search (Pinecone), and serverless GPU compute (Modal). That's most of what you'd reach for when building an AI feature. Whether you'd trust a platform layer between you and these APIs depends on how much you care about vendor lock-in, but for quick prototypes this removes a lot of setup friction.
@brotzky — a hook for subtle parallax
Subtle parallax ✨
Here's the hook I use to achieve this effect
Parallax on scroll is one of those effects that's either done well or it's nauseating. The "subtle" qualifier in the post is doing real work here — the demo shows a restrained offset that feels like depth rather than motion sickness. The hook itself tracks mouse/scroll position and maps it to a translate value; the implementation is short enough to just drop into a project rather than reaching for a library. Saved this to avoid rebuilding it from scratch next time.
@simonrohrbach — behind the new Liveblocks website
Alongside our brand-new Slack integration yesterday, we also launched a new website.
Here are a couple of details on how we made it, and what went into it.
Love this because product teams almost never document the "how we built the website" part — it's treated as marketing overhead, not engineering work. Simon sharing the decisions behind the Liveblocks site rebuild makes it useful. Whether it's the stack choice, the animations, or just the process of shipping it the same day as a feature launch, these behind-the-scenes threads are more instructive than most dedicated blog posts.
