-
Notifications
You must be signed in to change notification settings - Fork 12k
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
ng serve does not support the "define" argument #28905
Comments
This behavior is expected since the "architect": {
"build": {
"builder": "@angular-devkit/build-angular:application",
"options": {
"define": {
"GGCC_TARGET": "'hosted'"
}, |
Sorry, but I don't get it. Do you suggest to edit the "angular.json" instead of passing an env var, which worked for my team for years? |
Does the value of |
Yes, I pass different values to run the app in different configurations, i.e with some fractures hidden and different brandings. |
This feature request is now candidate for our backlog! In the next phase, the community has 60 days to upvote. If the request receives more than 20 upvotes, we'll move it to our consideration list. You can find more details about the feature request process in our documentation. |
Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends. Find more details about Angular's feature request process in our documentation. |
Command
serve
Description
I want to pass environment variables into the application during serve and build. In Angular 19, this works for build:
ng build --define="GGCC_TARGET='hosted'"
, while this doesn't for serve:ng serve --define="GGCC_TARGET='hosted'"
, with the following error:Describe the solution you'd like
The
--define
argument works for both serve and build commands.Describe alternatives you've considered
The custom "@ngx-env/builder:application" builder works, but I'd prefer to keep the amount of extra libraries to a minimum. Given how that builder is merely a thin wrapper around "@angular/build:application", I don't see why this couldn't work as I expect out of the box.
The text was updated successfully, but these errors were encountered: