Autodesk / Autodesk/theo-loader

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

Open
#127 2 comments 0 reactions 0 assignees View on GitHub
greenkeeper
Dominant language
JavaScript
Stars
21
Forks
9
PR merge metrics
No merged PRs in 30d

Description

## The dependency [loader-utils](https://github.com/webpack/loader-utils) was updated from `1.2.3` to `1.3.0`.

🚨 [View failing branch](https://github.com/Autodesk/theo-loader/compare/master...Autodesk:greenkeeper%2Floader-utils-1.3.0).

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

loader-utils is a direct dependency of this project, and **it is very likely causing it to break**. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/Autodesk/theo-loader/builds/652581321?utm_source=github_status&utm_medium=notification)).

---

Release Notes for v1.3.0


1.3.0 (2020-02-19)


Features



  • support the [query] template for the interpolatedName method (#162) (469eeba)

Commits

The new version differs by 5 commits.



  • 06d36cf chore(release): 1.3.0

  • 469eeba feat: support the [query] template for the interpolatedName method (#162)

  • 909c99d chore: funding.yml config and CI fix (#159)

  • b5b74f0 Set up CI with Azure Pipelines

  • 7970c48 docs: small grammar change (#144)


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

Open the contributing guide

Research direction

Start by checking the failing Greenkeeper branch and the Travis CI build for the update from loader-utils 1.2.3 to 1.3.0. Compare the loader-utils 1.2.3-to-1.3.0 release notes and reproduce the failure; done means the project 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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.