Conversation

Notices

1. Embed this notice
   洪 民憙 (Hong Minhee) (hongminhee@todon.eu)'s status on Thursday, 28-Mar-2024 18:05:22 JST 洪 民憙 (Hong Minhee)

   I was quite impressed with the result of the above poll, and am going to work on the non-#Deno compatibility of Fedify for the time being. Here's #Fedify's rough roadmap:

   https://github.com/dahlia/fedify/discussions/24

   #fedidev #ActivityPub

   • Embed this notice
     洪 民憙 (Hong Minhee) (hongminhee@todon.eu)'s status on Friday, 29-Mar-2024 10:52:37 JST 洪 民憙 (Hong Minhee)

     in reply to

     • gwil

     @gwil That phrase, I'm going to have to use it in Fedify!

   • Embed this notice
     gwil (gwil@post.lurk.org)'s status on Friday, 29-Mar-2024 10:52:38 JST gwil

     in reply to

     @hongminhee I have found the phrase “Deno is used as the development runtime” a really useful one for newcomers to my projects. dnt does the rest!

   • Embed this notice
     洪 民憙 (Hong Minhee) (hongminhee@todon.eu)'s status on Friday, 29-Mar-2024 15:24:29 JST 洪 民憙 (Hong Minhee)

     in reply to

     Progress report, March 29, 2024.

     Work on Node.js compatibility is currently being done in the dnt branch (the branch name may not be appropriate, but I like it because it's short).

     I've added the dnt.ts script in the root of the repository. It's not working yet—I'm getting the error below, and I'm trying to figure out a solution:

     TS2725: Class name cannot be 'Object' when targeting ES5 with module CommonJS.

     I added KvStore and MessageQueue interfaces, an abstraction layer for key-value storage and message queues. Although there are a couple of implementations for development purposes called MemoryKvStore and InProcessMessageQueue, they are not meant to be used in production.

     I haven't implemented an adapter for Deno KV yet, so it is not usable in #Fedify. Implementing the adapters for it itself isn't hard, it's the packaging that's the problem. Anyway, this regression is only temporary during development and will go away in the general release.

     It was pre-released to JSR as version 0.5.0-dev.79+562c62cf, and you can test it out:

     https://jsr.io/@fedify/fedify@0.5.0-dev.79+562c62cf

     https://github.com/dahlia/fedify/discussions/24#discussioncomment-8948476

   • Embed this notice
     洪 民憙 (Hong Minhee) (hongminhee@todon.eu)'s status on Friday, 29-Mar-2024 18:14:58 JST 洪 民憙 (Hong Minhee)

     in reply to

     • thomas 🌸
     • gwil

     @gwil It would be nice if dnt's deno shim would also replace the Deno KV API with the @deno/kv package, which @thomasreggi tried to do late last year, but unfortunately it didn't merge.

     https://github.com/denoland/node_shims/pull/164

   • Embed this notice
     gwil (gwil@post.lurk.org)'s status on Friday, 29-Mar-2024 18:15:00 JST gwil

     in reply to

     @hongminhee By all means, do! Funnily enough, what I’m working on seems to have a lot of overlap with Fedify (e.g. needing generic KV drivers). I was hoping to use the NPM version of Deno KV for Node, but it seems it’s not quite equivalent to Deno.KV on Deno (?)