-
-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add tests workflow for bun and deno #423
base: feature/deno
Are you sure you want to change the base?
Conversation
1d52066
to
dac0775
Compare
while I see the improvement on the source code, like not to import I guess we need to put this on hold until we have final approach on which javascript runtime that lodestar want to experiment ChainSafe/lodestar#7237 |
Deno is needed/recommended to publish packages to jsr.io which is intention to test with deno first in this PR. And here is the details that why I am moving to support jsr.io https://jsr.io/docs/why |
Does Bun support jsr.io? if yes I'd go with Bun as we'll most likely to go with it. Again, need to wait for the final decision on ChainSafe/lodestar#7237 if both NodeJS + Bun don't support jsr.io, only Deno does then we need to see if it's a must to support jsr.io. I found it weird to target Bun/NodeJS while having Deno specific resources in the repo |
jsr.io is a registry developed and maintained by Bun for typescript based packages. As it follow modern standards it's compatible with all runtimes. As it's mentioned on there website.
|
This reverts commit 344b389.
Motivation
Make the packages compatible with Deno+Bun.
Description
Steps to test or reproduce