leecade / leecade/fe

An in-range update of babel-loader is breaking the build 🚨

Open
#58 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

greenkeeper
Dominant language
JavaScript
Stars
15
Forks
4
No merged PRs in 30d

Description

Version 6.3.0 of babel-loader just got published.

Branch Build failing 🚨
Dependency babel-loader
Current Version 6.2.10
Type dependency

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

As babel-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

  • ✅ coverage/coveralls First build on greenkeeper/babel-loader-6.3.0 at 12.808% Details

  • ✅ ci/circleci Your tests passed on CircleCI! Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes v6.3.0
🚀 New Feature

Allow to override BABEL_ENV/NODE_ENV at loader-level. Useful for isomorphic applications which have separate babel config for client and server.

🐛 Bug Fix
  • Update loader-utils dependency to ^0.2.16 to fix compatibility with webpack 2 (#371) @leonaves
💅 Polish
  • Improve FS caching to do less sync calls which improves performance slightly (#375) @akx
Commits

The new version differs by 10 commits .

  • 877e956 6.3.0
  • 4b3bafa FS caching improvements (#375)
  • 0b19a6d Update loader-utils dependecy to ^0.2.16 (#371)
  • 15881f4 Add env query parameter. (#368)
  • e9e3702 Update yarn.lockk
  • 707f31c chore(package): update eslint-config-babel to version 6.0.0 (#360)
  • 5657f48 chore(package): update eslint-config-babel to version 5.0.0 (#359)
  • 757002a Remove plugin-babel (#358)
  • a7e16da Update eslint-config-babel to the latest version 🚀 (#357)
  • 3900952 Update CHANGELOG.md

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

  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 by examining the greenkeeper/babel-loader-6.3.0 comparison and the failed AppVeyor build linked in the issue. Reproduce the build with babel-loader 6.3.0, inspect the release changes for the cause, and confirm that the project build passes after the dependency issue is resolved.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.