revamp eslint config to barebone modern, remove remark, use prettier …

[ndelangen]

📦 Published PR as canary version: 4.0.0--canary.28.86989af.0

✨ Test out this PR locally via:

npm install @storybook/[email protected]
# or 
yarn add @storybook/[email protected]

[socket-security]

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

Packages	Version	New capabilities	Transitives	Size	Publisher
husky	8.0.3	environment	+0	6.44 kB	typicode
pinst	3.0.0	None	+0	5.73 kB	typicode
ejs-lint	2.0.0	eval, filesystem, shell, environment	+24	1.78 MB	ryanzim
@typescript-eslint/parser	6.11.0	None	+54	51.6 MB	jameshenry
lint-staged	15.1.0	environment	+15	682 kB	okonet
auto	11.0.4	None	+55	48.3 MB	alisowski
eslint-plugin-html	6.1.2...7.1.0	None	+6/-6	998 kB	benoitz
eslint-config-prettier	8.3.0...9.0.0	environment	+43/-32	8.98 MB	lydell
@types/react	17.0.11...18.2.37	None	+3/-3	1.59 MB	types
@typescript-eslint/eslint-plugin	4.27.0...6.11.0	None	+59/-50	54.6 MB	jameshenry
react	17.0.1...18.2.0	None	+0/-0	316 kB	gnoff
eslint-plugin-react	7.24.0...7.33.2	None	+124/-65	15.1 MB	ljharb
eslint-plugin-import	2.23.4...2.29.0	None	+111/-87	15 MB	ljharb
eslint-plugin-prettier	3.4.0...5.0.1	None	+76/-34	18.4 MB	jounqin
prettier	2.3.1...3.1.0	None	+0/-0	8.44 MB	prettier-bot
eslint	7.28.0...8.53.0	None	+42/-31	8.96 MB	eslintbot
eslint-plugin-react-hooks	4.2.0...4.6.0	environment	+43/-32	9.07 MB	gnoff
typescript	4.3.4...5.2.2	None	+0/-0	40.6 MB	typescript-bot

🚮 Removed packages: [email protected], [email protected], [email protected], [email protected], [email protected]

[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: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]

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 package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

[ndelangen]

@SocketSecurity ignore [email protected]
@SocketSecurity ignore [email protected]
@SocketSecurity ignore [email protected]
@SocketSecurity ignore [email protected]
@SocketSecurity ignore [email protected]
@SocketSecurity ignore [email protected]
@SocketSecurity ignore [email protected]
@SocketSecurity ignore [email protected]
@SocketSecurity ignore [email protected]
@SocketSecurity ignore [email protected].

[ndelangen]

@SocketSecurity ignore [email protected]

[ndelangen]

@SocketSecurity ignore [email protected]

[ndelangen]

@SocketSecurity ignore [email protected]
@SocketSecurity ignore [email protected]
@SocketSecurity ignore [email protected]