digidem / digidem/comapeo-core-react-native
Remove maps fastify plugin from @comapeo/core to drop iOS-only bundler work
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1
- Forks
- 0
- Avg merge
- 8h 24m
- Merged PRs (30d)
- 9
Description
Context
Milestone-doc nice-to-have: "Remove maps fastify plugin from core, so that we can remove extra build work that's done for iOS."
The map server (fastify) currently lives in core and forces extra backend-bundler handling on iOS (undici/polywasm/fetch shims — see backend/index.ios.js, backend/rolldown.config.ts). If the maps plugin moves out of core, that iOS-specific bundling could be simplified or removed.
Scope (to refine)
- Confirm what the iOS bundle pulls in solely because of the maps fastify plugin.
- Coordinate with @comapeo/core to extract the plugin.
- Simplify
rolldown.config.ts/ iOS fetch shims once the dependency is gone.
Note: the bundler has since moved rollup → rolldown (#94); re-evaluate the actual remaining cost before doing this.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with backend/index.ios.js and backend/rolldown.config.ts, then trace which iOS bundle dependencies come solely from the maps Fastify plugin. Coordinate with @comapeo/core on extracting the plugin and re-evaluate the remaining bundler cost after the Rollup-to-Rolldown move. Done means the plugin is no longer in core and unnecessary iOS bundler or fetch-shim work is simplified or removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, typescript
- Domain
- backend, build-system, mobile-dev
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100