[MAT-240] 필기 시스템 packages로 분리 작업

[b0nsu]

📌 Related Issue Number

• MAT-240: 필기 시스템 packages로 분리 작업

---

✅ Key Changes

이번 PR에서 작업한 내용을 간략히 설명해주세요

1. add @repo/pointer-native-drawing package

   • SCRAP 내부에 구현된 skia/drawing 기능을 유지보수를 위해 별도의 싱글톤 패키지로 추출 및 packages 추가
   • metro도 모듈이 중복 번들링 되지 않도록 단일 경로로 고정시킴

2. migrate to shared package and remove unsupported props

   • packages 로 분리된 pointer-native-drawing 의 기능이 minimal 하여 지원되지 않는 기능들을 일시적으로 제거

---

[linear]

MAT-240 [필기 시스템] packages 로 분리 작업

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
pointer-admin	Ready	Preview, Comment	Apr 12, 2026 8:34am

[Copilot]

Pull request overview

Extracts the Scrap drawing/Skia logic into a new shared workspace package (@repo/pointer-native-drawing) and migrates the native app to consume it, while temporarily removing unsupported features.

Changes:

• Added new @repo/pointer-native-drawing package (tsup build, TS config, Skia drawing canvas + path smoothing).
• Migrated apps/native Scrap Skia utilities to re-export/use the shared package and removed legacy local drawing/smoothing modules.
• Updated native UI/state wiring to drop undo/redo history props and adjusted Metro config to try to prevent singleton module double-bundling.

Reviewed changes

Copilot reviewed 18 out of 19 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
packages/pointer-native-drawing/package.json	Declares the new shared drawing package entrypoints/peers.
packages/pointer-native-drawing/tsup.config.ts	Adds build config for ESM/CJS + externals.
packages/pointer-native-drawing/tsconfig.json	TypeScript config for the shared package.
packages/pointer-native-drawing/src/index.ts	Public exports for the shared package.
packages/pointer-native-drawing/src/DrawingCanvas.tsx	New shared Skia drawing canvas implementation.
packages/pointer-native-drawing/src/smoothing.ts	New shared path smoothing implementation.
apps/native/src/features/student/scrap/utils/skia/index.ts	Re-exports drawing utilities from the shared package.
apps/native/src/features/student/scrap/utils/handwritingEncoder.ts	Updates type imports to use the new re-export surface.
apps/native/src/features/student/scrap/hooks/useHandwritingManager.ts	Updates ref type import path.
apps/native/src/features/student/scrap/screens/ScrapDetailScreen.tsx	Swaps to shared DrawingCanvas import and removes history/text props.
apps/native/src/features/student/scrap/hooks/useDrawingState.ts	Removes undo/redo history state plumbing.
apps/native/src/features/student/scrap/components/scrap/DrawingToolbar.tsx	Removes undo/redo UI and props.
apps/native/src/features/student/problem/screens/ProblemScreen.tsx	Removes history props wiring to the drawing toolbar/canvas.
apps/native/src/features/student/problem/components/ProblemDrawingToolbar.tsx	Removes undo/redo UI and props.
apps/native/package.json	Adds workspace dependency on @repo/pointer-native-drawing and bumps reanimated patch.
apps/native/metro.config.js	Adds custom resolve logic intended to pin singleton modules to a single physical path.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

DrawingCanvasRef.getTexts() always returns an empty array and setTexts() is a no-op. The app still loads/saves handwriting texts via these methods (e.g., useHandwritingManager calls setTexts and later persists getTexts), so this will silently drop previously-saved text items on the next save. Either implement real text storage (even if not rendered) or remove these methods from the ref type and update callers to avoid persisting/overwriting text data.

[Copilot]

DrawingCanvasProps still exposes several props (e.g. textMode, highlighterMode, zoom/pan options, viewportTransform, textFontPath) that are not used by the component implementation. This advertises unsupported behavior to consumers and makes migrations error-prone. Either remove these props from the public type for now or implement the corresponding behavior in DrawingCanvas.

Suggested change

	textMode?: boolean;
	highlighterMode?: boolean;
	highlighterWidth?: number;
	enableZoomPan?: boolean;
	minZoomScale?: number;
	maxZoomScale?: number;
	viewportTransform?: DrawingViewportTransform;
	textFontPath?: unknown;

[Copilot]

SkPath/SkPicture appear to be used only as types in this module. Importing them as runtime values can break the ESM build if @shopify/react-native-skia doesn't export those names at runtime, and it also increases the chance of duplicate/unused imports. Prefer import type { SkPath, SkPicture } ... and keep only runtime values (e.g. Skia) as value imports.

Suggested change

	SkPath,
	SkPicture,
	Skia,
	StrokeCap,
	StrokeJoin,
	} from '@shopify/react-native-skia';
	Skia,
	StrokeCap,
	StrokeJoin,
	} from '@shopify/react-native-skia';
	import type { SkPath, SkPicture } from '@shopify/react-native-skia';

[Copilot]

SkPath is only used as a return type here; importing it as a runtime value can break the generated ESM output if @shopify/react-native-skia doesn't export SkPath at runtime. Prefer a type-only import (import type { SkPath } ...).

Suggested change

	import { Skia, SkPath } from '@shopify/react-native-skia';
	import { Skia } from '@shopify/react-native-skia';
	import type { SkPath } from '@shopify/react-native-skia';

[Copilot]

Text mode is still exposed in the UI (DrawingToolbar uses isTextMode/onTextModePress), but DrawingCanvas is no longer passed textMode and the shared DrawingCanvas implementation doesn’t appear to implement text input. This makes the Text button misleading and can result in unexpected behavior (e.g., still drawing strokes while the UI indicates text mode). Either remove/disable text mode in this screen/state, or reintroduce proper text support via the shared package.

[Copilot]

The singleton-resolve logic computes singletonMap but doesn’t use it when resolving: for singleton packages you return require.resolve(moduleName), which may still resolve to different physical copies depending on Node resolution/hoisting and won’t reliably prevent duplicate bundling in a pnpm monorepo. Use the computed singleton base path when resolving (e.g., require.resolve(moduleName, { paths: [singletonMap[base]] }) or an equivalent Metro resolver approach) so the path is actually pinned.

Suggested change

	// 싱글턴 패키지는 항상 apps/native 기준 경로로 resolve
	const base = moduleName.split('/')[0];
	if (singletonMap[base]) {
	return { type: 'sourceFile', filePath: require.resolve(moduleName) };
	// 싱글턴 패키지는 항상 고정된 단일 설치 경로 기준으로 resolve
	const base = moduleName.startsWith('@')
	? moduleName.split('/').slice(0, 2).join('/')
	: moduleName.split('/')[0];
	if (singletonMap[base]) {
	return {
	type: 'sourceFile',
	filePath: require.resolve(moduleName, { paths: [singletonMap[base]] }),
	};