New issue
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
Add support for browser-sync 3 #97
Comments
Just ran into this dependency conflict as well, when upgrading a project to browser-sync@3 |
Hi, I have the same problem. npm ERR! code ERESOLVE |
Same here:
|
There's an updated repo on npm via npm install --save-dev browser-sync-v3-webpack-plugin |
Same here |
@Jas-n This did not work for me. As soon as I attempted to mix:
|
That's normal for the first run. Just run the run command again. You won't see it next time 😊. |
@Jas-n when running
Which then proceeds to install the older version and the issue still persists. |
I can confirm that the fix mentioned by @Jas-n does not work when using it together with the |
I am having the same issue. Security vulnerability still persists. Could we get some other more people to review mozilla/ssl-config-generator#235 and abandon this project switching to a fork that supports v3? I am unsure of the etiquette here as this project hasn't had a release since 2020. |
browser-sync-webpack-plugin requires browsery-sync^2 as peer-dependency https://github.com/Va1/browser-sync-webpack-plugin/blob/master/package.json#L23
Now that browser-sync 3 was released, it generates a dependency conflict when both packages are used
The text was updated successfully, but these errors were encountered: