We considered checking this and similar cases and stopping code execution if the element doesn't exist. Still, we concluded that it would add considerable and unnecessary bulk to the package and eliminate error messages that make debugging easier.

In this case, you used class "loading" that triggers auto init of loading management, yet you did not add all necessary elements. We plan to change auto init from classes to data attributes to prevent that kind of situation.

I did found the issue.

The problem lies in the poor MDB programming. As soon as there is an element with the "loading" class in the DOM, the error occurs because it is accessed in the loading-managment module and attempts to access other elements within the element. However, this is done without any check whether they are really present.

Some extracts from the source code..

*const SELECTOR_LOADING = '.loading'; const SELECTOR_LOADING_ICON = '.loading-icon'; const SELECTOR_LOADING_TEXT = '.loading-text';*

*this._loadingIcon = SelectorEngine.findOne(SELECTOR_LOADING_ICON, this._element); this._loadingText = SelectorEngine.findOne(SELECTOR_LOADING_TEXT, this._element);*

this crashes because this._loadingIcon and this._loadingText are null

*const spinnerCloned = this._loadingIcon.cloneNode(true); const loadingCloned = this._loadingText.cloneNode(true);*

this also

*this._loadingIcon.remove(); this._loadingText.remove();*

To be honest I am quite disappointed

I'm sorry but I need more details. How are you making your imports? Do you use any framework or bundler? Do you have some HTML or JS code that tries to use MDB package?