title: JSPM - Are there any advantages/disadvantages in including client side library files using import vs using the script tag?
body: <p>I'm starting to use JSPM in my Aurelia web projects and I want to know if there are any consequences or advantages in using the <code>import "&lt;client side library&gt;"</code> ?</p>
  
  <p>I've seen code like so for client side libraries inside JS classes :</p>
  
  <pre><code>import "jquery";
  import "bootstrap/css/bootstrap.css!"
  import "bootstrap";
  
  export class App {
      constructor {
  
      }
  }
  </code></pre>
  
  <p><strong>Question:</strong> What is the difference/advantages/disadvantages between importing it this way as oppose to the traditional include of <code>&lt;script&gt;</code> and <code>&lt;link&gt;</code> tags in the <code>.html</code> file?</p>
  
  <pre><code>&lt;html&gt;
  &lt;head&gt;
     &lt;link rel="stylesheet" src="&lt;bootstrap path&gt;/bootstrap.css"&gt;
  &lt;/head&gt;
  &lt;body&gt;
  
     &lt;script type="text/javascript" src="&lt;bootstrap path&gt;/bootstrap.js"&gt;&lt;/script&gt;
  &lt;/body&gt;
  &lt;/html&gt;
  </code></pre>
  
  <p>My trial and error shows me that by using <code>import</code> in a particular class/js file, it limits the libraries to that particular view file as oppose to being globally available.</p>
  
  <p>Ultimately when you go to build these project for production, don't these libraries need to exists in the index.html?</p>