It's gonna be so nice when npm stops silently allowing undefined config to be passed to it.

Is there any particular reason that commonjs was selected as the default type? Would it not be more logical to initialize new package with module considering they would likely be authored in ESM?

Is there any particular reason that commonjs was selected as the default type? Would it not be more logical to initialize new package with module considering they would likely be authored in ESM?

@jonkoops the default in nodejs is commonjs, before this when you initialized it was implicit, now by default it's fixed.

Understandable, but npm init is to generate a new package. There is very little reason (if any) why the default for new packages should be CommonJS, using module is a much better starting point for new developers that are starting out now.

I'll log a separate issue for this, I think this PR was a good starting point, just needs some tweaking to make it more useful for new users, rather than lock them into legacy module systems.

See #8159