feat: customizable frame state hook

[michalkvasnicak]

Change Summary

This PR allows using custom frame state hook.

Merge Checklist

• PR has a Changeset
• PR includes documentation if necessary
• PR updates the boilerplates if necessary

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
frames-js	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 19, 2024 9:15am
framesjs-debugger	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 19, 2024 9:15am
framesjs-examples	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 19, 2024 9:15am

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher

🚮 Removed packages: npm/@noble/ed25519@2.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	CI
Possible typosquat attack	npm/emoji-regex-xs@1.0.0	Did you mean: emoji-regex~~-xs~~	⚠︎

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

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/emoji-regex-xs@1.0.0