-
Notifications
You must be signed in to change notification settings - Fork 8
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
Publish to crates.io? #69
Comments
Tangentially, if the crate could be published to |
@bartlomieju Sorry for the long delay. I plan on cleaning up this repo and publishing everything, but I recently had a new job and it's harder to find time to work on it. I'll try to advance as best as I can this month. I agree, I'll move |
@demurgos thanks for response; for now I just forked and code and put it directly into our codebase; it's working great! Let me know if you need any help with it. |
No problem :) You should still be warned that the Rust version was less tested than the TypeScript one. The TypeScript version is widely used by My immediate goal is to share the tests between the Rust and TypeScript implementations to make sure both codebases agree. Once same tests pass on both sides, I'll publish an initial version to |
Sounds good, having a unified test suite would definitely be a benefit! Looking forward to a release to crates.io, your library saved me a lot of headaches :) |
Hi!
I wanted to use
v8-coverage
in Deno, where we're having some problems with reported coverage (turns out we don't merge ranges properly 🙃); however I'm unable to locate the crate oncrates.io
.Do you plan to publish it in near future?
The text was updated successfully, but these errors were encountered: