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

Add an asset entry point #31

Open
pimterry opened this issue Nov 28, 2023 · 1 comment
Open

Add an asset entry point #31

pimterry opened this issue Nov 28, 2023 · 1 comment

Comments

@pimterry
Copy link
Member

@pimterry , I are recently working on another kind of entry for the web environment of these packages with less "side-effects".
It is in asset.js with another export in package.json, the document is at asset.md, and an example is available at example/webpack-asset.
Do you think it is fine and can I open a PR for the new entry?

Originally posted by @myl7 in #18 (comment)

@pimterry
Copy link
Member Author

Just pulling this out as a separate topic @myl7, to avoid confusing that thread too much.

Can you explain more about how this works, and exactly why it's useful?

Is there a good reason why we'd need to do this here, instead of fixing the target (or adding a new target) in the wasm-pack project itself?

I'd really like to avoid maintaining more and more complicated entrypoints if we can - it would be much better if wasm-pack could handle this properly. That's less maintenance for each of us on these packages, but would also make it much easier for everybody else building wasm packages elsewhere to do the same thing automatically.

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

1 participant