react-doctor/remotion-deterministic-randomness
Randomness changes between rendered frames
- Category: Bugs
- Severity: error
- Source:
oxlint-plugin-react-doctor - Framework: global
- Enabled when: remotion:4
- Tags: react-jsx-only
- Default: Enabled
Validate the diagnostic
Confirm the reported code matches this rule before you edit it.
Confirm the reported code matches react-doctor/remotion-deterministic-randomness. Compare it with the Before example and verify the same API, framework, and execution context. Treat it as a false positive only when one of those conditions differs.
Compare the code
The corrected pattern shows a focused way to address the diagnostic.
Reported pattern
import { useCurrentFrame } from "remotion";
const Star = ({ id }) => {
useCurrentFrame();
return <div style={{ opacity: Math.random() }} />;
};Corrected pattern
import { random, useCurrentFrame } from "remotion";
const Star = ({ id }) => {
useCurrentFrame();
return <div style={{ opacity: random(id) }} />;
};How to fix
Use the corrected pattern as a reference. Preserve behavior that the rule does not require you to change.
Copyable fix prompt
Copy this self-contained prompt into your coding agent after you confirm the diagnostic.
Fix every confirmed
Reference transformation:Before:react-doctor/remotion-deterministic-randomness diagnostic in the current repository.
Required change:
- Use Remotion's seeded random(seed) helper so the same frame produces the same value in every render tab.import { useCurrentFrame } from "remotion";
const Star = ({ id }) => {
useCurrentFrame();
return <div style={{ opacity: Math.random() }} />;
};import { random, useCurrentFrame } from "remotion";
const Star = ({ id }) => {
useCurrentFrame();
return <div style={{ opacity: random(id) }} />;
};Constraints:
- Confirm the reported code matches the Before pattern.
- Make the smallest change that fixes the root cause.
- Preserve behavior and interfaces unrelated to this diagnostic.
- Reuse existing project components, utilities, and conventions.
- Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations.
- Adapt identifiers and framework details instead of copying blindly.
- Do not disable the rule or suppress matching code.
- Confirm this rule is enabled for the project:
remotion:4.
Verification:
- Run focused tests for the changed behavior.
- Run React Doctor and confirm this diagnostic no longer appears.
- Report the files changed and any checks you could not run.Related rules
More Bugs rules from the rules reference:
react-doctor/remotion-no-css-animation: CSS animation is not frame-drivenreact-doctor/remotion-no-css-transition: CSS transition is not frame-drivenreact-doctor/remotion-no-css-url-assets: CSS URL asset can flicker in Remotionreact-doctor/remotion-no-module-scope-delay-render: Module-scoped delayRender blocks every compositionreact-doctor/remotion-no-native-media-elements: Native media element bypasses Remotion loading