ctaggart opened issue #7192:
Feature
Publish wasmtime builds to npmjs.com.
Benefit
It will make getting wasmtime installed easier in many situations. For example, component component situations.
Implementation
I think it is probably best to map directly to your existing binaries and create:
- @bytecodealliance/wasmtime-cli-aarch64-linux@13.0.0
- @bytecodealliance/wasmtime-cli-aarch64-macos@13.0.0
- @bytecodealliance/wasmtime-cli-riscv64gc-linux@13.0.0
- @bytecodealliance/wasmtime-cli-s390x-linux@13.0.0
- @bytecodealliance/wasmtime-cli-x86_64-linux@13.0.0
- @bytecodealliance/wasmtime-cli-x86_64-macos@13.0.0
- @bytecodealliance/wasmtime-cli-x86_64-mingw@13.0.0
- @bytecodealliance/wasmtime-cli-x86_64-windows@13.0.0
I tried it out, but with just x86_64 builds.
https://www.npmjs.com/package/@cataggar/wasmtime-cli-linux
https://www.npmjs.com/package/@cataggar/wasmtime-cli-macos
https://www.npmjs.com/package/@cataggar/wasmtime-cli-windowsTo use:
npm -g i @cataggar/wasmtime-cli-linux
npm -g i @cataggar/wasmtime-cli-macos
npm -g i @cataggar/wasmtime-cli-windowsYou can see how I made it with:
https://github.com/ctaggart/npm-wasmtime-cliAlternatives
ctaggart edited issue #7192:
Feature
Publish wasmtime builds to npmjs.com.
Benefit
It will make getting wasmtime installed easier in many situations. For example, component governance situations.
Implementation
I think it is probably best to map directly to your existing binaries and create:
- @bytecodealliance/wasmtime-cli-aarch64-linux@13.0.0
- @bytecodealliance/wasmtime-cli-aarch64-macos@13.0.0
- @bytecodealliance/wasmtime-cli-riscv64gc-linux@13.0.0
- @bytecodealliance/wasmtime-cli-s390x-linux@13.0.0
- @bytecodealliance/wasmtime-cli-x86_64-linux@13.0.0
- @bytecodealliance/wasmtime-cli-x86_64-macos@13.0.0
- @bytecodealliance/wasmtime-cli-x86_64-mingw@13.0.0
- @bytecodealliance/wasmtime-cli-x86_64-windows@13.0.0
I tried it out, but with just x86_64 builds.
https://www.npmjs.com/package/@cataggar/wasmtime-cli-linux
https://www.npmjs.com/package/@cataggar/wasmtime-cli-macos
https://www.npmjs.com/package/@cataggar/wasmtime-cli-windowsTo use:
npm -g i @cataggar/wasmtime-cli-linux
npm -g i @cataggar/wasmtime-cli-macos
npm -g i @cataggar/wasmtime-cli-windowsYou can see how I made it with:
https://github.com/ctaggart/npm-wasmtime-cliAlternatives
alexcrichton commented on issue #7192:
Thanks for the report, but could you perhaps expand more on what the benefit of this might be? I'm at least not familiar of prior art of publishing Rust crate binaries on NPM, and while I don't doubt that it's possible it naively seems to me like a mishmash of different language ecosystems. I'm likely missing something thought so I'm curious to hear more about your motivations for this.
cataggar commented on issue #7192:
An example would be the ability to add it an approved Azure Artifacts feed. Azure Artifacts supports npm packages. Users and automation of the approved feed then are able to easily install wasmtime binary. Automation may be an Azure Pipeline. It would be easier to automate with
npm --global install @bytecodealliance/wasmtime-cli-x86_64-linux@13.0.0
.
Last updated: Nov 22 2024 at 16:03 UTC