The init generator should

• setup the .nx-pwm.json file
• allow to add a depcheck target for projects

Template for the config file:

{
  "$schema": "./node_modules/nx-pwm/src/lib/config-schema.json",
  "versionType": "independent",
  "depcheck": {
    "ignore": {
      "discrepancies": {
        "*": []
      },
      "missing": {
        "*": []
      }
    }
  }
}

I need to test all of this, it's time.

Tooling in each repo

nx-packages and nx-plugins are repos internal to my company. Both are packages workspaces, the plugins repo is synced-versions, and the packages repo is independent.

• Add same summary for the NX repo itself

What’s the scope of the CLI

Provides tooling for developing, validating, and optionally building & publishing packages in an NX workspace.

• Differentiation should be done for synced-version and independent-version.

TODO: Check how the semver plugin works for synced-version. Perhaps nx-release.js is deprecated.

• Take on the local-registry utility, improve it, add a status utility, etc.

• check-version.ts should be consolidated to a single tool and have it check plugins and normal libraries simultaneously.

• Perhaps check-lock-files should be adjusted to allow different package managers?

Requirements

CLI

nx-pwm should be a CLI so that it can be used the following way:

$ yarn add -D nx-pwm
$ yarn pwm check-versions
$ yarn pwm depcheck

Plugin

nx-pwm should also be a plugin so that it can be used the following way:

$ yarn add -D nx-pwm
$ yarn nx g nx-pwm:install

Implementation

Project generation

As far as I'm concerned, nx-pwm can be generated with @nrwl/nx-plugin.
This does limit the ability to extract logic to nx-based libraries.
For now, this is acceptable. If I want to extract certain behaviors to libraries, I might as well make nx-pwm modular and publish the behaviors.

CLI Impl

TBD

Please make this compatible with the newest version of Nx 👍

Also, add a status subcommand to help users understand what registry they are using, and if possible - where it is configured.

See: https://github.com/gioragutt/nx-pwm/blob/main/packages/nx-pwm/package.json

To temporarily resolve, i've added the following overrides to my package.json:

  "overrides": {
    "@nrwl/devkit@^15.2.4": "15.4.2",
    "@nrwl/workspace@^15.2.4": "15.4.2",
    "nx@^15.2.4": "15.4.2"
  }

it fails to require the .ts file due to export const ...

Can be done before #2 or after it

Tools to add:

• husky
• commitlint
• commitizen
• cz-customizable

Make sure every change is documented and automatable.
Think about incorporating https://github.com/jscutlery/semver into the automation.