[Warning] Promise hasn't resolved after 25 seconds when vike dev
#2719
-
|
Hello, recently my vike dev command has started randomly giving the following errors at runtime: > @cat/[email protected] dev D:\Web-Project\cat\apps\app
> cross-env NODE_ENV=development vike dev
23:35:33 [vike][Warning] Promise hasn't resolved after 25 seconds
at Object.get (file:///D:/Web-Project/cat/node_modules/.pnpm/[email protected][email protected]_@ty_e3390a99196956df3d2e8ec3315ea7a5/node_modules/vike/dist/esm/utils/genPromise.js:31:33)
at getOrResolveVikeConfig (file:///D:/Web-Project/cat/node_modules/.pnpm/[email protected][email protected]_@ty_e3390a99196956df3d2e8ec3315ea7a5/node_modules/vike/dist/esm/node/vite/shared/resolveVikeConfigInternal.js:91:43)
at getVikeConfigInternal (file:///D:/Web-Project/cat/node_modules/.pnpm/[email protected][email protected]_@ty_e3390a99196956df3d2e8ec3315ea7a5/node_modules/vike/dist/esm/node/vite/shared/resolveVikeConfigInternal.js:57:30)
at resolveConfigs (file:///D:/Web-Project/cat/node_modules/.pnpm/[email protected][email protected]_@ty_e3390a99196956df3d2e8ec3315ea7a5/node_modules/vike/dist/esm/node/api/prepareViteApiCall.js:32:30)
at Module.dev (file:///D:/Web-Project/cat/node_modules/.pnpm/[email protected][email protected]_@ty_e3390a99196956df3d2e8ec3315ea7a5/node_modules/vike/dist/esm/node/api/dev.js:10:44)
at cmdDev (file:///D:/Web-Project/cat/node_modules/.pnpm/[email protected][email protected]_@ty_e3390a99196956df3d2e8ec3315ea7a5/node_modules/vike/dist/esm/node/cli/entry.js:26:32)
at cli (file:///D:/Web-Project/cat/node_modules/.pnpm/[email protected][email protected]_@ty_e3390a99196956df3d2e8ec3315ea7a5/node_modules/vike/dist/esm/node/cli/entry.js:11:9)And the 'startServer' function in my 'vike-server' index. ts' entry will be delayed for tens of seconds to minutes before starting to run. I want to know if this is a potential issue or if I messed up something? If necessary, I will try to make a reproduction. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
This means Vike's config resolution is taking more than 25 seconds, which is very surprising. The order of magnitude is more in the realm of milliseconds rather than seconds.
That's very unusual as well. Are you making something out of the ordinary that would explain both of these things? You can use various DEBUG logs to try to find where the slowness comes from:
That would indeed be the best. But we can also try to find the issue by continuing this disucssion. |
Beta Was this translation helpful? Give feedback.
-
|
Since I haven’t been able to reproduce this issue again after posting this discussion, I’m going to close it. |
Beta Was this translation helpful? Give feedback.
Since I haven’t been able to reproduce this issue again after posting this discussion, I’m going to close it.