Show HN: WAPM – Package Manager for WebAssembly

Post by jake_the_third » Wed, Apr 24, 2019, 1:31 AM UTC

syrusakbary wrote: post #12

JeremyBanks wrote: post #6

I like Wasmer, but I very much dislike the idea of another major package repository being owned and operated by a commercial entity. They seem like good people doing valuable work now, but that doesn't tell us very much about who the company will be in five or ten years. I'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…

I completely understand your concerns, especially given the issues that NPM had lately. We are an open-source focused company and our success is tightly tied to the success of our open-source solutions. Here are some of the things that we are doing in order to resolve (or minimize) the concerns: * Completely open API to retrieve the registry data (it's a work in progress, but our GraphQL API is open to everyone to us…

Post by [deleted] » Wed, Apr 24, 2019, 3:47 AM UTC

yuvipanda wrote: post #22

syrusakbary wrote: post #12

Earlier quoted context omitted.

I completely understand your concerns, especially given the issues that NPM had lately. We are an open-source focused company and our success is tightly tied to the success of our open-source solutions. Here are some of the things that we are doing in order to resolve (or minimize) the concerns: * Completely open API to retrieve the registry data (it's a work in progress, but our GraphQL API is open to everyone to us…

Thanks! This is a good start. Do you have ideas on how you will make the governance of the registry open? Who will make important decisions around policies, and how will they be made? I personally find this to be the core reason I find it hard to use startup-run package registries.

Post by thefounder » Wed, Apr 24, 2019, 3:57 AM UTC

JeremyBanks wrote: post #6

I like Wasmer, but I very much dislike the idea of another major package repository being owned and operated by a commercial entity. They seem like good people doing valuable work now, but that doesn't tell us very much about who the company will be in five or ten years. I'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…

Post by Godel_unicode » Wed, Apr 24, 2019, 4:08 AM UTC

warpech wrote: post #19

Godel_unicode wrote: post #13

Earlier quoted context omitted.

Which general purpose package manager works correctly on Windows (not WSL, actual Windows) and Linux? Cross-platform is more important than not creating another package manager. I think a far more interesting question is, does the package repository support falling back to e.g. curl. That would allow those who don't want another package manager to still use the registry.

NuGet

Post by skybrian » Wed, Apr 24, 2019, 4:13 AM UTC

Godel_unicode wrote: post #41

catern wrote: post #21

Earlier quoted context omitted.

You should distinguish between "can run on Windows" and "can manage Windows software as packages". Most package managers could probably run fine on Windows; at worst they could use cygwin or, indeed, WSL. Managing Windows software is much harder, but isn't necessary: This is a package manager for WebAssembly packages, not Windows packages or Linux packages. And anyway, wasmer itself doesn't even support Windows.

If you run on Windows by using e.g. cygwin, you don't run on Windows. See previous statement about WSL. > wasmer itself doesn't even support Windows First, it will: https://github.com/wasmerio/wasmer/issues/51#issuecomment-44... Second, I write code that doesn't run on my terminal all the time, but I need the packages I'm using to be installed and versioned correctly.