A mesh package's tarball is unpacked straight into node_modules, so its own
dependencies were never there: the forge module's bundle failed with esbuild
"Could not resolve blakejs" from the SDK's seal code. After every mesh package
is placed, the fetch installs the dependencies they declare (not their
devDependencies, not a mesh package, not one already present) through the
same npm path as the module's own, before the bundle.
Builds: design 47 H H-A-491 (addendum)