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

Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM #297

Open
dakk opened this issue Mar 15, 2017 · 42 comments
Open

Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM #297

dakk opened this issue Mar 15, 2017 · 42 comments

Comments

@dakk
Copy link

dakk commented Mar 15, 2017

Today I tried to install lwip on ubuntu 16.04 and I get this error during the compilation phase:

   CC(target) Release/obj.target/lwip_decoder/src/lib/png/png.o
 In file included from ../src/lib/png/png.c:14:0:
 ../src/lib/png/pngpriv.h:805:4: error: error ZLIB_VERNUM != PNG_ZLIB_VERNUM "-I (include path) error: see the notes in pngpriv.h"
  #  error ZLIB_VERNUM != PNG_ZLIB_VERNUM \
lwip_decoder.target.mk:165: recipe for target 'Release/obj.target/lwip_decoder/src/lib/png/png.o' failed

Am I missing something?

@rsoladan
Copy link

+1

@ajuste
Copy link

ajuste commented Mar 15, 2017

I believe I used to have this error with node 7.x. have you tried 6.x ? This Is just to narrow the cause; not a solution.

@danibram
Copy link

danibram commented Mar 15, 2017

+1 in node 7,
In node 6 works fine! Thanks @ajuste

@willbamford
Copy link

Looks like libpng and zlib require an update #258 (comment)

@dakk dakk changed the title Failed to install: ZLIB_VERNUM != PNG_ZLIB_VERNUM Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM Mar 16, 2017
@dakk
Copy link
Author

dakk commented Mar 16, 2017

Yep, with node6 it's working fine, thank you. I left the issue open for node7

@phw
Copy link

phw commented Apr 3, 2017

Node 7.4 and earlier is also working for me, 7.8 not. Haven't tried other versions in between, yet.

@gagge
Copy link

gagge commented Apr 5, 2017

node 7.7.3 have the same issue it seems.

@mark-veenstra
Copy link

I have the exact same error using lwip v0.0.9 with Node v6.10.2 and npm version 4.4.4.
I can't understand what is wrong.

@ragecryx
Copy link

ragecryx commented Apr 6, 2017

I have this issue in node 6.10.2

@mark-veenstra
Copy link

Changing the lwip version in package.json to the development branch of this package solved the issue in Node v6.10.2:

Change the use of version 0.0.9 to https://github.com/Pajk/lwip#development

@dakk
Copy link
Author

dakk commented Apr 7, 2017

@mark-veenstra thanks; btw it's not a good idea using a development branch in production.

@mark-veenstra
Copy link

@dakk no it isn't but what to do if you have no other choice? Seems like Ubuntu is installing the latest Node 6.x version and I can't find a way to downgrade the NodeJS. Even if I could which versions should I use?

@dakk
Copy link
Author

dakk commented Apr 7, 2017

@mark-veenstra I'm doing the same (using it in production)

@edittler
Copy link

edittler commented Apr 7, 2017

I have same error in macOS 10.12.4, using node v4.8.2 or v6.10.2.

@edittler
Copy link

edittler commented Apr 7, 2017

Finally I solve my problem replacing lwip for pajk-lwip.

@ghost
Copy link

ghost commented Apr 7, 2017

@edittler save my day.
Have macOS 10.12.4 and I'm able to install it without error using node v6.0.0, but get the same error on node v6.10.2 and v.7.8.0.

@phoenix741
Copy link

phoenix741 commented Apr 10, 2017

Hi,

Waiting for a new version of this lib too.
I have the same probleme with the last version of node 6

@picheli20
Copy link

@nahody same for me! Worked only with version 6.0.0.

Tip: if sameone needs to changes the node version quickly I recommend the nvm, it's a node version manager.

@spchuang
Copy link

+1

@edittler
Copy link

It works also in version 6.10.1 or less. The problem is in version 6.10.2.

@maxceem
Copy link

maxceem commented Apr 21, 2017

Same for me on macOS 10.12.3, failed on v7.9.0 and v6.10.2 but works on v6.10.1.

@slava-viktorov
Copy link

slava-viktorov commented Apr 21, 2017

v7.9.0
~/home/slava/.node-gyp/7.9.0/include/node/zlib.h
#define ZLIB_VERSION "1.2.11"
#define ZLIB_VERNUM 0x12b0
#define ZLIB_VER_REVISION 11
#define ZLIB_VERNUM 0x12b0
v6.9.1
#define ZLIB_VERSION "1.2.8"
#define ZLIB_VERNUM 0x1280
#define ZLIB_VER_REVISION 8
#define ZLIB_VERNUM 0x1280

lwip/src/decoder/pnglibconf.h
#define PNG_ZLIB_VERNUM 0x1280

lwip/src/lib/png/pngpriv.h
if PNG_ZLIB_VERNUM != 0 && PNG_ZLIB_VERNUM != ZLIB_VERNUM error ZLIB_VERNUM != PNG_ZLIB_VERNUM \ "-I (include path) error: see the notes in pngpriv.h"

If you change the version of zlib to 0x12b0 in pnglibconf.h, then the project is compiled. And the tests are executed without errors.

It works, but it's not right ...
Probably you need to connect the zlib directory from the project instead of the node directory.

@suits-at
Copy link

suits-at commented May 4, 2017

@slava-viktorov Changing the ZLIB_VERSION to 0x1280 (I am using Node: v6.10.3) worked for me, but this is still a very dirty fix...

@meszaros-lajos-gyorgy
Copy link

meszaros-lajos-gyorgy commented May 5, 2017

I've tried using the development version of pajk-lwip and it resolves the issues, but it introduces a new one:

png.obj : error LNK2001: unresolved external symbol png_save_uint_32 [...\node_modules\pajk-lwip\build\lwip_decoder.vcxproj]

I'm using node v.7.7.3 and node-gyp v3.6.1

Editing the ZLIB_VERNUM of node-gyp solves the issue, I can install lwip.

@fatso83
Copy link

fatso83 commented May 9, 2017

I have manually tested a range of Node versions:

4.6.2 OK (used in Meteor 1.4)
4.8.4 NOT OK (used in Meteor 1.5.1)
6.10.0 OK
6.10.1 OK
6.10.2 NOT OK
7.3.0 OK
7.4.0 OK
7.5.0 OK
7.6.0 NOT OK
7.7.0 NOT OK
7.8.0 NOT OK
7.10.0 NOT OK

Hope this helps someone. Using a Node version manager you can install this using a working version on the same major version as you are currently using, and then after installing it, switch back to latest version of that major version.

P.S. An easier option might be to simply use a image manipulation library written solely in javascript. See below.

--
edit on July 19: added Node versions used in Meteor
edit on Nov 3: added comment to a patch to replace with jimp

@arackaf
Copy link

arackaf commented May 13, 2017

For the benefit of anyone else in search of a solution, your best bet may be to give jimp a try. It has a similar (and sometimes simpler) API, with zero external dependencies, so no more struggling with node-gyp.

https://www.npmjs.com/package/jimp

@GuyPaddock
Copy link

I was really hopeful with this solution:

The node-gyp version 4.4.2 has the right ZLIB_VERNUM=0x1280 in zlib.h.
I could solve the problem by specficing a target version for node-gyp via commandline:
SET NPM_CONFIG_TARGET=v4.4.2
npm config set target=v4.4.2 --global
npm install --global sprity

But after this trick, I get this error when trying to run the application:

Error: The module '/theme/node_modules/node-sass/vendor/linux-x64-57/binding.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 51. This version of Node.js requires
NODE_MODULE_VERSION 57. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).

Yukaii added a commit to hackmdio/emojify.js that referenced this issue Aug 17, 2019
@hotrush
Copy link

hotrush commented Aug 26, 2020

Hello from 2020 where this issue is still actual

pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 11, 2020
Drop 'sprity', use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 11, 2020
Drop 'sprity', use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 11, 2020
Drop 'sprity', use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 11, 2020
Drop 'sprity', use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 11, 2020
Drop 'sprity', use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 12, 2020
Drop 'sprity', use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 12, 2020
Drop 'sprity', use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 12, 2020
Drop 'sprity', use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 12, 2020
Drop 'sprity', use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 12, 2020
Drop 'sprity', use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 12, 2020
Drop 'sprity', use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 12, 2020
Drop 'sprity', use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 12, 2020
Drop 'sprity', use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 12, 2020
Drop 'sprity' and its dependencies, use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 12, 2020
Drop 'sprity' and its dependencies, use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 12, 2020
Drop 'sprity' and its dependencies, use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 12, 2020
Drop 'sprity' and its dependencies, use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 12, 2020
Drop 'sprity' and its dependencies, use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 12, 2020
Drop 'sprity' and its dependencies, use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 12, 2020
Drop 'sprity' and its dependencies, use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)

---

Let's embrace the new version of Node.js!
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 12, 2020
Drop 'sprity' and its dependencies, use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

Attention!
> If your img pipeline requires 'Buffer' contents, then this can be remedied via 'vinyl-buffer': [3]

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)
[3] [gulp.spritesmith  -  npm § Breaking changes in 6.0.0](https://www.npmjs.com/package/gulp.spritesmith#breaking-changes-in-600)

---

Let's embrace Node.js 8! (not 10 or 12 because gulp 3 does not support them)
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 12, 2020
Drop 'sprity' and its dependencies, use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].
> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

Attention!
> If your img pipeline requires 'Buffer' contents, then this can be remedied via 'vinyl-buffer': [3]

npm 6.13.4 (node 8.17.0) generated 'package-lock.json', so track its changes [4][5].

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](EyalAr/lwip#297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](google/material-design-icons#757)
[3] [gulp.spritesmith  -  npm § Breaking changes in 6.0.0](https://www.npmjs.com/package/gulp.spritesmith#breaking-changes-in-600)
[4] [npm-package-lock.json  |  npm Documentation](https://docs.npmjs.com/files/package-lock.json)
[5] [npm install not creating a new package-lock.json - Stack Overflow](https://stackoverflow.com/questions/45866533/npm-install-not-creating-a-new-package-lock-jsonc)

---

Let's embrace Node.js 8! (not 10 or 12 because gulp 3 does not support them)
pzhlkj6612 added a commit to pzhlkj6612/kitauji-gwent that referenced this issue Oct 14, 2020
Drop 'sprity' and its dependencies, use 'gulp.spritesmith-multi'.

The plugin 'sprity' is great, but its dependencies are so complicated [1].

And then,
> That library can be replaced by the spritesmith toolkit which aims
to do the same task. [2]

Attention!
> If your img pipeline requires 'Buffer' contents, then this can be remedied via 'vinyl-buffer': [3]

npm 6.13.4 (node 8.17.0) generated 'package-lock.json', so track its changes [4][5].

[1] [Failed to install with node7: ZLIB_VERNUM != PNG_ZLIB_VERNUM · Issue #297 · EyalAr/lwip](github.com/EyalAr/lwip/issues/297)
[2] [Change sprity/sprity-gm with spritesmith/gmsmith by goonode · Pull Request #757 · google/material-design-icons](github.com/google/material-design-icons/pull/757)
[3] [gulp.spritesmith  -  npm § Breaking changes in 6.0.0](https://www.npmjs.com/package/gulp.spritesmith#breaking-changes-in-600)
[4] [npm-package-lock.json  |  npm Documentation](https://docs.npmjs.com/files/package-lock.json)
[5] [npm install not creating a new package-lock.json - Stack Overflow](https://stackoverflow.com/questions/45866533/npm-install-not-creating-a-new-package-lock-jsonc)

---

Let's embrace Node.js 8! (not 10 or 12 because gulp 3 does not support them)

---

I'm sorry for a bunch of references (in EyalAr/lwip and google/material-design-icons) from amended commits after rewriting history. [6]

[6] [Remove references from amended commits after rewriting history · Issue #1081 · isaacs/github](github.com/isaacs/github/issues/1081)
@xhyrom
Copy link

xhyrom commented Nov 20, 2023

Hello from 2020 where this issue is still actual

Hello from 2023

@marcj
Copy link

marcj commented Jan 15, 2025

2025, just got the same problem on macos 15.2. great

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

No branches or pull requests