Actually... I realised that this is easily worked around by using one-off git add --force pkg/... and it's even better because you can selectively include only files you need in the repo (e.g. omit package.json or .d.ts).

I still think this would be nice to have.

Same, I'd like to generate only the wasm and js and skip all the extra stuff since I'm not using npm

git add --force is kinda icky, .gitignore lives in a repository to codify these things for a reason. Skipping the generation of this file entirely scales better for multiple collaborators and teams because the appropriate information exists at rest.

I ran into this issue when trying to publish a wrapper around the generated wasm-pack output.

src/index.ts imports ../pkg. I want to package both src and pkg into an npm package and publish it. However, bun sees the .gitignore file in pkg and skips adding it to the artifact, despite files: [ "pkg", "src" ].

$ bun pm pack --verbose
ignore [.gitignore:*] pkg/moq_web.d.ts
ignore [.gitignore:*] pkg/README.md
ignore [.gitignore:*] pkg/.gitignore
ignore [.gitignore:*] pkg/moq_web.js
ignore [.gitignore:*] pkg/moq_web_bg.js
ignore [.gitignore:*] pkg/moq_web_bg.wasm

I accidentally published a few broken versions, oops. My current work-around is to rm pkg/.gitignore after running wasm-pack.