Config option for `application` builder to set the exact path to output files, without hardcoded `browser` path #26632

e-oz · 2023-12-11T13:14:38Z

Command

build, new

Description

Please create an option to set the exact output path for "browser" and "server" files for application builder, to override the default browser path and avoid issues, described in #26304.

Would also be great to have some option in ng new to set this path during application/workspace initialization.

Describe the solution you'd like

As an idea: add clientFilesFolder field and give it the default value 'browser', so users could re-define it to '' to get the desired behavior. Maybe serverFilesFolder as well (or some better name).

Describe alternatives you've considered

As we found in #26627, the only existing alternative is a temporary solution that will be removed.

The text was updated successfully, but these errors were encountered:

jonatanpetersson · 2023-12-12T12:40:36Z

@e-oz Exactly what I need.

…cations This update introduces the ability for users to define the locations for storing `media`, `browser`, and `server` files. You can achieve this by utilizing the extended `outputPath` option. ```json { "projects": { "my-app": { "architect": { "build": { "builder": "@angular-devkit/build-angular:application", "options": { "outputPath": { "base": "dist/my-app", "browser": "", "server": "node-server", "media": "resources" } } } } } } } ``` While not recommended, choosing to set the `browser` option empty will result in files being output directly under the specified `base` path. It's important to note that this action will generate certain files like `stats.json` and `prerendered-routes.json` that aren't intended for deployment in this directory. Validation rules: - `browser` and `server` are relative to the configuration set in the `base` option. - When SSR is enabled, `browser` cannot be left empty. - `media` is relative to the value specified in the `browser` option. - Both `media` and `server` cannot be set to an empty strings. - `browser`, `media`, or `server` can contain slashes. Closes: angular#26632 and closes: angular#26057

…cations This update introduces the ability for users to define the locations for storing `media`, `browser`, and `server` files. You can achieve this by utilizing the extended `outputPath` option. ```json { "projects": { "my-app": { "architect": { "build": { "builder": "@angular-devkit/build-angular:application", "options": { "outputPath": { "base": "dist/my-app", "browser": "", "server": "node-server", "media": "resources" } } } } } } } ``` While not recommended, choosing to set the `browser` option empty will result in files being output directly under the specified `base` path. It's important to note that this action will generate certain files like `stats.json` and `prerendered-routes.json` that aren't intended for deployment in this directory. Validation rules: - `browser` and `server` are relative to the configuration set in the `base` option. - When SSR is enabled, `browser` cannot be left empty. - `media` is relative to the value specified in the `browser` option. - Both `media` and `server` cannot be set to an empty strings. - `browser`, `media`, or `server` cannot contain slashes. Closes: angular#26632 and closes: angular#26057

…cations This update introduces the ability for users to define the locations for storing `media`, `browser`, and `server` files. You can achieve this by utilizing the extended `outputPath` option. ```json { "projects": { "my-app": { "architect": { "build": { "builder": "@angular-devkit/build-angular:application", "options": { "outputPath": { "base": "dist/my-app", "browser": "", "server": "node-server", "media": "resources" } } } } } } } ``` While not recommended, choosing to set the `browser` option empty will result in files being output directly under the specified `base` path. It's important to note that this action will generate certain files like `stats.json` and `prerendered-routes.json` that aren't intended for deployment in this directory. Validation rules: - `browser` and `server` are relative to the configuration set in the `base` option. - When SSR is enabled, `browser` cannot be left empty. - `media` is relative to the value specified in the `browser` option. - `media` cannot be set to an empty string. - `browser`, `media`, or `server` cannot contain slashes. Closes: angular#26632 and closes: angular#26057

…cations This update introduces the ability for users to define the locations for storing `media`, `browser`, and `server` files. You can achieve this by utilizing the extended `outputPath` option. ```json { "projects": { "my-app": { "architect": { "build": { "builder": "@angular-devkit/build-angular:application", "options": { "outputPath": { "base": "dist/my-app", "browser": "", "server": "node-server", "media": "resources" } } } } } } } ``` While not recommended, choosing to set the `browser` option empty will result in files being output directly under the specified `base` path. It's important to note that this action will generate certain files like `stats.json` and `prerendered-routes.json` that aren't intended for deployment in this directory. Validation rules: - `browser` and `server` are relative to the configuration set in the `base` option. - When SSR is enabled, `browser` cannot be set to an empty string. - `media` is relative to the value specified in the `browser` option. - `media` cannot be set to an empty string. - `browser`, `media`, or `server` cannot contain slashes. Closes: angular#26632 and closes: angular#26057

