Storybook update 8.5.4

[vojtatranta]

Description

Related Issue

Resolve

Screenshots:

[vojtatranta]

also automigrate, it works with it tho

[vojtatranta]

this is the same config we have in the proejct and with it, it laods the coin icons properly

[vojtatranta]

Storybook had troubles running the JSX so I did this, I am not sure if it is a porlbme or not, I can tweak it to eat the JSX "in config"

[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	CI
Trivial Package	npm/[email protected]	Location: Package overview	packages/components/package.json	🚫
Network access	npm/[email protected]	Module: https-browserify Location: Package overview	packages/components/package.json	🚫
Shell access	npm/[email protected]	Module: child_process Location: Package overview	packages/components/package.json	🚫
Deprecated	npm/[email protected]	Reason: this will be v4	packages/components/package.json	🚫
Uses eval	npm/[email protected]	Eval Type: Function Location: Package overview	packages/components/package.json	🚫

View full report↗︎

Next steps

What are trivial packages?

Packages less than 10 lines of code are easily copied into your own project and may not warrant the additional supply chain risk of an external dependency.

Removing this package as a dependency and implementing its logic will reduce supply chain risk.

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

What is a deprecated package?

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.

What is dynamic code execution?

Package uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code.

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]

[github-actions]

🚀 Expo preview is ready!

• Project → trezor-suite-preview
• Platforms → android, ios
• Scheme → trezorsuitelite
• Runtime Version → 26
• More info

Learn more about 𝝠 Expo Github Action

[vojtatranta]

Damned storybook , it updated ton of dependencies and the yarn lock as well and now it breaks trillion of things.

[vojtatranta]

Okay, I am in the stage when nothing crashes like hell, the types are fixed. I went through the c hanges in the stories and it seems that the components controls work. But more eyes see more @jvaclavik would you check pls?

[vojtatranta]

@Nodonisko ask about the package updates

[jvaclavik]

Good job! ☀️