title: ｢wds｣: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema
body: <p>I've been trying to find a way to sort/explore millions of drum sounds on my computer for music production and came across <a href="https://experiments.withgoogle.com/ai/drum-machine/view/" rel="nofollow noreferrer">this project</a> and clone <a href="https://github.com/googlecreativelab/aiexperiments-drum-machine" rel="nofollow noreferrer">this github</a></p>
  
  <p>After running <code>npm start</code>, I get the <code>Invalid configuration object</code> error. Full log:</p>
  
  <pre><code>User-2:aiexperiments-drum-machine-master User$ npm start
  
  &gt; drums@1.0.0 start /Users/User/Dropbox/aiexperiments-drum-machine-master
  &gt; webpack-dev-server
  
  ✖ ｢wds｣: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
   - configuration.module has an unknown property 'loaders'. These properties are valid:
     object { defaultRules?, exprContextCritical?, exprContextRecursive?, exprContextRegExp?, exprContextRequest?, noParse?, rules?, strictExportPresence?, strictThisContextOnImports?, unknownContextCritical?, unknownContextRecursive?, unknownContextRegExp?, unknownContextRequest?, unsafeCache?, wrappedContextCritical?, wrappedContextRecursive?, wrappedContextRegExp? }
     -&gt; Options affecting the normal modules (`NormalModuleFactory`).
   - configuration.resolve has an unknown property 'modulesDirectories'. These properties are valid:
     object { alias?, aliasFields?, cachePredicate?, cacheWithContext?, concord?, descriptionFiles?, enforceExtension?, enforceModuleExtension?, extensions?, fileSystem?, mainFields?, mainFiles?, moduleExtensions?, modules?, plugins?, resolver?, symlinks?, unsafeCache?, useSyncFileSystemCalls? }
     -&gt; Options for the resolver
  npm ERR! code ELIFECYCLE
  npm ERR! errno 1
  npm ERR! drums@1.0.0 start: `webpack-dev-server`
  npm ERR! Exit status 1
  npm ERR! 
  npm ERR! Failed at the drums@1.0.0 start script.
  npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
  </code></pre>