chore(deps-dev): bump eslint-config-prettier from 9.1.0 to 10.1.5

[dependabot]

Bumps eslint-config-prettier from 9.1.0 to 10.1.5.

Release notes

Sourced from eslint-config-prettier's releases.

v10.1.5

Patch Changes

• #332 60fef02 Thanks @​JounQin! - chore: add funding field into package.json

Full Changelog: prettier/eslint-config-prettier@v10.1.4...v10.1.5

v10.1.4

Patch Changes

• #328 94b4799 Thanks @​silvenon! - fix(cli): do not crash on no rules configured

Full Changelog: prettier/eslint-config-prettier@v10.1.3...v10.1.4

v10.1.3

Patch Changes

• #325 4e95a1d Thanks @​pilikan! - fix: this package is commonjs, align its types correctly

New Contributors

• @​pilikan made their first contribution in prettier/eslint-config-prettier#325

Full Changelog: prettier/eslint-config-prettier@v10.1.2...v10.1.3

v10.1.2

Patch Changes

• #321 a8768bf Thanks @​Fdawgs! - chore(package): add homepage for some 3rd-party registry - see #321 for more details

v10.1.1

Patch Changes

• #309 eb56a5e Thanks @​JounQin! - fix: separate the /flat entry for compatibility

  For flat config users, the previous "eslint-config-prettier" entry still works, but "eslint-config-prettier/flat" adds a new name property for config-inspector, we just can't add it for the default entry for compatibility.

  See also prettier/eslint-config-prettier#308

  // before
  import eslintConfigPrettier from "eslint-config-prettier";
  // after
  import eslintConfigPrettier from "eslint-config-prettier/flat";

v10.1.0

Minor Changes

• #306 56e2e34 Thanks @​JounQin! - feat: migrate to exports field

... (truncated)

Changelog

Sourced from eslint-config-prettier's changelog.

10.1.5

Patch Changes

• #332 60fef02 Thanks @​JounQin! - chore: add funding field into package.json

10.1.4

Patch Changes

• #328 94b4799 Thanks @​silvenon! - fix(cli): do not crash on no rules configured

10.1.3

Patch Changes

• #325 4e95a1d Thanks @​pilikan! - fix: this package is commonjs, align its types correctly

10.1.2

Patch Changes

• #321 a8768bf Thanks @​Fdawgs! - chore(package): add homepage for some 3rd-party registry - see #321 for more details

10.1.1

Patch Changes

• #309 eb56a5e Thanks @​JounQin! - fix: separate the /flat entry for compatibility

  For flat config users, the previous "eslint-config-prettier" entry still works, but "eslint-config-prettier/flat" adds a new name property for config-inspector, we just can't add it for the default entry for compatibility.

  See also prettier/eslint-config-prettier#308

  // before
  import eslintConfigPrettier from "eslint-config-prettier";
  // after
  import eslintConfigPrettier from "eslint-config-prettier/flat";

10.1.0

Minor Changes

• #306 56e2e34 Thanks @​JounQin! - feat: migrate to exports field

10.0.3

... (truncated)

Commits

• 4c94893 chore: release eslint-config-prettier (#333)
• 60fef02 chore: add funding field into package.json (#332)
• f55501f chore: release eslint-config-prettier (#329)
• 50a8a22 chore(deps): update all dependencies (#330)
• 94b4799 fix(cli): do not crash on no rules configured (#328)
• cdc4a5c chore: release eslint-config-prettier (#326)
• 4e95a1d fix: this package is commonjs, align its types correctly (#325)
• 8911369 chore: release eslint-config-prettier (#322)
• a8768bf chore(package): add homepage url (#321)
• 4ae04c0 chore(deps): update yarn to v4.8.1 (#320)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by jounqin, a new releaser for eslint-config-prettier since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​babel/​traverse@​7.7.4
	@​types/​vfile-message@​2.0.0
	array-flatten@​1.1.1
	array-includes@​3.1.8 ⏵ 3.1.1	+1		-1
	array.prototype.flat@​1.3.2 ⏵ 1.2.3	+1		-1
	array.prototype.flatmap@​1.3.2 ⏵ 1.2.3	+1		-1
	@​types/​parse-json@​4.0.0
	assert@​1.5.0
	@​types/​get-port@​3.2.0
	@​types/​lodash.sample@​4.2.6
	@​types/​eslint-visitor-keys@​1.0.0
	@​babel/​plugin-transform-react-jsx-development@​7.9.0
	@​babel/​plugin-transform-react-pure-annotations@​7.10.4
	@​babel/​plugin-transform-regenerator@​7.8.7
	@​webassemblyjs/​helper-code-frame@​1.9.0
	@​babel/​plugin-transform-unicode-regex@​7.7.4
See 330 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Warn		@babel/[email protected] has a Critical CVE. CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: < 7.23.2 Patched version: 7.23.2 From: ui/package-lock.json → npm/@babel/[email protected] → npm/@babel/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: 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 [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@babel/[email protected] has a Critical CVE. CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: < 7.23.2 Patched version: 7.23.2 From: ui/package-lock.json → npm/@babel/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: 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 [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@babel/[email protected] has a Critical CVE. CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: < 7.23.2 Patched version: 7.23.2 From: ui/package-lock.json → npm/@babel/[email protected] → npm/@babel/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: 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 [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a Critical CVE. CVE: GHSA-76p3-8jx3-jpfq Prototype pollution in webpack loader-utils (CRITICAL) Affected versions: < 1.4.1 Patched version: 1.4.1 From: ui/package-lock.json → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: 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 [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a Critical CVE. CVE: GHSA-xvch-5gv4-984h Prototype Pollution in minimist (CRITICAL) Affected versions: >= 1.0.0, < 1.2.6 Patched version: 1.2.6 From: ui/package-lock.json → npm/@babel/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: 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 [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report