Dynamic imports shouldn’t be affected, e.g.
const { something } = await import('./somewhere')
Actually, dynamic imports would be improved from my perspective because they’d be served via HTTP vs DDP. See Nacho’s note here.
I assume nested imports likely would be affected, e.g.
if (Meteor.isServer) {
import { something } from './somewhere'
}
Though I think I recall Nacho mentioning that code in Meteor packages may still be able to use nested imports.
Maybe there’s still a way to keep nested imports for normal app code too, but if not, I still think the benefits of Vite outweigh this downside.