Skip to content

Establish shared legacy runtime initialization - #197

Merged
jdalton merged 1 commit into
dperini:masterfrom
jdalton:refactor/legacy-runtime-init
Sep 5, 2026
Merged

Establish shared legacy runtime initialization#197
jdalton merged 1 commit into
dperini:masterfrom
jdalton:refactor/legacy-runtime-init

Conversation

@jdalton

@jdalton jdalton commented Sep 5, 2026

Copy link
Copy Markdown
Collaborator

Give #178 and #167 shared runtime initialization that we can extend as more capabilities need legacy handling. Modern mode uses native implementations; legacy mode checks support once and reuses the native implementation or fallback.

createWeakMap() is the first helper: legacy mode still uses a native map when available and returns undefined otherwise.

Validation: node --test test/legacy-runtime.test.cjs passes all 4 tests, including reuse without repeated detection. Both dependent revisions are tested and ready to publish after this merges.

@jdalton
jdalton force-pushed the refactor/legacy-runtime-init branch from cc1d5d9 to 058c3e2 Compare September 5, 2026 15:10
@jdalton jdalton changed the title Initialize LEGACY before allocating runtime caches Select runtime cache support during legacy initialization Sep 5, 2026
@jdalton
jdalton force-pushed the refactor/legacy-runtime-init branch from 058c3e2 to bf9f225 Compare September 5, 2026 15:14
@jdalton jdalton changed the title Select runtime cache support during legacy initialization Establish shared legacy runtime initialization Sep 5, 2026
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