Post

Really though. What does it say about the JS ecosystem that so many high profile packages' maintainers let them get convinced by one weirdo to only ship CJS and add 500 transitive deps? THATs the state of our ecosystem?

Passle ☭@passle.dev

Amazes me how much of high profile JS libraries let themself get harb'd

What happened now? 😅

path-to-regexp is only available as cjs and doesnt ship as esm anymore

Emanuele (Ema)

@ematipico.xyz

1 Apr

I didn't know it was his package. And now that ESM can load CJS, he has the definitive excuse to not do it. Time to fork!

Jake Lazaroff

@jakelazaroff.com

1 Apr

not in browsers 🙃 CJS-only means it won't run on the web without a build step

Passle ☭

@passle.dev

1 Apr

^ we use it in our router package for frontend

Justin Fagnani

@justinfagnani.com

1 Apr

Can you switch to URLPattern?

Passle ☭

@passle.dev

Yeah looking into that now. Been on my radar for a while, but havent had the time to look into it. Also the router technically isn't part of my team's responsibilities, but probably does mean loading a polyfill in the app. Not the worst thing in the world though.

1/4/26, 7:11 am0 reposts1 like

Justin Fagnani

@justinfagnani.com

1 Apr

The polyfill is mostly a wrapper on a copy of path-to-regex published as modules :) And if you use it on the server, you can use this for very fast matching of very large URLPattern lists :) www.npmjs.com/package/url-...

Yeah like I said I dont really have a problem loading the polyfill, I use it in personal apps quite a bit.