-
Notifications
You must be signed in to change notification settings - Fork 377
Drop dependency on deprecated gulp-util
#647
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
Conversation
17b597b to
467d580
Compare
|
This PR also update the versions tested with CI to match the ones used by Sass itself. |
There was a problem hiding this 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" | |||
There was a problem hiding this comment.
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.
|
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? |
|
Hi, 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. |
|
Hi, I am having trouble to make Are you sure (Also, lock files are exactly there for this kind of situation, to avoid a transitive dependency to break everything) |
|
Correct. The latest release 4.7.2 pinned to a version on request that still
supported old node. Unfortunately that release has issues with iojs v3 so
I'm ok with not testing iojs in ci.
…On 29 Dec. 2017 12:52 am, "Charles Samborski" ***@***.***> wrote:
Hi, I am having trouble to make node-sass work with iojs (Node 3). I
pinned node-sass to exactly 4.2.0 but its install step has a dependency
on request which itself depends on hoek which requires Node 4.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#647 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjZWDYXqzAnfJmwiQpDM3CZb0-pneesks5tE50EgaJpZM4RN4zD>
.
|
|
@xzyfer Even if this Node issue is not related to |
|
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. |
|
@xzyfer @dlmanning |
|
@xzyfer @dlmanning |
|
We're happy to do it. We're just juggling release timelines for gulp-sass,
node-sass, and LibSass so that we're not leaving users behind with new
features landing in node-sass.
Dropping Node < 4 support is massive breaking change for us that requires
some coordination.
…On 27 Jan. 2018 10:28 am, "Charles Samborski" ***@***.***> wrote:
@xzyfer <https://github.com/xzyfer> @dlmanning
<https://github.com/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.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#647 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjZWL3Do0wUSQwdghmNxRAyODt6K1Fkks5tOl-EgaJpZM4RN4zD>
.
|
|
hi, any update about this PR? |
|
No. Any updates would appear on this issue.
…On 7 Feb. 2018 12:42 am, "Roberto Robson" ***@***.***> wrote:
hi, any update about this PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#647 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjZWHh3pxlNOQjYWGBNuQD91ELTAXCdks5tSFaxgaJpZM4RN4zD>
.
|
|
@xzyfer will it be fixed after 5 years (now) or we just wait node 4 EOL? |
|
@xzyfer @dlmanning any luck on merging this PR? :( |
4059a62 to
856294c
Compare
5c3ead2 to
cc4ed2f
Compare
|
Looks like there are a couple separate breaking changes that'll land soonish. |
|
any news if this will get merged or if a new PR to fix the merge conflicts is necessary, @demurgos @xzyfer @dlmanning ? |
|
There is linked pr that includes these changes and more and a checklist for
when it merged.
…On Mon., 26 Mar. 2018, 7:09 pm Veeck, ***@***.***> wrote:
any news if this will get merged or if a new PR to fix the merge conflicts
is necessary, @demurgos <https://github.com/demurgos> @xzyfer
<https://github.com/xzyfer> @dlmanning <https://github.com/dlmanning> ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#647 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjZWKHEuBVQptqdANYb5bt8eGYjTtkQks5tiKIggaJpZM4RN4zD>
.
|
|
Thanks heaps, this has been included in #667 |
Closes #646