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

Update eslint-import-resolver-node to the latest version 🚀 #77

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

greenkeeper[bot]
Copy link

@greenkeeper greenkeeper bot commented Jun 23, 2017

Version 0.3.1 of eslint-import-resolver-node just got published.

Dependency eslint-import-resolver-node
Current Version 0.3.0
Type devDependency

The version 0.3.1 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of eslint-import-resolver-node.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.


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 🌴

@coveralls
Copy link

Coverage Status

Coverage remained the same at 95.876% when pulling 9b351dd on greenkeeper/eslint-import-resolver-node-0.3.1 into 8c10fdf on master.

@greenkeeper
Copy link
Author

greenkeeper bot commented Jan 5, 2018

Version 0.3.2 just got published.

Update to this version instead 🚀

Release Notes re-exports + messages

Aggregates ExportAllDeclaration names (export * from './third-module';).
Caches export map. (didn't seem to especially help in tests, but the files are tiny.)
named rule has a more informative message.

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

Successfully merging this pull request may close these issues.

1 participant