[BUG]: @webpack-cli/[email protected] does not work #1127

vertuxx · 2019-11-20T08:22:15Z

Describe the bug

An error occurs when you run the webpack-cli init command.

What is the current behavior?

To Reproduce

yarn add --dev webpack webpack-cli @webpack-cli/init
yarn run webpack-cli init

Expected behavior
The webpack-cli init command works correctly.

Screenshots
N/A

Please paste the results of webpack-cli info here, and mention other relevant information

x-macbook-pro:test2 xuser$ yarn run webpack-cli info
yarn run v1.19.1
$ /Users/xuser/works/jsworks/virtual-dom/test2/node_modules/.bin/webpack-cli info
undefined

  System:
    OS: macOS 10.14.6
    CPU: (4) x64 Intel(R) Core(TM) i7-4558U CPU @ 2.80GHz
    Memory: 617.09 MB / 16.00 GB
  Binaries:
    Node: 10.16.3 - /var/folders/4j/7cl0sfxj4dv77hkj40xf9x340000gn/T/yarn--1574233136999-0.305712911277922/node
    Yarn: 1.19.1 - /var/folders/4j/7cl0sfxj4dv77hkj40xf9x340000gn/T/yarn--1574233136999-0.305712911277922/yarn
    npm: 6.9.0 - ~/.nodebrew/current/bin/npm
  Browsers:
    Chrome: 78.0.3904.97
    Firefox: 70.0.1
    Safari: 13.0.1
  npmPackages:
    webpack: ^4.41.2 => 4.41.2 
    webpack-cli: ^3.3.10 => 3.3.10

Additional context

