feat: create ci-package-manager.yml

[lumirlumir]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request?

In this PR, I've added the ci-package-manager.yml reusable workflow.

The original name ci-build-all-pm.yml was somewhat unclear to me about what the workflow does, so I renamed it to ci-package-manager.yml to better reflect its purpose. (Other name suggestions are also welcome, if exists.)

---

I've tested this workflow in the JSON repository (eslint/json#169), and it appears to be working well:

What changes did you make? (Give an overview)

In this PR, I've added the ci-package-manager.yml reusable workflow.

Related Issues

Ref: #4

Is there anything you'd like reviewers to focus on?

• Question: Should this workflow be able to check monorepo setups like the js or rewrite repositories? If so, I can update the workflow to support that.

[nzakas]

Yes, I think it would be worthwhile to add monorepo support.

[lumirlumir]

@nzakas @aladdin-add

I've updated the workflow to support a monorepo structure and tested it against the repositories below.

Everything is working as expected:

• ✅ Test in eslint/create-config: ci: centralize ci-package-manager create-config#210
• ✅ Test in eslint/css: ci: centralize ci-package-manager css#342
• ✅ Test in eslint/csstree: ci: centralize ci-package-manager csstree#92
• ✅ Test in eslint/eslint-transforms: ci: centralize ci-package-manager eslint-transforms#62
• ✅ Test in eslint/generator-eslint: ci: centralize ci-package-manager generator-eslint#237
• ✅ Test in eslint/js: ci: centralize ci-package-manager js#702 (monorepo)
• ✅ Test in eslint/json: ci: centralize ci-package-manager json#169
• ✅ Test in eslint/markdown: ci: centralize ci-package-manager markdown#596
• ✅ Test in eslint/rewrite: ci: centralize ci-package-manager rewrite#337 (monorepo)

[Copilot]

Pull request overview

This PR adds a new reusable workflow ci-package-manager.yml to test package installation across multiple package managers (npm, Yarn v1 Classic, Yarn Modern, pnpm, and Bun). The workflow creates a tarball from repository sources and verifies that each package manager can successfully install it, ensuring compatibility across the Node.js ecosystem.

Key Changes

• Adds ci-package-manager.yml with 6 jobs: one to build a tarball and five to test installation with different package managers
• Implements parallel testing strategy where all package manager jobs depend on the build-tarball job
• Includes support for both single-package and workspace-based repositories via the npm pack --workspace packages 2>/dev/null || npm pack fallback pattern

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.