I have an application with a <code>/client</code> and a <code>/server</code> folder. Currently there&#39;s a single <code>package.json</code> file in the root of the project that has scripts to build the client as well as run the server.
I&#39;ve been playing around with the thought of breaking this single <code>package.json</code> file to two different ones that would be in <code>client/package.json</code> and <code>server/package.json</code> so that the files hold semantic content - client has only client related packages and scripts while the server one has only server related packages and scripts.
An argument that I feel going for this is the fact that in the future, if I have to move my client and server folders to their own repositories, it will be really easy.
Thoughts?

I have an application with a `/client` and a `/server` folder. Currently there's a single `package.json` file in the root of the project that has scripts to build the client as well as run the server.

I've been playing around with the thought of breaking this single `package.json` file to two different ones that would be in `client/package.json` and `server/package.json` so that the files hold semantic content - client has only client related packages and scripts while the server one has only server related packages and scripts.

An argument that I feel going for this is the fact that in the future, if I have to move my client and server folders to their own repositories, it will be really easy.

Thoughts?


Single vs multiple package.json files

Product

Explore

Company

Blogs

Support