Is it considered right to use

@JsExport

on classes/interface in the common code? If I don't do that, the JS side complains about non-exportable types

Yes, sure. We implemented the @JsExport as an annotation (not as a separate keyword) to support the exact case - you have some declaration in common code and want it to be available in JS.