Skip to content

npm: false is not a valid config #132

@snebjorn

Description

@snebjorn

I'm trying to setup release-it and I noticed this in your documentaion

"npm": false

however it doesn't seem to be valid. I'm getting this error from typescript

Type 'false' has no properties in common with type '{ publish?: boolean | undefined; publishPath?: string | undefined; publishArgs?: any[] | undefined; tag?: any; otp?: any; ignoreVersion?: boolean | undefined; allowSameVersion?: boolean | undefined; versionArgs?: any[] | undefined; skipChecks?: boolean | undefined; timeout?: number | undefined; }'

export default {
  npm: false,
  // ... omitted
} satisfies Config;

and looking at the release-it docs it's not mentioned.

However having npm: false does change behavior.

Without it a dry run prints

npm version <OMITTED> --no-git-tag-version

With npm: false it doesn't.

But even with npm.ignoreVersion: true it'll print npm version <OMITTED> --no-git-tag-version

I'm confused.

Anyway npm: false doesn't appear to be a supported config, but without it the release flow will fail if npm.allowSameVersion: true isn't set.

What is going on?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions