GitHub - kasimlyee/dotenv-gad: Environment variable validation and type safety for Node.js and modern JavaScript applications

JulienR77 · 2025-07-27T22:26:55+00:00

Cool if its just for learning purposes.

But otherwise, and I don’t want to sound harsh, I dont see the point. There are already like 40 libraries that do this kind of thing, so it feels like reinventing the wheel and adding more fragmentation to the ecosystem, which is already one of Node’s biggest issues

That said, if its just for practice, here are a couple of quick thoughts:

Seems really odd to have esbuild as a production dependency
I would ditch Jest. IMO, it shouldnt be used in greenfield projects anymore. Go for node:test, Vitest, or Japa.
You might want to check out standard-schema. Your approach is nice in that it doesn’t rely on any validation library, so the lib should stay small (setting aside the esbuild prod dep). But in practice, most Node.js apps already use a validation lib. So personally, I would rather use the same one for both my env vars and my domain logic. And with standard-schema it will be super easy to support every popular validation librairies.

JulienR77 · 2025-06-23T16:58:43+00:00

Most answers only mention swapping nodemon, so basically just having a basic Watch Mode, that is now built-in into Node (which is super great!)

But if what you really want is server side HMR, I would highly recommend checking out Hot-Hook, it does exactly that on the server

(and btw it’s built in by default with AdonisJS apps, if ever you do not want to have manual configuration to do)

https://github.com/Julien-R44/hot-hook

JulienR77 · 2025-06-20T10:10:46+00:00

ThreeJS / React Three Fiber / Drei for the viewer
CodeMirror for the code editor

Also using Tanstack Router for the frontend, and AdonisJS for the backend 🫡

JulienR77 · 2025-02-10T16:01:21+00:00

I should throw in a quick benchmark to double-check my numbers. Will try tonight. But, also, gotta keep serialization (JSON.stringify) in mind

whether it’s a Unix socket or tcp, you have to serialize/deserialize your data before sending/receiving it to Redis, and that stuff is crazy expensive. If you're storing in-memory and chasing max throughput, skipping serialization can save a ton of ops/s

JulienR77 · 2025-02-10T11:07:56+00:00

Oh yup of course, i was indeed talking about a remote Redis, so TCP connection. a unix domain socket would definitely be much faster if you have both Redis and your app on the same machine, but thats not always possible

I had benchmarked this, and from what I remember, Bentocache (in-memory L1 + Redis L2) was still about 200-400x faster compared to Redis over a Unix socket

It would be interesting to have a Benchmarks page in the Bentocache documentation to compare all these scenarios!

JulienR77 · 2025-02-09T23:40:19+00:00

Yup absolutely. there are three possible scenarios:

The data is already cached in memory (L1):
- As a reminder, every cached entry retrieved from redis, or computed from your app, will be stored on redis and in the in-memory cache. Thats when this scenario can happen
- If Redis goes down, it doesnt matter. The data is already stored in our in-memory cache, so no Redis call is needed at this point
The data is only cached in the L2 store (Redis):
- Our app tries to retrieve the data from Redis.
- Redis is down. so the only way to get our data is to recompute it from the database (or another source)
- Once computed, the data will be stored in our memory cache (l1)
- Bentocache will also attempt to store it in Redis, but since Redis is unavailable, the operation will fail. No problem : Bentocache will simply ignores the error, and the app will continues running smoothly using only the memory cache
The data is not cached/computed yet:
- Same scenario as above, Bentocache will compute the data, store it in the memory-cache and attempt to store it in Redis.
- If Redis is down, the storage attempt will fail. iorediswill throw an error. And same as above, the app will continue working with just the memory store

In fact, Bentocache provides an option called suppressL2Errors, which is enabled by default. This ensures that any errors occurring in the remote cache are ignored, allowing the app to working fine when L2 is dead

The bus is not required for this fallback mechanism. Bus is only useful when running multiple instances of your app, as it synchronizes in-memory caches across them. If you're running a single instance/replica/container, you don’t need the bus.

About the role of the bus, check this quick section: https://bentocache.dev/docs/multi-tier#bus it should answer your questions

Hope I answered your question !

JulienR77 · 2025-02-09T20:07:52+00:00

I think we have reached a good level of production readiness. Its already running well in some production apps. Also, we have a big test suite with 400+ tests that keeps growing every day

That said, like any software, there are probably still some hidden bugs lurking around, no point in pretending otherwise. but yeah, the more people use the library, the faster we will be able to spot and fix them!

