fix: resolve Mobile Ink from the installed package - #5
Merged
Dronquavious merged 1 commit intoAug 15, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Remove OpenNotes’ hard-coded local
../mobile-inksource overrides from TypeScript and Metro.OpenNotes now resolves
@mathnotes/mobile-inkfromnode_modules, using the exact version committed inpackage.jsonandpackage-lock.json(0.3.3).This makes local development and GitHub Actions use the same package API and type declarations.
Why
The previous configuration always resolved Mobile Ink from a sibling local checkout. That could differ from the published dependency and caused TypeScript resolution failures in environments without the local engine workspace.
Validation
npm ci --legacy-peer-depsnpm run typecheck