ci: add package manager install checks

[MikeMcC399]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request?

Current CI checks do not include checking that the packaged version of the repo can be installed. This has allowed release of versions with installation regressions.

This PR adds a new workflow ci-build-all-pm.yml that fills the gap of checking the ability to install.

What changes did you make? (Give an overview)

A tarball is created from the repo package source using npm pack.

The tarball eslint-css-<version>.tgz is then used to install with each of the package manager instructions listed in the README > Installation section

npm install @eslint/css -D
yarn add @eslint/css -D
pnpm install @eslint/css -D
bun install @eslint/css -D

For Yarn, both Yarn v1 Classic and Yarn Modern are tested.

Related Issues

The following issues are related:

• Bug: pnpm install fails ERR_PNPM_LINKED_PKG_DIR_NOT_FOUND #56
• Bug: Yarn v1 Classic install fails non-existing file /typings/css-tree #58

Due to these issues the corresponding tests for Yarn v1 Classic and pnpm are disabled.

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

The outcome of the above two issues will determine whether the disabled tests can be enabled.

[nzakas]

LGTM. This seems super helpful, thank you.

[MikeMcC399]

@nzakas

LGTM. This seems super helpful, thank you.

You're welcome! 🙂

Once the issues with the two failing package managers are resolved, the two disabling lines in the workflow can be removed so that all package managers are then tested.