WebpackDevMiddlewareOptions.ProjectPath no longer sets Node project path #1389

New Issue

fergalmoran · 2025-08-09T17:19:57Z

fergalmoran commented

2025-08-09 17:19:57 +00:00

Originally created by @mattwcole on 9/13/2016

The recent change to WebpackDevMiddleware here has removed the ability to set the Node project path for webpack dev middleware, breaking #262. While the project path is used to build the path to the webpack.config, node_modules is now expected in the content root.

*Originally created by @mattwcole on 9/13/2016* The recent change to `WebpackDevMiddleware` [here](https://github.com/aspnet/JavaScriptServices/commit/f04fb8c42115d3816f9b8005dacefe7e6e485325#diff-cf4fed006c4f5ac483999ecf02221e0dL48) has removed the ability to set the Node project path for webpack dev middleware, breaking #262. While the project path is used to build the path to the webpack.config, node_modules is now expected in the content root.

fergalmoran closed this issue

2025-08-09 17:19:57 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#1389