Why need (apparently) nx daemon when execute webpack-cli build through nx:run-commands?

[drackp2m]

Hi, I eventually generate a new monorepo with my two favorite frameworks (nestJS + Angular) and migrate my old project to combine it with a fresh installation and taking advantage of the new/latest technologies available (since running nx migrate latest doesn't always give you the best result).

So, to get right to the point, I noticed that in my nest project running under Webpack, I don't have watch mode enabled by default. When I save a file, the change detection doesn't trigger and the application is recompiled. Also, when I start the application, I get the following message:

"NX Daemon is not running. Node process will not restart automatically after file changes."

So, comparing the configurations with my previous project that was running without any problems, I noticed two details.

project.json from my old setup where watch does work:

{
    ···
    "build": {
        "executor": "@nx/webpack:webpack",
        "outputs": ["{options.outputPath}"],
        "defaultConfiguration": "production",
        "options": {
            "target": "node",
            "compiler": "tsc",
            "outputPath": "dist/apps/api",
            "main": "apps/api/src/main.ts",
            "tsConfig": "apps/api/tsconfig.app.json",
            "assets": ["apps/api/src/assets"],
            "webpackConfig": "apps/api/webpack.config.js"
        },
        "configurations": {
            "development": {},
            "production": {}
        }
    },
    ···
}

webpack.config.js from my old setup where watch does work:

const { composePlugins, withNx } = require('@nx/webpack');
const patchNxSourceMapPaths = require('../../utils/patch-nx-source-map-paths');

// Nx plugins for webpack.
module.exports = composePlugins(withNx(), (config) => {
    // Update the webpack config as needed here.
    // e.g. `config.plugins.push(new MyPlugin())`
    patchNxSourceMapPaths(config); // This method only fixes an issue related to sourcemaps to allow debugging.
    
    return config;
});

And here is the new configuration that is giving me problems:

project.json

{
    ···
    "build": {
        "executor": "nx:run-commands",
        "options": {
            "command": "webpack-cli build",
            "args": ["node-env=production"]
        },
        "configurations": {
            "development": {
                "args": ["node-env=development"]
            }
        }
    },
    ···

webpack.config.js

const { NxAppWebpackPlugin } = require('@nx/webpack/app-plugin');
const { join } = require('path');

module.exports = {
    output: {
        path: join(__dirname, '../../dist/apps/api'),
    },
    plugins: [
        new NxAppWebpackPlugin({
            target: 'node',
            compiler: 'tsc',
            main: './src/main.ts',
            tsConfig: './tsconfig.app.json',
            assets: ['./src/assets'],
            optimization: false,
            outputHashing: 'none',
            generatePackageJson: true,
        }),
    ],
};

Does anyone know if I'm doing something wrong?
Is this behavior I'm getting normal?

In Visual Studio I've tried to have the NX Console plugin installed, but it still doesn't work.
I start the project from a Docker container using .devcontainer.

I use NX v20.2.2, node v22.12.0 and npm 10.9.0.