v1.3.0 — Configuration file support

What's new

predeploy.config.js support — create a config file in your project
root to customise which checks run and how they behave.

// predeploy.config.js
module.exports = {
  checks: {
    'render-start': false,   // disable checks you don't need
    'missing-engines': true,
  },
  ignore: ['legacy/'],       // skip specific paths
  options: {
    'env-vars': {
      envFiles: ['.env.production'],  // check extra env files
    },
  },
};

Partial configs work correctly — only specify what you want to change,
everything else stays enabled. Disabled checks appear as ⏭️ skipped with
a clear explanation rather than silently disappearing.

Details

• Config validation gives clear, actionable error messages for every
  invalid case (wrong type, unknown check ID, syntax errors, etc.)
• A "config loaded" notice appears in terminal output when a config file
  is found, so you always know whether your config was picked up
• --json output now includes a configFile field showing which config
  was used (or null if none)
• Fixed a self-dependency bug where predeploy-check was accidentally
  listed as its own npm dependency

Testing

Added 23 new tests covering the config system (82 total), including
validation error messages, partial config merging, ignore path matching,
and CLI integration tests.

Full Changelog: https://github.com/Alok-Fusion/predeploy_check/commits/v1.3.0