fix: backward-compat for ESM etherpad

[SamTV12345]

This PR makes the plugin backward-compatible with the upcoming ESM etherpad branch (ether/etherpad#7605).

Change: Remove trailing slash from require("ep_etherpad-lite/node/eejs/") → require("ep_etherpad-lite/node/eejs")

The trailing-slash form breaks under Node's strict ESM exports map resolution. This change is backward-compatible with the current CJS etherpad release.

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

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

Review Summary by Qodo

Remove trailing slash for ESM etherpad compatibility

🐞 Bug fix

Walkthroughs

Description

• Remove trailing slash from eejs require path
• Ensures compatibility with upcoming ESM etherpad
• Maintains backward compatibility with current CJS
• Bump version to 0.2.54

Diagram

flowchart LR
  A["require with trailing slash"] -- "breaks ESM exports" --> B["ESM etherpad incompatible"]
  C["require without trailing slash"] -- "works with both" --> D["CJS and ESM compatible"]

Loading

File Changes

1. eejs.js 🐞 Bug fix +1/-1

Remove trailing slash from eejs require

• Remove trailing slash from ep_etherpad-lite/node/eejs/ require statement
• Change from require('ep_etherpad-lite/node/eejs/') to require('ep_etherpad-lite/node/eejs')
• Fixes strict ESM exports map resolution compatibility

eejs.js

---

2. package.json ⚙️ Configuration changes +1/-1

Bump version for release

• Increment version from 0.2.53 to 0.2.54

package.json

---

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

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (1)

1. No regression test added 📘 Rule violation ☼ Reliability

Description

The PR changes production code in eejs.js but does not add or update any automated regression test
in the same commit. This risks the ESM/CJS compatibility fix regressing without detection.

Code

eejs.js[3]

Evidence

PR Compliance ID 1 requires that each bug fix include a regression test in the same commit. The diff
shows a production code change to the require('ep_etherpad-lite/node/eejs') import path, but no
test additions/updates are present in the PR diff.

AGENTS.md: Every bug fix must include a regression test in the same commit
eejs.js[3-3]

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 production bug fix was made (changing the `require()` path for `eejs`) without adding/updating a regression test in the same commit.

## Issue Context
The fix is intended to be backward-compatible and to work under Node's strict ESM exports map resolution; a test should fail with the trailing-slash path and pass with the new path.

## Fix Focus Areas
- eejs.js[3-3]
- (add) a new or updated test file under the project's existing test location (e.g., `static/tests/` or the plugin’s test harness) that exercises loading `eejs` and would have failed before this change

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

---

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

1. No regression test added 📘 Rule violation ☼ Reliability

The PR changes production code in eejs.js but does not add or update any automated regression test
in the same commit. This risks the ESM/CJS compatibility fix regressing without detection.

Agent Prompt

## Issue description
A production bug fix was made (changing the `require()` path for `eejs`) without adding/updating a regression test in the same commit.

## Issue Context
The fix is intended to be backward-compatible and to work under Node's strict ESM exports map resolution; a test should fail with the trailing-slash path and pass with the new path.

## Fix Focus Areas
- eejs.js[3-3]
- (add) a new or updated test file under the project's existing test location (e.g., `static/tests/` or the plugin’s test harness) that exercises loading `eejs` and would have failed before this change

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