question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

PluggableError: lwip not found

See original GitHub issue

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

Issue Analytics

  • State:open
  • Created 8 years ago
  • Reactions:3
  • Comments:21

github_iconTop GitHub Comments

30reactions
shehicommented, Oct 18, 2016

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.

2reactions
justforusecommented, Jul 20, 2017

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

Read more comments on GitHub >

github_iconTop Results From Across the Web

Developers - PluggableError: lwip not found - - Bountysource
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'......
Read more >
Sprity (gulp spriting image/scss generator) various errors ...
I just ran npm install lwip (https://www.npmjs.com/package/lwip#installation) and then npm install sprity --sav-dev ... It's working now!
Read more >
Type fatal error: lwip/err.h: No such file or directory
Hello,. I'm getting this error when i try to generate lwIP server Application project. I m using SDK 14.7 Tool.
Read more >
Error in include for lwip stack - NXP Community
lwip/opt.h: No such file or directory api_lib.c ... there is probably missing path in your project settings. By default is lwip/opt.h header ...
Read more >
Cloud9 pour jouer avec ZdS... • Forum • Zeste de Savoir
... 27 ms [08:30:19] Error: PluggableError: lwip not found. at formatError (/home/ubuntu/workspace/zds-site/node_modules/gulp/bin/gulp.js:169:10) at Gulp.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found