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

An in-range update of browserify is breaking the build 🚨 #190

Open
greenkeeper bot opened this issue Jul 5, 2019 · 4 comments
Open

An in-range update of browserify is breaking the build 🚨 #190

greenkeeper bot opened this issue Jul 5, 2019 · 4 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Jul 5, 2019

The devDependency browserify was updated from 16.2.3 to 16.3.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

browserify is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 8 commits.

  • 9824fae 16.3.0
  • 9e3397b Add http2 to builtins (#1913)
  • d2ade25 Add http2 to builtins
  • 876182d Tweak license text so Github detects it correctly
  • 16f82a7 Update license (#1906)
  • 7ad39ce Merge pull request #1139 from insidewarehouse/resolve-exposed-folders
  • f13b713 when a module is exposed, it should still resolve the way it would normally do, i.e. with/without extension and directories should fall back to index, and index from a directory should be accepted with/without extension too
  • 8f80729 Update license

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jul 5, 2019

After pinning to 16.2.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Aug 8, 2019

  • The devDependency browserify was updated from 16.3.0 to 16.4.0.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 5 commits.

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Aug 9, 2019

  • The devDependency browserify was updated from 16.4.0 to 16.5.0.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 4 commits.

  • 506533c 16.5.0
  • 85489cc Update changelog.markdown
  • 4c04949 Merge pull request #1918 from browserify/custom-browser-field
  • 8213b64 Support custom names for "browser" field resolution

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 30, 2020

  • The devDependency browserify was updated from 16.5.0 to 16.5.1.

Your tests are still failing with this version. Compare changes

Release Notes for v16.5.1

Remove deprecated mkdirp version in favour of mkdirp-classic.

00c913f

Pin dependencies for Node.js 0.8 support.

#1939

Commits

The new version differs by 8 commits.

See the full diff

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

No branches or pull requests

0 participants