SXO :: Optimized Server-Side JSX. Build Simple. Build Fast https://lobste.rs/s/krs8sm #javascript #nodejs #rust
https://github.com/gc-victor/sxo

Une explication simple de ce que sont les *Flame Graphs* et comment ils aident à détecter les parties du code qui consomment le plus de CPU.

https://nodesource.com/blog/understanding-flame-graphs-in-nodejs

Une alternative à `node-soap` pour appeler une API Soap en Node.

https://github.com/loopbackio/strong-soap

Rewriting the Windows section of Kitten’s installation instructions.

Update: it’s live now.

https://kitten.small-web.org/

If you want to get off #GitHub and want to export your data (like repos, followers, stars), I've written a #CLI tool (7 years ago!) that should help with that:

export-my-github:

https://github.com/janriemer/export-my-github

Warning: The tool _hasn't seen an update in 7 years_, so it might be broken. If you experience issues, please report them and I'll try to fix them.

The new integrated Markdown parser I’ve been implementing in Kitten has been kicking my ass for the past few weeks but I think I finally have it fully working and seamlessly so. Expect a new release this/next week that brings the parsing of Markdown pages (.page.md files) in your apps up to the standard of the recently-improved runtime Markdown parsing in Kitten HTML tagged-template strings (within `<markdown>…</markdown>` blocks).

The coolest thing is I was able to implement this without introducing any new syntax. In fact, I was able to simplify things so that you can now add arbitrary JavaScript to your Markdown pages within a multi-line script block in the YAML front matter (`script: |`) and use JavaScript string interpolation syntax in your Markdown (and, of course, Kitten components and conditionals, which, themselves, rely on string interpolation).

The only place where you have to deviate from standard Markdown in your Markdown pages is if you have JavaScript string interpolations or Kitten components/conditionals in code fences within your Markdown. In that case, you’ll have to escape them (e.g., `<\${Component} />`, `\<if \${something}>something\</if>`, etc.). And, to be fair, the person most impacted by this is likely me as the Kitten documentation at https://kitten.small-web.org is written in Kitten so I had a lot of escaping to do. But for any other use case, it means that things should just work and work exactly as they do in JavaScript pages (page.js files).

Anyway, so this is going to be a breaking change so I thought I’d give you (the three of you playing with Kitten right now?) a heads up. Of course, I’ll be updating the documentation to reflect all this.

(Remember, Kitten is in pre-release and it’s the framework I’m building/using to create Catalyst – the Small Web hosting solution – and Yarn – a small web – peer to peer – personal site app. So Kitten isn’t the means, not the end. And, at least until the Version 1 API freeze, things can and will break. That said, there’s nothing stopping you from playing with it now and, to be fair, at this point, such breaking changes should become rarer and rarer).

New Kitten Release

Housekeeping:

• Updated runtime version to Node version 22.18.0 (latest LTS).

• Removed `--experimental-global-customevent` in node launch command (as `CustomEvent` is no longer behing the CLI flag since Node v19.0.0)

• Renamed `--experimental-loader` flag to `--loader` as the experimental prefix is no longer required.

https://kitten.small-web.org

Enjoy!

Long live <?php

Sync-in Server 1.3.0 is now available on NPM!

Install it as a native Node.js package
Use the CLI (sync-in-server) to manage config, start/stop the server, run DB migrations, and more

This release makes it easier than ever to integrate Sync-in into your existing infrastructure !

More info: https://sync-in.com/docs/setup-guide/npm

#release #npm #opensource #foss #nodejs #npm #typescript #selfhosting #selfhosted #selfhoster #syncin #sync_in

Socket.IO Cheat Sheet #nodejs https://dev.to/abhishek-nexgen-dev/socketio-cheat-sheet-c9c

TIL that software (especially #scripting runtimes like #Python, #Perl, and #NodeJS) running in #Alpine #Linux containers is often slower than in other distros like #Ubuntu. This is despite Alpine being faster on startup and often vastly more efficient with CPU, memory, and storage.

It mostly comes down to Alpine’s use of musl libc rather than #GNU’s glibc. musl is optimized for minimalism, not raw performance. Also, the Alpine packages are often not compiled with as many optimizations.

Node.js LTS supporte maintenant officiellement TypeScript (uniquement la syntaxe "effaçable") par défaut.

https://nodejs.org/en/blog/release/v22.18.0

Message in a bottle time again #GetFediHired (not a peep from anyone yet).

Growing desperate in search for (remote) software developer work in the #Ottawa #Montreal areas. #C C# #Erlang #Java #NodeJS #Shell #SQL #BSD #Linux #English #French and more. Very versatile, adaptable, experienced.

http://www.snert.com/resume/

Hey! If its remote, its possible to work world wide too!

OK, who decided that in

```
for (const index in array) {...}
```

index should be a string and not an number?

Des considérations importantes à prendre en compte lorsque vous travaillez avec des variables d'environnement et la configuration de vos applications.

https://blog.platformatic.dev/stop-losing-sleep-over-nodejs-config-heres-how-to-get-it-right

Tous les gestionnaires de version de Node ne se valent pas. Spoiler : choisissez Volta, il est rapide, simple, et se laisse volontairement oublier.

https://nodevibe.substack.com/p/the-500x-performance-gap-between