Description
NPM packages are not allowed upper case characters in their name, seemingly because unix filesystems are case-sensitive, which creates "a recipe for confusion and nonportable software".
This makes perfect sense in the context of libraries intended as portable software; however, not so much when speaking about end-of-the-line applications, especially those developed in a case-insensitive environment like Windows.
PR1652 introduced project name validation using validate-npm-package-name
, assumedly to avoid issues with output displaying spaces in names.
Should "React applications", being a different (eg: less focused on "portability") category of software, have these same restrictions?
For example, I am not trying to make an npm package / library. I am trying to use create-react-app
to generate an application, and I need to follow application naming conventions in my company which requires the use of capital letters in the application name.
> create-react-app MyApp
Could not create a project called "MyApp" because of npm naming restrictions:
* name can no longer contain capital letters
Why does this restriction need to apply to react applications / create-react-app
and, if it doesn't, can this solution to #1649 be reconsidered? Perhaps with a subset of the npm restrictions more suited to applications?