Description

When specifying the contents flag like np --contents=./../../ --preview" it seems to be ignored.
This may be caused by my setup but I am not sure because using npm publish ./../../ --dry-run does what I expect.

My project has a dependency called vl-ui-util that has a package.json
containing an npm run script that calls np. When calling np in the parent project, np will try and publish vl-ui-util instead of the parent project. According to the documentation, this can be fixed using the --contents flag, however, this seems to fail.

Steps to reproduce

1. Create an empty project via npm init (project A)
2. Create an empty project via npm init (project B)
3. Install np as dependency in project B
4. Create an npm run script in project B which runs np --contents=./../../ --preview" (Script X)
5. Create an npm run script in project A (Script Y) which runs script X
6. Call script A

Expected behavior

Np wizard starts and tries to release project A.

Environment

np - 6.3.0
Node.js - 13.12.0
npm - 6.14.5
Git - 2.15.0
OS - OSX Catalina 10.15.5