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 ESM etherpad compatibility with strict exports
• Maintains backward compatibility with current CJS release
• Bump version to 0.0.58

Diagram

flowchart LR
  A["require with trailing slash"] -- "remove slash" --> B["require without trailing slash"]
  B -- "compatible with" --> C["ESM etherpad"]
  B -- "compatible with" --> D["CJS etherpad"]

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 compatibility with strict ESM exports map resolution

eejs.js

---

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

Bump version to 0.0.58

• Increment version from 0.0.57 to 0.0.58
• Reflects the bug fix release

package.json

---

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

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (1)

1. No regression test for eejs require 📘 Rule violation ☼ Reliability

Description

This PR changes the require() path in eejs.js as a bug fix, but it does not add or update any
automated test to prevent regression. Without a regression test, the ESM compatibility fix is not
verifiable and may break again unnoticed.

Code

eejs.js[3]

Evidence

PR Compliance ID 1 requires a regression test alongside any bug fix. The diff shows a bug-fix change
to the require() path in eejs.js, but there are no accompanying test additions/updates in this
PR to cover the fixed behavior.

AGENTS.md: Bug Fixes Must Include a Regression Test in the Same Commit
eejs.js[1-8]

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 (changing `require('ep_etherpad-lite/node/eejs/')` to `require('ep_etherpad-lite/node/eejs')`) but no regression test was added/updated in the same PR.

## Issue Context
The project already has CI workflows that execute plugin-provided backend tests from `static/tests/backend/specs/**` (via Etherpad core's Mocha runner). Add a small backend regression test that would fail with the old trailing-slash form and pass with the new form (for example, by asserting the plugin's `eejs.js` source does not contain the trailing-slash require path, or by requiring the module in a way that triggers resolution).

## Fix Focus Areas
- eejs.js[1-8]
- static/tests/backend/specs/eejs-esm-compat.spec.ts[1-200]

ⓘ 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 for eejs require 📘 Rule violation ☼ Reliability

This PR changes the require() path in eejs.js as a bug fix, but it does not add or update any
automated test to prevent regression. Without a regression test, the ESM compatibility fix is not
verifiable and may break again unnoticed.

Agent Prompt

## Issue description
A bug fix was made (changing `require('ep_etherpad-lite/node/eejs/')` to `require('ep_etherpad-lite/node/eejs')`) but no regression test was added/updated in the same PR.

## Issue Context
The project already has CI workflows that execute plugin-provided backend tests from `static/tests/backend/specs/**` (via Etherpad core's Mocha runner). Add a small backend regression test that would fail with the old trailing-slash form and pass with the new form (for example, by asserting the plugin's `eejs.js` source does not contain the trailing-slash require path, or by requiring the module in a way that triggers resolution).

## Fix Focus Areas
- eejs.js[1-8]
- static/tests/backend/specs/eejs-esm-compat.spec.ts[1-200]

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