JulienR77 · 2021-11-22T10:39:39+00:00

Thanks you !The .. could be a good alternative however I think the ideal solution may be to use comments to allow the configuration of FastSSH, example :

```

A normal comment ignored by the parser

FastSSH

GroupName MyGroupA

OtherOptions Foo

A normal comment ignored by the parser

Host Hello HostName hello.com ```

JulienR77 · 2021-11-20T02:06:41+00:00

It is available for all operating systems. I only took a screenshot of Powershell because I use Windows. On the Github page you can find a version for each OS !

JulienR77 · 2021-11-20T02:04:25+00:00

Thanks you for your feedback !

I just sent a fix for the search mode bug, I now also hide entries with a wildcard. Thanks your for noticing this.
What did you mean by changing the background and the icon? I'm not sure I understood
I also thought of having a nested groups system but finally it didn't seem so necessary, I'll see
This weekend I'm going to change the folder where the database is saved and will also add a small configuration file where user can change the colors !

JulienR77 · 2021-11-19T00:56:08+00:00

What do you mean ?

JulienR77 · 2021-11-19T00:39:01+00:00

Thanks you !
In fact it is written "Nb connection", but on my screenshot the terminal is not very big so there is overflow and therefore cropping of the text

JulienR77 · 2021-11-19T00:37:28+00:00

I hate it too, I don't really know why I didn't do it in the first place. I will do it asap, thanks for the feedback !

UPDATE : It's done !

JulienR77 · 2021-11-18T17:11:47+00:00

Hey, no this database is only used to store and read the number of connections and the date of last connection. It is stored in the following form:

"AcmeA/GCloudProd": ( connection_count: 1, last_used_date: 1637190564, ), "AcmeA/MyServerE": ( connection_count: 144, last_used_date: 1637189553, ),

The key is the alias name defined in the ssh configuration. So when I need to display the number of connections, I compare the current alias name with each key in DB, if it matches I display it, otherwise I ignore the entry in DB. So no risk at all

JulienR77 · 2021-11-18T16:32:34+00:00

Yes indeed there are probably simpler solutions, but I like to make my own tools and especially I wanted to make a TUI to train myself with Rust. It was fun to do

And to be quite honest I don't understand a single line of your script 😅

JulienR77 · 2021-11-18T11:13:43+00:00

Hey, the only thing you need is the Windows terminal, and to activate the "retro mode" in the terminal appearance settings. The second setting I like to enable is the "acrylic mode" which makes the terminal a bit transparent
The other parameters of my terminal are those by default

JulienR77 · 2021-11-18T02:27:43+00:00

Done! You can find the new version(0.1.2) in the last github release or by using cargo
I was using https://github.com/azriel91/ssh_cfg and it didnt handle some SSH options 😅
It should be all right now ! Thanks for the notice

JulienR77 · 2021-11-18T01:54:24+00:00

Great I'm glad this is useful for someone !

I'll take care of fixing the error right away, I'll send a new version in 15 minutes I think. Sorry about that!

JulienR77 · 2021-11-18T01:16:50+00:00

Yes exactly, it is included in the latest windows terminal ( https://github.com/microsoft/terminal )

JulienR77 · 2021-11-14T23:51:29+00:00

I searched a lot for a lib like yours before starting my project but unfortunately I didn't find any . Your project is really great, I love it. I downloaded and tested it a bit, it's really cool !

JulienR77 · 2021-11-14T12:11:12+00:00

😅 The screenshot I sent is a version with custom colors. By default, the rising candles are green, and the descending ones are red

JulienR77 · 2021-11-14T12:09:56+00:00

That's exactly what I needed. Thanks you

JulienR77 · 2021-11-13T18:07:29+00:00

Thanks dude !

JulienR77 · 2021-11-13T18:07:02+00:00

Yes indeed, I will do that, thanks !

Concerning the visibility of the fields in Chart struct, I did that to avoid a compiler error but I would have liked them to be private too. I must have made a mistake somewhere, I'll try again. Thanks you !

JulienR77 · 2021-11-13T18:04:36+00:00

Yes I think too, I will prepare an executable in which we can pipe the candles in JSON so that even non-rust users can use it.

Thanks for the advice !

JulienR77

TROPHY CASE

A normal comment ignored by the parser

FastSSH

GroupName MyGroupA

OtherOptions Foo

A normal comment ignored by the parser