We created a workaround to rename all the references in tempusdominus-bootstrap-4.js from datepicker to tempusdatetimepicker and it was enough to solve the problem, but it will be cool if can be fixed in the core and the new versions are completetely isolated in a way that styles do not create css conflicts anymore.
In my company we have a web application that uses https://github.com/uxsolutions/bootstrap-datepicker and some of the boostrap-datepicker styles are applied to tempusdominus widget.
We created a workaround to rename all the references in
tempusdominus-bootstrap-4.js
fromdatepicker
totempusdatetimepicker
and it was enough to solve the problem, but it will be cool if can be fixed in the core and the new versions are completetely isolated in a way that styles do not create css conflicts anymore.