NativeScript / NativeScript/android
Don't commit libs in repo
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 563
- Forks
- 144
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 14
Description
The github repo of the runtime is getting huge and thus hard to maintain. Even more if we think about releasing more flavors (wasm, Intl...)
Maybe we could think about publishing the libs as github releases with tags instead.
Then we would pull the correct one when installing the @nativescript/android. Or maybe even during prepare.
Another benefit(?) would be a smaller npm package.
All could be prepared/release through github action
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 auditing which libraries are committed to the repository and how @nativescript/android is installed and prepared. Review the existing release process and GitHub Actions configuration, if present. Done means agreeing on and implementing a complete release and installation flow that removes committed libraries while retrieving the correct flavor and keeps the package smaller.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, github-actions
- Domain
- build-system, mobile-dev, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100