#deno — Public Fediverse posts

Deno Land Inc. released #Deno version 2.8.1. https://deno.com/

Deno Land Inc. released #Deno version 2.8.1. https://deno.com/

Deno Land Inc. released #Deno version 2.8.1. https://deno.com/

Deno Land Inc. released #Deno version 2.8.1. https://deno.com/

Deno Land Inc. released #Deno version 2.8.1. https://deno.com/

Reading #Deno v2.8 release notes:

deno pack [...] builds a Deno or JSR project into an npm-publishable tarball. Given a deno.json, running deno pack produces a [tgz file] that’s ready for npm publish.

Deno 2.8 drops the npm: prefix requirement at the CLI: deno add and deno install now treat unprefixed names as npm packages by default. [...] JSR packages keep the jsr: prefix.

If that's not a eulogy for #JSR, I don't know what is.

https://deno.com/blog/v2.8

Reading #Deno v2.8 release notes:

deno pack [...] builds a Deno or JSR project into an npm-publishable tarball. Given a deno.json, running deno pack produces a [tgz file] that’s ready for npm publish.

Deno 2.8 drops the npm: prefix requirement at the CLI: deno add and deno install now treat unprefixed names as npm packages by default. [...] JSR packages keep the jsr: prefix.

If that's not a eulogy for #JSR, I don't know what is.

https://deno.com/blog/v2.8

Reading #Deno v2.8 release notes:

deno pack [...] builds a Deno or JSR project into an npm-publishable tarball. Given a deno.json, running deno pack produces a [tgz file] that’s ready for npm publish.

Deno 2.8 drops the npm: prefix requirement at the CLI: deno add and deno install now treat unprefixed names as npm packages by default. [...] JSR packages keep the jsr: prefix.

If that's not a eulogy for #JSR, I don't know what is.

https://deno.com/blog/v2.8

Reading #Deno v2.8 release notes:

deno pack [...] builds a Deno or JSR project into an npm-publishable tarball. Given a deno.json, running deno pack produces a [tgz file] that’s ready for npm publish.

Deno 2.8 drops the npm: prefix requirement at the CLI: deno add and deno install now treat unprefixed names as npm packages by default. [...] JSR packages keep the jsr: prefix.

If that's not a eulogy for #JSR, I don't know what is.

https://deno.com/blog/v2.8

Reading #Deno v2.8 release notes:

deno pack [...] builds a Deno or JSR project into an npm-publishable tarball. Given a deno.json, running deno pack produces a [tgz file] that’s ready for npm publish.

Deno 2.8 drops the npm: prefix requirement at the CLI: deno add and deno install now treat unprefixed names as npm packages by default. [...] JSR packages keep the jsr: prefix.

If that's not a eulogy for #JSR, I don't know what is.

https://deno.com/blog/v2.8

Deno 2.8.0 is out. The compatibility work is real: the #Node.js test suite pass rate jumped from 42% to 76.4%, deno install is now a drop-in for npm install, lib.node is included by default, and setTimeout() now returns a NodeJS.Timeout instead of a number. None of that is irrational on its own. Put it together, though, and #Deno starts looking less like an alternative to Node.js and more like a cleaner way to run Node.js-shaped code.

It reminds me of OS/2's Win32 compatibility layer. IBM offered it so developers wouldn't have to choose, but the effect was the opposite: people kept writing Windows apps, and OS/2-native software never got a reason to exist. The closer Deno gets to Node.js, the less reason anyone has to think about whether their code is Deno-aware. Maybe that helps adoption. I just don't see how a Deno-native package culture survives if the winning path is “pretend it's npm.”

Deno 2.8.0 is out. The compatibility work is real: the #Node.js test suite pass rate jumped from 42% to 76.4%, deno install is now a drop-in for npm install, lib.node is included by default, and setTimeout() now returns a NodeJS.Timeout instead of a number. None of that is irrational on its own. Put it together, though, and #Deno starts looking less like an alternative to Node.js and more like a cleaner way to run Node.js-shaped code.

