Skip to content

Conversation

@MylesBorins
Copy link

This uses a [email protected] version coupled with graceful-fs@4 as a
fallback for the regular combination of [email protected] and graceful-fs@3,
so that gulp@3 doesn't break on newer Node.js versions where
graceful-fs@3 is unsupported.

Current setups and Node.js versions (6.x and below) are not affected.

Alternative approach to #1760

This uses a [email protected] version coupled with graceful-fs@4 as a
fallback for the regular combination of [email protected] and graceful-fs@3,
so that gulp@3 doesn't break on newer Node.js versions where
graceful-fs@3 is unsupported.

Current setups and Node.js versions (6.x and below) are not affected.
@phated
Copy link
Member

phated commented Aug 18, 2016

I think this is the wrong approach. I know you want to attempt to handle this transparently but it would change the semantics of the runtime without any way to know. Let's continue discussion but I'm going to close so it doesn't accidentally get merged.

@phated phated closed this Aug 18, 2016
@MylesBorins
Copy link
Author

@phated would you be open to a cli flag?

gulp --node-compat?

@phated
Copy link
Member

phated commented Aug 18, 2016

Not really. We don't support forcing certain flags (yet) which makes that clumsy to use. So far I like the separate module idea but I need to think on it.

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.

2 participants