#deno — Public Fediverse posts

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!

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!

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

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

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

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

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

Today I coded for 4 hours with #OpenCode using GLM 5 instead of Claude Sonnet 4.6. The project is a #Deno app written in #typescript and the agent had to refactor code and HTML layout.

I perceived no difference in capabilities. GLM5 handled edits well, made some mistakes just like Sonnet, and produced output of the same quality.

But GLM 5 is 3x smaller than Sonnet!

Private AI models are wasteful. They're too big, use too much power, and are too expensive to run. #openweight is the future.

A few notes on why #SilverBullet recently migrated from #Deno to #Node https://community.silverbullet.md/t/migrating-silverbullet-plugs-from-deno-to-node/3957/7?u=zef

A few notes on why #SilverBullet recently migrated from #Deno to #Node https://community.silverbullet.md/t/migrating-silverbullet-plugs-from-deno-to-node/3957/7?u=zef

A few notes on why #SilverBullet recently migrated from #Deno to #Node https://community.silverbullet.md/t/migrating-silverbullet-plugs-from-deno-to-node/3957/7?u=zef

A few notes on why #SilverBullet recently migrated from #Deno to #Node https://community.silverbullet.md/t/migrating-silverbullet-plugs-from-deno-to-node/3957/7?u=zef

A few notes on why #SilverBullet recently migrated from #Deno to #Node https://community.silverbullet.md/t/migrating-silverbullet-plugs-from-deno-to-node/3957/7?u=zef

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

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

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

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

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

@poes sejujurnya, gak begitu nganggap lume, karena merasa jadi vendor lock-in tergantung sama kelangsungan hidup #deno, yang terus terang gua ragukan.

@poes sejujurnya, gak begitu nganggap lume, karena merasa jadi vendor lock-in tergantung sama kelangsungan hidup #deno, yang terus terang gua ragukan.

@poes sejujurnya, gak begitu nganggap lume, karena merasa jadi vendor lock-in tergantung sama kelangsungan hidup #deno, yang terus terang gua ragukan.

@poes sejujurnya, gak begitu nganggap lume, karena merasa jadi vendor lock-in tergantung sama kelangsungan hidup #deno, yang terus terang gua ragukan.

Updating my résumé turned into a DRY problem, so I overengineered my résumé.

Or maybe did it exactly right?

https://zeigert.com/posts/2026-04-18-i-kind-of-overengineered-my-resume/

#lume #deno

Updating my résumé turned into a DRY problem, so I overengineered my résumé.

Or maybe did it exactly right?

https://zeigert.com/posts/2026-04-18-i-kind-of-overengineered-my-resume/

#lume #deno

Updating my résumé turned into a DRY problem, so I overengineered my résumé.

Or maybe did it exactly right?

https://zeigert.com/posts/2026-04-18-i-kind-of-overengineered-my-resume/

#lume #deno

Updating my résumé turned into a DRY problem, so I overengineered my résumé.

Or maybe did it exactly right?

https://zeigert.com/posts/2026-04-18-i-kind-of-overengineered-my-resume/

#lume #deno

Updating my résumé turned into a DRY problem, so I overengineered my résumé.

Or maybe did it exactly right?

https://zeigert.com/posts/2026-04-18-i-kind-of-overengineered-my-resume/

#lume #deno

#Optique 1.0.0 is out! If you build #CLI tools with #TypeScript, it might be worth a look.

I started it because I wanted a TypeScript CLI parser that felt more like optparse-applicative than the usual builder-style APIs. You build up small typed parsers, compose them, and TypeScript infers the result. It handles subcommands, option dependencies, shell completion, and man pages, and it runs on #Deno, #Node.js, and #Bun.

For 1.0 I added @optique/env, so env vars can fill in missing flags, and @optique/inquirer, so missing values can fall back to Inquirer.js prompts. I also cleaned up a lot of awkward API edges and fixed a long backlog of completion bugs across five shells.

Packages are on JSR and npm.

https://github.com/dahlia/optique/discussions/796