It reminds me of OS/2's Win32 compatibility layer. IBM offered it so developers wouldn't have to choose, but the effect was the opposite: people kept writing Windows apps, and OS/2-native software never got a reason to exist. The closer Deno gets to Node.js, the less reason anyone has to think about whether their code is Deno-aware. Maybe that helps adoption. I just don't see how a Deno-native package culture survives if the winning path is “pretend it's npm.”

Deno 2.8.0 is out. The compatibility work is real: the #Node.js test suite pass rate jumped from 42% to 76.4%, deno install is now a drop-in for npm install, lib.node is included by default, and setTimeout() now returns a NodeJS.Timeout instead of a number. None of that is irrational on its own. Put it together, though, and #Deno starts looking less like an alternative to Node.js and more like a cleaner way to run Node.js-shaped code.

It reminds me of OS/2's Win32 compatibility layer. IBM offered it so developers wouldn't have to choose, but the effect was the opposite: people kept writing Windows apps, and OS/2-native software never got a reason to exist. The closer Deno gets to Node.js, the less reason anyone has to think about whether their code is Deno-aware. Maybe that helps adoption. I just don't see how a Deno-native package culture survives if the winning path is “pretend it's npm.”

Deno 2.8.0 is out. The compatibility work is real: the #Node.js test suite pass rate jumped from 42% to 76.4%, deno install is now a drop-in for npm install, lib.node is included by default, and setTimeout() now returns a NodeJS.Timeout instead of a number. None of that is irrational on its own. Put it together, though, and #Deno starts looking less like an alternative to Node.js and more like a cleaner way to run Node.js-shaped code.

It reminds me of OS/2's Win32 compatibility layer. IBM offered it so developers wouldn't have to choose, but the effect was the opposite: people kept writing Windows apps, and OS/2-native software never got a reason to exist. The closer Deno gets to Node.js, the less reason anyone has to think about whether their code is Deno-aware. Maybe that helps adoption. I just don't see how a Deno-native package culture survives if the winning path is “pretend it's npm.”

Deno 2.8.0 is out. The compatibility work is real: the #Node.js test suite pass rate jumped from 42% to 76.4%, deno install is now a drop-in for npm install, lib.node is included by default, and setTimeout() now returns a NodeJS.Timeout instead of a number. None of that is irrational on its own. Put it together, though, and #Deno starts looking less like an alternative to Node.js and more like a cleaner way to run Node.js-shaped code.

It reminds me of OS/2's Win32 compatibility layer. IBM offered it so developers wouldn't have to choose, but the effect was the opposite: people kept writing Windows apps, and OS/2-native software never got a reason to exist. The closer Deno gets to Node.js, the less reason anyone has to think about whether their code is Deno-aware. Maybe that helps adoption. I just don't see how a Deno-native package culture survives if the winning path is “pretend it's npm.”

Deno Land Inc. released #Deno version 2.8.0. https://deno.com/

Deno Land Inc. released #Deno version 2.8.0. https://deno.com/

Deno Land Inc. released #Deno version 2.8.0. https://deno.com/

Deno Land Inc. released #Deno version 2.8.0. https://deno.com/

Deno Land Inc. released #Deno version 2.8.0. https://deno.com/

🚀✨ "Deno 2.8" promises a universe of features: a #sandbox for your kiddie scripts, a #firewall named after a cartoon dog squad, and a package registry that screams "TypeScript or bust"! Meanwhile, the release post itself has entered a witness protection program. 🤦‍♂️💻
https://deno.com/blog/v2.8 #Deno #2.8 #features #TypeScript #tech #news #HackerNews #ngated

🚀✨ "Deno 2.8" promises a universe of features: a #sandbox for your kiddie scripts, a #firewall named after a cartoon dog squad, and a package registry that screams "TypeScript or bust"! Meanwhile, the release post itself has entered a witness protection program. 🤦‍♂️💻
https://deno.com/blog/v2.8 #Deno #2.8 #features #TypeScript #tech #news #HackerNews #ngated

