-
-
Notifications
You must be signed in to change notification settings - Fork 504
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
🐛 @biomejs/js-api not compatible with @biomejs/wasm-nodejs 1.9.0 #3881
🐛 @biomejs/js-api not compatible with @biomejs/wasm-nodejs 1.9.0 #3881
Comments
though |
Running into this issue as well. Can it be improved by having a CI release the |
I think the main problem is that we don't have any integration tests for it. PRs welcome. |
Is there any temporary solution for this before a new version is released with a fix? (Not downgrade) |
Sorry, I don't think so. You are welcome to help improve the situation though. |
@ematipico thanks for fix. @ericrafalovsky did you test with latest release
|
This hasn't bee released yet |
this is fixed now, |
Environment information
What happened?
The latest versions of
biomejs/js-api
(0.6.2) and@biomejs/wasm-nodejs
(1.9.0) appear to be incompatible.When trying an example similar to that in the README
it crashes with an error of the form:
Error: missing field
kind. This does not happen with @biomejs/wasm-nodejs
1.8.3. and appears to be a compatibility issue.I see that
biomejs/js-api
"is currently in alpha" and perhaps it's expected for it to not be compatible with the latest releases of@biomejs/wasm-nodejs
/@biomejs/biome
?Expected result
It should not throw an error
Code of Conduct
The text was updated successfully, but these errors were encountered: