Improve implicitDependencies to allow tasks and/or tags to create project linkages

[kschaefe]

Problem

Using the NX guide for a one-ring Storybook solution, there is a section at the bottom about implicitDependencies. Nx is unable to reason about the Storybook connections. This requires manual intervention for each library we add to our monorepo by updating implicitDependencies.

Proposed Solutions

I see 3 possible solutions for this:

1. Allow the specification of a project task, such as build-storybook. The implicit dependency resolution can use the task graph to populate that will the real set of implicit dependencies. This may require an additional property, like implicitTaskDependencies, or a prefix, like task:build-storybook, to be able to differentiate tasks from project names.
2. Allow the specification of a project tag. The implicit dependency resolution can use the project tags to create a list of implicit dependencies. This is less useful than a task-oriented solution as it requires users specify a tag that will be picked up by an implicitDependencies. This may also require an additional property or a prefix.
3. For this particular use-case, the master Storybook library, update the add-storybook to add an implicit dependency to another project. If that master Storybook project is a property for add-storybook, the default value can be set in nx.json, allowing users to automatically add implicit dependencies without realizing that they even need to. This solution is targeted at the specific problem that brings this issue to the forefront, but lacks any kind of wide use.

IMO, solution 1 requires the least end-user intervention for cases like this.

Related Discussions/Issues:

• Improve Project Dependency System #28132 - much higher level than this