Register our Markdown Articles with the Nx Dependency Graph

By leveraging the dependency graph, Nx is able to understand which parts in the monorepo changed and thus trigger actions on those nodes, such as building an app, running tests or linting. This already works out of the box. However, with our portfolio application, all of our markdown articles reside in the root-level _articles folder. Those are not captured by the Nx dependency graph and thus Nx would not correctly detect a change to our Next.js site application whenever we change or add a new markdown article. In this lesson, we learn how to register our _articles folder s.t. it appears as a dedicated node in the Nx dependency graph.

Prefer to read along as well? Here's the accompanying article.