You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Views now use a single shared Vite configuration by default, with a minimal `vanilla` fallback for simple HTML/JS/TS UIs.
6
-
- The CLI now exposes a public `createOpenCoreViteConfig` helper through `@open-core/cli/vite` so project-level Vite configs stay small and consistent.
7
-
- PostCSS is auto-resolved from the OpenCore project root when present, which keeps Tailwind and older Chromium targets like RageMP CEF working without extra wiring.
8
-
- Legacy framework-specific CLI view builders were removed. React, Vue, Svelte, and Astro should now be configured in Vite, not in the CLI.
9
-
- Build path normalization and explicit-resource resolution were fixed so duplicated resource builds and stale overrides no longer happen when paths are written with or without `./`.
10
-
11
-
### Recommended Setup
12
-
13
-
- Keep a shared root Vite config next to `opencore.config.ts`.
14
-
- Use `@open-core/cli/vite` to keep that config small.
15
-
- Use `views.framework: 'vite'` for React, Vue, Svelte, Astro, Tailwind, PostCSS, Sass, or any advanced UI setup.
16
-
- Use `views.framework: 'vanilla'` only for simple HTML/CSS/JS/TS views.
17
-
- Add PostCSS only when your project needs it, such as older embedded browsers like RageMP CEF.
18
-
19
-
### Breaking Change
20
-
21
-
- Existing configs using `views.framework: 'react'`, `'vue'`, `'svelte'`, or `'astro'` must be updated to `views.framework: 'vite'`.
22
-
- If those legacy framework values are still used, the CLI now fails with a clear migration error.
6
+
### Improve
7
+
- Improved entrypoint init templates, reduced and more elegant using `loggers` const
0 commit comments