Welp, I thought I will never see the day something like this happended to Next.js.

## Tf happened
On December 3, 2025 a catastrophically vulnerability allowed an attacker with a 2015 macbook and ChatGPT under their belt to exploit React's Server Components to arbitrarily run code and compromise the Next.js runtime. This is not fun, and for any Next.js user that drank the coolaid and moved to the new App Router it was an acid joke.

Luckly Vercel resolved it quickly, thank god, but a vulnerability this caliber is just way to scary 😅

## Is gamerexde.io affected?
It is yeah, I updated quite quickly the Next.js version into one that is patched, though I don't think the vulnerability applies. I'm quite stubborn with the release of the App Router, when it was released I imediately hated it, so I just stuck with the Page Router and forgot pretty fast about it. This website 100% uses the Page Router so no React Server Components, it should've been fine, but I updated it regardless.

Ironically enough I planned on migrating to App Router in a near future, but thank god my procrastination prevented me from doing it so yeah...

## Is NodeJS bad on the server?
In my opinion, JavaScript with TypeScript is fine enough I can bare it, for frontend development running on the browser and nothing more. The moment you want to use it on the server is just a bad idea overall.

Really just take a peek into [denysdovhan/wtfjs](https://github.com/denysdovhan/wtfjs) and see for yourself, if a language with that kind of behaviour should run on the server. Hell no. 

With some patience, carefulness, and abstinence from not letting an AI agent code for you, you can have a pretty secure infrastructure, even if it runs on code that behaves like a drunk dad. 


## Conclusion
Use a real language, don't use JavaScript on the server, I don't know, I just wanted to talk trash about NodeJS haha.

JavaScript on the server was and still is an error. CVE-2025-66478

It's really been a while. 

Last time I updated this it was exactly July 2023, and I made that website with the intention of never having to pay for it, at least that was the idea.

I uploaded the website with [Vercel](https://vercel.com) and used [Supabase](https://supabase.com) as the backend, but for some reason during that time it wasn't enough for me. I was tech-stack thirsty and I wanted to do the weirdest tech-stack possible. So I tried to redo it in Rust with [Actix](https://actix.rs), and that's where I left it all these years.

After paying a lot for this domain, leaving the home route stale for years I knew I needed to do something, so I came back to my roots and stick with [Vercel](https://vercel.com) and [Supabase](https://supabase.com), and forced myself to be happy.

Honestly now days I'm a fan of fast development for not so important stuff, or stuff I just want to work and not worry about it, this website is one prime example. Still for long term projects I consider other technologies due to the complexity.

For now this website is basic anyways, it doesn't need that ultra blazingly-fast shit from Actix, it just needs to display simple stuff and cost $0... After knowing that and accepting that fact here we are.

This website is not finished and there is a lot to fix, but I'm happy on how it ended up, and also accepted the fact that TypeScript is not that bad.

This will be all for now, I have ideas for articles to fill up this website a bit, for now that's all!

🐇

It's been a while... 2023 to be exact lol.

Blog

Latest Posts

JavaScript on the server was and still is an error. CVE-2025-66478
NEW

Updated my website (finally)

Blog

Latest Posts

JavaScript on the server was and still is an error. CVE-2025-66478NEW

Updated my website (finally)

JavaScript on the server was and still is an error. CVE-2025-66478
NEW