Skip to content

Include TypeScript and ESLint problem matchers from actions/setup-node #83

Open

Description

@htunnicliff

Background

In actions/setup-node, these three problem matchers are added automatically when the action is run:

Here is where actions/setup-node enables them:

https://github.com/actions/setup-node/blob/949feb2413d6458794dcd2491c4babbbce0c15c1/src/main.ts#L91-L102

These matchers add GitHub Actions annotation highlights for the respective patterns in TypeScript and ESLint logs.

Feature Request

Since pnpm/setup can now serve as a replacement for actions/setup-node, I think it would be useful to load these same problem matchers. Doing so would improve parity and help prevent an unexpected loss of functionality.

Would it make sense to copy in the matchers and add the commands to register them as part of this action?

Activity

  1. changed the title [-][Parity] Include problem matchers from actions/setup-node[/-] [+]Include TypeScript and ESLint problem matchers from `actions/setup-node`[/+] on Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions