An in-range update of browserify is breaking the build 🚨
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- build-system
Research direction
Start by reproducing the failed Travis CI build for the greenkeeper/browserify-13.2.0 branch and inspect the six-commit browserify diff linked in the issue. Done means the project build passes with the dependency update or a compatible version choice.
Written by the indexing model from the issue text.
Description
Version 13.2.0 of browserify just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | browserify |
| Current Version | 13.1.1 |
| Type | devDependency |
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
- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 6 commits .
163515713.2.0d2392a4Merge branch 'master' of https://github.com/laurynasl-wix/node-browserifybf061d8Allow configuring transformKey option for module-deps9e3b11eMerge branch 'master' of https://github.com/Abhinay077/node-browserify71240c2Update package.json5c87f47Update package.json
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 🌴
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from leostera/projector
-
greenkeeper
Difficulty 2/5 1-3 hours Newbie friendliness 38/100
-
greenkeeper
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
greenkeeper
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
greenkeeper
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
greenkeeper
Difficulty 3/5 1-2 days Newbie friendliness 25/100
All issues in leostera/projector
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100