refactor: Update to latest Node v2 (By using cartesi/cli alpha.9) #15
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ify the deployed DApp. Update README
…pect it later on.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Here are code changes to be able to use the latest cartesi/cli with node-v2 and other new supporting libraries (e.g. @cartesi/viem).
My goal is to rollback to communicate only with InputBox rather than going through the DA. At the moment I want to use Comet to test rollups-explorer as it is a complete solution with voucher generation and execution.
Later, we could see what is necessary (another hurdle) to config or set in the CLI to have a working environment with DAs.
CC: @riseandshaheen
Note
Currently I forked the deroll repository and made changes to the
walletpackage and submitted a PR. There is a pull-request open here, but I also packaged the changes for a release on my own repo here, that is what we are using while the PR is on review.Warning
Currently the node ran out of memory pretty quick with some kind of "sigfault" of sorts. Not sure if it is space that has been consumed too quickly with the inspects or something else within my docker settings.