Upgrade pnpm and fix the broken tests

Repository metrics

Stars

674 stars (674 stars)

PR merge metrics

No merged PRs in 30d (No merged PRs in 30d)

Description

This issue does not include a description.

Contributor guide

Research direction

First, check the current pnpm version in package.json and pnpm lock.yaml. Identify the broken tests by running the test suite and examining error output. Review the repository's CI configuration to understand the expected test environment. Look for any pinned pnpm version or migration notes. The fix may involve updating pnpm or adjusting test configurations.

Tech stack

nodejs

Domain

build system

Issue type

Bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-2 days

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Unclear

Prerequisites

Node.jsGradlepnpmbasic test debugging

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

20