You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After following the v3 quick start guide in an existing next.js app and setting up a call to trigger a job, I get two different kinds of errors when I run the next app:
Broken OpenTelemetry
⚠ ./node_modules/@opentelemetry/instrumentation/build/src/platform/node/instrumentation.js
Critical dependency: the request of a dependency is an expression
Import trace for requested module:
./node_modules/@opentelemetry/instrumentation/build/src/platform/node/instrumentation.js
./node_modules/@opentelemetry/instrumentation/build/src/platform/node/index.js
./node_modules/@opentelemetry/instrumentation/build/src/platform/index.js
./node_modules/@opentelemetry/instrumentation/build/src/index.js
./node_modules/@trigger.dev/core/dist/v3/index.mjs
./node_modules/@trigger.dev/sdk/dist/v3/index.mjs
./trigger/some-job.ts
./app/api/…/route.ts
./node_modules/@opentelemetry/instrumentation/build/src/platform/node/instrumentation.js
These can errors can be silenced with the workaround posted here, but it's unclear to me whether there's actually a problem.
Broken invocations
Trying to invoke a Trigger job results in an error:
⚠ ./node_modules/engine.io-client/node_modules/ws/lib/buffer-util.js
Module not found: Can't resolve 'bufferutil' in './node_modules/engine.io-client/node_modules/ws/lib'
Import trace for requested module:
./node_modules/engine.io-client/node_modules/ws/lib/buffer-util.js
./node_modules/engine.io-client/node_modules/ws/lib/sender.js
./node_modules/engine.io-client/node_modules/ws/wrapper.mjs
./node_modules/engine.io-client/build/esm-debug/transports/websocket-constructor.js
./node_modules/engine.io-client/build/esm-debug/index.js
./node_modules/socket.io-client/build/esm-debug/url.js
./node_modules/socket.io-client/build/esm-debug/index.js
./node_modules/@trigger.dev/core/dist/v3/index.mjs
./node_modules/@trigger.dev/sdk/dist/v3/index.mjs
./trigger/some-job.ts
./app/api/…/route.ts
./node_modules/engine.io-client/node_modules/ws/lib/validation.js
Module not found: Can't resolve 'utf-8-validate' in './node_modules/engine.io-client/node_modules/ws/lib'
Import trace for requested module:
./node_modules/engine.io-client/node_modules/ws/lib/validation.js
./node_modules/engine.io-client/node_modules/ws/lib/sender.js
./node_modules/engine.io-client/node_modules/ws/wrapper.mjs
./node_modules/engine.io-client/build/esm-debug/transports/websocket-constructor.js
./node_modules/engine.io-client/build/esm-debug/index.js
./node_modules/socket.io-client/build/esm-debug/url.js
./node_modules/socket.io-client/build/esm-debug/index.js
./node_modules/@trigger.dev/core/dist/v3/index.mjs
./node_modules/@trigger.dev/sdk/dist/v3/index.mjs
./trigger/some-job.ts
./app/api/…/route.ts
Running npm install bufferutil utf-8-validate seems to solve the problem.
Reproduction repo
To reproduce
In an existing next.js app, follow the steps in the quick start guide. Specifically, npx trigger.dev@beta init.
Occurred with @trigger.dev/sdk3.0.0-beta.12.
Additional information
No response
The text was updated successfully, but these errors were encountered:
Provide environment information
Describe the bug
After following the v3 quick start guide in an existing next.js app and setting up a call to trigger a job, I get two different kinds of errors when I run the next app:
These can errors can be silenced with the workaround posted here, but it's unclear to me whether there's actually a problem.
Trying to invoke a Trigger job results in an error:
Running
npm install bufferutil utf-8-validate
seems to solve the problem.Reproduction repo
To reproduce
In an existing next.js app, follow the steps in the quick start guide. Specifically,
npx trigger.dev@beta init
.Occurred with
@trigger.dev/sdk
3.0.0-beta.12
.Additional information
No response
The text was updated successfully, but these errors were encountered: