feat: support async deriveState

[jxom]

Supports asynchronous deriveState, and migrate to native structuredClone.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
frog	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 6, 2024 10:52am
frog-auth	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 6, 2024 10:52am
frog-frame	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 6, 2024 10:52am

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@types/bun@1.0.8	None	+4	4.46 MB	types
npm/bun@1.0.30	environment, filesystem, network, shell	+6	529 MB	robobun
npm/frog@0.2.14	network Transitive: environment, eval, filesystem, shell, unsafe	+197	907 MB	jmoxey
npm/typescript@5.3.3	None	0	32 MB	typescript-bot
npm/vercel@32.7.2	Transitive: environment, eval, filesystem, network, shell, unsafe	+221	275 MB	vercel-release-bot

🚮 Removed packages: npm/@biomejs/biome@1.5.3, npm/@bufbuild/buf@1.29.0, npm/@bufbuild/protoc-gen-es@1.7.2, npm/@changesets/changelog-github@0.5.0, npm/@changesets/cli@2.27.1, npm/@clack/prompts@0.7.0, npm/@hono/node-server@1.8.1, npm/@ngrok/ngrok@1.1.0, npm/@types/bun@1.0.7, npm/@types/fs-extra@11.0.4, npm/@types/node@20.11.19, npm/@types/path-browserify@1.0.2, npm/@types/qrcode@1.5.5, npm/@types/react-dom@18.2.19, npm/@types/react@18.2.57, npm/@types/react@18.2.58, npm/@vitest/coverage-v8@1.3.0, npm/buf@0.1.1, npm/bun@1.0.28, npm/bun@1.0.29, npm/detect-package-manager@3.0.1, npm/happy-dom@13.3.8, npm/hono@4.0.4, npm/hono@4.0.5, npm/hono@4.0.7, npm/ignore@5.3.1, npm/next@14.1.0

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Native code	npm/ref-napi@3.0.3	Location: Package overview	templates/default/package.json
Install scripts	npm/workerd@1.20240223.1	Install script: postinstall Source: node install.js	templates/default/package.json

View full report↗︎

Next steps

What's wrong with native code?

Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.

Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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

• @SocketSecurity ignore npm/ref-napi@3.0.3
• @SocketSecurity ignore npm/workerd@1.20240223.1