Which scope/s are relevant/related to the feature request?
platform
Information
Angular's current compilation model differs from that of Vite's. Angular uses a global compilation model, where Vite is based around single file compilation. The esbuild based builder in the Angular CLI uses an incremental build/watch model along with Vite as a dev server but doesn't allow any use of Vite plugins.
This feature would be similar but would use Vite in a build/watch mode to closer align with Angular's current compilation model, but still use Vite's build pipeline, plugins, etc. The @analogjs/vite-plugin-angular plugin would still be used underneath, and is still available to extend Angular to other ecosystems.
In the future if Angular allows a single file compilation model, that would be supported already.
A spike would be needed to validate this use case, and potential difference in rebuild times.
Describe any alternatives/workarounds you're currently using
No response
I would be willing to submit a PR to fix this issue
Closing as possible, but not recommended after talking with the Vite team. Ideally the Angular Compiler would get some form of single file compilation in the future
Which scope/s are relevant/related to the feature request?
platform
Information
Angular's current compilation model differs from that of Vite's. Angular uses a global compilation model, where Vite is based around single file compilation. The esbuild based builder in the Angular CLI uses an incremental build/watch model along with Vite as a dev server but doesn't allow any use of Vite plugins.
This feature would be similar but would use Vite in a build/watch mode to closer align with Angular's current compilation model, but still use Vite's build pipeline, plugins, etc. The
@analogjs/vite-plugin-angular
plugin would still be used underneath, and is still available to extend Angular to other ecosystems.In the future if Angular allows a single file compilation model, that would be supported already.
A spike would be needed to validate this use case, and potential difference in rebuild times.
Describe any alternatives/workarounds you're currently using
No response
I would be willing to submit a PR to fix this issue