RFC: @react-three/eslint-plugin rules · pmndrs/react-three-fiber#2701

(15 comments) (10 reactions) (0 assignees)TypeScript (25,748 stars) (1,464 forks)batch import

help wantedrequest for commentsv10

説明

Aligning with our docs for general performance pitfalls and API usage around context (use R3F hooks within Canvas):

no-clone-in-frame-loop: Prefer creating temporary objects in global space and copy rather than clone in hot paths. This should be restricted to three.js classes to avoid collisions. https://github.com/pmndrs/react-three-fiber/pull/2710
no-fast-state: Don't set state within loops or continuous events (startTransition can be used if you must, this can be disabled for specific polling cases)
prefer-useloader: Prefer useLoader for suspense and caching rather than calling Loader.load or Loader.loadAsync in an effect. This will de-dup resources on both the CPU and GPU and avoid later expensive runtime compilation.

技術スタック: reacttypescriptjavascript
領域: developer experiencetooling
Issue 種別: feature
難度: 3
推定時間: 3-5 days
活動状況: active
明確さ: clear
前提条件: Basic ESLint plugin knowledgeReact Three Fiber conceptsJavaScript/TypeScript
初心者向け度: 60
調査方針: Examine the existing pitfalls documentation (https://docs.pmnd.rs/react three fiber/advanced/pitfalls) and the reference PR #2710 for the no clone in frame loop rule. Study ESLint plugin structures (e.g., ast, rule creation) and decide on rule names and messages. Consider adding tests and documentation.