package name is not inferred from scope without project.json file about nx

[JamesHenry]

We only use one name as the source of truth for a project.

• In the case of a only package.json file being present there is name in there explicitly, so we use that.
• If you were to set the name field in project.json to that same value we would use that and not allow anything else either.

Finally, if a project.json is present, that is the ultimate source of truth, and the behavior you are seeing is that we don't force you to write a name in the project.json file and instead infer it from its location on disk if you don't.

I agree that this combination, where there is a package.json with a name, and a project.json without a name, is currently confusing.

[AgentEnder]

Hey - just providing an update here. In package.json you can rename the project under the nx key. The current behavior where the name changes by adding an empty json file is confusing, we should fall back on the package.json instead.

The linked PR corrects that behavior. We can't safely remove the scope from your project names without a configuration field telling us the new name as it introduces footguns around name collisions.