-
Notifications
You must be signed in to change notification settings - Fork 142
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
Export o1js testing framework #2013
Comments
see #1677 |
What will be the dependency tree between o1js, the o1js-testing-utils package, and some third party package that uses both? |
@45930 this should eventually be made available to external developers |
Got it. Are you opposed to exporting a simple version to developers now and eventually making it better, rather than the inverse? Specifically, we would like to use it in a library we are building. The alternative is to just put more code into o1js that doesn't have to be there, but if we could get the tools we want to use out faster, we could start adding more things as libraries as well. |
Export testing utilities from src/lib/testing to the npm package to enable their use by third party library developers.
The text was updated successfully, but these errors were encountered: