title: Angular, npm, nexus, and CI practices
body: <p>This post is an insight on <code>npm</code> for those of you who have a <code>maven</code> background.</p>
  
  <p>In the <code>Java/maven</code> world, you build a source code to a jar, then you push your jar to Nexus. <strong>All of this is done using <code>maven</code></strong>.<br>
  Eventually, your deployment tool retrieves your jar from where it was stored in Nexus, and delivers it to whatever environment it targeted.</p>
  
  <p>Now I'm working on an Angular project and have a hard time, putting all the pieces together.</p>
  
  <p>I understand I can publish my Angular project to an npm repository in Nexus. But what I will publish here will be an npm package, including a <code>package.json</code> file.<br>
  I understand I can build my Angular project to a <code>/dist</code> folder, and deliver this folder to an environment.</p>
  
  <p>But now, I don't understand how it all make sense: with my <code>maven</code> background, I'm expecting to use <code>npm</code> to push the content of the <code>/dist</code> to Nexus!</p>
  
  <p>What am I missing here? What are the good practices in this domain?</p>