build(vite-plugin-angular): emit both CJS and ESM formats

[arturovt]

No description provided.

[netlify]

✅ Deploy Preview for analog-blog ready!

Name	Link
🔨 Latest commit	51a11b0
🔍 Latest deploy log	https://app.netlify.com/sites/analog-blog/deploys/64c7cb6a6e74d50008afea9c
😎 Deploy Preview	https://deploy-preview-582--analog-blog.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for analog-docs ready!

Name	Link
🔨 Latest commit	51a11b0
🔍 Latest deploy log	https://app.netlify.com/sites/analog-docs/deploys/64c7cb6a6e74d50008afea9a
😎 Deploy Preview	https://deploy-preview-582--analog-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for analog-app ready!

Name	Link
🔨 Latest commit	51a11b0
🔍 Latest deploy log	https://app.netlify.com/sites/analog-app/deploys/64c7cb6a227853000821cba6
😎 Deploy Preview	https://deploy-preview-582--analog-app.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[brandonroberts]

Thanks @arturovt. I don't think you need to spin anymore cycles on this at the moment. We may end up just using async imports where needed to make this work in an ESM environment for now.

[benmccann]

I think you could convert vite-plugin-angular and vite-plugin-nitro to ESM only and leave the Nx plugin as CJS only. Is there any reason to dual publish this package? Vite works just fine with ESM plugins, so you really shouldn't need to provide a CJS plugin. Especially since user code is compiled to ESM for both the client-side and SSR. It seems like it just adds more complication and maintenance burden to keep CJS here and will eventually cause another migration to ESM only, so you might as well just go straight to the end state and be done with dealing with CJS in these packages for good

[brandonroberts]

Closing in favor of #598