Skip to content

Conversation

@demurgos
Copy link
Contributor

Closes #646

@demurgos demurgos changed the title Issue 646 Drop dependency on deprecated gulp-util Dec 27, 2017
@demurgos demurgos force-pushed the issue-646 branch 4 times, most recently from 17b597b to 467d580 Compare December 28, 2017 01:21
@demurgos
Copy link
Contributor Author

This PR also update the versions tested with CI to match the ones used by Sass itself.
The main difference is that 0.10.0 is no longer tested because Node stopped maintaining it, and most dependencies started to require Node 4+.

Copy link
Collaborator

@xzyfer xzyfer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove package.lock and yarn.lock files

@@ -1,6 +1,7 @@
language: node_js
node_js:
- "0.10"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Node sass still officiallly supports 0.10, 0.12, and iojs. It's not tested in Travis but is tested locally before releases.

@xzyfer
Copy link
Collaborator

xzyfer commented Dec 28, 2017

Thanks. Dropped support for old node versions will require a major version bump. I wasn't planning on bumping the major until node-sass@5 landed. Is it possible to make this work with Node 0.10?

@demurgos
Copy link
Contributor Author

demurgos commented Dec 28, 2017

Hi,
Thanks for the info: I did not know that Sass still wants to support these versions. I'll try to find some older versions of the dependencies that support Node 0.10.0. I opened an issue to discuss this change.

Regarding the lockfiles, you are better off by keeping them, especially if you plan to support unmaintained Node versions. The lock files are intended to be committed and have no effect on consumers: they are used for library developers and CI to make sure that you develop with the same working dependencies.
Edit: One concrete example is that I am currently having issues on Travis to compile Sass for iojs, I wouldn't have this issue if a lockfile was already there.

@demurgos
Copy link
Contributor Author

demurgos commented Dec 28, 2017

Hi, I am having trouble to make node-sass work with iojs (Node 3). I pinned node-sass to exactly 4.0.0 but its install step has a dependency on request which itself depends on hoek which requires Node 4.

Are you sure node-sass supports versions before Node 4?

(Also, lock files are exactly there for this kind of situation, to avoid a transitive dependency to break everything)

@xzyfer
Copy link
Collaborator

xzyfer commented Dec 28, 2017 via email

@demurgos
Copy link
Contributor Author

@xzyfer
I tried my best to support it but at the moment, the best would be to merge #649 first, it's just going to cause more issues.
You are effectively asking me to drop support for iojs, so it's better to do it properly in its own PR and then come back to this issue.

Even if this Node issue is not related to gulp-util, it should be fixed first. Please also note that dropping gulp-util is important because it is causing build issues with the latest release of Gulp 4. You are not the first person I am contacting to patch this and multiple other packages have similar issues were old versions of Node are wrecking havoc the builds because they weren't touched in a year but most dependencies have moved on. We reached a point were not keeping dependencies up-to-date is causing builds to break so I'd really like to have it sorted as fast as possible. Thanks for your support :)

@demurgos
Copy link
Contributor Author

demurgos commented Dec 29, 2017

I was wrong about lock files for libraries (they may have hidden issues with the transitive dependencies, it's better to have them break early), I'll remove them.
Still, please consider migrating to newer Node versions and dropping gulp-util.

@demurgos
Copy link
Contributor Author

@xzyfer @dlmanning
Any news about this PR? gulp-sass is one of the most popular gulp plugins so it is important to keep its dependencies up-to-date.

@demurgos
Copy link
Contributor Author

@xzyfer @dlmanning
Are you looking for maintainers? We're currently discussing in the Gulp team to eventually create an org for popular plugins so we'd be able to help with this kind of maintenance.

@xzyfer
Copy link
Collaborator

xzyfer commented Jan 27, 2018 via email

@betorobson
Copy link

hi, any update about this PR?

@xzyfer
Copy link
Collaborator

xzyfer commented Feb 6, 2018 via email

Repository owner deleted a comment from dima-takoy-zz Feb 10, 2018
@dima-takoy-zz
Copy link

@xzyfer will it be fixed after 5 years (now) or we just wait node 4 EOL?

@johnturingan
Copy link

johnturingan commented Feb 26, 2018

@xzyfer @dlmanning any luck on merging this PR? :(

@xzyfer xzyfer force-pushed the master branch 3 times, most recently from 4059a62 to 856294c Compare March 11, 2018 05:04
@xzyfer xzyfer force-pushed the master branch 10 times, most recently from 5c3ead2 to cc4ed2f Compare March 11, 2018 05:37
@xzyfer
Copy link
Collaborator

xzyfer commented Mar 11, 2018

Looks like there are a couple separate breaking changes that'll land soonish.

@rejas
Copy link

rejas commented Mar 26, 2018

any news if this will get merged or if a new PR to fix the merge conflicts is necessary, @demurgos @xzyfer @dlmanning ?

@xzyfer
Copy link
Collaborator

xzyfer commented Mar 26, 2018 via email

@xzyfer
Copy link
Collaborator

xzyfer commented Mar 26, 2018

Thanks heaps, this has been included in #667

@xzyfer xzyfer closed this Mar 26, 2018
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.

7 participants