Your app's package.json is wrong

Avoid using the name, version and description properties within package.json for an app. Instead, start with a minimal package.json for an app:

{
  "private": true
}

This is the ideal package.json for an app. You may not like it, but this is what peak performance looks like.

Then only add what you need, like scripts and dependencies.¹

Why private?

It's for declaring that you are not going to publish this package on npm. Which is the case for 99.999% of apps.²

Why no other metadata?

The purpose of properties like name, version, and description is to communicate metadata for your package to tools like npm. They are what power things like the npm info and npm search commands.

But what's the harm?, you may ask. To answer that, consider who are you trying to convey this information to.

Your users? Put the information where they'll actually see it. In your docs, or better yet, within your app itself. If users of your app have to look at your package.json to get your app's name and version, you've got some serious UX problems. Not to mention that if your app's code isn't easy to get, your users won't be able to access the package.json in the first place.

What about your coworkers? Do them (and your future self) a favor and write a README or some docs. There's already too many places to put your app's name (your repo name, README title, docs, etc...), so don't add yet another place in your package.json. That just makes it more confusing when all those name end up being different.

Unless...

If you need a central place to put your app's metadata where you will programmatically access it, then I won't judge you for putting it in package.json. For example, if you wanted to templetize your docs so that your app's name and version came directly from the name and version fields in package.json. Just remember that you are not using those properties for what they were designed for, which can create false affordances.