Perceived Problem

User wants an interface like this:

Case 1:
foo 

Case 2:
foo -i

Case 3:
foo -i yarn
foo -I npm
foo -i pnpm

Case 1, when nothing given, means, don't do -i thing. Case 2, when given as boolean, means, do -i thing with some default behaviour case 3, when given, means, do -i thing with this

Ideas / Proposed Solution(s)

How could this be represented in the Zod types?

z.boolean().or(z.enum(['a','b','c'])).default(false)

Should do it.

The internal type would be:

true | false | 'a' | 'b' | 'c'

The false case is because 1) its the default and 2) the user could do this explicitly:

foo --no-i

Currently Mold Command does not know how to parse based on an input union. Nor does it know how to generate docs for an input union.

For parsing there are few rules:

1. If the union includes string literals AND a boolean those string literals CANNOT be false or true since that would make it impossible to properly parse/cast the environment input.

2. Looking at the above example for a concrete example: When parsing the flags, we assume that this -i --something-else means the user is intending to pass as the boolean union member. When they pass -i yarn --something-else we assume the enum.

3. This kind of zod expression would be unsupportable by Molt: z.boolean().or(z.enum(['a','b','c']).default('b')).default(false). A default on a member within the union is not parsable.

~The above leads me to believe that we shouldn't support zod unions but instead roll our own, like we did with .mutuallyExclusive. We could have .union or .or or even simpler could just be accepting an array as the second parameter to .parameter:~

Ignore examples below and see comment below.

Command.parameter('i install', [z.boolean(), z.enum(['a','b','c'])])

Ah, but the problem with this is we lose the ability to express the concept of a default for the parameter. Ok, try again with a builder function then:

Command
  .parameter('i install', __ =>
    __.value(z.enum(['a','b','c']).description('...'))
      .value(z.boolean().description('...'))
      .default(true)
  )

Allow encoding that one of two fields must be given but not both

ts-node publish.ts --bump patch                 <-- OK
ts-node publish.ts --version 1.2.3              <-- OK
ts-node publish.ts                              <-- WRONG
ts-node publish.ts --bump patch --version 1.2.3 <-- WRONG

This is an ADT in hiding.

Be able to specify the group/concept and then have Alge compatible ADT returned within.

For example in the above we might identify:

• Method ADT
• Member 1: Bump
• Member 2: Version

const args = Command.mutuallyExclusiveParameters('method', {
  'b bump': z.enum(['major','minor','patch']),
  'v version': z.string().regex(semver)
}).parse()

if (args.method._tag === 'Bump') {
  args.method.value // static type: 'major'|'minor'|'patch'
}

if (args.method._tag === 'Version') {
  args.method.value // static type: string
}

// Plug it into Alge match

Alge.match(args.method)
  .Bump(() => ...)
  .Version(() => ...)

Compose Alge ADTs into Molt:

const Method = Alge.data('Method', {
  Bump: {
    value: z.enum(['major','minor','patch'])
  },
  Version: {
    value: z.string().regex(semver)
  }
})

const args = Command.parametersFromAlge(Method).parse()

Unresolved questions in the above (if we did that):

• How to apply aliases?
• If ADT members have more than one field, what to do? Each one becomes a flag and the whole group of them must be applied and are mutually exclusive to the other group?

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | chalk | 4 -> 5 | | | | |

Release Notes

-import chalk from 'chalk';
+import chalkTemplate from 'chalk-template';

-chalk`2 + 3 = {bold ${2 + 3}}`;
+chalkTemplate`2 + 3 = {bold ${2 + 3}}`;

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | strip-ansi | 6 -> 7 | | | | |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | string-length | 4 -> 5 | | | | |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

Command
  .create({})
  .settings({
    environment: {
      enabled: true,
      prefix: true,
      caseSensitive: false,
      mode: 'replace',
      parameters: {
        $all: false,
        githubToken: {
		  mode: 'replace',
          prefix: null,
          map: 'ghToken'
        },
        path: 'method',
        verbose: ['bar','qux']
      }
    }
  })

Command
  .create({})
  .settings({
    environment: {
      parameters: {
        githubToken: {
          prefix: null
        },
      }
    }
  })

Allow these to be the same:

GITHUB_TOKEN='abc' ts-node publish.ts
                   ts-node publish.ts --githubToken 'abc'

Allow a prefix to be optionally specified:

FOO_GITHUB_TOKEN='abc' ts-node publish.ts
                       ts-node publish.ts --githubToken 'abc'

Make this feature opt-in to avoid total surprises.

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | pnpm (source) | 7.20.0 -> 7.21.0 | | | | |

Release Notes

pnpm/pnpm

v7.21.0

Compare Source

Minor Changes

• The pnpm dlx command supports the --shell-mode (or -c) option. When used, the script is executed by a shell #​5679.

Patch Changes

• The config command should work with the --location=global CLI option #​5841.
• Only the pnpm add --global <pkg> command should fail if there is no global pnpm bin directory in the system PATH #​5841.

Our Gold Sponsors

Our Silver Sponsors

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | pnpm (source) | 7.18.2 -> 7.20.0 | | | | |

Release Notes

pnpm/pnpm

v7.20.0

Compare Source

Minor Changes

• pnpm gets its own implementation of the following commands:

  • pnpm config get
  • pnpm config set
  • pnpm config delete
  • pnpm config list

  In previous versions these commands were passing through to npm CLI.

  PR: #​5829 Related issue: #​5621

