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

Fix failing tests on Windows #67

Merged
merged 1 commit into from
Mar 13, 2018
Merged

Conversation

cspotcode
Copy link
Contributor

  • What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Bug fix

  • What is the current behavior? (You can also link to an open issue here)

Tests fail on Windows.

  • What is the new behavior (if this is a feature change)?

Tests pass on Windows. (not completely; see below)

  • Other information:

hashAllTheThings used to return paths with native separators, which did not match the hard-coded posix-style paths elsewhere in the tests.

Tests still do not completely pass because the latest version of execa is using an outdated version of cross-spawn with a bug. They've merged a PR to upgrade but haven't published it to NPM yet. sindresorhus/execa#131

@bitjson bitjson merged commit a661935 into bitjson:master Mar 13, 2018
@bitjson
Copy link
Owner

bitjson commented Mar 13, 2018

Awesome, thanks @cspotcode!

@bitjson
Copy link
Owner

bitjson commented Mar 13, 2018

@cspotcode I didn't realize that Node.js' path.relative() always return a *nix style path.

This works, so I merged this version already (thanks for the PR!) – have you seen path.normalize()? Should we use that rather than the normalizePath function?

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

Successfully merging this pull request may close these issues.

None yet

2 participants