Skip to content

[Snyk] Upgrade browser-sync from 2.27.10 to 2.29.3#20

Open
sushmak02 wants to merge 1 commit intomasterfrom
snyk-upgrade-6a662ec768442240468b002631538c8f
Open

[Snyk] Upgrade browser-sync from 2.27.10 to 2.29.3#20
sushmak02 wants to merge 1 commit intomasterfrom
snyk-upgrade-6a662ec768442240468b002631538c8f

Conversation

@sushmak02
Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to upgrade browser-sync from 2.27.10 to 2.29.3.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 11 versions ahead of your current version.

  • The recommended version was released 2 years ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Prototype Poisoning
SNYK-JS-QS-3153490
696 Proof of Concept
high severity Denial of Service (DoS)
SNYK-JS-SOCKETIOPARSER-5596892
696 No Known Exploit
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-ANSIREGEX-1583908
696 Proof of Concept
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-UAPARSERJS-3244450
696 Proof of Concept
Release notes
Package name: browser-sync
  • 2.29.3 - 2023-05-17

    What's Changed

    Full Changelog: v2.29.2...v2.29.3

  • 2.29.2 - 2023-05-17

    v2.29.2

  • 2.29.1 - 2023-03-22

    What's Changed

    Full Changelog: v2.29.0...v2.29.1

  • 2.29.1-alpha.0 - 2023-03-22

    v2.29.1-alpha.0

  • 2.29.0 - 2023-03-16

    What's Changed

    esbuild does not support down-level transpiling as far as IE11 - so when I switched to it, it accidentally broke IE11 support 😢

    This is an important issue for me - many devs that support old browsers like IE11 are doing so because their projects are used in public services, or internal applications. Not every developer out there has the luxury of supporting evergreen-only browsers.

    So, IE11 will work once again 🎉. Please use the issues thread to make me aware of any problem that's preventing you from using Browsersync in your day job 💪 (and be sure to thumbs-up the issues you want to see resolved)

    # IE11 works, again
    npm install browser-sync@latest

    Full Changelog: v2.28.3...v2.29.0

  • 2.28.3 - 2023-03-04

    v2.28.3

  • 2.28.2 - 2023-03-04

    v2.28.2

  • 2.28.1 - 2023-02-27

    v2.28.1

  • 2.28.0 - 2023-02-27

    What's Changed

    Full Changelog: v2.27.12...v2.28.0

  • 2.27.12 - 2023-02-23
  • 2.27.11 - 2022-12-19
  • 2.27.10 - 2022-05-16
from browser-sync GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade browser-sync from 2.27.10 to 2.29.3.

See this package in npm:
browser-sync

See this project in Snyk:
https://app.snyk.io/org/sushmak02/project/83f9a017-9bd1-4523-828b-0361a8a824fc?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants