maple3142 / maple3142/vuejs-contextmenu
An in-range update of rollup-plugin-vue is breaking the build 🚨
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
## The devDependency [rollup-plugin-vue](https://github.com/vuejs/rollup-plugin-vue) was updated from `4.7.1` to `4.7.2`.
🚨 [View failing branch](https://github.com/maple3142/vuejs-contextmenu/compare/master...maple3142:greenkeeper%2Frollup-plugin-vue-4.7.2).
This version is **covered** by your **current version range** and after updating it in your project **the build failed**.
rollup-plugin-vue 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/496049524?utm_source=github_status&utm_medium=notification)).
---
Commits
The new version differs by 3 commits.
487e589chore(release): 4.7.23f879f3fix: Add needMap option to disable source maps8115b06chore: lint
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
- 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.
Research direction
Start with the failing Greenkeeper branch and the linked Travis CI build to identify why rollup-plugin-vue 4.7.2 breaks the project build. Compare the dependency change with the prior 4.7.1 behavior, then verify that the build passes with a compatible dependency version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100