maple3142 / maple3142/vuejs-contextmenu

An in-range update of uglify-js is breaking the build 🚨

Open
#23 40 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

greenkeeper
Dominant language
JavaScript
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

## The devDependency [uglify-js](https://github.com/mishoo/UglifyJS2) was updated from `3.4.9` to `3.4.10`.

🚨 [View failing branch](https://github.com/maple3142/vuejs-contextmenu/compare/master...maple3142:greenkeeper%2Fuglify-js-3.4.10).

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

uglify-js 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](https://travis-ci.org/maple3142/vuejs-contextmenu/builds/507068167?utm_source=github_status&utm_medium=notification)).

---

Release Notes for v3.4.10

 

Commits

The new version differs by 18 commits.



  • 9707ccd v3.4.10

  • cb8f3a2 add Node.js 10 to CI tests (#3342)

  • 8b3259e fix corner case in reduce_vars (#3341)

  • b66f47b update dependencies

  • 8d2e6f3 fix function inlining after reduce_vars (#3340)

  • b3ef5e5 enhance evaluate (#3339)

  • 627f5fb fix corner case with nameCache (#3338)

  • d90777b parse mangle.properties.regex in --config-file properly (#3337)

  • e49297e improve usability of pure_funcs (#3336)

  • ebd82b3 fix corner case in collapse_vars (#3334)

  • d074aa6 fix corner case in collapse_vars (#3333)

  • b052f62 fix corner case in reduce_vars (#3332)

  • d4ac84b fix corner case in arguments & reduce_vars (#3331)

  • e250396 fix corner case in arguments (#3330)

  • c6fa39b Update README.md (#3311)


There are 18 commits in total.


See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Greenkeeper failing branch and the Travis CI build details linked in the issue, then inspect the uglify-js dependency update from 3.4.9 to 3.4.10. Reproduce the build failure and identify a compatible dependency change; done means the build passes again with the updated dependency range.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
build-system, ci-cd
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.