starred/plugins
1
0
Fork 0
mirror of https://github.com/pelican-dev/plugins.git synced 2026-05-09 00:08:54 +02:00
Code Issues 13 Projects Packages Wiki Activity

[PR #122] [MERGED] docs: use Corepack instead of npm i -g yarn in theme setup #123

New issue
Closed
opened 2026-05-07 00:18:15 +02:00 by BreizhHardware · 0 comments
BreizhHardware commented 2026-05-07 00:18:15 +02:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/pelican-dev/plugins/pull/122
Author: @snxRCS
Created: 4/22/2026
Status: ✅ Merged
Merged: 4/30/2026
Merged by: @Boy132

Base: main ← Head: patch-1

📝 Commits (2)

  • ef5c4a4 docs: use Corepack instead of npm i -g yarn in theme setup
  • 90b214d Apply suggestions from code review

📊 Changes

1 file changed (+5 additions, -1 deletions)

View changed files

📝 README.md (+5 -1)

📄 Description

The theme setup snippet in README.md currently installs Yarn via npm i -g yarn, which requires a global npm write and is the legacy way to get Yarn on Node.

Node.js 22 ships with Corepack, the officially supported mechanism for managing package managers (Yarn, pnpm, ...). Enabling Corepack is a single command, avoids the global npm install, and makes the Yarn version pinned per-project (via the packageManager field in a theme's package.json) rather than whatever happens to be globally installed on the host.

Changes

  • ## Additional setup for themes paragraph mentions Corepack instead of a global Yarn install.
  • Replaces npm i -g yarn with sudo corepack enable.

No other changes; the NodeSource install step is untouched.

Summary by CodeRabbit

  • Documentation
    • Updated theme setup to reflect that Yarn can be provided either via direct install or via Node.js Corepack; example commands updated to include enabling Corepack before installing Yarn globally and removed prior requirement to have Yarn preinstalled.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/pelican-dev/plugins/pull/122 **Author:** [@snxRCS](https://github.com/snxRCS) **Created:** 4/22/2026 **Status:** ✅ Merged **Merged:** 4/30/2026 **Merged by:** [@Boy132](https://github.com/Boy132) **Base:** `main` ← **Head:** `patch-1` --- ### 📝 Commits (2) - [`ef5c4a4`](https://github.com/pelican-dev/plugins/commit/ef5c4a458eb8c58ce73cf56669c6f45fbdf29894) docs: use Corepack instead of `npm i -g yarn` in theme setup - [`90b214d`](https://github.com/pelican-dev/plugins/commit/90b214d95fdc5ab020e53ab7b040f19e695eebc0) Apply suggestions from code review ### 📊 Changes **1 file changed** (+5 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+5 -1) </details> ### 📄 Description The theme setup snippet in `README.md` currently installs Yarn via `npm i -g yarn`, which requires a global npm write and is the legacy way to get Yarn on Node. Node.js 22 ships with [Corepack](https://nodejs.org/api/corepack.html), the officially supported mechanism for managing package managers (Yarn, pnpm, ...). Enabling Corepack is a single command, avoids the global npm install, and makes the Yarn version pinned per-project (via the `packageManager` field in a theme's `package.json`) rather than whatever happens to be globally installed on the host. ## Changes - `## Additional setup for themes` paragraph mentions Corepack instead of a global Yarn install. - Replaces `npm i -g yarn` with `sudo corepack enable`. No other changes; the NodeSource install step is untouched. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Updated theme setup to reflect that Yarn can be provided either via direct install or via Node.js Corepack; example commands updated to include enabling Corepack before installing Yarn globally and removed prior requirement to have Yarn preinstalled. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
BreizhHardware 2026-05-07 00:18:15 +02:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
register/email-verification
No results found.
Labels
Clear labels   
pull-request
Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/plugins#123
No description provided.