🚀✨ "Deno 2.8" promises a universe of features: a #sandbox for your kiddie scripts, a #firewall named after a cartoon dog squad, and a package registry that screams "TypeScript or bust"! Meanwhile, the release post itself has entered a witness protection program. 🤦‍♂️💻
https://deno.com/blog/v2.8 #Deno #2.8 #features #TypeScript #tech #news #HackerNews #ngated

🚀✨ "Deno 2.8" promises a universe of features: a #sandbox for your kiddie scripts, a #firewall named after a cartoon dog squad, and a package registry that screams "TypeScript or bust"! Meanwhile, the release post itself has entered a witness protection program. 🤦‍♂️💻
https://deno.com/blog/v2.8 #Deno #2.8 #features #TypeScript #tech #news #HackerNews #ngated

🚀✨ "Deno 2.8" promises a universe of features: a #sandbox for your kiddie scripts, a #firewall named after a cartoon dog squad, and a package registry that screams "TypeScript or bust"! Meanwhile, the release post itself has entered a witness protection program. 🤦‍♂️💻
https://deno.com/blog/v2.8 #Deno #2.8 #features #TypeScript #tech #news #HackerNews #ngated

Deno 2.8

https://deno.com/blog/v2.8

#HackerNews #Deno #Deno2.8 #JavaScript #WebDevelopment #TechNews

Deno 2.8

https://deno.com/blog/v2.8

#HackerNews #Deno #Deno2.8 #JavaScript #WebDevelopment #TechNews

Deno 2.8

https://deno.com/blog/v2.8

#HackerNews #Deno #Deno2.8 #JavaScript #WebDevelopment #TechNews

Deno 2.8

https://deno.com/blog/v2.8

#HackerNews #Deno #Deno2.8 #JavaScript #WebDevelopment #TechNews

Deno 2.8

https://deno.com/blog/v2.8

#HackerNews #Deno #Deno2.8 #JavaScript #WebDevelopment #TechNews

zed-live-server plugins tidak bisa jalan baik di Gram karena belum sempurna support code actions.

jadi gw ngadi - ngadi pakai live-server dari #Deno saja dan nemu ini yang setelah ane coba jadi mudah dan memudahkan (apalagi ringan).

https://jsr.io/@metalbolicx/httpath

jalankan saja langsung dengan beberapa pengaturan diijinkan dan boom! langsung jalan.

sedangkan alternatif lain adalah jsr:@kastrophony/live-server' ini juga asyik atau https://jsr.io/@bbcwqx/live-server

banyak pilihan, bersyukur deh Alhamdulillah

zed-live-server plugins tidak bisa jalan baik di Gram karena belum sempurna support code actions.

jadi gw ngadi - ngadi pakai live-server dari #Deno saja dan nemu ini yang setelah ane coba jadi mudah dan memudahkan (apalagi ringan).

https://jsr.io/@metalbolicx/httpath

jalankan saja langsung dengan beberapa pengaturan diijinkan dan boom! langsung jalan.

sedangkan alternatif lain adalah jsr:@kastrophony/live-server' ini juga asyik atau https://jsr.io/@bbcwqx/live-server

banyak pilihan, bersyukur deh Alhamdulillah

zed-live-server plugins tidak bisa jalan baik di Gram karena belum sempurna support code actions.

jadi gw ngadi - ngadi pakai live-server dari #Deno saja dan nemu ini yang setelah ane coba jadi mudah dan memudahkan (apalagi ringan).

https://jsr.io/@metalbolicx/httpath

jalankan saja langsung dengan beberapa pengaturan diijinkan dan boom! langsung jalan.

sedangkan alternatif lain adalah jsr:@kastrophony/live-server' ini juga asyik atau https://jsr.io/@bbcwqx/live-server

banyak pilihan, bersyukur deh Alhamdulillah

zed-live-server plugins tidak bisa jalan baik di Gram karena belum sempurna support code actions.

