uiwjs / uiwjs/react-codemirror

Dependencies Problem

Open
#721 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
2.3k
Forks
161
PR merge metrics
No merged PRs in 30d

Description

 "peerDependencies": {
    "@babel/runtime": ">=7.11.0",
    "@codemirror/state": ">=6.0.0",
    "@codemirror/theme-one-dark": ">=6.0.0",
    "@codemirror/view": ">=6.0.0",
    "codemirror": ">=6.0.0",
    "react": ">=16.8.0",
    "react-dom": ">=16.8.0"
  },
  "dependencies": {
    "@babel/runtime": "^7.18.6",
    "@codemirror/commands": "^6.1.0",
    "@codemirror/state": "^6.1.1",
    "@codemirror/theme-one-dark": "^6.0.0",
    "@uiw/codemirror-extensions-basic-setup": "4.23.10",
    "codemirror": "^6.0.0"
  },

This is the dependency declaration I saw. I found that everything in @codemirror/view is exported in @uiw/react-codemirror, so I can use it directly without needing to install @codemirror/view myself, which is great.

But when I want to use something from @codemirror/commands, it's not exported in @uiw/react-codemirror, so I need to install @codemirror/commands myself. If the versions are inconsistent, will this cause duplicate packaging? I'm confused about why @codemirror packages need to be declared in dependencies. Can someone help explain this? Thank you.

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.

Research direction

Review the peerDependencies and dependencies declarations shown in the issue, focusing on the @codemirror packages and how @uiw/react-codemirror exposes them. The issue does not name a file or test; done would be a clear explanation of the dependency declarations and whether the requested package should be installed separately.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.