• Add show alias to pnpm view #​5835.

• pnpm reads settings from its own global configuration file at $XDG_CONFIG_HOME/pnpm/rc #​5829.

• Add the 'description'-field to the licenses output #​5836.

Patch Changes

• pnpm rebuild should not fail if node_modules was created by pnpm version 7.18 or older #​5815.
• pnpm env should print help.
• Run the prepublish scripts of packages installed from Git #​5826.
• pnpm rebuild should print a better error message when a hoisted dependency is not found #​5815.

Our Gold Sponsors

Our Silver Sponsors

v7.19.0

Compare Source

Minor Changes

• New setting supported in the package.json that is in the root of the workspace: pnpm.requiredScripts. Scripts listed in this array will be required in each project of the worksapce. Otherwise, pnpm -r run <script name> will fail #​5569.
• When the hoisted node linker is used, preserve node_modules directories when linking new dependencies. This improves performance, when installing in a project that already has a node_modules directory #​5795.
• When the hoisted node linker is used, pnpm should not build the same package multiple times during installation. If a package is present at multipe locations because hoisting could not hoist them to a single directory, then the package should only built in one of the locations and copied to the rest #​5814.

Patch Changes

• pnpm rebuild should work in projects that use the hoisted node linker #​5560.
• pnpm patch should print instructions about how to commit the changes #​5809.
• Allow the -S flag in command shims pnpm/cmd-shim#​42.
• Don't relink injected directories if they were not built #​5792.

Our Gold Sponsors

Our Silver Sponsors

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | pnpm (source) | 7.18.0 -> 7.18.2 | | | | |

Release Notes

pnpm/pnpm

v7.18.2

Compare Source

Patch Changes

• Added --json to the pnpm publish --help output #​5773.
• pnpm update should not replace workspace:*, workspace:~, and workspace:^ with workspace:<version> #​5764.
• The fatal error should be printed in JSON format, when running a pnpm command with the --json option #​5710.
• Throw an error while missing script start or file server.js #​5782.
• pnpm license list should not fail if a license file is an executable #​5740.

Our Gold Sponsors

Our Silver Sponsors

v7.18.1

Compare Source

Patch Changes

• The update notifier should suggest using the standalone script, when pnpm was installed using a standalone script #​5750.
• Vulnerabilities that don't have CVEs codes should not be skipped by pnpm audit if an ignoreCves list is declared in package.json #​5756.
• It should be possible to use overrides with absolute file paths #​5754.
• pnpm audit --json should ignore vulnerabilities listed in auditConfig.ignoreCves #​5734.
• pnpm licenses should print help, not just an error message #​5745.

Our Gold Sponsors

Our Silver Sponsors

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | pnpm (source) | 7.17.1 -> 7.18.0 | | | | |

Release Notes

pnpm/pnpm

v7.18.0

Compare Source

Minor Changes

• Overrides may be defined as a reference to a spec for a direct dependency by prefixing the name of the package you wish the version to match with a `# pnpm.

  {
    "dependencies": {
      "foo": "^1.0.0"
    },
    "overrides": {
      // the override is defined as a reference to the dependency
      "foo": "$foo",
      // the referenced package does not need to match the overridden one
      "bar": "$foo"
    }
  }
  

  Issue: #​5703

Patch Changes

• pnpm audit should work when the project's package.json has no version field #​5728
• Dependencies specified via * should be updated to semver ranges by pnpm update #​5681.
• It should be possible to override a dependency with a local package using relative path from the workspace root directory #​5493.
• Exit with non-zero exit code when child process exits with a non-zero exit clode #​5525.
• pnpm add should prefer local projects from the workspace, even if they use prerelease versions #​5316

Our Gold Sponsors

Our Silver Sponsors

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | pnpm (source) | 7.21.0 -> 7.22.0 | | | | |

Release Notes

pnpm/pnpm

v7.22.0

Compare Source

Minor Changes

• The pnpm list and pnpm why commands will now look through transitive dependencies of workspace: packages. A new --only-projects flag is available to only print workspace: packages.
• pnpm exec and pnpm run command support --resume-from option. When used, the command will executed from given package #​4690.
• Expose the npm_command environment variable to lifecycle hooks & scripts.

Patch Changes

• Fix a situation where pnpm list and pnpm why may not respect the --depth argument.
• Report to the console when a git-hosted dependency is built #​5847.
• Throw an accurate error message when trying to install a package that has no versions, or all of its versions are unpublished #​5849.
• replace dependency is-ci by ci-info (is-ci is just a simple wrapper around ci-info).
• Only run prepublish scripts of git-hosted dependencies, if the dependency doesn't have a main file. In this case we can assume that the dependencies has to be built.
• Print more contextual information when a git-hosted package fails to be prepared for installation #​5847.

Our Gold Sponsors

Our Silver Sponsors

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Perceived Problem

Example: sometimes developer wants CLI to print help when no inputs are passed.

Ideas / Proposed Solution(s)

Allow developer to control the default behaviour.

Could start with a setting helpOnDefault or help: { enabled: true, showWhenNoInput: true }.

Perceived Problem

When @molt/parameters fail the output is ugly

Ideas / Proposed Solution(s)

Setting to control exit:

.settings({
  exitOnParseError: true
})

Helper function for pretty printing the rejections:

Parameters.presentRejection(rejections)