-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Node.js v6: Can't pass null to path module functions #272
Comments
Oh, wild. Good to know. We probably ought to go ahead and open a PR with v6 in the Travis config and start getting ready! Thanks! |
Also, for future reference: the |
Got it, thanks for the info. v6 isn't out officially yet so I'm not sure if there's a way to get Travis to build with it, but they're aiming to release it tomorrow I believe. In the meantime the rc builds are here: https://nodejs.org/download/rc/ |
fixed in #273 |
In Node.js v6, all
path
functions will now throw an error if they receive a non-string path argument.eslint-import-resolver-node
returnspath: null
for core modules which causesfileExistsWithCaseSync
to throw an error.I wasn't sure if it would be better to make the change in the resolver or the plugin itself so I'm just opening an issue about this for now.
The text was updated successfully, but these errors were encountered: