Compatibility with `nx affected` for test / build executors
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript, webpack
- Domain
- build-system, mobile-dev
Research direction
Start by reproducing nx run {my-app}:build, nx affected:build, and nx affected --target build and inspect the test, build, ios, and android executor configuration. Trace how the ios/android targets consume the regular build target and evaluate the suggested webpack-only build with Nx targetDependencies. Done means all three commands succeed without duplicating the webpack build for ios and Android.
Written by the indexing model from the issue text.
Description
Current behavior
The current setup fails when running the following:
nx run {my-app}:buildnx affected:buildnx affected --target build
Expected Behavior
The above succeed.
Notes
This is partially due to the setup of ios / android targets that pull config from the actual build target, which does not work on its own. This target should be made to work (possibly by invoking a webpack-only build), and then the ios / android targets could invoke it.
If the ios / android targets could consume a webpack-only build, then their executor could use targetDependencies to require the regular build target be hit first, and not have to do a separate webpack build for android and ios.
- Dominant language
- TypeScript
- Stars
- 68
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
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.
More from NativeScript/nx
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
NativeScript/nx#88 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
NativeScript/nx#84 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
NativeScript/nx#80 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
NativeScript/nx#78 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
NativeScript/nx#76 ·
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·