Possible to publish both CommonJS and ES6 modules in same package?

[mbalex99]

It looks like wasm_pack is sort of one or the other when it comes to publishing something for webpack browser consumption and one for nodejs.

Is it possible that wasm_pack can publish a package for both at the same time?

Ideally something like this:

Node

const { greet } = require('myModule')

Browser in Webpack

const { greet } = await import("myModule");

[ashleygwilliams]

hey @mbalex99 this is a great question! currently, wasm-pack can't do this, but i don't see why not! i can imagine a few ways to do this, so i'm gonna wait to hear other folks weigh in, but i think this could be a really neat feature! thanks for filing 🎉

[Pauan]

This syntax is wrong:

const { greet } = await import("myModule");

It should be like this:

import { greet } from "myModule";

I'm not sure if it makes sense to publish CommonJS packages: if Node supports importing to/from wasm, then it should also support ES6 modules.

[ashleygwilliams]

hey @Pauan - let's try to be a little more positive and constructive in our comments! yours was a bit blunt and critical (perhaps not your intention!) in a way that i don't think was necessary and doesn't fit the tone i'd like to set for this project. i'd love if you'd edit your comment to be friendlier. simply because we believe something "should" be the case doesn't always mean that it is the case, and we should endeavor to help folks deal with the current restrictions, even if they aren't ideal.

responding to your point: Node does not currently support ES6 modules out of the box (they are behind a flag), and many folks definitely still use CommonJS (in fact it's quite common)- i added support for commonJS to wasm-bindgen specifically to support this use case. it's a use case that ideally goes away in the future- but I don't think that future is very soon.

[Pauan]

@ashleygwilliams My intention was certainly not to be rude! How should I point out factually incorrect things in a friendlier way?

Ah, I did not realize that wasm-bindgen has support for CommonJS, in that case you're right that it does make sense to support it.

[bigfish24]

@ashleygwilliams could you share some of your thoughts on how to do this?

[ashleygwilliams]

@Pauan no worries- i didn't think your intention was to be rude at all <3<3 one way to point out things out in a friendly way is to express them as a question e.g. "did you mean to say...?" or to suggest that perhaps it was a mistake. it can also help to make it clear when you are expressing opinions by adding "i think" to statements, e.g. "i think it should be like X" instead if "it should be X".

re: how to do this (for @bigfish24 and others), there are 2 strategies i can imagine. 1 is rather brute force, we can just run the tool twice, generating 2 module files and 2 wasm files. i think there's probably a better way, but how wasm-bindgen works right now does require us to do it this way. this is because the wasm file refers to the generated js module file, and i don't think it refers to it in a way that it could refer to two files (tho i may be wrong here). i do know that i've had a few convos with @alexcrichton that suggested that this was not a required configuration (the wasm referring to the js) but just happens to be how it does work right now. i'd want to dig a little deeper into exactly how that works right now and double check my assumptions before moving forward.

so yeah, we have a few options:

• brute force, 2 js 2 wasm
• investigate how the generated wasm file refers to the js module file and figure out what constraints exist, and then likely make a PR to wasm-bindgen to change up some stuff to remove the file reference constraint

[mbalex99]

@ashleygwilliams thanks for the insight. Right now our project is constructing 2 js and 2 wasm. Which is fine but makes building a library on top sort of force their project to build 2 different paths. Ideally the 2nd way sounds much simpler for the future.

Thanks! CommonJS is sort of the standard when it comes to publishing it on NPM.

[FreeMasen]

I think I may have a solution in a PR to wasm-bindgen that will make this work right now.

rustwasm/wasm-bindgen#326

Any comments on the implementation there would be greatly appreciated. If this gets merged we could then add a new --target to wasm-pack to allow for this

[xtuc]

It seems that this discussion is redundant with the issue rustwasm/wasm-bindgen#233, see rustwasm/wasm-bindgen#233 (comment).

Here's what I have in mind: rustwasm/wasm-bindgen#326 (comment)

[ashleygwilliams]

tracking progress on this in #313