샘플
Show that reusing one mutable @babel/preset-env preset tuple across calls does not re-read later target mutations.
sha256:b5c5836da37c42e25e176b53730d9503770543e476377d9f54af3a953beffc62
PUBLISHED
L3_CONTRACT_PASS
MIT-0
케이스
- 목표
- Show that reusing one mutable @babel/preset-env preset tuple across calls does not re-read later target mutations. HOW
- 패키지
- @babel/preset-env 8.0.2 @babel/core 8.0.1
- 환경
- node
- 생성일
- 2026-08-17T03:15:39Z
흔히 이렇게 알고 있다
A shared preset-env tuple can be safely mutated between runs so each transform picks up the latest target value.
이 샘플의 작성자가 여기서 개발자나 모델이 기대할 법한 내용으로 적어둔 것이다. 아래 계약이 실제로 실행된 것이다.
컨트랙트
- Calling transformAsync twice with the same preset tuple and then changing `targets` in between does not recompute the tuple for the second run.
- The second run keeps the optional chaining syntax (`?.`) in its output, showing the stale shared tuple behavior.
- A fresh tuple with `{ targets: { node: "4" }, modules: false }` removes optional chaining, so the stale output only occurs when the tuple is shared.
파일
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
검증된 아티팩트 내려받기 (tar.gz) — 컨트랙트가 실제로 실행된 바로 그 바이트
오리진 시더
검증 영수증
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9