Skip to content
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

10 restructure the wasm deploy tool to be used as cli tool #24

Draft
wants to merge 8 commits into
base: 22-add-experimental-test-command
Choose a base branch
from

Conversation

gianfra-t
Copy link
Contributor

@gianfra-t gianfra-t commented Sep 21, 2023

Minor restructure to allow the tool to be used as a globally installed npm package cli tool. Branched from #22.

Readme file show the proposed steps to use it (wasm-deploy needs to be deployed to npm to work.
For now, to test locally:

  • Cd to api-solang and build using npm run build
  • Build the cli tool in the root folder with npm run build
  • Run npm install -g .
  • When running wasm-deploy init <project> an error will show since the package is not on npm. Run npm link wasm-deploy to overcome this.
  • Install typescript in the project npm install typescript

@gianfra-t gianfra-t changed the base branch from main to 22-add-experimental-test-command October 24, 2023 18:39
@TorstenStueber
Copy link
Member

@gianfra-t part of this PR should be that any references to Nabla are completely removed. This means that the Nabla deployment commands should be moved to the Nabla repository instead.

This is part of this ticket in the Nabla contract repository: https://github.com/0xamberhq/contracts/issues/73.

Once the above ticket is complete, we can continue with this PR here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ON- HOLD Restructure the WASM deploy tool to be used as CLI tool
2 participants