Repository navigation
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
devup 자체 API의 추출 결과가 JavaScript 의미와 다르거나 빠지는 문제들입니다.
전체 계획과 결정 사항은 추적 이슈(#682)에 있습니다. 조사 기준 커밋: 77daad74 (현재 main d0b84255).
결정에 따른 작업
- (필수) 배럴 re-export(
export { Box } from "@devup-ui/react",export *)를 모듈 해석으로 따라가 컴파일(KNOWN-5) - (필수) namespace/default import 멤버의 값 읽기(
Devup.Box,[Devup.css],const { css } = Devup)도 컴파일하거나 빌드 에러(KNOWN-6) - (권장) 사용 위치보다 뒤에 선언된 keyframes const(KNOWN-10), 함수 안 alias(KNOWN-11)
발견 항목
심각도: P0 = 흔한 사용에서 조용히 틀리거나 크래시, P1 = 흔한 패턴이 명시적 에러로 막히거나 드물게 조용히 틀림, P2 = 드문 경우·도구/문서 불일치, P3 = 있으면 좋음.
권장 (7)
- FN-08 (P1, ERR-gap) Computed enum members work locally but fail across modules
- 근거: local
enum Computed {A=2,B=A+3,C=8}producesheight:20pxinlocal-enums.tsx; importing the sameE.Bgivescss() cannot use `E.B`inmodules/entry.tsx - 수정 방향: evaluate imported enum initializers against preceding exact members, matching the local Boa path; retain conservative fallback after truly uncertain members
- 근거: local
- FN-09 (P1, ERR-gap) Imported constants lose documented exact Math computations
- 근거: locally
Math.imul,Math.clz32, andMath.froundcompile inexact-values.tsx; imported constants using each produce three build errors inmodules/math-entry.tsx.EXACT_MATHlists them, whileimported_constants.rs:1615-1671does not fold them - 수정 방향: share one exact-builtin policy/evaluator between local and imported constants and add parity tests for every
EXACT_MATHentry
- 근거: locally
- JSX-02 (P1, WRONG) Unknown spreads silently lose Devup style props
- 근거:
10-spreads.tsx:<Box {...runtime} bg="gray"/>becomes<div {...runtime} className={...} style={runtime?.style}/>; a runtime{color:'blue'}remains a meaningless DOMcolorattribute, while no color CSS/class/variable is generated. - 수정 방향: detect potentially style-bearing unknown spreads and either lower supported keys through an explicit runtime style object contract or reject them with a targeted diagnostic/documented escape hatch.
- 근거:
- JSX-03 (P1, WRONG) Lexical shadowing of an imported component name is ignored
- 근거:
21-shadow.tsx: insidefunction render(Box) { return <Box color="pink"/> }, output isreturn <div className="color-0-pink--255"/>; the caller-provided local component is discarded. - 수정 방향: identify Devup components by resolved symbol/reference identity, not identifier spelling; exclude references rebound by parameters or nested declarations.
- 근거:
- JSX-06 (P1, ERR-gap)
createElement(Box, ...)is unsupported although automatic JSX-runtime calls work- 근거:
18-create-element.tsxerrors:`Box` is read at runtime, where it does not exist: the build compiles it only where it is called or rendered. Equivalentjsx(Box,...)andjsxs(Box,...)compile in16-jsx-call.tsx/17-jsxs-call.tsx. - 수정 방향: recognize imported
createElement/React.createElementcalls whose first argument resolves to a Devup component, then reuse the existing component-call rewrite.
- 근거:
- JSX-09 (P2, WRONG) Dynamic non-conditional
styleOrderis silently discarded- 근거:
36-runtime-template-order.tsx:<Box color="red" styleOrder={runtime}/>becomes an ordinarycolor-0-red--255class;runtimevanishes. Static and ternary orders work in15-style-order.tsx. - 수정 방향: either reject non-build-known orders with a focused error or constrain/document the public type to supported static/conditional forms.
- 근거:
- JSX-12 (P3, PERF) Exact nested-scope constants are unnecessarily emitted as runtime variables
- 근거:
19-alias-scope.tsx:const color='green'; return <Box color={color}/>becomesstyle={{'--color-0-':color}}pluscolor:var(...), whereas equivalent top-level/imported constants fold. - 수정 방향: extend constant resolution to lexical scopes using resolved symbols and mutation analysis already required for shadowing correctness.
- 근거:
선택 (1)
- FN-04 (P2, WRONG) Type-only imports are stripped, leaving unresolved type names — 재검증 후 P1→P2: 번들러가 타입을 지우므로 런타임 영향 없음
- 근거: minimal
import type { Box, css } ...; export type A = typeof Boxtransforms toexport type A = typeof Boxwith no import; inlineimport { type Flex }is also removed (import-types.ts) - 수정 방향: honor declaration/specifier
import_kind; never register/remove type-only specifiers as compiled runtime bindings, and retain mixed imports when type specifiers remain
- 근거: minimal
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working
Activity
test(extractor): cover the namespace styled read a stylesheet still t…
test(extractor): cover alias forms that are not package exports
test(extractor): cover parenthesized function-local style objects
test(extractor): cover ClassNames whitespace and non-function children
test(extractor): cover composition and styled branches reported by Linux
fix(landing): keep selector defaults after Card DOM props
test(extractor): cover direct literal selection and dynamic value paths
test(extractor): cover native written class spread precedence
test(extractor): cover scalar order and runtime CSS suffix branches
test(extractor): cover initialization and exact constant safety branches
test(extractor): cover native logical and suspension capture edges
refactor(extractor): make JSX ordering and pruning paths measurable
fix(extractor): track object escapes before static folding
fix(extractor): preserve exact own scalar reads
65 remaining items
fix(extractor): scope build-time style callee detection
fix(extractor): resolve compiled APIs and lowered reads by lexical bi…
fix(extractor): scope aliased library number rewrites by binding
fix(extractor): follow barrel exports and aliases by symbol
chore: add scoped compiled names patch changepack
fix(extractor): close build-time composition and styled capture pipel…
chore(changepack): record composition and styled extraction patch
fix(extractor): preserve styled conditional spread precedence
fix(extractor): reject whole Devup namespace runtime escapes
fix(extractor): preserve exact lexical values and binding-aware require
fix(extractor): preserve JavaScript props evaluation during lowering
fix(components): reorder compile-time style defaults after DOM spreads
owjs3901 commentedon Nov 15, 2026
main(
1160bf646)에 병합된 수정을 확인해 체크리스트를 갱신했습니다. 이 이슈의 모든 항목이 체크되었습니다.새로 체크한 항목 (8건 + 결정 항목 3건)
libs/extractor/src/imported_constants/exact_tests.rs의fn08_*/jsx12_*,exact_math_tests.rs의fn09_*)jsx_semantics_tests/binding_edges.rs의createElement(Box, ...)/React.createElement)jsx_semantics_tests/style_order.rs: 런타임styleOrder는 위치가 있는 빌드 에러)jsx_semantics_tests/type_imports.rs)no-unknown-style-spread규칙). #682의 결정(모르는 spread는 그대로 넘기고 문서화)대로docs/limitations/page.mdx에 문서화되어 있습니다.owjs3901 commentedon Nov 17, 2026
모든 항목이 main에 병합된 PR로 해결되어 닫습니다(항목별 근거는 위 댓글). #682 요약에도 체크했습니다.