More relevant than ever: you can find my other social profiles on my website: lcas.dev/. I hope to see many of your there soon!
(no direct links because the almighty overlord blocks them now)
I am very proud of the team for the runtime level mitigation we rolled out to @deno_land Deploy for this. It's very precise, very fast, and way less prone to false positives than a WAF based block.
All React reversions are safe when running on Deno Deploy. Vertical integration!
There is critical vulnerability in React Server Components disclosed as CVE-2025-55182 that impacts React 19 and frameworks that use it.
A fix has been published in React versions 19.0.1, 19.1.2, and 19.2.1. We recommend upgrading immediately.
react.dev/blog/2025/12/03/crβ¦
We've published our official JavaScript SDK on @jsr_io. In Deno, we can use web standard interfaces like WebSocket on the server, as in this example with the Realtime API. Let us know what you think! π¦
Full transparency: someone from both @ncsc_nl and the incident response team from @Logius_minbzk reached out to me and are working on resolution. The system does work after all - report issues folks!
And thanks folks :)
I sent a CVD report to @ncsc_nl's CERT, and they are being wholly unhelpful. Do I know anyone that works on DigiD or other cyber security stuff at @Rijksoverheid? Is there a report channel for DigiD directly that bypasses NCSC?
I sent a CVD report to @ncsc_nl's CERT, and they are being wholly unhelpful. Do I know anyone that works on DigiD or other cyber security stuff at @Rijksoverheid? Is there a report channel for DigiD directly that bypasses NCSC?
It's done. Now itβs your turn, @Oracle.
Weβve submitted a formal petition to cancel the JavaScript trademark: it is generic, Oracle has abandoned it, and Oracle committed fraud on the USPTO during the last trademark renewal.
Oracle has until January 4th to respond, or the case will go into default, which will result in the trademark being canceled.
It's time to #FreeJavaScript.
deno.com/blog/deno-v-oracle
You're invited to another open working meeting this Friday, 10am PT, to discuss:
βοΈ review draft of governance document and provide feedback
βοΈ discuss pain points with JSR and brainstorm solutions
RSVP: deno.co/jsr-meeting
We just finished our first JSR working group meeting. We discussed a bit on moving JSR into a foundation, and various other things including finances and roadmap.
More in thread π§΅
Finally, we are looking for engineering help on JSR. JSR is open source and written in Rust and TypeScript. We have many issues that you could work on, including some labeled good-first-issue. Check them out on github.com/jsr-io, and contribute!
This Friday at 9am PT we will convene the first JSR working group meeting. We invite you to join this recurring open meeting where we answer questions, respond to feedback, and collectively plan and discuss the future roadmap of JSR.
deno.co/jsr-meeting