[BUG] Support for package.js to avoid json problems (comments, dangling commas etc)

[Eccenux]

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

I'm sure many people have stumbled upon this: I have a script named 'build-js', I want to try out a new build module, I want to comment it out, add a new script with the same name, try out npm run build pipeline. Comments are not allowed in JSON.

Expected Behavior

Would be nice if, much like eslint, npm would support package.js in the absence of package.json. Obviously it would take a "bit" of time for other tools to adapt, but long term having JS config would work better in some cases (removing items is also easier in JS and diffs are nicer, because you can have dangling commas).

Steps To Reproduce

N/A

Environment

N/A

[ljharb]

There’s a ton of reasons this isn’t viable imo; config needs to be static.

Either way, it’d need to be an RFC and not an issue here, so, closing.