jadi gw ngadi - ngadi pakai live-server dari #Deno saja dan nemu ini yang setelah ane coba jadi mudah dan memudahkan (apalagi ringan).

https://jsr.io/@metalbolicx/httpath

jalankan saja langsung dengan beberapa pengaturan diijinkan dan boom! langsung jalan.

sedangkan alternatif lain adalah jsr:@kastrophony/live-server' ini juga asyik atau https://jsr.io/@bbcwqx/live-server

banyak pilihan, bersyukur deh Alhamdulillah

Can someone please explain to me the point of the #bun rewrite? Doesn't rewriting it in #rust from #zig not just make it #deno? Actual question here.

#opensource #javascript

Can someone please explain to me the point of the #bun rewrite? Doesn't rewriting it in #rust from #zig not just make it #deno? Actual question here.

#opensource #javascript

Can someone please explain to me the point of the #bun rewrite? Doesn't rewriting it in #rust from #zig not just make it #deno? Actual question here.

#opensource #javascript

Can someone please explain to me the point of the #bun rewrite? Doesn't rewriting it in #rust from #zig not just make it #deno? Actual question here.

#opensource #javascript

Can someone please explain to me the point of the #bun rewrite? Doesn't rewriting it in #rust from #zig not just make it #deno? Actual question here.

#opensource #javascript

this vibe coded PR with 1,000,000+ additions is just open-source ransomware with prettier commit messages.

shoutout to the brave soul reviewing:

"LGTM" after skimming 14 lines… 🤡

uninstalling immediately!

https://github.com/oven-sh/bun/pull/30412

#npm #yarn #pnpm #bun #deno #js #javascript #typescript

this vibe coded PR with 1,000,000+ additions is just open-source ransomware with prettier commit messages.

shoutout to the brave soul reviewing:

"LGTM" after skimming 14 lines… 🤡

uninstalling immediately!

https://github.com/oven-sh/bun/pull/30412

#npm #yarn #pnpm #bun #deno #js #javascript #typescript

this vibe coded PR with 1,000,000+ additions is just open-source ransomware with prettier commit messages.

shoutout to the brave soul reviewing:

"LGTM" after skimming 14 lines… 🤡

uninstalling immediately!

https://github.com/oven-sh/bun/pull/30412

#npm #yarn #pnpm #bun #deno #js #javascript #typescript

this vibe coded PR with 1,000,000+ additions is just open-source ransomware with prettier commit messages.

shoutout to the brave soul reviewing:

"LGTM" after skimming 14 lines… 🤡

uninstalling immediately!

https://github.com/oven-sh/bun/pull/30412

#npm #yarn #pnpm #bun #deno #js #javascript #typescript

karena #Deno Deploy kasih ane region EU dan US, blog ane kayak nyendat dikit diakses dari Indo. Apa perlu pindahan yes?

karena #Deno Deploy kasih ane region EU dan US, blog ane kayak nyendat dikit diakses dari Indo. Apa perlu pindahan yes?

karena #Deno Deploy kasih ane region EU dan US, blog ane kayak nyendat dikit diakses dari Indo. Apa perlu pindahan yes?

karena #Deno Deploy kasih ane region EU dan US, blog ane kayak nyendat dikit diakses dari Indo. Apa perlu pindahan yes?

gw deploy #Lume ke #Deno pas build OK selesai dengan lancar, pas deploy dapat error seperti ini

JSR package version manifest for '@std/[email protected]' failed to load: Specifier not found in cache: "https://jsr.io/@std/cli/1.0.29_meta.json", --cached-only is specified.
    at https://jsr.io/@std/http/1.0.25/file_server.ts:51:27

error: JSR package version manifest for '@std/[email protected]' failed to load: Specifier not found in cache: "https://jsr.io/@std/cli/1.0.29_meta.json", --cached-only is specified.
    at https://jsr.io/@std/http/1.0.25/file_server.ts:51:27

