NativeScript / NativeScript/nativescript-cli
Feature - nativescript specific entry point in package.json
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 204
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 8
Description
@gngeorgiev commented on Thu Mar 16 2017
Hey guys,
Different module loaders and frameworks recognize specific fields in the package.json of installed packages as an entry point e.g.
- Node.js - main
- Browserify - browser
- Rollup - rollup
- Rect Native - react-native
Since in Everlive we are looking to create platform specific bundles we could really use such a feature in NativeScript.
Regards.
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 how the CLI resolves installed package entry points and review the package.json fields mentioned: main, browser, rollup, and react-native. Define the NativeScript-specific entry-point behavior and verify how platform-specific bundles should be selected without disrupting existing resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100