Topic: Package conflict
mmmarkk01 priority asked 10 months ago
When importing the free mdb.min.js from the CDN we get some nice functionalities from a lightweight package. To get additional functionalities we add packages from the pro version as needed. Currently while working on the sidenav we've encountered a package conflict between the free mdb.min.js and the sidenav.min.js
The behaviour is that when importing both packages the sidenav collapse element will collapse out but not in.
Likely due to a package conflict since with just the sidenav.min.js imported the functionality works fine.
We expect to be able to add pro packages as imports while using the free mdb.min.js from the CDN and not have any package conflicts that create these strange behaviours.
Resources (screenshots, code snippets etc.)
Thanks for reporting this bug. We'll check why this doesn't work as expected. At the moment, the only solution we can propose is to use our webpack starter to prepare a custom version of the MDB: https://mdbootstrap.com/docs/standard/getting-started/optimization/#section-custom-version-of-mdb-ui-kit this will allow you to add only the components you need.
Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.
- User: Priority
- Premium support: Yes
- Technology: MDB Standard
- MDB Version: MDB5 3.10.2
- Device: PC
- Browser: Edge
- OS: Windows
- Provided sample code: No
- Provided link: No