voxel51/fiftyone

[FR] Replace yarn for pnpm

Open

#4513 opened on Jun 19, 2024

View on GitHub
 (0 comments) (2 reactions) (0 assignees)Python (4,021 stars) (400 forks)batch import
featuregood first issue

Description

Proposal Summary

Replace yarn for pnpm as node package manager

Motivation

  • What is the use case for this feature? Use pnpm instead of yarn on plugin development
  • Why is this use case valuable to support for FiftyOne users in general?
    1. Pnpm saves space by creating symlinks to the dependency management, saving developer disk space
    2. pnpm takes does not re-download a dependency that was already installed
  • Why is this use case valuable to support for your project(s) or organization? pnpm reduces the time to download dependencies and saves space
  • Why is it currently difficult to achieve this use case? pnpm motivation

What areas of FiftyOne does this feature affect?

  • App: FiftyOne application
  • Core: Core fiftyone Python library
  • Server: FiftyOne server

Details

Use this section to include any additional information about the feature. If you have a proposal for how to implement this feature, please include it here.

Willingness to contribute

The FiftyOne Community welcomes contributions! Would you or another member of your organization be willing to contribute an implementation of this feature?

  • Yes. I can contribute this feature independently
  • Yes. I would be willing to contribute this feature with guidance from the FiftyOne community
  • No. I cannot contribute this feature at this time

Contributor guide

Tech stack
nodejsjavascript
Domain
build systemdevops
Issue type
feature
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.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Node.jsYarn configurationFamiliarity with package managers
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Examine the current Yarn configuration files in the repository (e.g., package.json, yarn.lock, .yarnrc.yml). Identify all places where Yarn commands are used (CI scripts, makefiles). Then outline steps to migrate to pnpm, including updating lock files, changing commands, and ensuring pnpm is installed in CI. Check for any pnpm specific features that could improve the workflow. Finally, create a pull request to replace Yarn with pnpm and update documentation.