Unused runtime deps: jquery, popper.js, @popperjs/core bloat install

Open Beginner friendly
#367 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
90/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Quiet
Tech stack
bootstrap, javascript
Domain
build-system, tooling

Research direction

Start with dependencies in package.json and confirm the imports in src/index.js, src/index.html, src/styles.scss, and src/sass/vendors/_bootstrap.scss. Remove the three unused runtime dependencies, retain bootstrap and vanilla-tilt, then run the project’s install or build command to verify the dependency cleanup does not break the Parcel build.

Written by the indexing model from the issue text.

Description

Problem

package.json declares runtime deps that are never imported by source, and ships two conflicting Popper versions.

Read cite

package.json lines 20-25:

"dependencies": {
  "@popperjs/core": "^2.11.6",
  "bootstrap": "^5.2.3",
  "jquery": "^3.6.3",
  "popper.js": "^1.16.1",
  "vanilla-tilt": "^1.8.0"
}

src/index.js (full contents) only imports ./scripts/scrollReveal and ./scripts/tiltAnimation. src/index.html loads a single <script defer type="module" src="index.js"></script>. src/styles.scss and src/sass/vendors/_bootstrap.scss (@import "~bootstrap/scss/bootstrap") only pull Bootstrap's SCSS — no JS.

Actual

  • jquery never imported (Bootstrap 5 does not require it)
  • popper.js@1 is the deprecated v1 name; @popperjs/core@2 is its successor — both are listed
  • Neither Popper package is imported (Bootstrap 5 JS components not used)

Expected

Remove jquery, popper.js, and @popperjs/core from dependencies. Keep only bootstrap and vanilla-tilt.

Environment

bootstrap ^5.2.3, parcel ^2.8.2 per package.json; README still says "Bootstrap v4.3" (separate doc drift).

Thanks for maintaining cobiwave/simplefolio!

Dominant language
SCSS
Stars
14.2k
Forks
6.1k
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 cobiwave/simplefolio

All issues in cobiwave/simplefolio

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.