home.social

Search

1000 results for “deno_diary”

  1. poes 🇵🇸 @[email protected] ·

    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!

    #lume #deno
  2. poes 🇵🇸 @[email protected] ·

    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!

    #lume #deno
  3. poes 🇵🇸 @[email protected] ·

    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 #lume
  4. Patch Notification Robot 🔔 @[email protected] ·

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

    #deno
  5. Patch Notification Robot 🔔 @[email protected] ·

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

    #deno
  6. Patch Notification Robot 🔔 @[email protected] ·

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

    #deno
  7. Patch Notification Robot 🔔 @[email protected] ·

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

    #deno
  8. Patch Notification Robot 🔔 @[email protected] ·

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

    #deno
  9. Mark Farragher @[email protected] ·

    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.

    #opencode #deno #typescript #openweight
  10. Zef Hemel @[email protected] ·

    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

    #silverbullet #deno #node
  11. Zef Hemel @[email protected] ·

    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

    #silverbullet #deno #node
  12. Zef Hemel @[email protected] ·

    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

    #silverbullet #deno #node
  13. Zef Hemel @[email protected] ·

    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

    #node #deno #silverbullet
  14. Zef Hemel @[email protected] ·

    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

    #silverbullet #deno #node
  15. Patch Notification Robot 🔔 @[email protected] ·

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

    #deno
  16. Patch Notification Robot 🔔 @[email protected] ·

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

    #deno
  17. Patch Notification Robot 🔔 @[email protected] ·

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

    #deno
  18. Patch Notification Robot 🔔 @[email protected] ·

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

    #deno
  19. Patch Notification Robot 🔔 @[email protected] ·

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

    #deno
  20. Thiago, the one they call Jedi @[email protected] ·
    CW: Falando Dev

    Todo dia um novo ataque de suply-chain no NPM. Por isso não abro mão do Deno e suas flags de permissão.

    Acho que meu próximo texto / vídeo vai ser alguma coisa nessa linha...

    #deno

    #deno
  21. Thiago, the one they call Jedi @[email protected] ·
    CW: Falando Dev

    Todo dia um novo ataque de suply-chain no NPM. Por isso não abro mão do Deno e suas flags de permissão.

    Acho que meu próximo texto / vídeo vai ser alguma coisa nessa linha...

    #deno

    #deno
  22. Thiago, the one they call Jedi @[email protected] ·
    CW: Falando Dev

    Todo dia um novo ataque de suply-chain no NPM. Por isso não abro mão do Deno e suas flags de permissão.

    Acho que meu próximo texto / vídeo vai ser alguma coisa nessa linha...

    #deno

    #deno
  23. Thiago, the one they call Jedi @[email protected] ·
    CW: Falando Dev

    Todo dia um novo ataque de suply-chain no NPM. Por isso não abro mão do Deno e suas flags de permissão.

    Acho que meu próximo texto / vídeo vai ser alguma coisa nessa linha...

    #deno

    #deno
  24. Thiago, the one they call Jedi @[email protected] ·
    CW: Falando Dev

    Todo dia um novo ataque de suply-chain no NPM. Por isso não abro mão do Deno e suas flags de permissão.

    Acho que meu próximo texto / vídeo vai ser alguma coisa nessa linha...

    #deno

    #deno
  25. Sek Sakeudeung @[email protected] ·

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

    #deno
  26. Sek Sakeudeung @[email protected] ·

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

    #deno
  27. Sek Sakeudeung @[email protected] ·

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

    #deno
  28. Sek Sakeudeung @[email protected] ·

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

    #deno
  29. Andy Zeigert @[email protected] ·

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

    Or maybe did it exactly right?

    zeigert.com/posts/2026-04-18-i

    #lume #deno

    #lume #deno
  30. Andy Zeigert @[email protected] ·

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

    Or maybe did it exactly right?

    zeigert.com/posts/2026-04-18-i

    #lume #deno

    #lume #deno
Next page