Many frameworks like prettier, eslint etc provides the support to configure the functionality of the framework by giving the configurations in package.json itself.
A key named migrate-mongo-config would be good and pretty easy to pick, provided, when we have certain frameworks that gives reading of the configurations from anywhere, like cosmicconfig npm module.
After this we have one less config file in the root of the project, which is the main concern since root of the project becomes som messy with so many config files, and easy to maintain, as well like this:
Many frameworks like prettier, eslint etc provides the support to configure the functionality of the framework by giving the configurations in package.json itself.
A key named migrate-mongo-config would be good and pretty easy to pick, provided, when we have certain frameworks that gives reading of the configurations from anywhere, like cosmicconfig npm module.
After this we have one less config file in the root of the project, which is the main concern since root of the project becomes som messy with so many config files, and easy to maintain, as well like this:
package.json