Caleb Boyd

@EricMCornelius Thanks for tracking that down looks like it landed in 13. I'll see if I can get it resolved.

Not if you need patches (as far as I know). If you just delete the resource (node binary) and use `-j` in `make` its usually pretty quick

Ahh Sorry, yeah, that option is aggressive.

Are you executing the file with this command `/example/dir/testNexe` ? I'm unable to replicate this....

If you could provide a code reproduction that would help.

@anmonteiro This was partially fixed with https://github.com/nexe/nexe/commit/c9c9b5a0a31c7ebe6ed4195fecff36b78be8b328 and is available on npm. The other part of this issue is here https://github.com/nexe/nexe/blob/6fc2ed95193c2649097f91f8698518bb31c12db8/src/fs/patch.ts#L190 Where the best solution (I think) would be to...

Okay. I'm guessing you'll have correct behavior with the latest version. The VFS is just a picture of the files as determined at buildtime by analyzing your entrypoint (`input`) and...

Your snapshot change and an additional (not documented/experimental) [option](https://github.com/nexe/nexe/commit/0dca0745eebd447008c6ffebdc748750dc1208dd) `fs: false` or `--no-fs` are in v3.1.0

@ALexander4295502 Can you run your app outside the project folder with the `DEBUG=nexe:require` environment variable set?. Or even better if you can provide a small reproduction/example repo?

Yeah, That's super odd! If you use the debug flag we may be able to track down why that's being included!