x-macbook-pro:test2 xuser$ yarn run webpack-cli init
yarn run v1.19.1
$ /Users/xuser/works/jsworks/virtual-dom/test2/node_modules/.bin/webpack-cli init
/Users/xuser/works/jsworks/virtual-dom/test2/node_modules/@webpack-cli/utils/npm-packages-exists.js:42
            throw new TypeError(chalk_1.default.bold(`${scaffold} isn't a valid name.\n`) +
            ^

TypeError: init isn't a valid name.

It should be prefixed with 'webpack-scaffold', but have different suffix.

    at pkg.forEach (/Users/xuser/works/jsworks/virtual-dom/test2/node_modules/@webpack-cli/utils/npm-packages-exists.js:42:19)
    at Array.forEach (<anonymous>)
    at Object.npmPackagesExists [as default] (/Users/xuser/works/jsworks/virtual-dom/test2/node_modules/@webpack-cli/utils/npm-packages-exists.js:26:9)
    at initializeInquirer (/Users/xuser/works/jsworks/virtual-dom/test2/node_modules/@webpack-cli/init/index.js:23:41)
    at runWhenInstalled (/Users/xuser/works/jsworks/virtual-dom/test2/node_modules/webpack-cli/bin/utils/prompt-command.js:46:9)
    at promptForInstallation (/Users/xuser/works/jsworks/virtual-dom/test2/node_modules/webpack-cli/bin/utils/prompt-command.js:140:10)
    at /Users/xuser/works/jsworks/virtual-dom/test2/node_modules/webpack-cli/bin/cli.js:32:43
    at Object.<anonymous> (/Users/xuser/works/jsworks/virtual-dom/test2/node_modules/webpack-cli/bin/cli.js:366:3)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

package.json

x-macbook-pro:test2 xuser$ cat package.json 
{
  "name": "test2",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "devDependencies": {
    "@webpack-cli/info": "^0.2.0",
    "@webpack-cli/init": "^0.3.0",
    "webpack": "^4.41.2",
    "webpack-cli": "^3.3.10"
  }
}

@webpack-cli/[email protected] is works fine.

{
  "name": "test1",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "devDependencies": {
    "@webpack-cli/info": "^0.2.0",
    "@webpack-cli/init": "0.2.2",
    "webpack": "^4.41.2",
    "webpack-cli": "^3.3.10"
  }
}

Thank you.

The text was updated successfully, but these errors were encountered:

evenstensberg · 2019-11-22T04:59:58Z

Could you try the same with webpack-cli@beta?

szundel · 2019-11-24T21:03:25Z

I had a similar issue on Node 10.17.0. It worked for me after I downgraded to 10.15.3

vertuxx · 2019-11-25T02:14:55Z

Could you try the same with webpack-cli@beta?

The following command was executed.

yarn add --dev webpack webpack-cli@beta @webpack-cli/init @webpack-cli/info

However, another error occurs and it does not work.

xuser@x-macbook-pro ➜  test3 yarn run webpack-cli init
yarn run v1.19.1
$ /Users/xuser/works/jsworks/virtual-dom/test3/node_modules/.bin/webpack-cli init
(node:77940) [DEP_WEBPACK_MAIN_TEMPLATE_HASH_FOR_CHUNK] DeprecationWarning: MainTemplate.hooks.hashForChunk is deprecated (use JavascriptModulesPlugin.getCompilationHooks().chunkHash instead)
(node:77940) [DEP_WEBPACK_CHUNK_TEMPLATE_HASH_FOR_CHUNK] DeprecationWarning: ChunkTemplate.hooks.hashForChunk is deprecated (use JavascriptModulesPlugin.getCompilationHooks().chunkHash instead)

✅ Compilation Results       

🌏 Version: 5.0.0-beta.7
⚒️  Built: Mon Nov 25 2019 11:00:03 GMT+0900 (GMT+09:00)
⏱  Compile Time: 417ms
📂 Output Directory: /Users/xuser/works/jsworks/virtual-dom/test3/dist

┌───────────────┬─────────────────────────────────────────────┬───────────────┐
│ Build Status  │ Bundle Name                                 │ Bundle Size   │
├───────────────┼─────────────────────────────────────────────┼───────────────┤
│ failed        │ main.js                                     │ 0 kb          │
└───────────────┴─────────────────────────────────────────────┴───────────────┘

⬢ webpack: configuration
The 'mode' option has not been set, webpack will fallback to 'production' for this value. Set 'mode' option to 'development' or 'production' to enable defaults for each environment.
You can also set it to 'none' to disable any default behavior. Learn more: https://webpack.js.org/configuration/mode/

⬢ webpack: NoModeWarning: configuration
The 'mode' option has not been set, webpack will fallback to 'production' for this value. Set 'mode' option to 'development' or 'production' to enable defaults for each environment.
You can also set it to 'none' to disable any default behavior. Learn more: https://webpack.js.org/configuration/mode/
    at compiler.hooks.thisCompilation.tap.compilation (/Users/xuser/works/jsworks/virtual-dom/test3/node_modules/webpack-cli/node_modules/webpack/lib/WarnNoModeSetPlugin.js:20:30)
    at Hook.eval [as call] (eval at create (/Users/xuser/works/jsworks/virtual-dom/test3/node_modules/webpack-cli/node_modules/xpable/lib/HookCodeFactory.js:19:10), <anonymous>:13:1)
    at Hook.CALL_DELEGATE [as _call] (/Users/xuser/works/jsworks/virtual-dom/test3/node_modules/webpack-cli/node_modules/xpable/lib/Hook.js:14:14)
    at Compiler.newCompilation (/Users/xuser/works/jsworks/virtual-dom/test3/node_modules/webpack-cli/node_modules/webpack/lib/Compiler.js:857:30)
    at hooks.beforeCompile.callAsync.err (/Users/xuser/works/jsworks/virtual-dom/test3/node_modules/webpack-cli/node_modules/webpack/lib/Compiler.js:898:29)
    at Hook.eval [as callAsync] (eval at create (/Users/xuser/works/jsworks/virtual-dom/test3/node_modules/webpack-cli/node_modules/xpable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/Users/xuser/works/jsworks/virtual-dom/test3/node_modules/webpack-cli/node_modules/xpable/lib/Hook.js:18:14)
    at Compiler.compile (/Users/xuser/works/jsworks/virtual-dom/test3/node_modules/webpack-cli/node_modules/webpack/lib/Compiler.js:893:28)
    at readRecords.err (/Users/xuser/works/jsworks/virtual-dom/test3/node_modules/webpack-cli/node_modules/webpack/lib/Compiler.js:424:12)
    at Compiler.readRecords (/Users/xuser/works/jsworks/virtual-dom/test3/node_modules/webpack-cli/node_modules/webpack/lib/Compiler.js:736:11)
    at hooks.run.callAsync.err (/Users/xuser/works/jsworks/virtual-dom/test3/node_modules/webpack-cli/node_modules/webpack/lib/Compiler.js:421:11)
    at Hook.eval [as callAsync] (eval at create (/Users/xuser/works/jsworks/virtual-dom/test3/node_modules/webpack-cli/node_modules/xpable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/Users/xuser/works/jsworks/virtual-dom/test3/node_modules/webpack-cli/node_modules/xpable/lib/Hook.js:18:14)
    at hooks.beforeRun.callAsync.err (/Users/xuser/works/jsworks/virtual-dom/test3/node_modules/webpack-cli/node_modules/webpack/lib/Compiler.js:418:20)
    at Hook.eval [as callAsync] (eval at create (/Users/xuser/works/jsworks/virtual-dom/test3/node_modules/webpack-cli/node_modules/xpable/lib/HookCodeFactory.js:33:10), <anonymous>:24:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/Users/xuser/works/jsworks/virtual-dom/test3/node_modules/webpack-cli/node_modules/xpable/lib/Hook.js:18:14)


⬢ webpack: Module not found: Error: Can't resolve './src' in '/Users/xuser/works/jsworks/virtual-dom/test3'

✨  Done in 2.30s.

I am also using [email protected].

xuser@x-macbook-pro ➜  test3 cat package.json 
{
  "name": "test3",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "devDependencies": {
    "@webpack-cli/info": "^0.2.0",
    "@webpack-cli/init": "^0.3.0",
    "webpack": "^4.41.2",
    "webpack-cli": "^4.0.0-beta.1"
  }
}
xuser@x-macbook-pro ➜  test3 node -v
v10.17.0

Thank you.

vertuxx · 2019-11-25T03:06:01Z

I also tried [email protected] but it seems to be no good as well. @webpack-cli/[email protected]

I use @webpack-cli/[email protected] which is fine for now.

yarn add --dev webpack webpack-cli @webpack-cli/[email protected]

node -v                                                   
v12.13.1

Thank you.

evenstensberg · 2019-11-25T11:33:12Z

Thx for the feedback!

rishabh3112 · 2019-12-03T13:34:56Z

Hi @vertuxx thanks for reporting error.

v0.3.0 was launched from next branch without beta tag.
For webpack-cli v4, we have renamed init to create
v0.3.0 should work with following commands with webpack-cli@beta:

webpack-cli create
webpack-cli create webpack-scaffold-pwa #example with custom scaffold

cc @evenstensberg

rishabh3112 · 2019-12-03T13:36:13Z

Add npx against commands if CLI is installed locally

dictateurfou · 2019-12-04T17:28:47Z

@rishabh3112 if im use webpack-cli@beta create work but im have the following error when use npm run build

 webpack


⬢ webpack: ValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration.optimization.splitChunks should be one of these:
   false | object { automaticNameDelimiter?, cacheGroups?, chunks?, fallbackCacheGroup?, filename?, hidePathInfo?, maxAsyncRequests?, maxAsyncSize?, maxInitialRequests?, maxInitialSize?, maxSize?, minChunks?, minRemainingSize?, minSize?, name? }
   -> Optimize duplication and caching by splitting chunks by shared modules and cache group
   Details:
    * configuration.optimization.splitChunks.name should be one of these:
      false | function | string
      -> Give chunks created a name (chunks with equal name are merged)
      Details:
       * configuration.optimization.splitChunks.name should be false.
       * configuration.optimization.splitChunks.name should be an instance of function.
       * configuration.optimization.splitChunks.name should be a string.

rishabh3112 · 2019-12-05T03:20:01Z

@dictateurfou
This error seems to be due to error in the configuration. Refer following steps:

If you are using webpack v5, refer Migration Guide to update the scaffolded configuration.
If you are using webpack v4, use webpack-cli v3, @webpack-cli/init v0.2.2.

DanielRuf · 2019-12-08T20:25:08Z

Same here. None of these ways work:

npx webpack-cli init
init isn't a valid name.

It should be prefixed with 'webpack-scaffold', but have different suffix.

➜  patch-cutter-browser git:(master) ✗ rm -rf node_modules 
➜  patch-cutter-browser git:(master) ✗ npx webpack-cli init
npx: Installierte 204 in 9.322s
The command moved into a separate package: @webpack-cli/init
Would you like to install init? (That will run yarn global add @webpack-cli/init) (yes/NO) : yes
yarn global v1.19.1
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning "@webpack-cli/init > @webpack-cli/[email protected]" has unmet peer dependency "[email protected]".
warning "@webpack-cli/init > @webpack-cli/generators > [email protected]" has unmet peer dependency "inquirer@^5.0.0 || ^6.0.0".
[4/4] 🔨  Building fresh packages...
warning "@webpack-cli/[email protected]" has no binaries
✨  Done in 5.14s.
{ Error: Cannot find module '/Users/danielruf/.nodenv/versions/10.16.3/lib/node_modules/@webpack-cli/init'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (/Users/danielruf/.npm/_npx/3622/lib/node_modules/webpack-cli/node_modules/v8-compile-cache/v8-compile-cache.js:161:20)
    at npmGlobalRoot.then.then.pathForInit (/Users/danielruf/.npm/_npx/3622/lib/node_modules/webpack-cli/bin/utils/prompt-command.js:114:18)
    at process._tickCallback (internal/process/next_tick.js:68:7) code: 'MODULE_NOT_FOUND' }

DanielRuf · 2019-12-08T20:26:01Z

* For `webpack-cli` v4, we have renamed `init` to `create`

Well, this is a breaking change and not reflected in the docs.

aesyondu · 2020-01-07T02:33:13Z

@dictateurfou
This error seems to be due to error in the configuration. Refer following steps:

1. If you are using `webpack v5`, refer [Migration Guide](https://github.com/webpack/changelog-v5/blob/master/MIGRATION%20GUIDE.md) to update the scaffolded configuration.

2. If you are using `webpack v4`, use `webpack-cli v3`, `@webpack-cli/init v0.2.2`.

Thanks, i used npm install -D @webpack-cli/[email protected] and npx webpack-cli init worked.

sevillaarvin · 2020-01-12T03:42:06Z

Tested npx webpack-cli init --auto based on the docs https://github.com/webpack/webpack-cli/blob/next/packages/init/README.md#webpack-cli-init and it works for v0.3.0.

jwbth · 2020-01-13T14:14:53Z

I'm sorry, but how come that on a clean project npx webpack-cli init (that is in the docs everywhere, from https://webpack.js.org/configuration/ to https://github.com/webpack/webpack-cli/) doesn't run well?

npx: installed 204 in 23.624s
init isn't a valid name.

It should be prefixed with 'webpack-scaffold', but have different suffix.

I had to run npm i -D @webpack-cli/[email protected] before npx webpack-cli init as adviced here.

Could something be wrong with my setup (but as I said, I have a clean project, and nothing in my environment seems unusual) since I don't see a lot of feedback here, and if not, is anybody going to do anything about it? Running into errors on a default setup doesn't seem good.

RVyrvin · 2020-01-18T10:25:00Z

Hi all, pls help.
I have npm v6.13.4, node v12.14.1.
When i create new project, i use this steps (i use VSCode and is one empty folder.):

npm init -y (to create file pakage.json)
npm install webpack webpack-cli --save-dev
(after instalation i have: webpack: ^4.41.5, webpack-cli: ^3.3.10 )
3 After, i try to create project struct whith .node_modules\.bin\webpack-cli init --auto, and i have crated project struct, but without file "webpack.config.js"

Why? What i do wrong? I dont whant to downgrade to "@webpack-cli/[email protected]"!

DanielRuf · 2020-01-18T11:37:21Z

Hi @RVyrvin,

Please open a new issue.

Also see the previous replies.

@webpack-cli/[email protected]

Try npm i @webpack-cli/[email protected] --save-dev.

DanielRuf · 2020-01-18T11:39:09Z

webpack.config.js

So you mean the file is not generated? webpack 4 does not require a config by default. Try it without the --auto option.

RVyrvin · 2020-01-18T13:51:02Z

Hi, ty for answer. without --auto dont work. And yes, now i need self create webpack.config.js. El Sáb 18/01/2020, 12:39, Daniel Ruf <[email protected]> escribió:

…

webpack.config.js So you mean the file is not generated? webpack 4 does not require a config by default. Try it without the --auto option. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1127?email_source=notifications&email_token=AKFTPSCBSZ63LW4RK6XJ7J3Q6LS57A5CNFSM4JPPAHI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJJWNGA#issuecomment-575891096>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKFTPSAONV3QQDNZIOEYUGTQ6LS57ANCNFSM4JPPAHIQ> .

DanielRuf · 2020-01-18T16:09:38Z

Please check the readme and the previous replies, --init should work.

sevillaarvin · 2020-01-19T06:58:01Z

Is it supposed to generate a webpack.config.js file?

Here are the files generated using ./node_modules/.bin/webpack-cli init --auto:

node --version
v13.6.0
npm --version
6.13.6

git status

On branch master

No commits yet

Untracked files:
(use "git add ..." to include in what will be committed)

.yo-rc.json
README.md
index.html
node_modules/
package-lock.json
package.json
src/

nothing added to commit but untracked files present (use "git add" to track)

package.json

{
  "name": "tryinit",
  "version": "1.0.0",
  "description": "My webpack project",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "build": "webpack",
    "start": "webpack-dev-server"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "@webpack-cli/init": "^0.3.0",
    "babel-plugin-syntax-dynamic-import": "^6.18.0",
    "html-webpack-plugin": "^3.2.0",
    "terser-webpack-plugin": "^2.3.2",
    "webpack": "^4.41.5",
    "webpack-cli": "^3.3.10",
    "webpack-dev-server": "^3.10.1",
    "workbox-webpack-plugin": "^4.3.1"
  }
}

node_modules/.bin/webpack-cli init --init # produces error

/home/aes/Sandbox/webpack/tryinit/node_modules/@webpack-cli/utils/npm-packages-exists.js:42 throw new TypeError(chalk_1.default.bold(`${scaffold} isn't a valid name.\n`) + ^

TypeError: init isn't a valid name.

It should be prefixed with 'webpack-scaffold', but have different suffix.

at /home/aes/Sandbox/webpack/tryinit/node_modules/@webpack-cli/utils/npm-packages-exists.js:42:19
at Array.forEach (<anonymous>)
at Object.npmPackagesExists [as default] (/home/aes/Sandbox/webpack/tryinit/node_modules/@webpack-cli/utils/npm-packages-exists.js:26:9)
at initializeInquirer (/home/aes/Sandbox/webpack/tryinit/node_modules/@webpack-cli/init/index.js:23:41)
at runWhenInstalled (/home/aes/Sandbox/webpack/tryinit/node_modules/webpack-cli/bin/utils/prompt-command.js:46:9)
at promptForInstallation (/home/aes/Sandbox/webpack/tryinit/node_modules/webpack-cli/bin/utils/prompt-command.js:140:10)
at /home/aes/Sandbox/webpack/tryinit/node_modules/webpack-cli/bin/cli.js:32:43
at Object.<anonymous> (/home/aes/Sandbox/webpack/tryinit/node_modules/webpack-cli/bin/cli.js:366:3)
at Module._compile (internal/modules/cjs/loader.js:1144:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1164:10)

P.S. How to make use of the .yo-rc.json?

DanielRuf · 2020-01-19T09:00:23Z

TypeError: init isn't a valid name.

It should be prefixed with 'webpack-scaffold', but have different suffix.

Please see the previous comments and the readme in the repository. By default webpack does not need a config anymore (0 config) unless you want to change the defaults.

RVyrvin · 2020-01-22T17:24:26Z

Hi. So "node_modulos/.bin/webpack-cli init --auto" create struct of project, and don't create "webpack.config.js". I understand with this file when i run "npm run build/start", dont run application on the browser? Now, i need to create "webpack.config.js" by self or i can create him automaticaly? Sorry my english and ty for help me. El dom., 19 ene. 2020 a las 10:00, Daniel Ruf (<[email protected]>) escribió:

…

TypeError: init isn't a valid name. It should be prefixed with 'webpack-scaffold', but have different suffix. Please see the previous comments and the readme in the repository. By default webpack does not need a config anymore (0 config) unless you want to change the defaults. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1127?email_source=notifications&email_token=AKFTPSHEL3Q5QT7WFGPQPZLQ6QJCRA5CNFSM4JPPAHI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJKMUAA#issuecomment-575982080>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKFTPSH2MXXR2NLVWW2Q273Q6QJCRANCNFSM4JPPAHIQ> .

ematipico · 2020-01-23T16:10:18Z

@RVyrvin you don't need to create a configuration file, webpack has its own defaults now.
If you need to add particular configuration, plugin, etc. you'd need to create yourself or use a scaffold

aman29271 · 2020-04-10T17:50:02Z

For webpack-cli v4, we have renamed init to create

@ematipico Should I make a PR for this to be reflected in docs?

snitin315 · 2020-04-10T22:05:37Z

No we are back to init again.

DanielRuf · 2020-04-10T23:29:52Z

Uh, what? So you changed back? Is there additional information @snitin315?

#1127 (comment)

Also why the "thumbs down" reaction? A simple "no we need no PR because ..." is sufficient.

snitin315 · 2020-04-11T01:26:39Z

Uh, what? So you changed back? Is there additional information @snitin315?

There is no such additional info.

Also why the "thumbs down" reaction? A simple "no we need no PR because ..." is sufficient.

Just in support of my comment.

aman29271 · 2020-04-11T04:10:29Z

No we are back to init again.

@snitin315 But I am still getting the same error.

Init isn't a valid name.

snitin315 · 2020-04-11T04:12:58Z

Against Beta?

works fine for me.

aman29271 · 2020-04-11T05:43:47Z

I am still getting the following error.

 throw new TypeError(chalk_1.default.bold(`${scaffold} isn't a valid name.\n`) +
            ^

TypeError: init isn't a valid name.

It should be prefixed with 'webpack-scaffold', but have different suffix.

    at pkg.forEach (/home/phoenix/Desktop/temp2/node_modules/@webpack-cli/utils/npm-packages-exists.js:42:19)
    at Array.forEach (<anonymous>)
    at Object.npmPackagesExists [as default] (/home/phoenix/Desktop/temp2/node_modules/@webpack-cli/utils/npm-packages-exists.js:26:9)
    at initializeInquirer (/home/phoenix/Desktop/temp2/node_modules/@webpack-cli/init/index.js:23:41)
    at runWhenInstalled (/home/phoenix/Desktop/temp2/node_modules/webpack-cli/bin/utils/prompt-command.js:46:9)
    at promptForInstallation (/home/phoenix/Desktop/temp2/node_modules/webpack-cli/bin/utils/prompt-command.js:140:10)
    at /home/phoenix/Desktop/temp2/node_modules/webpack-cli/bin/cli.js:32:43
    at Object.<anonymous> (/home/phoenix/Desktop/temp2/node_modules/webpack-cli/bin/cli.js:366:3)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)

and output of npx webpack-cli info is

System:
    OS: Linux 4.19 Debian GNU/Linux 10 (buster) 10 (buster)
    CPU: (4) x64 Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
    Memory: 2.95 GB / 7.66 GB
  Binaries:
    Node: 10.15.2 - /usr/bin/node
    Yarn: 1.22.4 - /usr/bin/yarn
    npm: 5.8.0 - /usr/bin/npm
  Browsers:
    Chrome: 80.0.3987.149
    Firefox: 68.6.0esr
  npmPackages:
    webpack-cli: ^3.3.11 => 3.3.11

snitin315 · 2020-04-11T05:53:12Z

You are using version 3, please try with beta once.

aman29271 · 2020-04-11T06:25:06Z

Yes, it worked. But i have a question that because [email protected] version is being shipped through yarn or npm and also init is not working as expected with it. Can't we provide some documentation or a little help tips somewhere so that people facing this issue for first time don't get scared @snitin315 ?

snitin315 · 2020-04-11T06:31:35Z

I'm not sure refer this comment.

Also what changes in docs do you suggest?

DanielRuf · 2020-04-11T07:33:29Z

There is no such additional info.

There is definitely a commit for this (reverted) change and a PR ;-)

belauzas · 2020-06-11T21:09:23Z

Finally, it works with webpack-cli init if

"devDependencies": {
    "webpack": "^4.43.0",
    "webpack-cli": "^4.0.0-beta.8"
  }

because, default install does not work 🙁

jfo8000 · 2020-07-15T22:48:05Z

Hey if we need to npm i -D @webpack-cli/[email protected] before npx webpack-cli init now, can someone update the outdated instructions here? Can confirm this was required on a clean project.
https://webpack.js.org/configuration/

alexander-akait · 2020-08-01T14:03:10Z

/cc @webpack/cli-team Just clarify, have we test on this stuff?

snitin315 · 2020-09-24T09:00:47Z

Yes,
here https://github.com/webpack/webpack-cli/tree/next/test/init and https://github.com/webpack/webpack-cli/blob/next/packages/webpack-cli/__tests__/init.test.js

alexander-akait · 2020-09-24T10:40:54Z

Let's close, I think the problem fixed, feel free to open a new issue if you faced with issue again

evenstensberg changed the title ~~@webpack-cli/[email protected] does not work~~ [BUG]: @webpack-cli/[email protected] does not work Nov 22, 2019

rishabh3112 mentioned this issue Jan 1, 2020

[BUG]: webpack does not find globally installed @webpack-cli/init by Yarn #986

Closed

This was referenced Aug 1, 2020

NPX WEBPACK-CLI INIT #1129

Closed

webpack-cli init <your-scaffold> is error #1626

Closed

alexander-akait closed this as completed Sep 24, 2020

[BUG]: @webpack-cli/[email protected] does not work #1127

[BUG]: @webpack-cli/[email protected] does not work #1127

Comments

vertuxx commented Nov 20, 2019

evenstensberg commented Nov 22, 2019

szundel commented Nov 24, 2019

vertuxx commented Nov 25, 2019

vertuxx commented Nov 25, 2019

evenstensberg commented Nov 25, 2019

rishabh3112 commented Dec 3, 2019 • edited Loading

rishabh3112 commented Dec 3, 2019

dictateurfou commented Dec 4, 2019 • edited Loading

rishabh3112 commented Dec 5, 2019

DanielRuf commented Dec 8, 2019

DanielRuf commented Dec 8, 2019

aesyondu commented Jan 7, 2020

sevillaarvin commented Jan 12, 2020

jwbth commented Jan 13, 2020

RVyrvin commented Jan 18, 2020

DanielRuf commented Jan 18, 2020

DanielRuf commented Jan 18, 2020

RVyrvin commented Jan 18, 2020 via email

DanielRuf commented Jan 18, 2020

sevillaarvin commented Jan 19, 2020 • edited Loading

DanielRuf commented Jan 19, 2020

RVyrvin commented Jan 22, 2020 via email

ematipico commented Jan 23, 2020 • edited Loading

aman29271 commented Apr 10, 2020

snitin315 commented Apr 10, 2020

DanielRuf commented Apr 10, 2020

snitin315 commented Apr 11, 2020

aman29271 commented Apr 11, 2020

snitin315 commented Apr 11, 2020 • edited Loading

aman29271 commented Apr 11, 2020

snitin315 commented Apr 11, 2020 • edited Loading

aman29271 commented Apr 11, 2020

snitin315 commented Apr 11, 2020

DanielRuf commented Apr 11, 2020

belauzas commented Jun 11, 2020 • edited Loading

jfo8000 commented Jul 15, 2020 • edited Loading

alexander-akait commented Aug 1, 2020

snitin315 commented Sep 24, 2020

alexander-akait commented Sep 24, 2020

rishabh3112 commented Dec 3, 2019 •

edited

Loading

dictateurfou commented Dec 4, 2019 •

edited

Loading

sevillaarvin commented Jan 19, 2020 •

edited

Loading

ematipico commented Jan 23, 2020 •

edited

Loading

snitin315 commented Apr 11, 2020 •

edited

Loading

snitin315 commented Apr 11, 2020 •

edited

Loading

belauzas commented Jun 11, 2020 •

edited

Loading

jfo8000 commented Jul 15, 2020 •

edited

Loading