Skip to content

@ngtools/webpack expects yarn or npm, but not pnpm #22632

Closed

Description

@Usaga

Hi!

@ngtools/webpack performs a ngcc run check to determine if an initial execution is required. It looks for yarn.lock or package-lock.json to run this check. But our project uses pnpm, which has pnpm-lock.yaml. And @ngtools/webpack thinks it is first time build and runs 'ngcc'.

We are using version 12.2.14, but I see this code still there:

    try {
      let lockData;
      let lockFile = 'yarn.lock';
      try {
        lockData = readFileSync(path.join(projectBasePath, lockFile));
      } catch {
        lockFile = 'package-lock.json';
        lockData = readFileSync(path.join(projectBasePath, lockFile));
      }

      let ngccConfigData;
      try {
        ngccConfigData = readFileSync(path.join(projectBasePath, 'ngcc.config.js'));
      } catch {
        ngccConfigData = '';
      }

Activity

  1. modified the milestone: Backlog on Feb 2, 2022
  2. self-assigned this
    on Feb 2, 2022
  3. added 2 commits that reference this issue on Feb 7, 2022
    966dd01
    1317e47
  4. angular-automatic-lock-bot commented on Mar 10, 2022

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  5. locked and limited conversation to collaborators on Mar 10, 2022
  6. added a commit that references this issue on Mar 26, 2024
    bfec69d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions