🩹 — Avoid duplicate key "types" in tsconfig

[ldidry]

The key types is present two times in src/tsconfig.json, issuing warnings in log:

[2026-04-27T12:32:09.976] [INFO] Minify - Compress CSS file skins/colibris/index.css.
▲ [WARNING] Duplicate key "types" in object literal [duplicate-object-key]
    tsconfig.json:18:4:
      18 │     "types": ["node", "jquery", "mocha"]
         ╵     ~~~~~~~
  The original key "types" is here:
    tsconfig.json:6:4:
      6 │     "types": ["node", "jquery"],
        ╵     ~~~~~~~

This PR remove the first types, which contains only two values.

[qodo-free-for-open-source-projects]

Review Summary by Qodo

Remove duplicate "types" key from tsconfig.json

🐞 Bug fix

Walkthroughs

Description

• Remove duplicate "types" key from tsconfig.json
• Consolidate TypeScript type definitions into single entry
• Eliminate compiler warnings about duplicate object keys

Diagram

flowchart LR
  A["tsconfig.json<br/>with duplicate types"] -- "remove first types entry" --> B["tsconfig.json<br/>single types definition"]

Loading

File Changes

1. src/tsconfig.json 🐞 Bug fix +0/-1

Remove duplicate types key from config

• Removed duplicate "types" key from compilerOptions
• Kept the second "types" entry with extended type definitions
• Eliminated TypeScript compiler warnings about duplicate keys

src/tsconfig.json

---

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (1)

1. No test for tsconfig fix 📘 Rule violation ☼ Reliability

Description

This PR fixes a warning-causing bug (duplicate types key) but does not add an automated regression
test/check that would fail if the duplicate key were reintroduced. Without a test, the issue can
silently regress in future changes.

Code

src/tsconfig.json[6]

-    "types": ["node", "jquery"],

Evidence

PR Compliance ID 1 requires a regression test for bug fixes. The diff shows only a configuration
change removing the duplicated types key and includes no accompanying test/check changes in this
PR diff.

src/tsconfig.json[6-6]
Best Practice: Repository guidelines

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
A bug fix was made to `src/tsconfig.json` (removing a duplicate `types` key), but there is no automated regression test/check to prevent reintroducing duplicate keys.

## Issue Context
Build tooling already emitted a warning about the duplicate key. A lightweight CI check (test or lint-like script) should fail if `src/tsconfig.json` contains duplicate keys (especially `types`) so the fix is verifiable and non-regressing.

## Fix Focus Areas
- src/tsconfig.json[6-6]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[qodo-free-for-open-source-projects]

1. No test for tsconfig fix 📘 Rule violation ☼ Reliability

This PR fixes a warning-causing bug (duplicate types key) but does not add an automated regression
test/check that would fail if the duplicate key were reintroduced. Without a test, the issue can
silently regress in future changes.

Agent Prompt

## Issue description
A bug fix was made to `src/tsconfig.json` (removing a duplicate `types` key), but there is no automated regression test/check to prevent reintroducing duplicate keys.

## Issue Context
Build tooling already emitted a warning about the duplicate key. A lightweight CI check (test or lint-like script) should fail if `src/tsconfig.json` contains duplicate keys (especially `types`) so the fix is verifiable and non-regressing.

## Fix Focus Areas
- src/tsconfig.json[6-6]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

[JohnMcLear]

@ldidry how did this manifest? Did you get a warning/error? Thanks for the PR :) Hope you are doing good buddy!

[ldidry]

I got the above warning in the logs, which I read when testing a new release to be sure that all plugins works well.

I’m doing fine, thank you. Hope you’re doing well too 🙂