Description
The outputPath option for the server configuration, which was added in the 0.37.0 release, does not work correctly with the build command. It only works with the dev command.
Expected Behavior
The outputPath option should be respected and applied during the build process, allowing users to specify a custom output directory for the server build.
Actual Behavior
The outputPath option is ignored during the build command execution. The server output is placed in the default location instead of the specified custom path.
Code Reference
The issue appears to be in the build configuration:
https://github.com/gravity-ui/app-builder/blob/main/src/commands/build/build-service/server.ts#L17
Pull Request with outputPath option:
#293
Impact
Users cannot customize the server output directory when building for production, which limits deployment flexibility and breaks expected functionality introduced in v0.37.0.
FYI: @daniil-filippov-dev
Description
The
outputPathoption for the server configuration, which was added in the 0.37.0 release, does not work correctly with thebuildcommand. It only works with thedevcommand.Expected Behavior
The
outputPathoption should be respected and applied during the build process, allowing users to specify a custom output directory for the server build.Actual Behavior
The
outputPathoption is ignored during the build command execution. The server output is placed in the default location instead of the specified custom path.Code Reference
The issue appears to be in the build configuration:
https://github.com/gravity-ui/app-builder/blob/main/src/commands/build/build-service/server.ts#L17
Pull Request with
outputPathoption:#293
Impact
Users cannot customize the server output directory when building for production, which limits deployment flexibility and breaks expected functionality introduced in v0.37.0.
FYI: @daniil-filippov-dev