build(shims): Bundle eventual-send using @endo/bundle-source

[SMotaal]

Resolves:

• shims: Bundle eventual-send using @endo/bundle-source #10

This use @endo/bundle-source to bundle eventual-send in @ocap/shims from its node_modules source instead of the pre-bundled src/eventual-send.mjs that was introduced in #8 for expediency.

Possible concerns:

• The changes rely on import.meta.resolve in Node.js which is still flagged as Stability 1.2 - Release candidate.

Other notable changes:

• Bumps related @endo/* dependencies for @ocap/extension and `@ocap/shims.
• Drops mkdirp from the devDependencies of @ocap/shims in favour of using mkdir(<path>, { recursive: true }) directly in Node.js.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@endo/bundle-source@3.3.0	environment, eval, filesystem Transitive: unsafe	+34	11 MB	kriskowal

🚮 Removed packages: npm/@babel/generator@7.24.10, npm/@babel/helper-environment-visitor@7.24.7, npm/@babel/helper-function-name@7.24.7, npm/@babel/helper-hoist-variables@7.24.7, npm/@babel/helper-split-export-declaration@7.24.7, npm/@babel/template@7.24.7, npm/@babel/traverse@7.24.8, npm/@babel/types@7.24.9

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/glob@7.2.3, npm/inflight@1.0.6, npm/source-map@0.5.7

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

[SMotaal]

@SocketSecurity ignore npm/glob@7.2.3 npm/inflight@1.0.6 npm/source-map@0.5.7

• Both npm/glob@7.2.3 and npm/inflight@1.0.6 already existed as nested dependencies (checked via yarn why <package>).
• npm/source-map@0.5.7 is introduced as a nested dependency for @endo/bundle-source@3.3.0 via @agoric/babel-generator@7.17.6

[rekmarks]

LGTM!