Search
1000 results for “deno_land”
-
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:27gw hapus
deno.lock, terus rubah"lock": falsemenjaditrue. Reload cache dan build ulang. Proses build selesai tapi deploy masih bermasalah.coba update
@std/clike 1.0.29 secara manual dengandeno cache --reload jsr:@std/[email protected]kemudian update isideno.lockdengandeno cache --frozen=false _config.tsdan build ulang.build sukses, deploy sukses. Cakep!
-
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...
-
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...
-
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...
-
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...
-
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...
-
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/
-
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.txztapi 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.txztapi 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.txztapi 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.txztapi soal keamanan gimana ya?
-
I liked Excalidraw so I wanted to make a self-hosted version. It's FOSS, so I just had to take the library and make it load boards hosted on my server. Seems easy, right?
So, if it seems easy, I can just use #Deno and run deno bundle, so I don't need to care about node_modules, right? Well, it worked, but...
It cannot import CSS from NPM modules, so I had to import them using a hack, and, because it's importing without node_modules, I can't do hacky editing of the library to implement a change (that lots of people proposed but no PR was merged at the moment). Also, I had to use hacky things to allow my code to use the built-in icons, which aren't exported by the library.
So, most of issues are on Excalidraw side, but working around them was easier with Vite and Node.js than with Deno.
-
I liked Excalidraw so I wanted to make a self-hosted version. It's FOSS, so I just had to take the library and make it load boards hosted on my server. Seems easy, right?
So, if it seems easy, I can just use #Deno and run deno bundle, so I don't need to care about node_modules, right? Well, it worked, but...
It cannot import CSS from NPM modules, so I had to import them using a hack, and, because it's importing without node_modules, I can't do hacky editing of the library to implement a change (that lots of people proposed but no PR was merged at the moment). Also, I had to use hacky things to allow my code to use the built-in icons, which aren't exported by the library.
So, most of issues are on Excalidraw side, but working around them was easier with Vite and Node.js than with Deno.
-
I liked Excalidraw so I wanted to make a self-hosted version. It's FOSS, so I just had to take the library and make it load boards hosted on my server. Seems easy, right?
So, if it seems easy, I can just use #Deno and run deno bundle, so I don't need to care about node_modules, right? Well, it worked, but...
It cannot import CSS from NPM modules, so I had to import them using a hack, and, because it's importing without node_modules, I can't do hacky editing of the library to implement a change (that lots of people proposed but no PR was merged at the moment). Also, I had to use hacky things to allow my code to use the built-in icons, which aren't exported by the library.
So, most of issues are on Excalidraw side, but working around them was easier with Vite and Node.js than with Deno.
-
@geerlingguy it's gotten really bad. That's why for a while now I've only been developing in a DevContainer. For my side projects, I'm relying more and more on #Deno, as I hope its security architecture will prevent exactly these kinds of threats.
-
I guess I will have to migrate to Deno Deploy to something else as they messed up the migration from their old platform to the new one so badly that I can't access the new platform, I can't access the old platform, and I can't even open tickets there. I wonder if they slop coded it!
Not a huge issue, I chose Deno exactly because it's easy to switch off their platform. On the other hand, my coworker wanted to use Firebase. :HoloLaugh:
-
BotKitは、ActivityPubボットを作るためのTypeScriptフレームワークです。既存のMastodon/Misskeyボットとの違いは、ボット自体が独立したサーバーとして動作すること。プラットフォームのアカウントは不要です。
文字数制限もなければ、APIレート制限に悩まされることもありません。
bot.onMention = async (session, message) => { await message.reply(text`こんにちは、${message.actor}さん！`); };フェデレーション、HTTP Signatures、配送キューといったActivityPub周りの処理はFedifyがすべて引き受けます。ボットのロジックを書くだけです。
DenoでもNode.jsでも動きます。
-
BotKitは、ActivityPubボットを作るためのTypeScriptフレームワークです。既存のMastodon/Misskeyボットとの違いは、ボット自体が独立したサーバーとして動作すること。プラットフォームのアカウントは不要です。
文字数制限もなければ、APIレート制限に悩まされることもありません。
bot.onMention = async (session, message) => { await message.reply(text`こんにちは、${message.actor}さん！`); };フェデレーション、HTTP Signatures、配送キューといったActivityPub周りの処理はFedifyがすべて引き受けます。ボットのロジックを書くだけです。
DenoでもNode.jsでも動きます。
-
BotKitは、ActivityPubボットを作るためのTypeScriptフレームワークです。既存のMastodon/Misskeyボットとの違いは、ボット自体が独立したサーバーとして動作すること。プラットフォームのアカウントは不要です。
文字数制限もなければ、APIレート制限に悩まされることもありません。
bot.onMention = async (session, message) => { await message.reply(text`こんにちは、${message.actor}さん！`); };フェデレーション、HTTP Signatures、配送キューといったActivityPub周りの処理はFedifyがすべて引き受けます。ボットのロジックを書くだけです。
DenoでもNode.jsでも動きます。
-
BotKitは、ActivityPubボットを作るためのTypeScriptフレームワークです。既存のMastodon/Misskeyボットとの違いは、ボット自体が独立したサーバーとして動作すること。プラットフォームのアカウントは不要です。
文字数制限もなければ、APIレート制限に悩まされることもありません。
bot.onMention = async (session, message) => { await message.reply(text`こんにちは、${message.actor}さん！`); };フェデレーション、HTTP Signatures、配送キューといったActivityPub周りの処理はFedifyがすべて引き受けます。ボットのロジックを書くだけです。
DenoでもNode.jsでも動きます。
-
BotKit은 ActivityPub 봇을 만드는 #TypeScript 프레임워크입니다. 일반적인 Mastodon/Misskey 봇과 다른 점은, 봇 자체가 독립된 서버로 돌아간다는 겁니다. 플랫폼 계정이 필요 없습니다.
글자 수 제한도 없고, API 호출 제한에 시달릴 일도 없습니다.
bot.onMention = async (session, message) => { await message.reply(text`안녕하세요, ${message.actor}님!`); };연합(federation), HTTP Signatures, 메시지 전달 같은 #ActivityPub 관련 처리는 Fedify가 알아서 해줍니다. 봇 로직만 짜면 되는 거죠.
-
BotKit은 ActivityPub 봇을 만드는 #TypeScript 프레임워크입니다. 일반적인 Mastodon/Misskey 봇과 다른 점은, 봇 자체가 독립된 서버로 돌아간다는 겁니다. 플랫폼 계정이 필요 없습니다.
글자 수 제한도 없고, API 호출 제한에 시달릴 일도 없습니다.
bot.onMention = async (session, message) => { await message.reply(text`안녕하세요, ${message.actor}님!`); };연합(federation), HTTP Signatures, 메시지 전달 같은 #ActivityPub 관련 처리는 Fedify가 알아서 해줍니다. 봇 로직만 짜면 되는 거죠.
-
BotKit은 ActivityPub 봇을 만드는 #TypeScript 프레임워크입니다. 일반적인 Mastodon/Misskey 봇과 다른 점은, 봇 자체가 독립된 서버로 돌아간다는 겁니다. 플랫폼 계정이 필요 없습니다.
글자 수 제한도 없고, API 호출 제한에 시달릴 일도 없습니다.
bot.onMention = async (session, message) => { await message.reply(text`안녕하세요, ${message.actor}님!`); };연합(federation), HTTP Signatures, 메시지 전달 같은 #ActivityPub 관련 처리는 Fedify가 알아서 해줍니다. 봇 로직만 짜면 되는 거죠.
