ruthmoog / bee

🐝 A mobile application for surveying bumblebees.
https://purple-wood-8308.fly.dev/
MIT License
2 stars 0 forks source link

npm watch bug? #19

Closed ruthmoog closed 1 year ago

ruthmoog commented 1 year ago

ruthmoog@Ruths-Mac-mini bee % npm run watch

> watch
> npm-watch

No task specified. Will go through all possible tasks
[build] [nodemon] 2.0.22
[build] 
src/main.js → static/bundle.js...
[build] created static/bundle.js in 36ms
[build] node:events:489
      throw er; // Unhandled 'error' event
      ^

Error: write EPIPE
    at afterWriteDispatched (node:internal/stream_base_commons:160:15)
    at writeGeneric (node:internal/stream_base_commons:151:3)
    at Socket._writeGeneric (node:net:946:11)
    at Socket._write (node:net:958:8)
    at writeOrBuffer (node:internal/streams/writable:399:12)
    at _write (node:internal/streams/writable:340:10)
    at Writable.write (node:internal/streams/writable:344:10)
    at console.value (node:internal/console/constructor:299:16)
    at console.log (node:internal/console/constructor:376:26)
    at log (/Users/ruthmoog/Computer/bee/node_modules/nodemon/lib/utils/log.js:34:15)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}

Node.js v20.1.0
gypsydave5 commented 1 year ago

Ah, node. How I've missed you.

gypsydave5 commented 1 year ago

First step to debugging this is to do some error handling in the builder

gypsydave5 commented 1 year ago

ah you can't because it's a black box. BAH.

gypsydave5 commented 1 year ago

My only guess at this point is that you're changing files in the watched file directory?

gypsydave5 commented 1 year ago

Might also be a conflict with the internal npm build command? try renaming to something else like bob and see what you get.

ruthmoog commented 1 year ago

This command now runs ok, assume it's fixed by @quii 's changes running via the package.json file