Been working on this for the past few months. I think its stable enough for other developers to start building on and next release of noStrudel is going to be using it as the core
nostr:naddr1qvzqqqr4gupzqfngzhsvjggdlgeycm96x4emzjlwf8dyyzdfg4hefp89zpkdgz99qyf8wumn8ghj7mn0wd68yat99e3k7mf0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qqmv9c8qmr9wdsh2cm994mrzt3s9ccz6dp0xguj7v3sxg6sqczaw4
For the non-devs - what is applesauce nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr ?
A toolbox for nostr web clients and a competitor to NDK
Its main focus is being modular and letting the developer pick and choose which parts they want to use.
Top 😍😍🤟
I don’t know what it is but it does sound delicious…Apple sauce 😁
Nice!
Would love to see it on JSR, since it's all TypeScript anyway.
How do I publish to JSR? I'm using https://github.com/changesets/changesets to manage changelogs and publish versions
The docs are here: https://jsr.io/docs/publishing-packages
I would try one of the manual options first, but it's also easy to do from a GitHub Action later: https://jsr.io/docs/publishing-packages#publishing-from-github-actions
It should not be put on both, or it will create dependency resolution issues where if two packages depend on it from different registries, bundlers can't remove the duplicate. As much as I love JSR.
Good to know, thanks. Would it be enough to have it in a namespace on one of the two?
I can’t recommend it enough. Its CQRS/Event Sourcing approach fits Nostr clients perfectly. I’ve been using the previous unstable version for months and the only issue I found is now fixed in this release. Great job nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0ep332w 👏
I've been using it with gitworkshop.dev for a while and I'm very happy with it. You can pick and choose the parts of it you want use and what bit you want a custom implementation for. Its an really flexible library.
