Skip to content
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

remove localtunnel #2059

Merged
merged 7 commits into from Dec 27, 2023
Merged

Conversation

shakyShane
Copy link
Contributor

@shakyShane shakyShane commented Dec 27, 2023

it was always an optional code-path, so now anyone wanting to use localtunnel can continue to do so, after installing it themselves.

npm i browser-sync@3

@shakyShane
Copy link
Contributor Author

Current dependencies on/for this PR:

This stack of pull requests is managed by Graphite.

@shakyShane shakyShane merged commit 6030e87 into master Dec 27, 2023
3 checks passed
@shakyShane shakyShane changed the title moving localtunnel to peer dependency remove localtunnel Dec 27, 2023
@lsmith77
Copy link

lsmith77 commented Jan 10, 2024

FYI changes to dependencies and semver is a hotly debated topic but for a security fix like this, imho it would have been nicer to release it within the same major version since now other packages need to be updated to allow the new major version first.

see angular/angular-cli#26587

@shakyShane
Copy link
Contributor Author

@lsmith77 - thanks. Yeah I did consider that.

Honestly I'd be happy to release this same tag into 2.x too (to increase adoption) - it's just hard to judge if it's impacting anyone or not (since Browsersync has both a giant user base + zero telemetry)

@lsmith77
Copy link

angular users would appreciate a release since there is not yet a release of a browsersync 3.0 compatible version

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.

None yet

2 participants