Show HN: WAPM – Package Manager for WebAssembly
1–10 of 82 posts
Re: Show HN: WAPM – Package Manager for WebAssembly
#2Would love to hear your thoughts!
Re: Show HN: WAPM – Package Manager for WebAssembly
#3Re: Show HN: WAPM – Package Manager for WebAssembly
#4How does the dependency model work? Can I safely install parallel streams of software? Does it support unprivileged installation? Is the installation stateless (no scriptlets/lifecycle scripts)?
Re: Show HN: WAPM – Package Manager for WebAssembly
#5Are all the 'packages' here reproducible? I'd love to be able to run something like `wapm verify `, or `wapm verify --all`. Running arbitrary code from random people on my computer is sketchy even when I can look at the code. Its far more sketchy when I can't.
Reproducible builds are definitely something great, but they are quite tricky. However we are very open to hear more thoughts on how to do it!
Re: Show HN: WAPM – Package Manager for WebAssembly
#6I've grown uncomfortable with NPM being operated by NPM Inc instead of The Node.js Foundation, but it's a hard thing to change once it's established. We should hesitate to support the establishment of another community package manager by a for-profit company.
Re: Show HN: WAPM – Package Manager for WebAssembly
#7btw it has "telemetry" enabled by default.
edit: thanks for the link, didn't find the source previously
Re: Show HN: WAPM – Package Manager for WebAssembly
#8Are all the 'packages' here reproducible? I'd love to be able to run something like `wapm verify `, or `wapm verify --all`. Running arbitrary code from random people on my computer is sketchy even when I can look at the code. Its far more sketchy when I can't.
We are working on supporting signed packages to assure they can't be tampered with. At the same time WebAssembly provides some nice sandboxing capabilities and we are working to add permissions on top of syscalls, so packages will not do what they are not suppose to do. Reproducible builds are definitely something great, but they are quite tricky. However we are very open to hear more thoughts on how to do it!
One fairly simple thing you can do to improve this would be to include build scripts as part of the package, and allow people to run those build scripts through wapm. The exact versions of any involved tools will need to be recorded too, but since there arent too many ways to generate wasm blobs yet, this shouldnt be too out there.
Eventually it would be great if everyone had fully reproducible build formulae (kinda like https://github.com/polydawn/repeatr).
Re: Show HN: WAPM – Package Manager for WebAssembly
#9Making a new package manager is very expensive in terms of developer times - developers have to learn yet another new thing to use your platform. Can you justify this?
Edit: For example, as matthewbauer commented below, Nix can support WebAssembly as a compilation target: https://github.com/NixOS/nixpkgs/pull/56555
Re: Show HN: WAPM – Package Manager for WebAssembly
#10anyway, sounds really cool and hoping it gets inspired by things like bundler/homebrew more than npm/yarn. btw it has "telemetry" enabled by default. edit: thanks for the link, didn't find the source previously
We are also planning to open-source the registry as well :)