You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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