microsoft / microsoft/react-native-windows
package cleanup: Remove internal build logic (/Scripts)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
This is one of a set of issues mentioned in PR #4796 to continue to improve the shipping package layout.
This tracks removal of /Scripts. from the files property of /package.json.
It is currently used by deploy.js#291 which is part of what customers call.
The pr #4796 has more details
This issue tracks:
- Update deploy.js to not depend on it.
- The actual removal.
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
Read PR #4796 for the package-layout context, then inspect vnext/local-cli/runWindows/utils/deploy.js around line 291 and the /Scripts entry in package.json. Update deploy.js so the customer-facing flow no longer depends on vnext/Scripts, remove /Scripts from package.json's files property, and verify the package layout no longer includes it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- build-system, cli
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100