Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Npm start not working #118

Closed
cabb opened this issue Jan 22, 2022 · 2 comments
Closed

Npm start not working #118

cabb opened this issue Jan 22, 2022 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@cabb
Copy link

cabb commented Jan 22, 2022

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:

  1. check out the project
  2. perform npm i
  3. perform npm start
  4. 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.

@cabb cabb added the bug Something isn't working label Jan 22, 2022
@paullaros paullaros self-assigned this Jan 23, 2022
@paullaros
Copy link
Contributor

Resolved in #121

@cabb
Copy link
Author

cabb commented Feb 7, 2022

Works as expected

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants