search

vercel / pkg

Package your Node.js project into an executable
https://npmjs.com/pkg
MIT License
24.33k stars 1.02k forks source link

thread worker exited #1893

Closed erpadmin closed 1 year ago

erpadmin commented 1 year ago

What version of pkg are you using?

5.8.1

What version of Node.js are you using?

v16.18.0

What operating system are you using?

arch

What CPU architecture are you using?

x86_64

What Node versions, OSs and CPU architectures are you building for?

node16-linux

Describe the Bug

node:events:505 throw er; // Unhandled 'error' event ^

Error: The worker thread exited at Worker.onWorkerExit (/snapshot/api/node_modules/thread-stream/index.js:180:32) at Worker.emit (node:events:527:28) at Worker.[kOnExit] (node:internal/worker:278:10) at Worker..onexit (node:internal/worker:198:20) Emitted 'error' event on ThreadStream instance at: at destroy (/snapshot/api/node_modules/thread-stream/index.js:349:12) at Worker.onWorkerExit (/snapshot/api/node_modules/thread-stream/index.js:180:3) at Worker.emit (node:events:527:28) at Worker.[kOnExit] (node:internal/worker:278:10) at Worker..onexit (node:internal/worker:198:20)

Expected Behavior

to run same as when app run directly with node

To Reproduce

.

erpadmin commented 1 year ago

any way to get more detail on the node:events?

baparham commented 1 year ago

I suspect this is the same or similar issue as https://github.com/vercel/pkg-fetch/issues/282 Have you been able to try using a newer version of pkg-fetch and node.js to see if that resolves the issue?

github-actions[bot] commented 1 year ago

This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label