You should remove the @babel/runtime dependency

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Quiet
Tech stack
javascript, react, typescript
Domain
build-system, tooling

Research direction

No file or test is named. Start by locating the @babel/runtime dependency and the package publication or transpilation configuration, then determine which published libraries include it. Done means the dependency is no longer required by the published packages while supported consumers and existing tests still pass.

Written by the indexing model from the issue text.

Description

There's really no reason to have this baked into a library anymore. You can publish a fairly modern ES year, like ES2022 or ES2024, and let applications transpile to an older ES year if they need to according to their browser support policy.

Publishing old JS syntax and requiring @babel/runtime makes these libraries untenable for a modern project.

Dominant language
TypeScript
Stars
2.3k
Forks
161
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 uiwjs/react-codemirror

All issues in uiwjs/react-codemirror

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.