We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Don't known / other
Yes
I update my angular project with firebase to v18. When I run ng deploy, I get the below error. Reverting back to angular v17 fixed the error.
No response
ng-deploy's browserTarget and prerender's browserTarget do not match. Please check your angular.json
ng version
Angular CLI: 18.0.4 Node: 20.9.0 Package Manager: npm 10.8.1 OS: darwin arm64 Angular: 18.0.3 ... animations, cdk, common, compiler, compiler-cli, core, forms ... material, platform-browser, platform-browser-dynamic ... platform-server, router, service-worker Package Version --------------------------------------------------------- @angular-devkit/architect 0.1800.4 @angular-devkit/build-angular 18.0.4 @angular-devkit/core 18.0.4 @angular-devkit/schematics 18.0.4 @angular/cli 18.0.4 @angular/fire 18.0.1 @angular/ssr 18.0.4 @schematics/angular 18.0.4 rxjs 7.8.1 typescript 5.4.5 zone.js 0.14.7
The text was updated successfully, but these errors were encountered:
This issue does not seem to follow the issue template. Make sure you provide all the required information.
Sorry, something went wrong.
No branches or pull requests
Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
Yes
Description
I update my angular project with firebase to v18. When I run ng deploy, I get the below error. Reverting back to angular v17 fixed the error.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response
The text was updated successfully, but these errors were encountered: