NativeScript / NativeScript/nx
Plugins with native components installed at workspace-level fail to work
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 68
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Overview
Following on this comment, it is known that NativeScript plugins installed at workspace-level, that have native components (libs) will fail to work. This is a confirmed bug as it is not the intended behaviour (as explained by Nathan).
Versions info
Nx workspace: v12.2
NS CLI: v8.0.2
NS Nx Plugin v1.0.4
OS: macOS 10.15.7
node: v15.14.0
npm: v7.7.6
More details
I created this issue to have a reference for anyone having the same issue at the moment, until it is fixed.
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 reproducing the workspace-level NativeScript plugin setup described in the issue with Nx v12.2, NS CLI v8.0.2, and NS Nx Plugin v1.0.4. Trace how native components are resolved for workspace-level plugins and compare that with the intended behavior referenced in the linked comment. Done means such plugins work from the workspace level without failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100