Move yargs and subcommands to node-core
Prerequisites
- [ ] Are you running the latest version(s)?
- [ ] Did you check the debugging guide?
- [ ] Did you check the FAQs and Discussions?
- [ ] Are you reporting to the correct repository?
- [ ] Did you search for an existing issue or pull request?
Description
Since they shared a lot in common, we should move it to node-core package.
Keep in mind we should check if yargs allow us to override command in the network node package.
Details
These details can help to reproduce the environment the issue is occurring
Local Environment: [You can get this information from executing subql version.]
Query Version: [What is the version of the query service?]
Indexer Version: [What is the version of the indexer service?]
Network Details:
- [Network]
- [Block height, a block height where the issue is happening]
- [Dictionary endpoint, if used]
Steps to Reproduce
- [First Step]
- [Second Step]
- [and so on...]
Example project: [A link to a minimal example that can reproduce the issue]
Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Any other information
Is there any other information you would like to add?
Yargs has been moved to node core https://github.com/subquery/subql/pull/2144