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

Checking wasm-pack artifacts into repo #307

Open
ptdecker opened this issue Oct 30, 2024 · 0 comments
Open

Checking wasm-pack artifacts into repo #307

ptdecker opened this issue Oct 30, 2024 · 0 comments
Labels

Comments

@ptdecker
Copy link

Summary

At our company, we are tripping over each other with respect to the artifacts generated by wasm-pack: foo.d.ts, foo.ts, foo_bg.wasm, foo_bg.wasm.ts, and (sometimes) package.json.

What are best practices around these? Is it proper to be checking these into our repo? Or, should we always omit them from the repo and just generate them and move them to static directories to be served up when needed?

If discussions or guidance on this topic already exists, could someone point me to it? I'm not finding anything when searching.

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant