title: Error changing sequelize-cli configuration to dynamic configuration
body: <p>I am running into a problem, trying change the sequelize-cli configuration to dynamic configuration, as described in the <a href="https://sequelize.org/master/manual/migrations.html#dynamic-configuration" rel="nofollow noreferrer">documentation</a>. I created the .sequelizerc-file in the root-directory of my project and configured the path to config.js.</p>
  <p>After running <code>npx sequelize-cli db:migrate</code> I get the following error:</p>
  <blockquote>
  <p>Sequelize CLI [Node: 12.14.1, CLI: 5.5.1, ORM: 5.21.3]</p>
  <p>Loaded configuration file &quot;config/config.js&quot;.</p>
  <p>Using environment &quot;development&quot;.</p>
  <p>ERROR: Server requests authentication using unknown plugin sha256_password. See TODO: add plugins doco here on how to configure or author authentication plugins.</p>
  </blockquote>
  <p>It doesn't matter if I try it on my development environment (localhost) or on my production environment (clearDB with heroku) I still get the same Error message, not being able to connect to the server. Without the dynamic configuration (config in a *.json) everything worked fine.</p>
  <p>This is the content of my .sequelizerc file</p>
  <pre><code>const path = require('path');
  
  module.exports = {
        'config': path.resolve('config', 'config.js'),
  }
  </code></pre>
  <p>and this is simply the content of my config.js</p>
  <pre><code>module.exports = {
    development: {
      username: process.env.DB_USER,
      password: process.env.DB_PASSWORD,
      database: process.env.DB_NAME,
      host: process.env.DB_HOST,
      dialect: 'mysql',
    },
    production: {
      username: process.env.DB_PROD_USER,
      password: process.env.DB_PROD_PASSWORD,
      database: process.env.DB_PROD_NAME,
      host: process.env.DB_PROD_HOST,
      dialect: 'mysql',
    }
  };
  </code></pre>
  <p>It doesn't matter if I try it on my development environment (localhost) or on my production environment (clearDB with heroku) I still get the same Error message, not being able to connect to the server. Without the dynamic configuration (config in a *.json) everything worked fine.</p>