Investigate and perform upgrade to bootstrap v5

Open
#254 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
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
bootstrap, javascript
Domain
frontend, security

Research direction

Start by examining the Gallery Carousel and the module list pagination, then compare the current dependency behavior with bootstrap v5 and its reactstrap usage. Identify the breaking change causing the pagination layout shown in the screenshot, update the affected code if possible, and verify that the pagination matches the expected screenshot while the Carousel vulnerability is addressed.

Written by the indexing model from the issue text.

Description

bug help wanted

Dependabot found a vulnerability in our current bootstrap version: https://github.com/MovingBlocks/movingblocks.github.com/security/dependabot/146
The vulnerability affects the Carousel component which we're using for the Gallery.
We don't use the data-slide and data-slide-to attributes directly and from what I've seen, reactstrap doesn't use them either for their CarouselControl implementation. However, I don't know whether they are used by any of reactstrap's dependencies or any place else, so just to be sure, we should consider upgrading bootstrap to v5.

Upgrading bootstrap v5 would fix this issue, but that breaks the module list pagination (see screenshot below).
We need to figure out the breaking change and adjust our code accordingly if possible.

That's what the upgrade made it look like:
image

Should look like this instead:
image

Dominant language
JavaScript
Stars
7
Forks
17
PR merge metrics
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 MovingBlocks/movingblocks.github.com

All issues in MovingBlocks/movingblocks.github.com

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.