Repository navigation
The early preview: an app starts from npx sv create, adds the library with pnpm add and runs svelte-native init (the guide is docs/). Checked on the release branch: the package, harness and showcase tests, the engine's host checks, the consumer check in its three modes (tarball, git and the guide's starter path, each through a Gradle build), the starter on the OVH emulator to its second screen, and the showcase on the Samsung A16 (the generic camera and image views, the scroll clip under a plain header, the status bar) and the iPhone SE 3 (ExpoView checked by hand; the release build launches). The device suites of native-qa were not run again for this release: PLAN.md has their last full round, on 0.3.0.
Added
svelte-native initturns a SvelteKit project (npx sv create: minimal template, TypeScript, pnpm) into a Svelte Native app, afterpnpm addof the library: the custom-renderer Svelte, the peers at the versions the library was exercised on, SvelteKit pinned to the version it patches,main, the Reanimated flag, the scriptsnative,android,iosandcheck-setup(dev,buildandcheckstay SvelteKit's), pnpm'sallowBuilds,overridesandpatchedDependenciesmerged into the project'spnpm-workspace.yaml, the patch files,metro.config.cjs,app.json, the Vite config (svelteNative()around SvelteKit's plugin, when the file has the shapesvwrites; otherwise the change is printed), the first native routes when there are none, and the.gitignoreentries; thenpnpm installand the doctor.--dry-runprints the plan, a second run changes nothing, a file it cannot change safely is left alone, and--name,--android-package,--ios-bundle-id,--forceand--no-installare the options. It loads neither Svelte's compiler nor Metro, so it runs before the project is set up.svelte-native --helplists the commands.- The guide,
docs/: creating a project fromnpx sv create, the project structure, native routes, development builds andexpo prebuild, native libraries, adding the library to an existing Expo app, and troubleshooting. scripts/consumer-check.sh starter: the path of the guide,sv create,pnpm addof the local package,svelte-native init(and again, which must change nothing),pnpm check, the web build, and the native stages after them.
Changed
- SvelteKit 3.1.1 is the supported version, instead of 3.0.0-next.27. It is what
sv createinstalls. The patch is regenerated for it (patches/@sveltejs__kit@3.1.1.patch) and the peer is3.1.1; the version of the prerelease is no longer supported (the doctor and its tests know one patch per package). Reviewed against the prerelease: the error and warning messages of SvelteKit's client runtime moved to message modules (Metro resolves them, andesm-envstill givesBROWSER), prerender'sFinalizationRegistryis no longer guarded (the library's stand-in is injected where the runtime is compiled),query.liveasks fortext/event-stream, andfor(key)form instances are held from inside the effect (ported toremote/form.svelte.ts). The QA app's bundle is 91,291 bytes (1.6 %) larger from SvelteKit's runtime. examples/minimal's doctor script ischeck-setup(pnpm doctoris pnpm's own command), as in the showcase.- The doctor's fix for a Svelte that is not the custom-renderer build, and for a missing dependency on the library, point at
svelte-native initand the README section that holds the instructions ("Install in an app"); they named "Set up an app".
Fixed
- An app is held to the Node a fresh install accepts, not to the repository's. A new
sv createapp on Node 25, the Node the doctor asked for, stopped at its firstpnpm addwithERR_PNPM_UNSUPPORTED_ENGINE: React Native asks for@react-native/metro-configby a range, so the install took 0.88 beside React Native 0.86.3, and its tools (and Metro 0.87) exclude Node 25.svelte-native doctornow asks an app for^22.17.0 || ^24.3.0 || >=26.0.0(Node 24 LTS first) and the repository's own apps for>=25.0.0, with a fix text for each;svelte-native initpins@react-native/metro-configto React Native's version inoverrides(examples/minimaldoes too); the guide and troubleshooting name the Node to use and show the Node 25 error; the consumer build runs on Node 24. - A SvelteKit app's
svelte-checkis clean without setup.watchRoutesno longer calls.unrefonReturnType<typeof setTimeout>, which a SvelteKit app's tsconfig (no Node types) types as a number, andwithWebRunestakes adynamicCompileOptionscallback of any vite-plugin-svelte release (7.3 adds Vite'senvironmentto its data), so an app needs neither@types/nodenor the 7.2.0 pin. - Android: a
<Screen>that sets nostatusBargets the default status bar appearance, and thestatusBarandnavigationBaroptions take effect at all. The engine looked for the activity through the decor view's context, which on Android 16 is the platform'sDecorContextaround the application context, soSystemBarsreturned before it wrote anything; and its first write was skipped when no option was set (appliedbegan as the spec of "no option"). The window kept the activity theme's light icons: a white clock on the light header of a fresh app. The icons now follow the system appearance, dark by day and light at night, as the engine's header does. Checked on an emulator in light mode; the rules are a host check (SystemBarsRulesCheck).