Automattic / Automattic/harper

mjs (Why lib/ or light-base/ alone forces an npm bump: wasm-node/javascript/prepare.mjs compiles smoldot-light-wasm at pack time) marked as capitalization problem

Open
#4,140 0 comments 0 reactions 0 assignees View on GitHub
bug false-positive harper-core linting
Dominant language
Rust
Stars
15.4k
Forks
627
Avg merge
1d 15h
Merged PRs (30d)
106

Description

**What got flagged?**
mjs

**Why is this incorrect?**
mjs (Why lib/ or light-base/ alone forces an npm bump: wasm-node/javascript/prepare.mjs compiles smoldot-light-wasm at pack time) marked as capitalization problem. File name in this case (In Node.js, .mjs is a file extension used to indicate that a JavaScript file uses ES modules with import/export syntax instead of CommonJS's require/module.exports.)

**Example of correct usage:**
No capitalization problems.

Contributor guide

Open the contributing guide

Research direction

Reproduce the capitalization warning for `mjs`, then inspect Harper's capitalization-checking entry point and the `wasm-node/javascript/prepare.mjs` example mentioned in the issue. Done means `.mjs` is accepted as a file extension while genuine capitalization problems continue to be reported.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js, rust, wasm
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.