feat(scripts-executors): add inferred projects support to start experience

[Hotell]

Previous Behavior

New Behavior

• feat: adds support to inferred projects
  • metadata retrieval for description
  • target configurations unwrap into separate commands
• fix: generate-api local flag resolution on CI

Related Issue(s)

• Follows chore: migrate v9 and tools to nx inferred tasks #33074

[fabricteam]

📊 Bundle size report

✅ No changes found

[Hotell]

#33200

[dmytrokirpa]

Would it be feasible to include this as a dependency for gererate-api in nx.json, or perhaps even integrate it into an executor?

[Hotell]

yeah

my initial thinking when building these executors was to not make generate-api part of build rather invoke it via nx task dependency definition

"build": "dependsOn": ["^build","generate-api"]

after some thinking I opted out from doing that as build in our scope ( library domain ) needs integrated both generate-api (.d.ts) and build (js transpilation) - to make things encapsulated while composable right.

Now, this issue is rather exotic in context of react-jsx-runtime project, so while I think it's easy and doable to decouple copy assets into a separate executor/function and add it to both build and generate-api, it creates a bit verbose configuration options that start to be misleading IMO.

Only purpose of generate-api should be run tsc and rollup types , not completely "sold" in incorporating assets api because this 1 use case we have is a good idea ATM.

Definitely open to more brainstorming here 💪, ty