webpack-dev-server doesn't work with installed webpack and webpack-cli in the parent folder about webpack-cli HOT 7 CLOSED

Ah, I see the whole picture now ... because I'm running webpack which is in the parent, it doesn't know about the webpack-dev-server. Sorry it is quite obvious.

Well, I would to point that on my local NODE_PATH is empty by default and to have webpack-dev-server in child and the rest in parent I need to locate both node_modules folders.

NODE_PATH="$NODE_PATH:/Users/*****/my/development/parent-app/child-app/node_modules:/Users/*****/my/development/parent-app/node_modules" npm run serve:dev

for reference.

from webpack-cli.

It is a limitation you should have webpack-cli on the same level on webpack-dev-server

from webpack-cli.

I understand that there may be some limits. So if it is meant to work like this it is ok, but I would expect some level of consistency at least in case where webpack is installed automatically when running npm i webpack-dev-server, but webpack-cli doesn't .

from webpack-cli.

Aha, I see your point now @alexander-akait so wouldn't be better to install all dependencies (+ webpack-cli in my case) automatically or maybe even better, just throw an error with meaningful message and do not install anything, because this is more educative for developers I think. Also I'm thinking about webpack-dev-server as additional thing/plugin, so it doesn't make sense to install anythig if I'm going to use plugin. It is like because I want to install some Wordpress plugin, the Wordpress will install automatically as a plugin dependecy, this seems to me oposite direction of thinking.

from webpack-cli.

@dominikj111 It is not related to webpack-dev-server, there is a logic and answer why it doesn't work https://github.com/webpack/webpack-cli/blob/master/packages/webpack-cli/src/webpack-cli.ts#L140, no magic, we can't do what you want and no one package can do it - you can't require/import package on the parent level and awating loading it from child, sorry

Webpack-dev-server is not full featured CLI, it is just a runner for webpack-cli

from webpack-cli.

@alexander-akait I just don't understand why.
And you wrote the apposite direction I'm talking about in this issue. I want to install package in the parent and then I want to require/import in the child.
And that really works, I just install express in the parent and then I did require in the child and in the child I ran node index.js and it works.

If I'm wrong, just explain why and we close this issue without resolving it. But from my perspective it is a buggy behavior even there is not problem with running it, but the architecture self I suppose.

from webpack-cli.

Shortly :

• you run webpack serve
• when you use webpack serve, webpack try to run webpack-cli, because webpack itself doesn't have CLI https://github.com/webpack/webpack/blob/main/bin/webpack.js#L106
• webpack-cli in the parent directory
• webpack-cli is running with the serve command and webpack-cli try to find webpack-dev-server
• webpack-cli can't find webpack-dev-server because - looking at the current node_modules directory and up to the top until it will be found https://github.com/webpack/webpack-cli/blob/master/packages/webpack-cli/src/webpack-cli.ts#L140, like require and import works
• because webpack-dev-server in the child directory we can't find it

Another solution without installing the webpack-cli is to set the NODE_PATH, so command
NODE_PATH="$NODE_PATH:/usr/src/app/child-app/node_modules" ./node_modules/.bin/webpack serve --mode development
will serve as expected also.

It is not a workaround, it is a valid solution

from webpack-cli.