TheSoftwareHouse / react-starter-boilerplate

A highly scalable React SPA boilerplate focused on performance and best practices, written in TypeScript.
https://tsh.io/
MIT License
62 stars 19 forks source link

chore(deps-dev): bump @typescript-eslint/parser from 7.6.0 to 7.11.0 #194

Closed dependabot[bot] closed 3 months ago

dependabot[bot] commented 4 months ago

Bumps @typescript-eslint/parser from 7.6.0 to 7.11.0.

Release notes

Sourced from @​typescript-eslint/parser's releases.

v7.11.0

7.11.0 (2024-05-27)

🚀 Features

  • eslint-plugin: deprecate prefer-ts-expect-error in favor of ban-ts-comment (#9081)

🩹 Fixes

  • ast-spec: add EmptyStatement to Statement (#8892)
  • eslint-plugin: [consistent-type-assertions] prevent syntax errors on arrow functions (#8826)
  • typescript-estree: truncate number of files printed by the maximum file error (#9127)

❤️ Thank You

You can read about our versioning strategy and releases on our website.

v7.10.0

7.10.0 (2024-05-20)

🚀 Features

  • eslint-plugin: [sort-type-constituents] support case sensitive sorting (#8760)

🩹 Fixes

  • eslint-plugin: [prefer-regexp-exec] fix heuristic to check whether regex may contain global flag (#8764)
  • typescript-estree: don't add in-project files to defaultProjectMatchedFiles (#9097)
  • utils: remove function form type from flat config files and ignores (#9111)

❤️ Thank You

You can read about our versioning strategy and releases on our website.

v7.9.0

7.9.0 (2024-05-13)

... (truncated)

Changelog

Sourced from @​typescript-eslint/parser's changelog.

7.11.0 (2024-05-27)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

7.10.0 (2024-05-20)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

7.9.0 (2024-05-13)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

7.8.0 (2024-04-29)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

7.7.1 (2024-04-22)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

7.7.0 (2024-04-15)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

Commits


Dependabot compatibility score

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 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)
changeset-bot[bot] commented 4 months ago

⚠️ No Changeset found

Latest commit: f4cf18d2815de06b87ce1765fa20a8c71a5c0b6b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

socket-security[bot] commented 4 months ago

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

Package New capabilities Transitives Size Publisher
npm/@typescript-eslint/parser@7.11.0 Transitive: environment, filesystem +26 2.01 MB jameshenry
npm/msw@2.2.13 environment, filesystem, shell +33 5.77 MB kettanaito

🚮 Removed packages: npm/@playwright/test@1.43.1, npm/@typescript-eslint/parser@7.6.0, npm/dotenv@16.4.5, npm/eslint-plugin-playwright@1.6.0, npm/http-server@14.1.1, npm/typescript@5.4.3

View full report↗︎

socket-security[bot] commented 4 months ago

🚨 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 NoteSource
Install scripts npm/msw@2.2.13
  • Install script: postinstall
  • Source: node -e "try{require('./config/scripts/postinstall')}catch(e){}"

View full report↗︎

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.

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/msw@2.2.13
dependabot[bot] commented 3 months ago

Superseded by #196.