-
Notifications
You must be signed in to change notification settings - Fork 11
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 🚨 #1
Comments
After pinning to 13.2.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 14.4.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 28 commits.
There are 28 commits in total. See the full diff |
Version 14.5.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 37 commits.
There are 37 commits in total. See the full diff |
Version 16.2.2 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv16.2.2Remove some extraneous files from the published package. CommitsThe new version differs by 76 commits.
There are 76 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v16.2.3add empty stub for the change the "browser" field link to the browser-field-spec repo instead of the old gist. CommitsThe new version differs by 81 commits.
There are 81 commits in total. See the full diff |
Version 13.3.0 of browserify just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As browserify is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
Commits
The new version differs by 4 commits .
6efcd65
13.3.0
cbc20ac
use carat on assert package
30b30ca
Merge branch 'patch-2' of https://github.com/jscissr/node-browserify
dd9edd7
deps: update assert
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: