augustin-mauroy.bsky.social
@nodejs.org contributor. Open source software lover ! Junior dev.
augustinmauroy.github.io
310 posts
64 followers
63 following
Getting Started
Active Commenter
comment in response to
post
đź—żđź—żđź—ż
comment in response to
post
I'd much rather see how people do it in a real-life case than a N° tuto
comment in response to
post
IF you're going to do a concept like this, I'd advise you to just tell us what you're going to do, and then add a few “why's” and you're good to go.
comment in response to
post
I think there are several interesting points:
- How the project is built
- Tracking project progress
- to see everyone's approach
- discovering new ways of doing things
comment in response to
post
When I say “complicating things” I'm talking about 10k packages, 100 external cloud services that can be implemented in a single API route...
comment in response to
post
And what's more, what kind of runtime needs an externl dep to make an assert?
comment in response to
post
working on both deno and node it's always horible, just use node
comment in response to
post
docs.deno.com/runtime/fund...
comment in response to
post
github.com/nodejs/node/...
comment in response to
post
I was thinking about single page application
comment in response to
post
I can’t join this time
comment in response to
post
It's just that people are always a little afraid of long configuration files.
comment in response to
post
Imo we should never make this happens
comment in response to
post
it's also mean that `@nodejs-loaders/tsx` work for v22
comment in response to
post
I try to publish on both so that users of the package can choose what suits them best.
comment in response to
post
For me all new package should be on JSR and old should be publish on both
comment in response to
post
JSR is cool and easy to use. Npm is also cool. But publish a package on both can be tricky
comment in response to
post
🙄🙄🙄
comment in response to
post
And ofc write down a blog post about this research
comment in response to
post
Next step is to build same thing but with npm workspaces
comment in response to
post
Lucas should be a teacher IMO
comment in response to
post
I've been using mistral for 6 months but the app is really cool.
comment in response to
post
And thank you for taking everyone's opinion into account. I consciously believe that JSR can eventually replace NPM.
comment in response to
post
This is where my feelings about JS+jsdoc packages come from github.com/nodejs-loade... . On the other hand, a simple TS package is great: github.com/AugustinMaur...
comment in response to
post
Basically I think a new document that explains how to publish a package on JSR if it has been designed for NPM without changing everything.
comment in response to
post
It's when you publish a package written in JS with JSdoc and @types/node.
It's poorly documented on how to do it. Do you have to get the definition before publishing and use `@ts-self-types`. Or does jsr do it.
comment in response to
post
I don't think adding a paragraph about JSR would be too much of a shock.
comment in response to
post
Haha
But not we need to go out of package.json
comment in response to
post
"Drop support of `deno.json`":
I think that to be truly javascript regestery you would have to be runtime agnostic. In other words, the tool should not be defined with a runtime.
comment in response to
post
"Better design of `jsr.json`":
- `description` field
- way to define runtime support
comment in response to
post
For my personal website I use GitHub pages it’s reduce the amount of thing to maintain
comment in response to
post
@fredkiss.dev
comment in response to
post
I beg you to make the runtime support defined in the `jsr.json`.
comment in response to
post
Woowww
comment in response to
post
"... or forming its own 501(c)(3) or similar entity." not good idea IMO
comment in response to
post
Oh wow strange so you need to put it in the oven ?
comment in response to
post
What happens ??? Did you put alcohol in oil bottle ?
comment in response to
post
Same but I have an issue: I am drunk
comment in response to
post
Interesting 🤔
comment in response to
post
GitHub (so why my initial question) about my project I recommend just this page l augustinmauroy.github.io/en/projects
comment in response to
post
So why because major part of oss community use GitHub ?
comment in response to
post
Nan that’s the @rafaelgss.dev lib ref augustinmauroy.github.io/en/blog/post...