augustin-mauroy.bsky.social
@nodejs.org contributor. Open source software lover ! Junior dev.
augustinmauroy.github.io
450 posts
93 followers
83 following
Regular Contributor
Active Commenter
comment in response to
post
There's a package suite that I love, but it's still written in CJS, and what's holding maintainers back from adopting ESM is that there would be breaking changes.
REF: github.com/PrismarineJS...
comment in response to
post
for my packages I use JSR so ESM is the only choice.
jsr.io/@augustinmau...
jsr.io/@am
comment in response to
post
Ahahah 😆
comment in response to
post
Nice !
comment in response to
post
jsr.io/user/f685b57...
comment in response to
post
`calendar` sound cool but yeah kind of big ambition.
also `amauroy` will be kind of name squatting because I already have `@am` and `@augustinmauroy` on JSR
comment in response to
post
and what if it's just on JSR ?
comment in response to
post
I have a solution for you: don’t use X
comment in response to
post
spoiler: yes
comment in response to
post
And I think we can also talk about bun, which is in the same vein.
comment in response to
post
What's more, with all their good will, they're fighting to make Node.js as compatible as possible.
comment in response to
post
I agree with you in every way. The big question is why not invest this energy in node directly. I feel like it's just reinventing the wheel.
comment in response to
post
Ahahah I follow you on both
comment in response to
post
👍👍👍
comment in response to
post
I really want the md support but I can’t do it personally
comment in response to
post
Already done a long time ago! I come from Belgium yeahhh
comment in response to
post
Already done !
comment in response to
post
Please make them all full ESM
comment in response to
post
Pourquoi il n'y a pas de style ?
Perso j'ai une idée 🔴🚩⚫️🏴
comment in response to
post
You should
comment in response to
post
It's crazy how simple it is with @jsr.io but it's a hassle with NPMJS (you have to generate a token and put it in the secret for each repo ...) whereas with JSR you just have to link the repo once with the package when you create it.
comment in response to
post
and btw JSR have dark theme
comment in response to
post
for the moment I'm doing a dual repo publish. But for each new package/repo I need a new npmjs token.
So to keep it simple I would like to just use JSR.
But I'm afraid I'm going to miss out on a piece of the JS package market.
comment in response to
post
so yeah mean only on JSR
comment in response to
post
too boring:
- need to generate tokens all the time for the repo
- disgusting UI/UX
- I only write in ESM (ts)
comment in response to
post
What happened ?
comment in response to
post
github.com/jrieken/vsco...
comment in response to
post
Now I'm thinking about how to write the issue. I wonder if “let's be ESM” isn't a bit of a rubbish title.
comment in response to
post
Let's contribute to all extension that we use
comment in response to
post
Yesss 🎀
comment in response to
post
Also you should do it as Sweat. For example I use my sweat as jacket
comment in response to
post
is it possible to have it in Europe???