Is there support for dynamic and nested imports?

[filipenevola]

Hey, my friend! It's nice to see Meteor & Vite together.

At Quave, we use Vite for simple React client-side-only projects (like websites).

As we know from past attempts with Webpack, one of the challenges is to support features where Meteor is the only one supporting (nested imports), or Meteor implements the feature differently (dynamic imports).

What is the status of these two features using Vite + Meteor?

Thanks ;)

[nachocodoner]

Hey Filipe!

This repository covers Viter integration and is a similar implementation as the Webpack approach described here, this is the simplest form of adoption of a modern bundler. While sacrificing Meteor-specific bundle capabilities, it aligns with standard bundlers, making porting outside the Meteor ecosystem easier and benefit of all modern optimizations. I've used it for my projects, finding it sufficient without concerns about Meteor-specific imports.

Now, with the Meteor community prioritizing backward compatibility, I'm reevaluating. The current repository approach faces challenges on adopting Meteor-specific imports. However, I discovered meteor-vite, a more advanced project ensuring compatibility with Meteor specifics. I'm in touch with the developer, exploring a fully compatible approach for the Meteor community. Maybe this is something you and your team can also evaluate.

Check out this Meteor community discussion on modern bundlers integration.