let's add a custom key to the package.json to log that it's a wasm-pack project

[ashleygwilliams]

thinking something like this:

{
   "name": "x",
...
    "toolchain": { "wasm-pack" : "0.5.1" }
}

cc @tschneidereit

[tschneidereit]

@ashleygwilliams I assume this is something that could be searched for using the CLI or something else? Ideally both for the key—"wasm-pack", and the value—the version? If so, that looks excellent. If only the key, that'd probably be good enough, too.

[Pauan]

@tschneidereit Yeah, npm view <PACKAGE> toolchain.wasm-pack should work.

[tschneidereit]

@Pauan that covers part of it, thanks. Can I also do searches across the package repository? I.e. does something like npm search toolchain.wasm-pack work? Perhaps even with a regexp for the value of wasm-pack?

[Pauan]

@tschneidereit I don't know, but I don't think so. I did some basic testing, npm search seems to only look at the name, description, author, and keywords.

So if wasm-pack was added to the keywords it should be possible to search for the existence of wasm-pack-compiled packages (but that still won't tell you the version, you'd need to use npm view for that).

[ashleygwilliams]

@tschneidereit keywords would be best for the search UI exposed on the npm webpage (and the CLI) but my intention is to have a follower that collects these and displays them on a website. i figured this was good enough for analytics- do we supposed folks would want to search for wasm-pack in the UI itself? for team analytics (which i consider a different use case) i dont think using npm's UI is necessary, but i'm open to suggestions

[tschneidereit]

@ashleygwilliams ah, ok. I agree that as long as we have a way to get this information, we don't need to do it via npm's tools. And I don't think there's a strong reason we'd need to make it very easy for people to find these on npmjs.com: for most people this should ideally just be an implementation detail :)

[ashleygwilliams]

in case you're curious- i'm functionally using this (based on a tutorial i wrote for npm years ago lol): https://github.com/npm/registry-follower-tutorial