Author | Lightnews

Arjun @arjun.xyz · 2h

web-fragments.dev/ seems interesting. Seems to be using a combination of iframes and shadow dom for isolation. Reminded me of remote-dom from my Shopify days!

Web Fragments - A radically new way to do micro-frontends.

🚀 An incremental, low-risk, high ROI approach, to building micro-frontends.

github.com

Arjun @arjun.xyz · 29d

This is really nifty to generate CLI tools.
x.com/simonw/stat...

1

Arjun @arjun.xyz · Jul 13

Handy command to force kill any process using a port number

2

Arjun @arjun.xyz · Jul 12

Exploring @tanstack router. The file based type generation is really nifty!

2

Arjun @arjun.xyz · Jul 9

Stay tuned for more tips like these!

1

Arjun @arjun.xyz · Jul 9

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

1 1

Arjun @arjun.xyz · Jul 9

Need multiple version sets? Use named catalogs!

1

Arjun @arjun.xyz · Jul 9

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

1

Arjun @arjun.xyz · Jul 9

In any `package.json`, simply reference `catalog:` instead of the version!

1

Arjun @arjun.xyz · Jul 9

In your `pnpm-workspace.yaml`, you can set up a catalog like this:

1 1

Arjun @arjun.xyz · Jul 9

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 👇

1