[DEPR]: edx-ui-toolkit

[sarina]

RFC Start Date

TBD

Target Plan Accepted Date

TBD

Target Transition Unblocked Date

TBD

Earliest Breaking Changes Unblocked Date

TBD

Earliest Open edX Named Release with Breaking Changes

Verawood 04-2026

Rationale

This package is Used only for video block. Should be deprecated, and move it to just live in the video block, for ease of packaging and clarity of use.

Removal

This repo will be deprecated, and the https://www.npmjs.com/package/edx-ui-toolkit npm package will be archived.

Replacement

This package will be moved into the video block, the only place that it is used.

This is blocked by the block extraction work; see openedx/xblocks-contrib#37

Deprecation

No response

Migration

No response

Additional Info

See the npm package migration and deprecation list for a full audit of npm packages used within the Open edX codebase.

Task List

No response

Task List

No response

[kdmccormick]

FYI: The VideoBlock is being extracted from edx-platform into xblocks-contrib. Rather than moving edx-ui-toolkit into edx-platform, I propose that we wait until the block is fully moved to xblocks-contrib, and then merge edx-ui-toolkit into a subfolder of xblocks-contrib.

[sarina]

Agree, thanks for the context @kdmccormick . Is there a timeline on that work, so we can note this is blocked until the block is migrated?

[kdmccormick]

I would expect the old VideoBlock (the one in edx-platform) to be removed between Ulmo and Verawood, which would block this ticket until Verawood.

[sarina]

Thanks, I updated the Earliest Release date to Verawood, and indicated this is blocked for now.

[farhan]

I have added the ticket to @openedx/axim-aximprovements board

[feanil]

If I recall, I think the video block uses a very small subset of the edx-ui-toolkit, we should make sure to only keep what we need and not shift a bunch of code that we don't want around.

[farhan]

If I recall, I think the video block uses a very small subset of the edx-ui-toolkit, we should make sure to only keep what we need and not shift a bunch of code that we don't want around.

I have same understanding, thanks for recalling

[feanil]

This will get done as a part of dropping legacy frontend but we're keeping the tickets so we don't forget about this.