Release 0.2.0

[yannbf]

Release Notes

@storybook/testing-library now uses @testing-library/dom version 9 and @testing-library/user-event version 14! 🎉

To refer to new features and bugfixes and you can check them in the user-event release page and testing-library dom release page.

📦 Published PR as canary version: 0.2.0--canary.46.dbbc187.0

✨ Test out this PR locally via:

npm install @storybook/testing-library@0.2.0--canary.46.dbbc187.0
# or 
yarn add @storybook/testing-library@0.2.0--canary.46.dbbc187.0

[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.

Issue	Package	Version	Note	Source
Install scripts	esbuild	0.17.19	Install script: postinstall Source: node install.js	package.json via tsup@6.7.0
Network access	esbuild	0.17.19	Module: globalThis["fetch"] Location: install.js	package.json via tsup@6.7.0
Shell access	esbuild	0.17.19	Module: child_process Location: install.js	package.json via tsup@6.7.0
Network access	mz	2.7.0	Module: dns Location: dns.js	package.json via tsup@6.7.0
Shell access	mz	2.7.0	Module: child_process Location: child_process.js	package.json via tsup@6.7.0
New author	source-map	0.8.0-beta.0	New Author: loganfsmyth Previous Author: nickfitzgerald	package.json via tsup@6.7.0
Shell access	commander	4.1.1	Module: child_process Location: index.js	package.json via tsup@6.7.0
Shell access	tree-kill	1.2.2	Module: child_process Location: index.js	package.json via tsup@6.7.0
Uses eval	is-generator-function	1.0.10	Eval Type: Function Location: index.js	package.json via util@0.12.5
Uses eval	load-tsconfig	0.2.5	Eval Type: Function Location: dist/index.cjs	package.json via tsup@6.7.0
Uses eval	rollup	3.25.1	Eval Type: Function Location: dist/shared/loadConfigFile.js	package.json via tsup@6.7.0
Uses eval	tsup	6.7.0	Eval Type: Function Location: dist/chunk-OSC67C6M.js	package.json

Next steps

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.

What is network access?

This module accesses the network.

Packages should remove all network access that isn't 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 new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

What is eval?

Package uses eval() which is a dangerous function. This prevents the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Avoid packages that use 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 package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore is-generator-function@1.0.10
• @SocketSecurity ignore load-tsconfig@0.2.5
• @SocketSecurity ignore rollup@3.25.1
• @SocketSecurity ignore tsup@6.7.0
• @SocketSecurity ignore source-map@0.8.0-beta.0
• @SocketSecurity ignore commander@4.1.1
• @SocketSecurity ignore esbuild@0.17.19
• @SocketSecurity ignore mz@2.7.0
• @SocketSecurity ignore tree-kill@1.2.2

[socket-security]

New and updated dependency changes detected. Learn more about Socket for GitHub ↗︎

Packages		Version	New capabilities	Transitives1	Size	Publisher
tsup	🆕	6.7.0	eval, network, filesystem, environment	+48	247 MB	egoist
util	🆕	0.12.5	environment	+1	65.6 kB	goto-bus-stop
typescript	⬆️	4.9.5...5.1.3	None	+0/-0	40.1 MB	typescript-bot
@testing-library/user-event	⬆️	13.5.0...14.4.3	None	+0/-18	420 kB	testing-library-bot

🚮 Removed packages: @testing-library/dom@8.20.1

Footnotes

1. https://docs.socket.dev ↩

[github-actions]

🚀 PR was released in v0.2.0 🚀