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
TypeError: e is not iterable
at ne.addWorkflows (D:\practical\expressServer\node_modules@novu\framework\dist\express.js:21:12052)
at new ae (D:\practical\expressServer\node_modules@novu\framework\dist\express.js:25:2598)
at kr (D:\practical\expressServer\node_modules@novu\framework\dist\express.js:25:6079)
at file:///D:/practical/expressServer/app.js:11:22
at ModuleJob.run (node:internal/modules/esm/module_job:218:25)
at async ModuleLoader.import (node:internal/modules/esm/loader:329:24)
at async loadESM (node:internal/process/esm_loader:28:7)
at async handleMainPromise (node:internal/modules/run_main:113:12)
Node.js v20.11.1
Novu version
2.0.0-canary.7
npm version
9.7.1
node version
20.11.1
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
📜 Description
Follow QuickStart Steps For Express Server
start the express server and BOOM
👟 Reproduction steps
follow quickStart Express steps
start express and BOOM
👍 Expected behavior
it should start the express on 4000 port easily
👎 Actual Behavior with Screenshots
TypeError: e is not iterable
at ne.addWorkflows (D:\practical\expressServer\node_modules@novu\framework\dist\express.js:21:12052)
at new ae (D:\practical\expressServer\node_modules@novu\framework\dist\express.js:25:2598)
at kr (D:\practical\expressServer\node_modules@novu\framework\dist\express.js:25:6079)
at file:///D:/practical/expressServer/app.js:11:22
at ModuleJob.run (node:internal/modules/esm/module_job:218:25)
at async ModuleLoader.import (node:internal/modules/esm/loader:329:24)
at async loadESM (node:internal/process/esm_loader:28:7)
at async handleMainPromise (node:internal/modules/run_main:113:12)
Node.js v20.11.1
Novu version
2.0.0-canary.7
npm version
9.7.1
node version
20.11.1
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Contributing Guidelines?
Are you willing to submit PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: