I did not understand why we keep the individual utility modules. Wasn't the idea to modify react-components to add a static version of Utility.module.css to the repo instead?

Right, we could then drop utilities too. My only concern with copying is that file can be out of sync if we make dome changes, unless we generate it from utility.css from Lumo package.

Generating it from the CSS file also shouldn't be too much of an issue. I'll try to take a look at that.

Created vaadin/react-components#358 to generate the utilities CSS modules from the CSS sources.

Thanks, merged and removed utilities in this PR as well.

I'm a bit confused what the purpose of this is now, as it just imports random bits and pieces that are remaining. I don't think the package needs to have an entrypoint. Then again I'm lacking context on icon set and such.

Maybe something to discuss in the Daily.

The iconset is the only part still loaded by Lumo class. I agree that we could drop an entrypoint, I just wasn't sure.

I'll merge this PR for now, let's discuss removal of all-imports.js on Monday. One of its benefits is to ensure user apps load vaadin-iconset with the following JS import (even though it's not a common scenario):

import '@vaadin/vaadin-lumo-styles';