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
I'm not sure what the issue is, deprecation warning or not finding the token?
npx nx serve demo-nextjs-page-router --verbose
> NX No access token found
Nx will continue running, but nothing will be written or read from the remote cache.
Run details will also not be available in the Nx Cloud UI.
> nx run demo-nextjs-page-router:serve:development
(node:80489) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
node:events:498
throw er; // Unhandled 'error' event
^
Error: spawn /opt/homebrew/Cellar/node/22.7.0/bin/node ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:286:19)
at onErrorNT (node:internal/child_process:484:16)
at process.processTicksAndRejections (node:internal/process/task_queues:90:21)
Emitted 'error' event on ChildProcess instance at:
at ChildProcess._handle.onexit (node:internal/child_process:292:12)
at onErrorNT (node:internal/child_process:484:16)
at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
errno: -2,
code: 'ENOENT',
syscall: 'spawn /opt/homebrew/Cellar/node/22.7.0/bin/node',
path: '/opt/homebrew/Cellar/node/22.7.0/bin/node',
spawnargs: [
'/Users/user/Projects/fal-js/node_modules/next/dist/bin/next',
'dev',
'--port=4200',
''
]
}
Node.js v22.7.0
———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————
> NX Running target serve for project demo-nextjs-page-router failed
Failed tasks:
- demo-nextjs-page-router:serve:development
Hint: run the command with --verbose for more details.
The text was updated successfully, but these errors were encountered:
.env
is created withFAL_KEY=….
I'm not sure what the issue is, deprecation warning or not finding the token?
The text was updated successfully, but these errors were encountered: