Sounds good, . The doable work here is done!

 are you Ok about closing this task?
Replacing private paths with @folio/stripes path will be done in scope of .

 I've merged changes related to JS imports, For CSS imports. I created a separate task https://folio-org.atlassian.net/browse/UIDEXP-247  and linked it to this one, as it will probably require additional effort.

You are correct about the CSS imports, . , , , any thoughts on if/how we can do this with some webpack magic? Reaching into the private structure of stripes-components feels icky.

If not, maaaaaybe we could mitigate the ickiness by declaring, "Thou shalt provide lib/ComponentName/ComponentName.css" for everything in stripes-components? Granted that's still icky, but at least it provides a veneer of standardization.

 I've fixed all the imports for JS, but I'm not sure if we can import CSS this way. To import CSS, we need the absolute path to the corresponding file. You may know of some webpack plugins that can help us import and export CSS this way, but I couldn't find it.

I mean that is'n possible to do something like this, because it's not possible to export CSS files from index, like we do in JS files:

Error: