We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Just in case you are not aware of this new issue.
node_modules/portscanner/node_modules/async portscanner 0.1.1 - 2.1.1 Depends on vulnerable versions of async node_modules/portscanner browser-sync <=0.6.2 || >=2.0.0-rc1 Depends on vulnerable versions of portscanner node_modules/browser-sync @11ty/eleventy-server-browsersync * Depends on vulnerable versions of browser-sync node_modules/@11ty/eleventy-server-browsersync
The text was updated successfully, but these errors were encountered:
Yeah, this one applies to more than browser-sync (but also browser-sync)
Filed at core too 11ty/eleventy#2327
(I’d like to keep this one open too, it seems like the core version might be fixed on a different timeline than the browser-sync one)
Sorry, something went wrong.
released as browser-sync@2.27.10 - thank you :)
Thank you @shakyShane!
No branches or pull requests
Just in case you are not aware of this new issue.
node_modules/portscanner/node_modules/async
portscanner 0.1.1 - 2.1.1
Depends on vulnerable versions of async
node_modules/portscanner
browser-sync <=0.6.2 || >=2.0.0-rc1
Depends on vulnerable versions of portscanner
node_modules/browser-sync
@11ty/eleventy-server-browsersync *
Depends on vulnerable versions of browser-sync
node_modules/@11ty/eleventy-server-browsersync
The text was updated successfully, but these errors were encountered: