Posts by Gautier
Render your site in black and white to see if contrast is good and that meaning (e.g. error messages) is not only conveyed by colors
`read` would be really easy to implement, Vite takes care of everything
The good news is you don't really need `read`, you can inline fonts using Vite's ?inline feature. As for instrumentation, I need to take a look at what adapter-node does and hopefully it's just copy/pasting. And regarding stability, I hope you are patient, it's currently 1.1 in Node...
The biggest blocker I've encountered is `@resvg/resvg-js`, it depends on an external binary and won't work with the adapter in its current shape BUT there is a way. If you are willing to invest more time in this I'll happily take PRs on the adapter, other than that, thank your for giving it a try!
I'm a madman, you can continue using node:slim as your base. I'm trying on my end (you'll face issue as node-adapter-sea does not declare support for instrumentation and read), but the build hangs after the client-side build, even on adapter-node. I'm using .env.example, do you know what's wrong?
I would love to add a `sea: boolean` option to adapter-node, but I forked sirv to support reading from assets instead of files, not it's not as straightforward as running --build-sea after the current adapter-node build. As for argon2, since it requires another bin, it will fail but I don't know how
All JS code (including node_module dependencies) will be bundled into a single JS file. Then node will be called with --build-sea, this JS file and a list of all assets to produce a fully self-contained binary. Then you can copy this binary in a FROM scratch docker image like this one:
I see that you are running adapter-node, would you like to give my (very) experimental adapter-node-sea a try for slightly better performance and a smaller docker image? ๐
Nice!
On GitHub at least, workflows don't run for first-time contributors, and need a maintainer action instead; I think it's a great default, returning contributors get to publish to pkg.pr.new autonomously to test features and fixes with reporters
I use it and like it, it's great for PR previews where you don't want to publish to npm
๐ค I hope I saw the future properly on this one
Big win for @hmans.dev here
Really cool! Out of curiosity, what does zpm mean?
This is a fantastic new feature, well done @joyeecheung.bsky.social and thank you all Node maintainers for the work all year long!
Hey! I reported another one two weeks ago, have you had the time to review it as well?
Thank you! It's pure Node, no need for electron nor build tools. I'm not sure it would make sense with static builds, you can serve your files with tools much smaller and faster than a 130MB Node binary. As for the release date, I'm waiting for maintainers to approve the concept before opening a PR.
Thank you!
You can grab the WIP adapter here github.com/GauBen/gauti... (you'll need to install the dependencies imported in the code) then use github.com/hatoo/oha to compare adapter-node vs adapter-node-sea. Please share your benchmark results!
Hi fellow Svelters!
I just concluded an investigation to know whether it's possible to use the experimental Node SEA feature with SvelteKit, and I'm thrilled to announce that the answer is yes!
You can read all about it there:
Not only the answer is yes, but IIRC it is backed by experiments:
I'm terrible at coming up with names, how do you feel about "Hippopotime" for a social calendar application?
Indeed! I'll try to build integrations with other atproto apps
I'm currently building a "social calendar" application and because of @danabra.mov I now want to rebuild it on top of atproto
Meme of sirv being excluded from the catalog, with cute birds
Well, they use sirv v3
Is it because of the software suite they use, or because their secretary only knows how to use Word 2003 and sends the PDF directly from it? ๐คญ