With many third-party integrations, customers must maintain configuration for every third party, making the manifest file proliferate. It becomes challenging to keep the files with multiple brands and configurations. It would be easier to split the manifest file based on the field category and include the field in the main manifest file.
Our top recommendation is to use the single manifest.json out-of-the-box, as it is supported and would avoid additional work. You are correct that you'd have to build and run your own custom [JS] solution if you want to split the files and compile or write them into the single manifest file ahead of every bundle upload to Theme Settings.
Hi Denise Rivera,
When you say a script, does that mean we must write custom JS code that will run during the bundle creation? If yes, are there any ways you suggest doing so?
Hi Mirsohail, thank you for submitting this idea. I understand your concern with your manifest file growing to maintain all of your custom properties. At this time, Theme Settings does require the manifest.json to be in its complete form to properly deploy your bundle. We are unable to support split manifest files. Should you opt to split your manifest files and create your own script to compile those, please be aware this would require the script to be run each time you update your bundle and upload to Theme Settings.