Webpack-cli: Possible regression [email protected]

[brunoscopelliti]

Do you want to request a feature or report a bug? BUG

What is the current behavior?

Webpack just does nothing.
It just doesn't execute the config file.

If the current behavior is a bug, please provide the steps to reproduce.

console.log("Ok?")

const path = require("path");

module.exports = {
  entry: "./src/index.js",
  output: {
    path: path.resolve(__dirname, "dist"),
    filename: "index.js"
  }
};

What is the expected behavior?

See the log in console, and assets in the dist folder.

Please paste the results of webpack-cli info here, and mention other relevant information such as programming language.

Nothing is logged in console; neither the "Ok?" log.
I've tested on windows 10.

[evenstensberg]

Maybe related to #413 PR, I've rebased, give it some minutes and a new version will be published. All tests were green, a bit strange. Let's see in some minutes

[brunoscopelliti]

Take the time you need.

[iernie]

I think have the same problem with 2.1.0.

Webpack did nothing and node ended up using all available memory in task manager. The longer you wait, the more memory it uses. Downgraded to 2.0.14 and things works again.

[evenstensberg]

Could you try installing 2.1.1?

[iernie]

2.1.1 still doesn't work for me. Multiple node-instances are spun up every second until process is killed.

I forgot to add I'm running Windows 10 with node 10 and npm 6

[andreujuanc]

Same here.

2.0.15: OK
2.1.0: Stuck
2.1.1: Stuck

Win10, npm 5.3, node 8.3

[evenstensberg]

Alright, let's try 2.1.2

[iernie]

2.1.2 works for me! 👍

[evenstensberg]

Sweet :100: , sorry for the inconvenience!

[andreujuanc]

Works! 🏹 😛