-
Notifications
You must be signed in to change notification settings - Fork 1
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
ON- HOLD Restructure the WASM deploy tool to be used as CLI tool #10
Labels
Comments
Hey team! Please add your planning poker estimate with Zenhub @ebma @TorstenStueber |
@gianfra-t what stopping this ticket from getting closed? Is it already reviewed? |
It's on hold: #24 (comment) |
Thanks for informing will add that label as on-hold |
@gianfra-t whats the latest update here? still on hold? |
@prayagd Still on hold. And it will require some re-work once the mentioned blocking issue is finished. |
gianfra-t
changed the title
Restructure the WASM deploy tool to be used as CLI tool
ON- HOLD Restructure the WASM deploy tool to be used as CLI tool
Mar 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
Ticket related to make the WASM deploy tool usable to for builders other than Nabla.
Requirement
Currently wasm-deploy contains a sample project in its own repository and works only with this sample project. Instead of this wasm-deploy should be a standalone tool that is agnostic of a particular project and can should be usable for any other npm project.
Wasm-deploy should contain a bin tool so that after adding it as a dependency in a 3rd party project it should be possible to add an npm script of the form
npm wasm-deploy
to that 3rd party project.On-Hold
Waiting for this issue to be completed, which will move the Nabla deployment scripts to the corresponding Nabla repository.
The text was updated successfully, but these errors were encountered: