Skip to content

raea play works in a folder with its own tsconfig.json - #141

Merged
shinyobjectz merged 1 commit into
mainfrom
play-tsconfig
Nov 13, 2026
Merged

shinyobjectz merged 1 commit into
mainfrom
play-tsconfig

Conversation

@shinyobjectz

Copy link
Copy Markdown
Owner

raea play FILE threw TypeError: (0, import_react.__at) is not a function before its first frame when FILE's folder holds a tsconfig.json (even {}). So did the app's stage and every still drawn by playing. raea render was not affected, which is why it went unnoticed: a still falls back to a render.

Cause

A played composition is bundled from a work folder: its sources are copied to work/src, and work/tsconfig.json carries the paths that point react at the live runtime. The copy took the folder's own tsconfig.json along, and the bundler reads the tsconfig nearest a source, so the project's shadowed the work folder's: react resolved to the engine's React, which has no __at.

raea project new has written a tsconfig.json into every project since the project layout change (for the editor), so any composition kept at a project's root beside it is affected. The 0.1.2 app's own raea fails the same way.

Fix

The work copy leaves out tsconfig.json and jsconfig.json (drop_tsconfigs, after the copy). The project's own files are untouched. A project's own paths never resolved from the work copy anyway (they are relative to the project).

Checked

  • cargo test -p raea-runtime-bundle tsconfig: the copy has neither file, the sources and other JSON stay, the project keeps its own.
  • A composition beside {} and beside the scaffolded tsconfig: refused before, plays after.
  • Three compositions of a real project that failed: each now plays to a still (1.4 s, 5.0 s, 1.9 s).
  • tools/agents/check --land --lane play-tsconfig: L1 ok.

… leaves it out (it shadowed the live runtime's paths; play, the stage and played stills threw __at is not a function)
@shinyobjectz
shinyobjectz merged commit ea5e901 into main Nov 13, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant