Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
ashleygwilliams opened this issue Oct 22, 2020 · 10 comments
Closed

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

ashleygwilliams opened this issue Oct 22, 2020 · 10 comments

Comments

@ashleygwilliams
Copy link
Member

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.

@azriel91
Copy link
Contributor

Heya, would like for #698 to be fixed in the next release (PR: #851).

@robojumper
Copy link

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).

@lucashorward
Copy link
Contributor

@lwansbrough
Copy link

#888 can probably ship with trivial changes

@quaos
Copy link

quaos commented Nov 20, 2020

Deno support?

@oplik0
Copy link

oplik0 commented Dec 6, 2020

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.

@torokati44
Copy link

torokati44 commented Jan 12, 2021

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 ruffle-rs/ruffle#2173. However, at least version 98 seems to work fine.)

@domoritz
Copy link

domoritz commented Feb 4, 2021

#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, #928 helped clarify the status of this repo for me.

@tv42
Copy link

tv42 commented Sep 21, 2021

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

@serprex
Copy link
Contributor

serprex commented Dec 5, 2021

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

@drager drager closed this as completed Jun 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests