sprity: PluggableError: lwip not found

I just install sprity with npm i sprity and then when I used it with gulp I have this error:

[10:50:58] Starting 'sprites'...
[10:50:59] 'sprites' errored after 1.39 s
[10:50:59] Error: PluggableError: lwip not found.
    at formatError (/usr/lib/node_modules/gulp/bin/gulp.js:169:10)
    at Gulp.<anonymous> (/usr/lib/node_modules/gulp/bin/gulp.js:195:15)
    at emitOne (events.js:77:13)
    at Gulp.emit (events.js:169:7)
    at Gulp.Orchestrator._emitTaskDone (/.../node_modules/gulp/node_modules/orchestrator/index.js:264:8)
    at /.../node_modules/gulp/node_modules/orchestrator/index.js:275:23
    at finish (/.../node_modules/gulp/node_modules/orchestrator/lib/runTask.js:21:8)
    at module.exports (/.../node_modules/gulp/node_modules/orchestrator/lib/runTask.js:36:10)
    at Gulp.Orchestrator._runTask (/.../node_modules/gulp/node_modules/orchestra

Sprity: 1.0.8 Node: 4.2.4 NPM: 2.14.12

About this issue

Original URL
State: open
Created 8 years ago
Reactions: 3
Comments: 21

Most upvoted comments

It’s funny how people ask to change Node version, instead of updating their packages. How can a serious project (I don’t mean this package, but our - users’ - projects) play with the version of platform so easily, is beyond me. If I am locked to, let’s say Node v6, I am dead locked. Please guys, don’t ask this or that version of Node, instead update your works. We won’t have a progress if we are locked to an archaic version of it.

+30

shehi on Oct 18, 2016

Maybe you can try spritesmith, I tried it and it has no error, https://github.com/Ensighten/spritesmith

justforuse on Jul 20, 2017

it was such a pain trying to work around this with the most recent node version ( node 8 in my case), but I eventually did what @rickdoesburg did, somewhat. https://github.com/sprity/sprity/issues/47#issuecomment-239791099

How I worked around it:

Installed nvm
nvm install 5.12.0
nvm use 5.12.0
rm -fr ./node_modules
npm install && npm install --save sprity@1.0.8

notes:

if your node scripts contain some exotic esnext features with no transpilation done to them beforehand, then you’re going to have a bad time with this work around. check https://node.green/ first

I never had a reason to use nvm until now. Seems like a handy tool for mess like this.

I agree with @shehi https://github.com/sprity/sprity/issues/47#issuecomment-254444325

I did not test this, but it may be possible to skip the whole nvm dance by using sprity the programmatic way https://github.com/sprity/sprity#programatic-usage and swapping the defualt engine to sprity-gm https://github.com/sprity/sprity#options

lmj0011 on Mar 31, 2018

I’m having this issue. Probably linked to this? https://stackoverflow.com/questions/32707229/getting-errors-while-doing-npm-in-my-project

Alright edit: How I fixed it:

Installed nvm, installed node 0.12.7
nvm use 0.12.7
npm install lwip
npm install sprity
npm install sprity-sass

rickdoesburg on Aug 15, 2016