Skip to content

The v17 version has abandoned the parameter 'resources output path'. What is the alternative? #26748

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 task done
sailengsi opened this issue Dec 26, 2023 · 2 comments
Closed
1 task done

Comments

@sailengsi
Copy link

Command

build

Is this a regression?

  • Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

16

Description

The v17 version has abandoned the parameter 'resources output path'. What is the alternative?

Minimal Reproduction

The v17 version has abandoned the parameter 'resources output path'. What is the alternative?

Exception or Error

No response

Your Environment

The v17 version has abandoned the parameter 'resources output path'. What is the alternative?

Anything else relevant?

No response

@JeanMeche
Copy link
Member

#26675, the new application builder will accept outputPath customization in 17.1. You can already test this with 17.1.0-next.3

@JeanMeche JeanMeche closed this as not planned Won't fix, can't repro, duplicate, stale Dec 26, 2023
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jan 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants