wasm-pack icon indicating copy to clipboard operation
wasm-pack copied to clipboard

what needs to happen for the next release of wasm-pack

Open ashleygwilliams opened this issue 5 years ago • 10 comments
trafficstars

it has been quite a while since wasm-pack has been released. this is an issue to track what needs to be fixed so that we can release a new version of wasm-pack.

ashleygwilliams avatar Oct 22 '20 00:10 ashleygwilliams

Heya, would like for https://github.com/rustwasm/wasm-pack/issues/698 to be fixed in the next release (PR: https://github.com/rustwasm/wasm-pack/pull/851).

azriel91 avatar Oct 22 '20 08:10 azriel91

It would be great if #886 could be fixed (PR at #887) because the issue broke the game of life example (and basically every rust wasm app derived from it).

robojumper avatar Oct 22 '20 09:10 robojumper

  • CI should be functional again, and preferably moved to github actions so that open-source contributors can also see what is happening and fix it / make improvements. I see a lot of the travis ci actions are on pending, but not sure what is wrong (and can't see the details to investigate that either as that requires admin access vs a github action with files inside the repo)
  • Old versions of other libs should be updated. In #919, #917 and #926 I see wasm-opt, chromedriver and possibly openssl/curl versions are outdated. In some cases these seem to be responsibly for crashes.

lucashorward avatar Oct 22 '20 19:10 lucashorward

#888 can probably ship with trivial changes

lwansbrough avatar Oct 25 '20 09:10 lwansbrough

Deno support?

quaos avatar Nov 20 '20 02:11 quaos

Deno support?

#908 addresses this, and it looks like it could be merged with minimal changes - it doesn't change much code and it seems the biggest questionable thing there is creating an empty .gitignore file (instead of adding * to its contents), so that might be reverted (I think the idea is that deno modules are usually kept online with git and imported from urls, so no reason to make default .gitignore ignore the result).

One thing that should be added there is listing deno target in wasm-pack build --help.

oplik0 avatar Dec 06 '20 23:12 oplik0

Having a new release with newer wasm-opt would indeed be really nice! As requested in #919 as well. (The old wasm-opt in the 0.9.1 release has a crash which is the current blocker for https://github.com/ruffle-rs/ruffle/pull/2173. However, at least version 98 seems to work fine.)

torokati44 avatar Jan 12 '21 03:01 torokati44

https://github.com/rustwasm/wasm-pack/pull/937 would also be awesome so that wasm-pack passes --weak-refs --reference-types through to wasm-bindgen.

For anyone else wondering about a new release, https://github.com/rustwasm/wasm-pack/issues/928 helped clarify the status of this repo for me.

domoritz avatar Feb 04 '21 19:02 domoritz

This issue seems to one of the two new issues mentioned in https://github.com/rustwasm/wasm-pack/issues/914 without linking. Since #914 is now locked, mention it here so hopefully it'll cross-reference right.

tv42 avatar Sep 21 '21 14:09 tv42

#1089 is necessary for importing wasm-pack modules in node

serprex avatar Dec 05 '21 13:12 serprex