Executor nx/webpack:dev-server broken on NX 18

[gabrielbryk]

Current Behavior

The executor is supposed to have options as defined in the schema defined in the documentation. However when I use it, it's not recognizing any of the values provided in options, and instead expects a webpack configuration

Expected Behavior

Works similar to how @nx/webpack:webpack works

GitHub Repo

No response

Steps to Reproduce

Using this target in my project.json

    "dev": {
      "executor": "@nx/webpack:dev-server",
      "defaultConfiguration": "development",
      "options": {
        "buildTarget": "backend:build",
        "hot": true,
        "hmr": true,
        "liveReload": true,
        "webpackConfig": "apps/backend/webpack.config.js"
      },
      "configurations": {
        "development": {
          "buildTarget": "backend:build:development"
        },
        "production": {
          "buildTarget": "backend:build:production",
          "hot": false,
          "hmr": false,
          "liveReload": false
        }
      }
    },

Nx Report

Node   : 20.10.0
OS     : darwin-arm64
pnpm   : 8.15.4

nx (global)        : 18.0.6
nx                 : 18.0.6
@nx/js             : 18.0.6
@nx/jest           : 18.0.6
@nx/linter         : 18.0.6
@nx/eslint         : 18.0.6
@nx/workspace      : 18.0.6
@nx/cypress        : 18.0.6
@nx/eslint-plugin  : 18.0.6
@nx/nest           : 18.0.6
@nx/node           : 18.0.6
@nx/react          : 18.0.6
@nx/vite           : 18.0.6
@nx/web            : 18.0.6
@nx/webpack        : 18.0.6
typescript         : 5.3.3

Failure Logs

nx run backend:dev:backend:build:development


 NX   Invalid configuration object. Webpack has been initialized using a configuration object that does not match the API schema.

 - configuration should be an object:
   object { amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?, entry?, experiments?, extends?, externals?, externalsPresets?, externalsType?, ignoreWarnings?, infrastructureLogging?, loader?, mode?, module?, name?, node?, optimization?, output?, parallelism?, performance?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, snapshot?, stats?, target?, watch?, watchOptions? }
   -> Options object as provided by the user.

ValidationError: Invalid configuration object. Webpack has been initialized using a configuration object that does not match the API schema.
 - configuration should be an object:
   object { amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?, entry?, experiments?, extends?, externals?, externalsPresets?, externalsType?, ignoreWarnings?, infrastructureLogging?, loader?, mode?, module?, name?, node?, optimization?, output?, parallelism?, performance?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, snapshot?, stats?, target?, watch?, watchOptions? }
   -> Options object as provided by the user.

Package Manager Version

No response

Operating System

• macOS
• Linux
• Windows
• Other (Please specify)

Additional Information

No response

[Achder]

Experiencing the same issue.
I found this in the code:

nx/packages/webpack/src/executors/dev-server/dev-server.impl.ts

Line 88 in 64b2396

// Only add the dev server option if user is composable plugin.

// Only add the dev server option if user is composable plugin.
// Otherwise, user should define `devServer` option directly in their webpack config.

Is there maybe a workaround?

[jaysoo]

@Achder @gabrielbryk What is inside the webpack.config.js file?

If someone can link a repro that would help in debugging this issue. We need to add another if-else block to match the @nx/webpack:webpack executor:

nx/packages/webpack/src/executors/webpack/webpack.impl.ts

Lines 77 to 79 in 64b2396

	} else if (userDefinedWebpackConfig) {
	// New behavior, we want the webpack config to export object
	return userDefinedWebpackConfig;

Just want to confirm that this is the issue.

[jaysoo]

This PR brings the same feature from @nx/webpack:webpack to @nx/webpack:dev-server. If someone wants to make that patch in their node_modules/, or provide a repro.

[github-actions]

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.