This script is guaranteed to talk to the big bad internet on yarn pnp, or any other package manager that strictly enforces dependencies.

This is a big no-no for any offline-build environment, and inadvisable anywhere else.

However, I can see the benefit of not requiring a completely separate file to orchestrate the napi-postinstall process.

Given that postinstall scripts run in the directory of the package that invokes them, could a first fallback option be to attempt to read package.json from the cwd?