Remove the datatables.net-dt package (nothing uses it after the dead scripts go)

Open
#7,304 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@IG-ABHINAV is already working on this.

Since Nov 13, 2026.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
52/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript, jquery

Research direction

This is blocked until #7302 and #7303 are merged, so wait for those first. Then remove the datatables.net-dt require line from app/javascript/application.js, drop the package from package.json, and run npm install to update package-lock.json. Run grep -rn -i datatables app/ config/ to catch leftover CSS imports. Done when no DataTables references remain, npm run build succeeds, and bin/rails spec passes.

Written by the indexing model from the issue text.

Description

Difficulty: Easy Good First Issue Help Wanted javascript

What

Once the two dead DataTables scripts are deleted (see the linked issues), nothing uses DataTables. Remove the package.

Blocked by: #7302 and #7303.

Checklist

  • Remove require('datatables.net-dt')(null, window.jQuery) from app/javascript/application.js
  • Remove datatables.net-dt from package.json and run npm install to update package-lock.json
  • Remove any DataTables CSS imports (grep -rn -i datatables app/ config/)
  • npm run build works, and bin/rails spec passes
  • In the PR description, note that this makes #7278 (the DataTables 3 upgrade) unnecessary

Before you start

  • Comment here to be assigned. Setup is bin/setup, then bin/dev. Logins are in the README.
  • JS tests: npm run test. Lint: bin/lint.
  • Part of #7301 (removing jQuery). Keep this PR to just this file.
Dominant language
Ruby
Stars
384
Forks
558
Avg merge
1d 7h
Merged PRs (30d)
63

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 rubyforgood/casa

All issues in rubyforgood/casa

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.