Resolve a defect discovered in Octane or an Octane library with a correct fix PR or actionable issue in the owning repository instead of a workaround.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
14건(octanejs의 저장소) · 인기순
Resolve a defect discovered in Octane or an Octane library with a correct fix PR or actionable issue in the owning repository instead of a workaround.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit one, several, or all existing Octane bindings; implement selected maintenance findings or remove redundant copied files with evidence matched to source ownership. Use for binding updates, lifecycle fixes, dependency or metadata maintenance, and convenience-import requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Check that a diff, branch, or PR keeps Octane hot paths fast - stable V8 shapes and monomorphic sites, DOM work without forced layout, no new microtask hops or ad-hoc task posters - and that it carries the evidence each risk needs. Use before readying a PR that touches packages/octane/src, compiler output, or binding hot paths, or when reviewing agent-written code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find and fix a bug in the octane monorepo. Use when given a failing test, a regression, or a report that behavior differs from expectation, including deciding whether a React mismatch is an intentional divergence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Open a pull request for octane work. Load before creating the branch, commit, changeset, or PR, including when opening a PR is the tail step of a task that was about something else.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Change Octane's runtime, compiler, scheduler, reconciler, SSR, or hydration engine. Use before editing packages/octane/src. Covers the observable contract, hot-path analysis, and the performance evidence required before handoff.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compatibility entry point for React-library work in Octane; routes existing-binding maintenance to update-bindings and actual React implementation ports to octane-react-library-port.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Octane bindings for TanStack DB. useLiveQuery hook with dependency arrays (8 overloads: query function, config object, pre-created collection, disabled state via returning undefined/null). useLiveSuspenseQuery for Octane Suspense with Error Boundaries (data always defined). useLiveInfiniteQuery for cursor-based pagination (pageSize, fetchNextPage, hasNextPage, isFetchingNextPage). usePacedMutations for debounced Octane state updates. Return shape: data, state, collection, status, isLoading, isReady, isError. Import from @octanejs/tanstack-db (re-exports all of @tanstack/db).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write a new Octane component in .tsrx, convert JSX to .tsrx, or add scoped <style> blocks and themes. Use when creating a .tsrx file rather than editing one, because the path-scoped tsrx-authoring rule only fires once such a file is open.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement and verify new React-library ports or copied/rewritten React surfaces in Octane bindings from npm names or npm/GitHub links/lists. Enforces immutable provenance, license boundaries, dependency ordering, full-surface parity, and machine evidence. Existing-binding audits and maintenance start with update-bindings.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Work out which part of the octane monorepo owns an unfamiliar failure or task. Use when the area is unclear, before picking a more specific skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Work a GitHub issue in the octane repo. Use when given an issue number or link. Fetches the issue, classifies the owning area, and plans the fix.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Keep a change small and in the existing idiom - size the plan and weigh smaller alternatives before writing it, reuse the mechanism that already owns the behavior instead of adding a parallel one, and simplify the diff before handoff. Use when planning any change beyond a few lines, before readying a PR, or when reviewing agent-written code for bloat.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit or defend Octane performance. Use when a change can affect per-render, per-node, scheduling, compiler-output, SSR, hydration, or bundle cost, or when asked whether something is fast enough. Holds the V8-shape, DOM, and scheduling rules hot-path code must follow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.