Skip to content

Conversation

@Fishrock123
Copy link
Contributor

See https://github.com/nodejs/io.js/pull/1920/files#r32701699, this also requires the long path fix from #1991

@Fishrock123Fishrock123 added the module Issues and PRs related to the module subsystem. label Jun 18, 2015
@bnoordhuis
Copy link
Member

LGTM but a regression test would be nice.

@targos
Copy link
Member

this test I added in #1991 may be enough. I can try when I am back home.

@targos
Copy link
Member

or start a CI on master ? It will fail if I am right

@ChALkeR
Copy link
Member

I still think that it might be better to wrap internalModuleStat and internalModuleReadFile

@Fishrock123
Copy link
ContributorAuthor

@targos
Copy link
Member

@ChALkeR I agree. We can introduce internal/fs to expose the wrapped functions

@mscdexmscdex added the windows Issues and PRs related to the Windows platform. label Jun 18, 2015
@Fishrock123
Copy link
ContributorAuthor

CI on master does not appear to catch it?

@ChALkeRChALkeR mentioned this pull request Jun 18, 2015
@targos
Copy link
Member

apparently not 😞

@vkurchatkin
Copy link
Contributor

I still think that it might be better to wrap internalModuleStat and internalModuleReadFile…

+1

@Fishrock123
Copy link
ContributorAuthor

#2013

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

moduleIssues and PRs related to the module subsystem.windowsIssues and PRs related to the Windows platform.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants

@Fishrock123@bnoordhuis@targos@ChALkeR@vkurchatkin@mscdex