Skip to content
This repository was archived by the owner on Oct 15, 2025. It is now read-only.
This repository was archived by the owner on Oct 15, 2025. It is now read-only.

Yarn package install does not use custom.prisma.version #36

@kyle-swanson

Description

@kyle-swanson

runPackageInstallCommand doesn't use the param from custom.prisma.version if webpack packager is set to yarn.

The issue seems to be in

runPackageInstallCommand({ packageName, cwd, dev }) {
    let params = '';
    let version = this.getPrismaVerisonParam();
    if (dev) params += '-D ';
    if (version) version = `@${version}`;
    const command =
      this.getPackageManager() === 'npm'
        ? `npm install ${params}${packageName}${version}`
        : `yarn add ${params}${packageName}`; // Missing ${version}
    childProcess.execSync(command, { cwd });
  }

prisma is always installed at the latest version when using Yarn.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions