-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Animations won't trigger after build #20685
Comments
Animations also don't work when running the app with "ng serve --prod". |
This worked : animations work when build-optimizer is turned off. ng build --prod --build-optimizer false --base-href /app Is this a bug ? |
dupe of #20374 |
This guy fixes it: #20725 |
#20725 is closed now. Sorry for asking such a basic question, but what exactly does that mean ? |
The next release will be next week. If you want to use the HEAD release of Angular, just point your NPM deps to
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
I'm submitting a...
Current behavior
Animations work when served via "ng serve", but won't trigger when served after "ng build".
Expected behavior
Minimal reproduction of the problem with instructions
Here's how to recreate the error inside one simple file: app.component.ts
ng new animtest
opened app.component.ts in notepad and pasted content below
modified app.module.ts to include 'BrowserAnimationsModule'
ng serve
when clicked Chrome and FF animate the animation correctly
Ctrl + c (server stopped)
ng build --prod --base-href /app/
copied content of 'dist' to folder /var/www/html/app
in Chrome and FF opened http://localhost/app
animations don't work
app.component.ts :
app.module.ts :
What is the motivation / use case for changing the behavior?
Environment
The text was updated successfully, but these errors were encountered: