NativeScript / NativeScript/runtimes
Autolinker for React Native apps
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 25
- Forks
- 4
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 3
Description
Now that we support embedding NativeScript's native interop layer in RN apps as a turbomodule, it would be really convenient to be able to have native sources live alongside JS/TS app source like it does in NativeScript apps - and be able to access those in TS types upon a metagen run.
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 by tracing the existing NativeScript native interop layer exposed as a turbomodule in React Native apps, then inspect how a metagen run produces TypeScript types. Define the autolinking entry points and source-layout expectations before implementing them. Done means native sources can live alongside the app’s JS/TS sources and are represented in generated types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native, typescript
- Domain
- build-system, mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100