I second this notion. I was really excited to try it out, only to have it fail to run most of our projects: * can't use AWS SDK v3 because throws an error when

I second this notion. I was really excited to try it out, only to have it fail to run most of our projects: * can't use AWS SDK v3 because throws an error when parsing a response; * can't use octokit (or anything that depends on jsonwebtoken, for that matter) because node:crypto is not fully implemented; * can’t run our tests, because jest.resetAllMocks() is missing * in another project, bun test failed to even run, complaining about invalid call to shared library So for me the local workflow is “run it with bun, see if it fails, re-run with node if it does”. At least I can always replace npm with it, I guess? Can’t imagine running our services with it just yet. Really excited for the future of the project, because when it works - it really is amazing. But I wouldn’t call it 1.0 if the selling feature is Node compatibility.