Skip to content
This repository was archived by the owner on Aug 25, 2025. It is now read-only.
This repository was archived by the owner on Aug 25, 2025. It is now read-only.

Checking wasm-pack artifacts into repo #307

@ptdecker

Description

@ptdecker

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions