np is including irrelevant yarn.lock files

[tansanDOTeth]

Description

I have multiple yarn.lock files in my library: one for the library and one for an example application.
I added the example application directory into .npmignore, but np is still trying to include it.

This is the output even though .npmignore specifically has example/:

The following new files will be published the first time:
- example/yarn.lock
- rollup.config.js
- yarn.lock

Steps to reproduce

1. Have a yarn.lock file in the root
2. Have a yarn.lock file in example/
3. Add example/ to .npmignore
4. Run np

Expected behavior

I expect it to respect .npmignore file.

Environment

np - 7.6.2
Node.js - v16.13.0
npm - 8.1.4
Git - 2.32.1
OS - macOS 12.5

[fregante]

np is not packaging your files, it just calls npm publish.

Run npm pack --dry-run to ensure your npmignore is set correctly