Consistently getting ENOSPC errors when using live-reloading

[ebolyen]

I'm following the instructions in the README, and some of the time, there's no issue, but if I change enough subpackages I end up hitting my limit on watched files.

It looks like node_modules isn't exempted from chokidar's file watcher. So I tend to get a lot of these:

@myst-theme/book:dev: [1] Error: ENOSPC: System limit for number of file watchers reached, watch '/home/evan/consulting/qiime2/myst-theme/packages/frontmatter/node_modules/@scienceicons/react/24/solid/esm/package.json'
@myst-theme/book:dev: [1]     at FSWatcher.<computed> (node:internal/fs/watchers:247:19)
@myst-theme/book:dev: [1]     at Object.watch (node:fs:2471:36)
@myst-theme/book:dev: [1]     at createFsWatchInstance (/home/evan/consulting/qiime2/myst-theme/node_modules/chokidar/lib/nodefs-handler.js:119:15)
@myst-theme/book:dev: [1]     at setFsWatchListener (/home/evan/consulting/qiime2/myst-theme/node_modules/chokidar/lib/nodefs-handler.js:166:15)
@myst-theme/book:dev: [1]     at NodeFsHandler._watchWithNodeFs (/home/evan/consulting/qiime2/myst-theme/node_modules/chokidar/lib/nodefs-handler.js:331:14)
@myst-theme/book:dev: [1]     at NodeFsHandler._handleFile (/home/evan/consulting/qiime2/myst-theme/node_modules/chokidar/lib/nodefs-handler.js:395:23)
@myst-theme/book:dev: [1]     at NodeFsHandler._addToNodeFs (/home/evan/consulting/qiime2/myst-theme/node_modules/chokidar/lib/nodefs-handler.js:637:21) {
@myst-theme/book:dev: [1]   errno: -28,
@myst-theme/book:dev: [1]   syscall: 'watch',
@myst-theme/book:dev: [1]   code: 'ENOSPC',
@myst-theme/book:dev: [1]   path: '/home/evan/consulting/qiime2/myst-theme/packages/frontmatter/node_modules/@scienceicons/react/24/solid/esm/package.json',
@myst-theme/book:dev: [1]   filename: '/home/evan/consulting/qiime2/myst-theme/packages/frontmatter/node_modules/@scienceicons/react/24/solid/esm/package.json'

I could update my limits, but I don't think there's any point to observing node_modules is there? In the event you updated package versions, I don't think doing a fresh rebuild is that onerous.

[ebolyen]

I've been muddling through by just restarting and doing fresh builds until I magically avoid the issue.

[rowanc1]

I haven't ever come across this error before. 🤔

You can also go into the packages that you need to watch individually and dev/build.