#Optique 1.0.0 is out! If you build #CLI tools with #TypeScript, it might be worth a look.

I started it because I wanted a TypeScript CLI parser that felt more like optparse-applicative than the usual builder-style APIs. You build up small typed parsers, compose them, and TypeScript infers the result. It handles subcommands, option dependencies, shell completion, and man pages, and it runs on #Deno, #Node.js, and #Bun.

For 1.0 I added @optique/env, so env vars can fill in missing flags, and @optique/inquirer, so missing values can fall back to Inquirer.js prompts. I also cleaned up a lot of awkward API edges and fixed a long backlog of completion bugs across five shells.

Packages are on JSR and npm.

https://github.com/dahlia/optique/discussions/796

#Optique 1.0.0 is out! If you build #CLI tools with #TypeScript, it might be worth a look.

I started it because I wanted a TypeScript CLI parser that felt more like optparse-applicative than the usual builder-style APIs. You build up small typed parsers, compose them, and TypeScript infers the result. It handles subcommands, option dependencies, shell completion, and man pages, and it runs on #Deno, #Node.js, and #Bun.

For 1.0 I added @optique/env, so env vars can fill in missing flags, and @optique/inquirer, so missing values can fall back to Inquirer.js prompts. I also cleaned up a lot of awkward API edges and fixed a long backlog of completion bugs across five shells.

Packages are on JSR and npm.

https://github.com/dahlia/optique/discussions/796

#Optique 1.0.0 is out! If you build #CLI tools with #TypeScript, it might be worth a look.

I started it because I wanted a TypeScript CLI parser that felt more like optparse-applicative than the usual builder-style APIs. You build up small typed parsers, compose them, and TypeScript infers the result. It handles subcommands, option dependencies, shell completion, and man pages, and it runs on #Deno, #Node.js, and #Bun.

For 1.0 I added @optique/env, so env vars can fill in missing flags, and @optique/inquirer, so missing values can fall back to Inquirer.js prompts. I also cleaned up a lot of awkward API edges and fixed a long backlog of completion bugs across five shells.

Packages are on JSR and npm.

https://github.com/dahlia/optique/discussions/796

#Optique 1.0.0 is out! If you build #CLI tools with #TypeScript, it might be worth a look.

I started it because I wanted a TypeScript CLI parser that felt more like optparse-applicative than the usual builder-style APIs. You build up small typed parsers, compose them, and TypeScript infers the result. It handles subcommands, option dependencies, shell completion, and man pages, and it runs on #Deno, #Node.js, and #Bun.

For 1.0 I added @optique/env, so env vars can fill in missing flags, and @optique/inquirer, so missing values can fall back to Inquirer.js prompts. I also cleaned up a lot of awkward API edges and fixed a long backlog of completion bugs across five shells.

Packages are on JSR and npm.

https://github.com/dahlia/optique/discussions/796

tapi bisa jadi kayak #Deno yang bisa import langsung dari URL bukan hanya dari repo.

kalo lihat changelog'snya sepertinya kedepannya bisa pakai begini misalnya

pkg install https://sok.egois.org/pkg/cuek-0.1.txz

tapi soal keamanan gimana ya?

tapi bisa jadi kayak #Deno yang bisa import langsung dari URL bukan hanya dari repo.

kalo lihat changelog'snya sepertinya kedepannya bisa pakai begini misalnya

pkg install https://sok.egois.org/pkg/cuek-0.1.txz

tapi soal keamanan gimana ya?

tapi bisa jadi kayak #Deno yang bisa import langsung dari URL bukan hanya dari repo.

kalo lihat changelog'snya sepertinya kedepannya bisa pakai begini misalnya

pkg install https://sok.egois.org/pkg/cuek-0.1.txz

tapi soal keamanan gimana ya?

tapi bisa jadi kayak #Deno yang bisa import langsung dari URL bukan hanya dari repo.

kalo lihat changelog'snya sepertinya kedepannya bisa pakai begini misalnya

pkg install https://sok.egois.org/pkg/cuek-0.1.txz

tapi soal keamanan gimana ya?