-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Fails with "Path must be a string" on Node 8 #6
Labels
Comments
marionebl
added a commit
to conventional-changelog/commitlint
that referenced
this issue
Nov 19, 2017
Avoid sindresorhus/import-fresh#6 for the time being
marionebl
added a commit
to conventional-changelog/commitlint
that referenced
this issue
Nov 19, 2017
* chore: avoid gpg password prompt * test(core): add failing test case for global extends resolving * fix(core): fall back to globally installed config if available #126 * test: use cwd correctly for git config * test: improve testability of global fallback * fix(core): ensure resolve-globals is detected as dependency * fix: use more recent import-fresh * fix: fall back to require-uncached Avoid sindresorhus/import-fresh#6 for the time being * fix: pull in patch releases
same issue in eslint: eslint/eslint#11066 |
friendly ping @sindresorhus |
Can you try out v3.0.0? It improves the logic for finding the module to clear. |
oops it's working, thanks for fixing this! |
@sindresorhus seems the issue could be closed! |
Great! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In certain conditions
import-fresh
fails with the error messagePath must be a string. Received null
on Node 8.Example build: travis/commitlint#L1738
Digging deeper reveals this is caused by
caller-path
returning aCallsite
that returns null from itsgetFileName
method: caller-path/index.js#L4This in turn is caused by
caller-callsite
returning always the very firstCallsite
it finds by breaking out of the iteration here: caller-callsite/index.js#L13Removing the
break
statement fixes the issue for me - I am not familiar with the APIs used here, so I am not very confident this is the appropriate fix though.Steps to reproduce
The text was updated successfully, but these errors were encountered: