Brandon Roberts

We did something similar with an esbuild plugin https://github.com/analogjs/analog/blob/beta/packages%2Fvite-plugin-angular%2Fesbuild.ts#L5 Maybe that implementation could be adapted for bun

This is a known limitation with how Angular compilation works with Vite. The analog plugin needs to be first in the chain

Good point and should need some clarification in the docs

Thanks @ahmedhmf. You're correct that most of the files are set up correctly by running `ng add @angular/pwa`, except the `index.html`, the manifest, and the icon assets. The build does...

Yea, I think it might be better to create our own `pwa` generator that wraps the Angular one, moves the files to their intended place, and add a `serviceWorker` option...

> any known workaround or updates on this? Yes, you can see the changes in the commits in this repo https://github.com/brandonroberts/analog-service-worker

Can you share what's in your `package.json`?

Did you move the `index.html` to the root of the `project`? That's usually the case for the `page not found` on startup.

I think you need to set the `root` back to `projects/frontend` and make sure the `index.html` is at `projects/frontend/index.html` And update the options to include the `project/frontend` path along with...

Feel free to reopen if this is still an issue