Packages installed with napa removed after install other package

[Anonym-tsk]

I have in my package.json

"napa": {
  "foo": "author/foo#branch"
},
"scripts": {
  "install": "napa"
},
"devDependencies": {
  "napa": "^3.0.0"
}

When i do npm i, napa creates node_modules/foo with my module.
But when i do npm i -D other-package, directory node_modules/foo will be removed.
What i do wrong?

[caseyWebb]

As far as I know, the only solution is to re-run npm install after adding the dependency. Installing a single dep does not trigger any package.json run scripts.

[ajbogh]

I have a PR that might solve this issue by allowing you to specify a different folder for napa dependencies, such as vendor. See #84.

[JakedUp]

Why not just have Napa build a package.json for said library so that it does not get scrubbed?

[caseyWebb]

@JakedUp napa already builds and writes a package.json to the file system. If you're suggesting automatically publishing to npm, I think that's way out of the scope of this package.

[JakedUp]

Ah, ok -- I did not know this. Thanks for the clarification