…cations This update introduces the ability for users to define the locations for storing `media`, `browser`, and `server` files. You can achieve this by utilizing the extended `outputPath` option. ```json { "projects": { "my-app": { "architect": { "build": { "builder": "@angular-devkit/build-angular:application", "options": { "outputPath": { "base": "dist/my-app", "browser": "", "server": "node-server", "media": "resources" } } } } } } } ``` While not recommended, choosing to set the `browser` option empty will result in files being output directly under the specified `base` path. It's important to note that this action will generate certain files like `stats.json` and `prerendered-routes.json` that aren't intended for deployment in this directory. Validation rules: - `browser` and `server` are relative to the configuration set in the `base` option. - When SSR is enabled, `browser` cannot be set to an empty string, and cannot be the same as `server`. - `media` is relative to the value specified in the `browser` option. - `media` cannot be set to an empty string. - `browser`, `media`, or `server` cannot contain slashes. Closes: angular#26632 and closes: angular#26057

…cations This update introduces the ability for users to define the locations for storing `media`, `browser`, and `server` files. You can achieve this by utilizing the extended `outputPath` option. ```json { "projects": { "my-app": { "architect": { "build": { "builder": "@angular-devkit/build-angular:application", "options": { "outputPath": { "base": "dist/my-app", "browser": "", "server": "node-server", "media": "resources" } } } } } } } ``` While not recommended, choosing to set the `browser` option empty will result in files being output directly under the specified `base` path. It's important to note that this action will generate certain files like `stats.json` and `prerendered-routes.json` that aren't intended for deployment in this directory. **Validation rules:** - `browser` and `server` are relative to the configuration set in the `base` option. - When SSR is enabled, `browser` cannot be set to an empty string, and cannot be the same as `server`. - `media` is relative to the value specified in the `browser` option. - `media` cannot be set to an empty string. - `browser`, `media`, or `server` cannot contain slashes. Closes: angular#26632 and closes: angular#26057

…cations This update introduces the ability for users to define the locations for storing `media`, `browser`, and `server` files. You can achieve this by utilizing the extended `outputPath` option. ```json { "projects": { "my-app": { "architect": { "build": { "builder": "@angular-devkit/build-angular:application", "options": { "outputPath": { "base": "dist/my-app", "browser": "", "server": "node-server", "media": "resources" } } } } } } } ``` While not recommended, choosing to set the `browser` option empty will result in files being output directly under the specified `base` path. It's important to note that this action will generate certain files like `stats.json` and `prerendered-routes.json` that aren't intended for deployment in this directory. **Validation rules:** - `browser` and `server` are relative to the configuration set in the `base` option. - When SSR is enabled, `browser` cannot be set to an empty string, and cannot be the same as `server`. - `media` is relative to the value specified in the `browser` option. - `media` cannot be set to an empty string. - `browser`, `media`, or `server` cannot contain slashes. Closes: #26632 and closes: #26057

angular-automatic-lock-bot · 2024-01-14T00:10:44Z

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}

e-oz mentioned this issue Dec 11, 2023

ng new --ssr=false creates angular.json with application builder #26627

Closed

alan-agius4 self-assigned this Dec 11, 2023

alan-agius4 added feature Issue that requests a new feature area: @angular-devkit/build-angular feature: in backlog Feature request for which voting has completed and is now in the backlog angular/build:application labels Dec 11, 2023

e-oz mentioned this issue Dec 12, 2023

[es-build] Browser directory created in outputPath #26304

Closed

1 task

alan-agius4 mentioned this issue Dec 14, 2023

feat(@angular-devkit/build-angular): allow customization of output locations #26675

Merged

alan-agius4 closed this as completed in #26675 Dec 14, 2023

angular-automatic-lock-bot bot locked and limited conversation to collaborators Jan 14, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Config option for `application` builder to set the exact path to output files, without hardcoded `browser` path #26632

Config option for `application` builder to set the exact path to output files, without hardcoded `browser` path #26632

e-oz commented Dec 11, 2023 •

edited

Loading

jonatanpetersson commented Dec 12, 2023

angular-automatic-lock-bot bot commented Jan 14, 2024

Config option for application builder to set the exact path to output files, without hardcoded browser path #26632

Config option for application builder to set the exact path to output files, without hardcoded browser path #26632

Comments

e-oz commented Dec 11, 2023 • edited Loading

Command

Description

Describe the solution you'd like

Describe alternatives you've considered

jonatanpetersson commented Dec 12, 2023

angular-automatic-lock-bot bot commented Jan 14, 2024

Config option for `application` builder to set the exact path to output files, without hardcoded `browser` path #26632

Config option for `application` builder to set the exact path to output files, without hardcoded `browser` path #26632

e-oz commented Dec 11, 2023 •

edited

Loading