An in-range update of stylus-loader is breaking the build 🚨
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 15
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Version 2.4.0 of stylus-loader just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | stylus-loader |
| Current Version | 2.3.1 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As stylus-loader is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
Status Details
Commits
The new version differs by 6 commits .
9611dcf2.4.098b7002Add 2.4.0 to changelog21f48e0Merge pull request #154 from mzgoddard/webpack-2-options4d30096Bump webpack 2 version tested on travis8d08bacAdd a bit to the README about using?configwith webpack 1a235bd8Add some help for configuring the loader with webpack 2
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 🌴
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 by inspecting the Greenkeeper branch for stylus-loader 2.4.0 and the linked AppVeyor failure, then compare its dependency changes with the project's current configuration. Done means identifying the build failure and restoring a passing build without breaking the supported webpack setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, webpack
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100