Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of rollup-plugin-typescript2 is breaking the build 🚨 #127

Closed
greenkeeper bot opened this issue Dec 3, 2019 · 3 comments
Closed

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Dec 3, 2019

The dependency rollup-plugin-typescript2 was updated from 0.25.2 to 0.25.3.

🚨 View failing branch.

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

rollup-plugin-typescript2 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).

Release Notes for 0.25.3

cwd option

Commits

The new version differs by 4 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

@FND
Copy link
Contributor

FND commented Dec 4, 2019

seems like a fluke; works locally

ESLint couldn't find the config "ljharb" to extend from. Please check that the name of the config is correct.

The config "ljharb" was referenced from the config file in "/home/travis/build/faucet-pipeline/faucet-pipeline-js/pkg/faucet-pipeline-typescript/node_modules/resolve/.eslintrc".

@FND FND closed this as completed Dec 4, 2019
@ljharb
Copy link

ljharb commented Dec 4, 2019

This is because something is linting your nested node_modules; you need to make sure your project's eslintignore is ignoring all node_modules folders.

@FND
Copy link
Contributor

FND commented Dec 4, 2019

Sorry for accidentally pinging you, @ljharb, but I appreciate your response; thanks for pointing that out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants