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 from eejs require path

🐞 Bug fix

Walkthroughs

Description

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

Diagram

flowchart LR
  A["ep_etherpad-lite/node/eejs/"] -- "remove trailing slash" --> B["ep_etherpad-lite/node/eejs"]
  B -- "compatible with" --> C["ESM etherpad"]
  B -- "compatible with" --> D["CJS etherpad"]

Loading

File Changes

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

Remove trailing slash from eejs require

• Remove trailing slash from require('ep_etherpad-lite/node/eejs/') path
• Change to require('ep_etherpad-lite/node/eejs') for ESM compatibility
• Maintains backward compatibility with current CJS etherpad

copy_paste_select_all.js

---

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

Bump version to 0.0.62

• Increment version from 0.0.61 to 0.0.62

package.json

---

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

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (1)

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

Description

This PR changes the module resolution path for eejs to fix ESM compatibility, but it does not add
or update any automated test to prevent the bug from reappearing. Merging without a regression test
increases the risk of future refactors reintroducing the ESM breakage unnoticed.

Code

copy_paste_select_all.js[3]

Evidence

PR Compliance ID 1 requires that every bug fix include a regression test in the same change set. The
diff shows a functional bug fix to the eejs import path but no accompanying test changes are
present in the PR diff.

AGENTS.md: Bug Fixes Must Include a Regression Test
copy_paste_select_all.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 bug fix was made to the `eejs` `require()` path for ESM compatibility, but no regression test was added/updated in this PR.

## Issue Context
The change removes the trailing slash from `require('ep_etherpad-lite/node/eejs/')` to avoid strict ESM exports-map resolution failures. To meet compliance, add an automated test that would fail with the trailing-slash form and pass with the fixed import.

## Fix Focus Areas
- copy_paste_select_all.js[3-3]
- static/tests/frontend-new/specs/smoke.spec.ts[1-13]

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

---

2. Double version bump 🐞 Bug ☼ Reliability

Description

This PR manually bumps package.json to 0.0.62, but the release workflow also auto-increments the
patch version from package.json and commits/tags it, so the published release will jump an extra
patch (e.g., 0.0.62 → 0.0.63). This can skip versions and increase merge-conflict risk when multiple
PRs touch the version field.

Code

package.json[3]

Evidence

The PR changes the version in package.json, and the release workflow clearly performs its own
patch bump by reading and rewriting package.json, then committing/tagging; together, these
guarantee an extra increment after merge.

package.json[1-6]
.github/workflows/npmpublish.yml[54-86]

Agent prompt

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

### Issue description
The repo’s release pipeline already bumps `package.json` (patch) and creates a tag/commit on merges to `main`/`master`. Keeping a manual version bump in the PR will cause a *double bump* and skipped version numbers.

### Issue Context
The workflow `.github/workflows/npmpublish.yml` reads `./package.json`, increments the patch component, commits, and tags.

### Fix Focus Areas
- package.json[1-6]

**Suggested change**: Revert `"version": "0.0.62"` back to the pre-PR value and let the release workflow perform the patch bump after merge (or, if you intentionally want manual bumps, update the workflow to detect and skip bumping when the version was already changed).

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

This PR changes the module resolution path for eejs to fix ESM compatibility, but it does not add
or update any automated test to prevent the bug from reappearing. Merging without a regression test
increases the risk of future refactors reintroducing the ESM breakage unnoticed.

Agent Prompt

## Issue description
A bug fix was made to the `eejs` `require()` path for ESM compatibility, but no regression test was added/updated in this PR.

## Issue Context
The change removes the trailing slash from `require('ep_etherpad-lite/node/eejs/')` to avoid strict ESM exports-map resolution failures. To meet compliance, add an automated test that would fail with the trailing-slash form and pass with the fixed import.

## Fix Focus Areas
- copy_paste_select_all.js[3-3]
- static/tests/frontend-new/specs/smoke.spec.ts[1-13]

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