JSR package version manifest for '@std/[email protected]' failed to load: Specifier not found in cache: "https://jsr.io/@std/cli/1.0.29_meta.json", --cached-only is specified.
    at https://jsr.io/@std/http/1.0.25/file_server.ts:51:27

error: JSR package version manifest for '@std/[email protected]' failed to load: Specifier not found in cache: "https://jsr.io/@std/cli/1.0.29_meta.json", --cached-only is specified.
    at https://jsr.io/@std/http/1.0.25/file_server.ts:51:27

gw hapus deno.lock, terus rubah "lock": false menjadi true. Reload cache dan build ulang. Proses build selesai tapi deploy masih bermasalah.

coba update @std/cli ke 1.0.29 secara manual dengan deno cache --reload jsr:@std/[email protected] kemudian update isi deno.lock dengan deno cache --frozen=false _config.ts dan build ulang.

build sukses, deploy sukses. Cakep!

gw deploy #Lume ke #Deno pas build OK selesai dengan lancar, pas deploy dapat error seperti ini

JSR package version manifest for '@std/[email protected]' failed to load: Specifier not found in cache: "https://jsr.io/@std/cli/1.0.29_meta.json", --cached-only is specified.
    at https://jsr.io/@std/http/1.0.25/file_server.ts:51:27

error: JSR package version manifest for '@std/[email protected]' failed to load: Specifier not found in cache: "https://jsr.io/@std/cli/1.0.29_meta.json", --cached-only is specified.
    at https://jsr.io/@std/http/1.0.25/file_server.ts:51:27

JSR package version manifest for '@std/[email protected]' failed to load: Specifier not found in cache: "https://jsr.io/@std/cli/1.0.29_meta.json", --cached-only is specified.
    at https://jsr.io/@std/http/1.0.25/file_server.ts:51:27

error: JSR package version manifest for '@std/[email protected]' failed to load: Specifier not found in cache: "https://jsr.io/@std/cli/1.0.29_meta.json", --cached-only is specified.
    at https://jsr.io/@std/http/1.0.25/file_server.ts:51:27

gw hapus deno.lock, terus rubah "lock": false menjadi true. Reload cache dan build ulang. Proses build selesai tapi deploy masih bermasalah.

coba update @std/cli ke 1.0.29 secara manual dengan deno cache --reload jsr:@std/[email protected] kemudian update isi deno.lock dengan deno cache --frozen=false _config.ts dan build ulang.

build sukses, deploy sukses. Cakep!

gw deploy #Lume ke #Deno pas build OK selesai dengan lancar, pas deploy dapat error seperti ini

JSR package version manifest for '@std/[email protected]' failed to load: Specifier not found in cache: "https://jsr.io/@std/cli/1.0.29_meta.json", --cached-only is specified.
    at https://jsr.io/@std/http/1.0.25/file_server.ts:51:27

error: JSR package version manifest for '@std/[email protected]' failed to load: Specifier not found in cache: "https://jsr.io/@std/cli/1.0.29_meta.json", --cached-only is specified.
    at https://jsr.io/@std/http/1.0.25/file_server.ts:51:27

JSR package version manifest for '@std/[email protected]' failed to load: Specifier not found in cache: "https://jsr.io/@std/cli/1.0.29_meta.json", --cached-only is specified.
    at https://jsr.io/@std/http/1.0.25/file_server.ts:51:27

error: JSR package version manifest for '@std/[email protected]' failed to load: Specifier not found in cache: "https://jsr.io/@std/cli/1.0.29_meta.json", --cached-only is specified.
    at https://jsr.io/@std/http/1.0.25/file_server.ts:51:27

gw hapus deno.lock, terus rubah "lock": false menjadi true. Reload cache dan build ulang. Proses build selesai tapi deploy masih bermasalah.

coba update @std/cli ke 1.0.29 secara manual dengan deno cache --reload jsr:@std/[email protected] kemudian update isi deno.lock dengan deno cache --frozen=false _config.ts dan build ulang.

build sukses, deploy sukses. Cakep!