patternfly / patternfly/patternfly-react

Packages do not specify a `type` field

Open
#10,831 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Pinned
Dominant language
TypeScript
Stars
862
Forks
392
Avg merge
4d 8h
Merged PRs (30d)
9

Description

Packages in the workspaces should set the type field in the package.json file. If this field is not set Node.JS may attempt to detect the package type causing a small performance hit. Ideally this field is set to `"type": "module" to indicate an ESM-first approach.

This is part of a series of issues resulting from publication linting introduced under #10764

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Inspect the workspace package.json files and the publication linting context introduced under #10764. Identify which packages lack a type field, confirm the intended ESM value from the issue, and verify that all workspace packages satisfy the publication linting checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
build-system
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.