Code splitting unstable?

[ryb73]

The docs for code splitting have a warning that says:

Code splitting is still a work in progress. It currently only works with the esm output format. There is also a known ordering issue with import statements across code splitting chunks. You can follow the tracking issue for updates about this feature.

This makes it sound like code splitting is unstable/not production-ready. I'm looking at migrating from Rollup but this may be a deal breaker.

Is code splitting ready for use in production?

[evanw]

Yes, the documentation means what it says. Code splitting is still a work in progress. I don't consider it to be ready for use in production yet.

[ryb73]

Thanks for the clarification. I wasn't sure because "work in progress", to me, could mean many things, and it seems that the feature has been around and in use for a long time.

…

On Thu, Jul 20, 2023 at 6:45 PM Evan Wallace ***@***.***> wrote: Yes, the documentation means what it says. Code splitting is still a work in progress. I don't consider it to be ready for use in production yet. — Reply to this email directly, view it on GitHub <#3259 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHGK5F7PGHTMK65SGFO3XLXRGYJHANCNFSM6AAAAAA2R7ZENI> . You are receiving this because you authored the thread.Message ID: ***@***.***>