tailwind + publishable libs build error about nx HOT 4 CLOSED

Thanks for reporting this!

The issue happens because of a constraint regarding build target names (https://nx.dev/recipes/angular/setup-incremental-builds-angular#build-target-name). What's happening is that the target with an executor that supports incremental builds in your containers library now has a different name (build-angular) while its dependencies (e.g. the project that contains the file/from/another/lib path) probably still have build. The way incremental builds currently work, the target names should be the same.

We are trying out (and plan to enable it by default) a new way of calculating the target dependencies for incremental builds that should not be constrained by this. Could you try running your command with the NX_BUILDABLE_LIBRARIES_TASK_GRAPH=true env var and let me know if it works?

from nx.

thanks for your response @leosvelperez but no luck :(

from nx.

hey @PatoDeVille! Apologies for the delay in getting back to you.

One thing I missed last time is that we need to make sure the task graph has the correct dependencies so Nx can properly figure out the buildable libs dependencies. To do so, please update your targetDefaults in nx.json and add the following:

{
  ...
  "targetDefaults": {
    ...
    "build-angular": {
      "dependsOn": ["^build"]
    },
  },
  ...
}

With that in place, you can build your library (or app) setting the env var I mentioned in my last comment:

NX_BUILDABLE_LIBRARIES_TASK_GRAPH=true nx build my-lib
NX_BUILDABLE_LIBRARIES_TASK_GRAPH=true nx build my-app

The important bit is that any target using one of the Nx executors that supports incremental builds (e.g. @nx/angular:package) must specify the tasks it depends on. In this case, the build-angular task uses the @nx/angular:package executor, and it depends on projects that use the build task with a similar executor. That's why we need to set up that dependency in the build pipeline. Additionally, the NX_BUILDABLE_LIBRARIES_TASK_GRAPH env var enables a new way of calculating those dependencies relying on the task graph and not just on the target name (previous behavior).

Please let me know if you still have any issues after making the adjustments above.

from nx.

I'm closing this since a solution was provided in #22043 (comment) (I tested it in a repo with a similar setup as this issue's description).

@PatoDeVille, if you still have any issues after following the instructions on that comment, please leave a message, and I'll take a look.

from nx.