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

Version 2.26.0 broke my dependencies tree #1615

Closed
2 of 10 tasks
lazysoftwareman opened this issue Oct 8, 2018 · 4 comments · Fixed by jeremyrajan/vscode-exts#46 · May be fixed by bizoton19/hdwih-hugo-cms#4
Closed
2 of 10 tasks

Version 2.26.0 broke my dependencies tree #1615

lazysoftwareman opened this issue Oct 8, 2018 · 4 comments · Fixed by jeremyrajan/vscode-exts#46 · May be fixed by bizoton19/hdwih-hugo-cms#4

Comments

@lazysoftwareman
Copy link

Issue details

My module have a dependency to browser-synch version ~2.11.0, and after the publishing of version 2.26 of browser-synch (and browser-synch-client), I've got this error:

Cannot find module 'etag'

Because my dependencies tree is broken

Steps to reproduce/test case

  • I'm declaring a dependency to browser-synch version ~2.11.0 (so I get 2.11.2)
  • This version declares a dependency to browser-synch-client version ^2.3.3 (so I got 2.5.1)
  • After the publishing of version 2.26.0 of browser-synch and browser-synch-client ^2.3.3 = 2.26.0 of browser-synch-client that is not compatible with browser-synch 2.11.2

Please specify which version of Browsersync, node and npm you're running

  • Browsersync [ 2.11.2 ]
  • Node [ 8.12.0 ]
  • Npm [ 6.4.1 ]

Affected platforms

  • linux
  • windows
  • OS X
  • freebsd
  • solaris
  • other (please specify which)

Browsersync use-case

  • API
  • Gulp
  • Grunt
  • CLI
@selected-pixel-jameson
Copy link

I think that the issue I'm running into is related to this as well. When trying to build I get an error stating that it can't find a reference to the module etag. It looks like this might have been a problem in a previous build as well. #1471

@Akiyamka
Copy link

I join, the same problem.
Linux: [ 4.14.74-1-MANJARO ]
Node:[ v8.9.4 ]
Npm: [ 6.4.1 ]
Gulp: [ 3.9.1 ]
Browsersync [ 2.26.0 ]

@shakyShane
Copy link
Contributor

Hi all, I've published browser-sync-client@2.26.1 which should fix this :)

@lazysoftwareman
Copy link
Author

Thank you shakyShane

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants