-
Notifications
You must be signed in to change notification settings - Fork 28
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
Depending on @substrate/txwrapper-dev
#314
Comments
Yea feel free to totally use this package. It was always intended to be a dev package for testing in txwrapper-*, but if you find merit in using it then I would say feel free to use it. I will update the README as this has changed. That being said there is some drawbacks. One drawback to using |
I think it's a trade-off we can accept. Furthermore, since it is an open-source project, we can always contribute to the development work here to ease and fasten the iterations |
Awesome, sounds really great :) We are more than happy at doing weekly releases at the beginning of every week as well! |
Greetings! 👋
We are currently working on an open-source library that aims to facilitate offline decoding of Polkadot and Westend transactions. While exploring potential dependencies, we came across the
@substrate/txwrapper-dev
package, which offers numerous useful functions for our purpose. However, we noticed that it appears in your README under the "non-published" section, although the package is indeed published onnpm
. This led us to wonder whether it is acceptable to include it as a dependency in our project.Can you advise us if depending on
@substrate/txwrapper-dev
is recommended or if we should instead duplicate the relevant parts of the code in our library?Thank you for your attention, and we look forward to your guidance on this matter.
The text was updated successfully, but these errors were encountered: