Nx.json - Be able to add as implicit dependency value a RegExp

Currently, Nx does not allow you to specify a regexp as the value of an implicit dependency such as package.json

Prerequisites

  "npmScope": "mycompany",
  "implicitDependencies": {
    "angular.json": "*",
    "package.json": {
      "dependencies": "@mycompany/lib/*",
      "devDependencies": "*"
    }

Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

• I am running the latest version
• I checked the documentation (nx.dev) and found no answer
• I checked to make sure that this issue has not already been filed
• I’m reporting the issue to the correct repository (not related to React, Angular or any dependency)

Expected Behavior

Should trigger the target action only if the @mycompany/lib has been changed

Please describe the behavior you are expecting

Current Behavior

What is the current behavior?

Failure Information (for bugs)

Please help provide information about the failure if this is a bug. If it is not a bug, please remove the rest of this template.

Steps to Reproduce

Please provide detailed steps for reproducing the issue.

1. step 1
2. step 2
3. …

If you can provide steps to reproduce from scratch, that would be enormously appreciated (i.e. where the first step is npx create-nx-workspace@latest repro-workspace)

Context

Please provide any relevant information about your setup:

Example of nx.json

  "npmScope": "mycompany",
  "implicitDependencies": {
    "angular.json": "*",
    "package.json": {
      "dependencies": "@mycompany/lib/*",
      "devDependencies": "*"
    }

A minimal reproduction scenario allows us to quickly confirm a bug (or point out coding problem) as well as confirm that we are fixing the right problem.

Failure Logs

Please include any relevant log snippets or files here.

Other

Any other relevant information that will help us help you.

[bekos]

@mehrad-rafigh Yes.

[bekos]

@mehrad-rafigh sorry I missed your response! no, it doesn’t seem to be supported 😞 the problem I see though, is that the proposed syntax is not compliant with the current format, as the value of implicitDependencies is always the affected projects 🤔 So a syntax that would make more sense could be:

"implicitDependencies": {
  "angular.json": "*",
  "package.json": {
    "dependencies": {
      "@mycompany/lib/*": ["myapp"],
     },
    "devDependencies": "*"
  }
}

I will try to take a look and see if this an easy change 😃