Deno Fresh support for Remotion Player
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- deno, typescript, vite
Research direction
The issue identifies Fresh 2.3.3, Preact compat, Deno package resolution, and Vite pre-bundling, but names no repository files or tests. Start by reading the live reproduction and tracing how Fresh applies deno.json aliases to bundled npm dependencies; first determine whether the issue belongs in Fresh or Vite. Done means documenting a supported workaround or providing working Remotion Player support with runtime inputProps.
Written by the indexing model from the issue text.
Description
Ask
Add (or document) support for @remotion/player
in Fresh. Player is how you embed a Remotion composition in a React/Preact
app and pass runtime inputProps so one composition can render
differently per user/scenario/record. In Fresh + Preact-compat it doesn't
render — the SVG container mounts but stays empty.
Without it, the only path is pre-rendered mp4s. Fine for fixed marketing
assets, kills the runtime-parameterised use case Remotion is best at.
Live evidence
https://skyprospector.com/test-remotion — both delivery options
side-by-side (working static mp4 vs broken Player), with browser-side
diagnostic data printed inline (typeof Player === "object", Player keys
= [$$typeof, render]). Also has the full root-cause writeup, the things
I tried, and possible resolution paths so you don't have to repro
anything to see the shape of the problem.
Root cause (TL;DR)
Player's pre-bundled ESM does var Player = forwardRef(PlayerFn) with
forwardRef from import "react". That import resolves to real
react@19 from npm at runtime, not to the preact/compat alias declared
in deno.json. Real React's forwardRef returns {$$typeof, render}
(an object); Preact's returns a function. Preact silently can't render
the object → empty DOM, no error.
Confirmed in the browser that our island's import "react" correctly
aliases to preact/compat — the aliasing just doesn't propagate to
internal imports of pre-bundled npm packages.
Environment
Fresh 2.3.3, Preact 10.29.1, @remotion/player + remotion
4.0.456, react / react-dom aliased in deno.json to
npm:preact@^10.27.2/compat. Deno (current stable).
Tried (none fixed it): client-only mount via useEffect, Fresh 2.2 →
2.3.3, project-root vite.config.ts with resolve.alias + dedupe +
optimizeDeps.include. Details on the page.
Possible directions
- Fresh's aliasing reaches into pre-bundled npm package internals (likely
helps other React-ecosystem packages too) - Upstream Vite fix if it's fundamentally Vite's pre-bundling behaviour
- Documented Fresh workaround (e.g. esbuild rebundle of Player with
react → preact/compatat bundle time, served fromstatic/) - First-class Remotion guidance in the Fresh handbook — even just a
yes/no would help users decide
Happy to open a standalone repro repo, test a patch, or add diagnostics
to the live page if useful.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 757
- Avg merge
- 3m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from freshframework/fresh
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
freshframework/fresh#3920 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
freshframework/fresh#3833 ·
-
feat
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
freshframework/fresh#3803 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
freshframework/fresh#3918 · 1 comment · 4 reactions ·
-
Tab title doesn't update to <Head> <title> when navigating to a page with another <title>Possibly taken @1AbdullahButt claimed this 7 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 57/100
freshframework/fresh#3916 ·
All issues in freshframework/fresh
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tintinweb/pi-subagents#459 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
danielmiessler/LifeOS#2830 ·
Maintainers usually reply within 6 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area: client enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#3681 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day