feat: add native Svelte runtime - #398
Conversation
|
@maxffarrell is attempting to deploy a commit to the open-slide Team on Vercel. A member of the Team first needs to authorize it. |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
@open-slide/shared@open-slide/reactwithout changing its viewer, presenter, inspector, editing, export, or HMR behavior@open-slide/coreas a compatibility facade that installs React transitively and preserves the legacy root, subpath, environment, andopen-slidebinary contracts@open-slide/sveltewith native Svelte mounting, authoring components, viewer and presenter modes, steps, transitions and morphs, HMR, source editing, comments, assets, themes, notes, and HTML/PDF/PPTX exports--framework react|svelteto@open-slide/cli; React remains the default and both templates ship in the published package@open-slide/reactMigration
Existing React workspaces require no changes. Updating
@open-slide/coreautomatically installs@open-slide/reactand@open-slide/shared; existing imports, TypeScript environment references, Vite configuration, package scripts, and theopen-slidecommand continue working.Core remains on the
1.xline as a compatibility package, so current compatible installations receive the migration automatically. New React projects use@open-slide/reactdirectly, and inspector source edits preserve existing@open-slide/coreimports in legacy projects.Verification
@open-slide/coreand keeps the old imports and binary/vite,/locale,/files,/http, and/envcontractsThe root Turbo wrapper can stall locally before starting package commands because of the checkout's pnpm/Corepack wrapper, so the underlying package gates were also run directly. The unchanged Next.js marketing build stall reproduces independently of this refactor.
Notes
The Svelte implementation targets functional workflow parity while remaining idiomatic Svelte; its internal component structure and exact inspector UI are not intended to mirror the React implementation line for line.