Arjun
banner
arjun.xyz
Arjun
@arjun.xyz
Stay tuned for more tips like these!
July 9, 2025 at 1:28 PM
When you publish, PNPM replaces `catalog:` references with the actual version ranges, ensuring your packages remain compatible with other tools. Learn more at pnpm.io/catalogs.
Catalogs | pnpm
"Catalogs" are a workspace feature for defining dependency version ranges as reusable constants. Constants defined in catalogs can later be referenced in package.json files.
pnpm.io
July 9, 2025 at 1:28 PM
Need multiple version sets? Use named catalogs!
July 9, 2025 at 1:28 PM
Why use catalogs?
• Maintain unique versions across your workspace
• Easy upgrades (change one line in the catalog, done!)
• Fewer merge conflicts in `package.json` files
July 9, 2025 at 1:28 PM
In any `package.json`, simply reference `catalog:` instead of the version!
July 9, 2025 at 1:28 PM
In your `pnpm-workspace.yaml`, you can set up a catalog like this:
July 9, 2025 at 1:28 PM
Catalogs are a powerful way to manage dependency versions in your monorepo! Instead of repeating version ranges in every package, define them once as reusable constants. Here’s how it works 👇
July 9, 2025 at 1:28 PM
I'll report back after using it as my primary browser for a while.
July 7, 2025 at 9:29 PM
Here is the privacy screen!
July 7, 2025 at 9:29 PM
You can even configure the AI response voice and style
July 7, 2025 at 9:29 PM
The gradient progress bar is a nice touch!
July 7, 2025 at 9:29 PM
Recently came across a similar post from @hvpandya post as well.
hvpandya.com/what-i-use/
What I use
Hardik Pandya is a seasoned design leader with experience in building and scaling design teams. Read his thoughts on design, leadership, and technology.
hvpandya.com
July 6, 2025 at 7:03 PM
I enjoy reading about how people setup their workspaces. @workspacesxyz is a good follow.
July 6, 2025 at 7:03 PM