title: New Vaadin 14 app fails to run, error "Failed to determine 'node' tool." Missing Node.js and npm tools
body: <p>I used the <a href="https://vaadin.com/start/latest" rel="noreferrer"><em>Get Started</em></a> page to create a new Vaadin 14 app, after choosing the <em>Plain Java Servlet</em> option. </p>
  
  <p>The web page successfully downloaded a <code>.zip</code> file which I unzipped, and opened with IntelliJ Ultimate Edition version 2019.2. I waited a few minutes while Maven did its thing, downloading and reconfiguring the project. Eventually I went to the Maven panel within IntelliJ, and ran the <code>Lifecycle</code> items <code>clean</code> and <code>install</code>. </p>
  
  <p>I received the following error message on the console.</p>
  
  <pre class="lang-none prettyprint-override"><code>[ERROR] Failed to execute goal com.vaadin:vaadin-maven-plugin:14.0.0:prepare-frontend (default) on project acme: Execution default of goal com.vaadin:vaadin-maven-plugin:14.0.0:prepare-frontend failed: 
  [ERROR] 
  [ERROR] ======================================================================================================
  [ERROR] Failed to determine 'node' tool.
  [ERROR] Please install it either:
  [ERROR]   - by following the https://nodejs.org/en/download/ guide to install it globally
  [ERROR]   - or by running the frontend-maven-plugin goal to install it in this project:
  [ERROR]   $ mvn com.github.eirslett:frontend-maven-plugin:1.7.6:install-node-and-npm -DnodeVersion="v10.16.0" 
  [ERROR] ======================================================================================================
  </code></pre>
  
  <p>See <a href="https://vaadin.com/forum/thread/17797984/error-failed-to-determine-node-tool-with-new-vaadin-14-0-0-rc9-project" rel="noreferrer">discussion on Vaadin Forum</a>.</p>
  
  <p>I filed <a href="https://github.com/vaadin/flow/issues/6262" rel="noreferrer">Ticket # 6262 <em>Configure Maven to automatically install Node.js &amp; npm</em></a>, suggesting to the Vaadin team that requiring and omitting Node.js &amp; npm is a problem. </p>