Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DX: Implement Vite (and optionally basic codesplitting) #14422

Open
7 of 12 tasks
Jondyr opened this issue Jan 15, 2025 · 0 comments
Open
7 of 12 tasks

DX: Implement Vite (and optionally basic codesplitting) #14422

Jondyr opened this issue Jan 15, 2025 · 0 comments

Comments

@Jondyr
Copy link
Member

Jondyr commented Jan 15, 2025

Vite documentation

Discussionpoints

  • We do this somewhat iteratively by using vite as a purely dev server and keep the old webpack bundling for production
    • Not as big change all at once, can spot vague issues before on prod
    • There may be differences that can cause a bug to not be spotted when developing and serving in two different tools?
  • Static asset management
    • Do we serve static assets (now served by kestrel on the backend along with razor html) through the bundle or CDN? Or something else?

TODO

  • Configuring vite dev & preview server
    • Implement basic replication of webpack bundling
    • Import aliases moved to own file for reuse studio.alias.ts
    • CSS module name hashing, try to mimick how webpack transforms css rules?
  • Add loadbalancer proxy redirecting to vite dev server
  • Moving razor/backend static resources
    • Move razor cshtml to index.html entrypoint
    • Make sure ApplicationInsights ConnectionString is set correctly (maybe from environment variable?)
    • Move static files from backend to either the bundle as static resources or to the CDN?
  • Basic codesplitting
    • Add route-based code-splitting to app-development/routes.tsx
    • Add manual chunks where suitable
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 📈 Todo
Development

No branches or pull requests

1 participant