-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to create application because name contains uppercase letters #2165
Comments
I see your point but I don’t think it’s worth complicating the validation logic with special cases like this. There’s no uppercase name that can’t be converted to |
As a Windows user developing an application, this restriction does nothing for me and hinders my usage of this awesome tool. I've edited |
I’m glad you found a workaround. I am hesitant because npm explicitly disallows this (I can’t even run
Also, who knows if some future version of So it’s just not worth the maintenance risks and costs to me. If it truly hinders your productivity, I’m sorry. IMO there are more important things to stress over, and I wouldn’t spend too much energy on folder naming 😉 . |
I work in a predominantly MS-tech-centric company and repeatedly bang my head against this wall (colleagues can get really ruffled feathers over trivial things like this). I note Perhaps we could add a Thoughts? |
What's wrong with manually renaming it after? I don't see why we'd want to add a flag when you can simply rename the folder (and people seldom create apps). |
Sorry I was just enquiring; it's not worth arguing for. |
Sorry, I hope I didn't come off harsh due to my tersity. 😰 |
This is really annoying |
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.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?The text was updated successfully, but these errors were encountered: