Gregory's ServerDeno 2.1 is out 🎉️
✈️️ first class Wasm support
🌳️ Long Term Support branch
⭐️ Improved dependency management
and much more!
#deno #node #javascript #nodejs #typescript #webdev #npm #wasm
|
10 posts total
4 years after Deno 1.0, the next generation of JavaScript is ready for production at scale. Deno 2 is out today Deno 2 Release Candidate has dropped: ‣ Add `process` global variable, remove `window`  @deno_land I guess there are no plans to fix importing from source, and broken local development, with the new JSR/deno.json package stuff prior to Deno 2.0? seems a glaring oversight to me [1] https://github.com/jsr-io/jsr/issues/133#issuecomment-2274239545 [2] https://dbushell.com/2024/08/09/jsr-and-deno-final-review/#deno-ish I don't understand why Deno didn't just go full adoption of package.json and copy Node, it's objectively superior.
Show previous comments
 @deno_land am I the only one that doesn’t see any issue with this? From the page: > Unlike typical trademark holders who protect their trademarks by extracting licensing fees or enforcing usage restrictions, Oracle has allowed the JavaScript name to be used by anyone. Doesn’t that mean you should just ignore the trademark? Imagine the confusion that would arise if a random third party created "Javascript Conf". Deno 1.46 is not only the last 1.x release, but also one of the biggest: #Deno 1.39 is released! - WebGPU support Read more:  @deno_land What I actually want is for you to give me the source code to Deno Deploy, because I don't trust that you won't censor my users.
|
@deno_land Long Term Support = 6 months
@deno_land
And Deno Deploy?
Console logging
`Deno ${Deno.version.deno} (${navigator.userAgent.toLowerCase()})`
still writes just
"Deno (deno/1.46.3)"
@deno_land "Deno v2.1 is the first LTS release of Deno. The v2.1 branch will receive important bug fixes and performance improvements for the next six months."
Long-term.