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 was not able to start the project with the configured packages and their versions.
Current Behavior 馃槸
The project is not running with npm start.
It receives the following error:
$ npm run start
> @adminkit/core@3.1.0 start
> webpack serve --config webpack.config.js --progress
[webpack-cli] Unable to load '@webpack-cli/serve' command
[webpack-cli] TypeError: options.forEach is not a function
at WebpackCLI.makeCommand (/Users/workspace/frontend/adminkit/node_modules/webpack-cli/lib/webpack-cli.js:173:25)
at ServeCommand.apply (/Users/workspace/frontend/adminkit/node_modules/@webpack-cli/serve/lib/index.js:41:19)
at loadCommandByName (/Users/workspace/frontend/adminkit/node_modules/webpack-cli/lib/webpack-cli.js:909:35)
at async Command.<anonymous> (/Users/workspace/frontend/adminkit/node_modules/webpack-cli/lib/webpack-cli.js:1485:17)
at async Promise.all (index 0)
at async WebpackCLI.run (/Users/workspace/frontend/adminkit/node_modules/webpack-cli/lib/webpack-cli.js:1523:9)
at async runCLI (/Users/workspace/frontend/adminkit/node_modules/webpack-cli/lib/bootstrap.js:11:9)
Expected Behavior 馃
The project should correctly start with npm start
Steps to Reproduce 馃暪
Steps:
check out the project
perform npm i
perform npm start
check the command line output
Your Environment 馃寧
OS: MacOS
node: 16.13.0
npm: 8.3.1
Additional Information
I took a quick check on the options variable in webpack-cli. And somehow the options variable is a promise (rejected) and not an array. Upgrading the dependency webpack-cli to 4.9.1 solves it for me.
The text was updated successfully, but these errors were encountered:
I was not able to start the project with the configured packages and their versions.
Current Behavior 馃槸
The project is not running with
npm start
.It receives the following error:
Expected Behavior 馃
The project should correctly start with
npm start
Steps to Reproduce 馃暪
Steps:
npm i
npm start
Your Environment 馃寧
Additional Information
I took a quick check on the options variable in webpack-cli. And somehow the options variable is a promise (rejected) and not an array. Upgrading the dependency
webpack-cli
to4.9.1
solves it for me.The text was updated successfully, but these errors were encountered: