Combining multiple package.json files into one using Gulp or other tools

Other Questions NPM
1

I’ve got a project set up with a main folder and three subfolders (A, B, and C). Each subfolder contains its own package.json file with dependencies and devDependencies.

I’m trying to merge all these package.json files into one in the main folder. I’m wondering if there’s a Gulp plugin or any alternative tool that can achieve this.

While handling version conflicts isn’t a strict necessity, a solution that covers them would be a bonus. I’m open to suggestions using Gulp or any other approach that works effectively.

If anyone has tackled this before, could you please share a sample gulpfile.js or guide me through the process? Your help is greatly appreciated!

Thanks in advance for any support!

2

hey, ive done this before! u dont need gulp, just use npm-merge-driver. its super easy 2 setup and handles conflicts automatically. just install it globally and run npm-merge-driver install in ur main folder. itll merge package.json files when u pull or merge branches. saved me tons of time!

3

I have tackled a similar issue in my own projects. Rather than using a Gulp plugin, I built a Node.js script using the fs module to read each package.json, merge their dependencies and devDependencies, and handle version conflicts by determining the highest version. This approach was surprisingly straightforward and efficient, eliminating the need for more complex build tools. The simplicity and reliability of the script have made maintaining my projects easier over time, and I can say it’s a smart solution if you are open to using Node.js directly for such tasks.

4

While Gulp and npm-merge-driver are viable options, I’ve found success using a simple Node.js script with the ‘deepmerge’ package. It’s lightweight and offers precise control over the merging process. Here’s a basic approach:

  1. Install deepmerge: npm install deepmerge
  2. Create a merge script that reads all package.json files
  3. Use deepmerge to combine the objects
  4. Write the result to a new package.json in the root

This method allows for custom conflict resolution and can be easily integrated into your existing build process. It’s been reliable across multiple projects and scales well as your project structure evolves.