Nx 16.7.4: how to configure dependency check to find root level package.json

[hrajauria]

Current Behavior

I upgraded my nx version to 16.7.4 and created a few libraries which throw an error for missing dependencies due to the @nx-dependency-check.

Description

I have a monorepo setup with a single package.json on the workspace level. All older libraries/apps do not have a package.json and refer to the common one in the root of the package.

I created new libraries using @nx/js:library plugin and selected tsc as the bundler. As a new feature, it defaults to creating a package.json per library if it is buildable. Link to documentation on this.

The lint target to these libraries fail since it checks the library's package.json for dependencies.

How can I tell nx that the package.json is maintained on the workspace level while creating the libs or skip on generating the package.json at all in the new nx version?

[loxy]

Hi!

This is also something I don't understand.

In docs for dependency-management it is stated that there are two ways of maintaining deps:

• Independently Maintained Dependencies
• Single Version Policy

The recommendation is to use Single Version Policy, which is also again stated in multiple issues: (#3023 or #1777)

But when I create a buildable lib, a package.json is created. How does that fit together? Especially in combination with ESLint rule @nx/dependency-checks, which is also applied always.

I also found this (which is somehow related):

• Decoupled App Dependencies #15360
• NX 17 does not update package.json with internal buildable dependency versions during build #19989
• Buildable library dependencies with single version policy #9510
• Please explain how peer dependencies are used with a single package.json #20451
• dependency-check lint rule should separate options for "including an unused package" vs. ignoring it #20070
• Integrated monorepo. Linter will fail if a publishable libs depends on another lib of the same repo. #20029

My main questions are:

• Do I always have to specify dependencies in my buildable libs even if I use Single Version Policy?
  • If yes: Should I specify all of my deps as peer deps and using * as version?
• Can/should I remove that ESLint rule when I use Single Version Policy?

The thread is now open for nearly two month. Can someone from the core team please enlighten us? Thank you!

[tbarlow12]

Having the same issue here - any updates?

[luisalfonsosandoval]

I'm also having the same issue

[fgirardey]

I have the same issue as well, I don't want to put every packages I use in libs into their respectives package.json files because it would break the same version policy. Is there an opened issue for that?

[binaryartifex]

if this could be looked at that'd be awesome. creating workspace plugins? they come prebaked with their own package.json. @nx/remix apps? come with their own package.json. whats the point of an integrated monorepo if you cant keep it....integrated?

[patrickmichalina]

Does this help? (check the overrides property)

{
    files: ['package.json'], // Only for these files
    rules: {
      '@nx/dependency-checks': 'off', // Disable it for root-level JSON files
    },
  },