Help debugging vague error

Description

Site deploys to netlify and builds fine but if I try to run it locally with npm run build or gatsby develop- it’s ‘compiles’ fine but then if you navigate to localhost:8000 it will ‘load’ for several minutes while displaying nothing and then the server will crash.

Steps to reproduce

Repo: https://github.com/Fazyyy/Trago2Wheels

Simply run a local development and navigate to localhost then watch the console for the build to crash and display the error.

Expected result

Site compiles and runs locally without issue

Actual result

` i ｢wdm｣: Compiling… error UNHANDLED EXCEPTION

Error: UNKNOWN: unknown error, watch

• watchers.js:123 FSEvent.FSWatcher._handle.onchange internal/fs/watchers.js:123:28 `

Environment

Run gatsby info --clipboard in your project directory and paste the output here.

` System: OS: Windows 10 CPU: (4) x64 Intel® Core™ i5-3210M CPU @ 2.50GHz Binaries: npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD Languages: Python: 2.7.15 - /c/Users/user/.windows-build-tools/python27/python Browsers: Edge: 42.17134.1.0 npmPackages: gatsby: ^2.1.14 => 2.1.14 gatsby-image: ^2.0.29 => 2.0.29 gatsby-plugin-google-fonts: 0.0.4 => 0.0.4 gatsby-plugin-react-helmet: ^3.0.6 => 3.0.6 gatsby-plugin-sharp: ^2.0.21 => 2.0.21 gatsby-remark-copy-linked-files: ^2.0.9 => 2.0.9 gatsby-remark-images: ^3.0.4 => 3.0.4 gatsby-source-filesystem: ^2.0.23 => 2.0.23 gatsby-transformer-remark: ^2.2.5 => 2.2.5 gatsby-transformer-sharp: ^2.1.14 => 2.1.14

error The system cannot find the path specified.

Error: The system cannot find the path specified.

• envinfo.js:1 Function.e.exports.sync [npm]/[gatsby]/[envinfo]/dist/envinfo.js:1:4970

• envinfo.js:1 Object.copySync [npm]/[gatsby]/[envinfo]/dist/envinfo.js:1:66948

• envinfo.js:1 Object.t.writeSync.e [as writeSync] [npm]/[gatsby]/[envinfo]/dist/envinfo.js:1:48777

• envinfo.js:1 [npm]/[gatsby]/[envinfo]/dist/envinfo.js:1:46934

• envinfo.js:1 Promise.all.then.e [npm]/[gatsby]/[envinfo]/dist/envinfo.js:1:46949

• util.js:16 tryCatcher [npm]/[gatsby]/[bluebird]/js/release/util.js:16:23

• promise.js:512 Promise._settlePromiseFromHandler [npm]/[gatsby]/[bluebird]/js/release/promise.js:512:31

• promise.js:569 Promise._settlePromise [npm]/[gatsby]/[bluebird]/js/release/promise.js:569:18

• promise.js:614 Promise._settlePromise0 [npm]/[gatsby]/[bluebird]/js/release/promise.js:614:10

• promise.js:694 Promise._settlePromises [npm]/[gatsby]/[bluebird]/js/release/promise.js:694:18

• promise.js:638 Promise._fulfill [npm]/[gatsby]/[bluebird]/js/release/promise.js:638:18

• promise_array.js:126 PromiseArray._resolve [npm]/[gatsby]/[bluebird]/js/release/promise_array.js:126:19

• promise_array.js:144 PromiseArray._promiseFulfilled [npm]/[gatsby]/[bluebird]/js/release/promise_array.js:144:14

• promise.js:574 Promise._settlePromise [npm]/[gatsby]/[bluebird]/js/release/promise.js:574:26

• promise.js:614 Promise._settlePromise0 [npm]/[gatsby]/[bluebird]/js/release/promise.js:614:10

• promise.js:694 Promise._settlePromises [npm]/[gatsby]/[bluebird]/js/release/promise.js:694:18

error UNHANDLED REJECTION

Error: The system cannot find the path specified.

• envinfo.js:1 Function.e.exports.sync [npm]/[gatsby]/[envinfo]/dist/envinfo.js:1:4970

• envinfo.js:1 Object.copySync [npm]/[gatsby]/[envinfo]/dist/envinfo.js:1:66948

• envinfo.js:1 Object.t.writeSync.e [as writeSync] [npm]/[gatsby]/[envinfo]/dist/envinfo.js:1:48777

• envinfo.js:1 [npm]/[gatsby]/[envinfo]/dist/envinfo.js:1:46934

• envinfo.js:1 Promise.all.then.e [npm]/[gatsby]/[envinfo]/dist/envinfo.js:1:46949

• util.js:16 tryCatcher [npm]/[gatsby]/[bluebird]/js/release/util.js:16:23

• promise.js:512 Promise._settlePromiseFromHandler [npm]/[gatsby]/[bluebird]/js/release/promise.js:512:31

• promise.js:569 Promise._settlePromise [npm]/[gatsby]/[bluebird]/js/release/promise.js:569:18

• promise.js:614 Promise._settlePromise0 [npm]/[gatsby]/[bluebird]/js/release/promise.js:614:10

• promise.js:694 Promise._settlePromises [npm]/[gatsby]/[bluebird]/js/release/promise.js:694:18

• promise.js:638 Promise._fulfill [npm]/[gatsby]/[bluebird]/js/release/promise.js:638:18

• promise_array.js:126 PromiseArray._resolve [npm]/[gatsby]/[bluebird]/js/release/promise_array.js:126:19

• promise_array.js:144 PromiseArray._promiseFulfilled [npm]/[gatsby]/[bluebird]/js/release/promise_array.js:144:14

• promise.js:574 Promise._settlePromise [npm]/[gatsby]/[bluebird]/js/release/promise.js:574:26

• promise.js:614 Promise._settlePromise0 [npm]/[gatsby]/[bluebird]/js/release/promise.js:614:10

• promise.js:694 Promise._settlePromises [npm]/[gatsby]/[bluebird]/js/release/promise.js:694:18 `

[treechime]

@sthielen Lifesaver 🙏 Just had this exact same thing and moved the project to the local drive and it worked perfectly.

[sthielen]

For anyone else who might be troubleshooting this, we just encountered it on a Windows build where the user was using a Net Use alias to access the Gatsby project. Using the true path on the filesystem resolved the issue - seems like there was an issue initializing the file watcher for aliased paths. My Windows knowledge is limited, so I’m not sure how to debug any more deeply, but hopefully this helps anyone encountering the same issue.