blasco

As a walk-around, it does work with ngFor, so we can pass the data to the component as an @Input. Not great, but better than copy pasting...

Maybe the code owner can guide us about why this is not working and we can all find a solution.

@Viktor-Bredihin True that each carousel has its own design, but still, making components reusable is very important. For example, I have a carousel where I have arrows for the next...

@romulodanzot it should be ``, I've tested your proposed solution and unfortunately it doesn't work.

Same issue here, any possible solution?

As a provisional solution, disable the snap animation, with out the animation the component works perfectly fine.

Same here, it started happening after upgrading to version 9. For the moment you can roll back to 8.0.0-beta.2 to make it work with angular universal. It shows a warning...

Any news on this?

@bfwg Thank you for the great work. Unfortunately I have no clue what is causing the issue, for the moment I'm staying with 8.0.0-beta.2 version.

Any updates on this? Thank you again