Shouldn't pnpm init make the package name attribute valid?

[MrAmericanMike]

So I'll post this as a question just to be sure, I believe it should be a feature request but...

Lets say I have a folder called "Playground", it's an empty folder, I go inside it and run pnpm init

I get something that looks like this:

{
  "name": "Playground",
  "version": "0.0.1",
  "description": "",
  "main": "src/main.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "MrAmericanMike",
  "license": "UNLICENSED",
  "packageManager": "[email protected]"
}

on "Playground" I get a warning that says:

String does not match the pattern of "^(?:(?:@(?:[a-z0-9-*~][a-z0-9-*._~]*)?/[a-z0-9-._~])|[a-z0-9-~])[a-z0-9-._~]*$".

(I'm guessing it's Visual Studio Code doing this)

If it's something "standard" that a project name must be lowercase in package.json, and follow whatever all that regex pattern means.

Shouldn't pnpm at least do folder name to lowercase? Or even better try to convert whatever the folder name is, to something that would be valid "name" field for a package.json file?

[zkochan]

To lower case sounds good to me.