Published version on npm pulls in React 19

Open Beginner friendly
#41 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
react, typescript
Domain
frontend

Research direction

Start with packages/grapesjs-react/package.json at the linked peer-dependency entry, then compare it with the published metadata using npm view @grapesjs/react dependencies --json. Done means the published package no longer installs React 19 as regular dependencies and matches the intended React 18/19 peer-dependency range.

Written by the indexing model from the issue text.

Description

We have a React 18 project and adding @grapesjs/react pulls in React 19 even though package.json correctly has "react": "^18.0.0 || ^19.0.0" as a peer dependency.

https://github.com/GrapesJS/react/blob/main/packages/grapesjs-react/package.json#L34

The published package on npm has react@^19.0.0 listed as a regular dependency though

$ npm view @grapesjs/react dependencies --json
{
  "react": "^19.0.0",
  "react-dom": "^19.0.0",
  "@types/react": "^19.0.0",
  "@types/react-dom": "^19.0.0"
}
Dominant language
TypeScript
Stars
183
Forks
45
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from GrapesJS/react

All issues in GrapesJS/react

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.