Align @a2ui/react markdown dependency architecture with v0.9 and release @a2ui/react@0.10.2

Open Beginner friendly
#1,956 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Quiet
Tech stack
nodejs, react, typescript
Domain
build-system, release

Research direction

The work is in the renderers/react/package.json file. Start by checking the current dependencies and peerDependencies. Use the provided script ./renderers/scripts/increment_version.mjs to bump the version. Run the tests with yarn workspace @a2ui/react run test. Ensure the changes align with the dependency injection model used in @a2ui/lit and @a2ui/angular.

Written by the indexing model from the issue text.

Description

P2

Once @a2ui/markdown-it@0.1.0 is released (see #1955), clean up @a2ui/react's package dependency architecture to align with the v0.9 dependency injection model (matching @a2ui/lit and @a2ui/angular) and release @a2ui/react@0.10.2.

Tasks
  1. In renderers/react/package.json, move @a2ui/markdown-it from "dependencies" to optional "peerDependencies": 
    "peerDependencies": {
  "@a2ui/markdown-it": "^0.1.0",
  "react": "^19.2.7",
  "react-dom": "^19.2.7"
},
"peerDependenciesMeta": {
  "@a2ui/markdown-it": {
    "optional": true
  }
}
  2. Remove standalone "markdown-it" (^14.2.0) from @a2ui/react's "dependencies" since markdown parsing is handled within @a2ui/markdown-it.
  3. Bump @a2ui/react to 0.10.2 via ./renderers/scripts/increment_version.mjs react 0.10.2.
  4. Run unit and integration tests (yarn workspace @a2ui/react run test).
  5. Open PR and publish @a2ui/react@0.10.2.
Dominant language
TypeScript
Stars
16.4k
Forks
1.3k
Avg merge
3d 5h
Merged PRs (30d)
117

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.

More from a2ui-project/a2ui

All issues in a2ui-project/a2ui

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.