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.

ENOSPC error after ng serve

See original GitHub issue

Linux with node 5.3.0 (and plenty of free disk space 😉 ) Got this stack

Build successful - 1857ms.

Slowest Trees                                 | Total               
----------------------------------------------+---------------------
DiffingTSCompiler                             | 1769ms              

Slowest Trees (cumulative)                    | Total (avg)         
----------------------------------------------+---------------------
DiffingTSCompiler (1)                         | 1769ms              

fs.js:1315
    throw error;
    ^

Error: watch /home/t8g/devs/talc/tata/node_modules/angular-cli/node_modules/ember-cli/node_modules/bower/node_modules/update-notifier/node_modules/string-length/node_modules ENOSPC
    at exports._errnoException (util.js:855:11)
    at FSWatcher.start (fs.js:1313:19)
    at Object.fs.watch (fs.js:1341:11)
    at NodeWatcher.watchdir (/home/t8g/devs/talc/tata/node_modules/angular-cli/node_modules/ember-cli/node_modules/sane/src/node_watcher.js:144:20)
    at Walker.<anonymous> (/home/t8g/devs/talc/tata/node_modules/angular-cli/node_modules/ember-cli/node_modules/sane/src/node_watcher.js:351:12)
    at emitTwo (events.js:87:13)
    at Walker.emit (events.js:172:7)
    at /home/t8g/devs/talc/tata/node_modules/angular-cli/node_modules/ember-cli/node_modules/sane/node_modules/walker/lib/walker.js:69:16
    at FSReqWrap.oncomplete (fs.js:82:15)

Issue Analytics

State:
Created 8 years ago
Reactions:1
Comments:5

Top GitHub Comments

3reactions

brombombcommented, Jan 5, 2016

Ran into a similar issue. It was due to using up the maximum number of file watchers on my system. A good reference I found: http://unix.stackexchange.com/questions/13751/kernel-inotify-watch-limit-reached

Specifically mine was caused by powerline daemon using a few and then NodeWatcher trying to use the rest. Setting this to a larger number as linked above fixed it for me.

0reactions

angular-automatic-lock-bot[bot]commented, Sep 5, 2019

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}

Top Results From Across the Web

Angular 2 quickstart ENOSPC error - Stack Overflow

Its a problem of space. When your installing packages, your disc can nolonger accomodate them thus the error. Solution ...

How To Fix - Error "ENOSPC: System Limit for Number of File ...

First thing first – ENOSPC -> Denotes that means that there is not sufficient space on the drive (or Temp folder also) to...

Error: ENOSPC: System limit for number of file watchers ...

When developing JavaScript-based applications on App Service Linux, ... Error: ENOSPC: System limit for number of file watchers reached on ...

How to Fix "throw er; // Unhandled 'error' event"?

If you have a number of node processes running this might be part of your issue. I've noticed the problem coming up more...

Error ng serve in angular tutorial Agenda app - MDBootstrap

Then remove node_modules and package-lock.json and reinstall your dependencies with npm install command. The project should work correctly after that. Aurora ...