Guidelines for packages generating shiny modules

[StatisMike]

I'm developing packages which provide some shiny modules. Every one of them is also generating some UI with shinyInputs - and, as far as I can gather, it would be suboptimal in the current state (where the functions take a dependency on generating inputs from shiny (more specific: textInput, modified numericInput (allowing no initial value and placeholder text), selectizeInput and radioButtons.

What would be the best practices to provide support for shiny.semantic (if the shiny.semantic is loaded use it to import functions from it) without making it dependency?

I'm thinking about creating an argument (eg. shiny.semantic = c(TRUE, FALSE)), so the module will use a different strategy of UI generation for shiny.semantic. Furthermore, adding shiny.semantic to "Suggests" in the DESCRIPTION file. Do you think it would be enough, or should any other way be used?