Consider porting .mjs files to .js with "type": "module"

Open
#1,850 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript, node.js
Domain
backend

Research direction

Start by inventorying the repository’s .mjs files and reviewing package.json, then identify import paths that depend on the extension. The change is complete when the files use .js, package.json declares "type": "module", and all affected imports are updated consistently.

Written by the indexing model from the issue text.

Description

The v6 migration converted all files from CommonJS to ESM using the .mjs extension. The .mjs extension was a transitional mechanism — the intended long-term approach is "type": "module" in package.json, which makes plain .js files ES modules by default.

This is now the ecosystem convention (Node.js docs, major frameworks, etc.). Keeping .mjs signals an incomplete migration.

The change is mechanical — rename all .mjs → .js, add "type": "module" to package.json, update any import paths — but worth doing for consistency with modern Node.js conventions.

Dominant language
JavaScript
Stars
1.8k
Forks
308
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 nodeSolidServer/node-solid-server

All issues in nodeSolidServer/node-solid-server

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.