-
Notifications
You must be signed in to change notification settings - Fork 25.5k
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
Always include the NoopAnimationsModule in ServerModule #14784
Comments
|
Dupe of #15098 |
…efault (angular#15131) This is so that server side rendering does not throw an exception when it encounters animations on the server side and does not need the user to explicitly setup NoopAnimationsModule in their app server module. Fixes angular#15098, angular#14784. PR Close angular#15131
@kukjevov can you fix the problem? |
It was already fixed |
…efault (angular#15131) This is so that server side rendering does not throw an exception when it encounters animations on the server side and does not need the user to explicitly setup NoopAnimationsModule in their app server module. Fixes angular#15098, angular#14784. PR Close angular#15131
…efault (angular#15131) This is so that server side rendering does not throw an exception when it encounters animations on the server side and does not need the user to explicitly setup NoopAnimationsModule in their app server module. Fixes angular#15098, angular#14784. PR Close angular#15131
@kukjevov what version was it fixed? I'm using 4.1.3 and it still throws an error. |
Sorry for late answer, but i think it was fixed in one of 4.0.x releases. Not sure thou. |
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. |
This will let animations work as a no-op on the server side when the AnimationModule included in the client app module.
The text was updated successfully, but these errors were encountered: