title: RequireJS absolute path produces Script Error
body: <p>I have a simple file which I'm loading dependencies with requireJS using <code>define</code>:</p>
  
  <pre><code>define([
      "dojo/_base/declare",
      "dojo/aspect",
      "local/path/to/myFile"
  ], function(
      declare,
      aspect,
      myFile
  ) { ...
  </code></pre>
  
  <p>This works as it should, the files are mapped in the requireJS config.</p>
  
  <p>However, if I try to access one of the files using an absolute path (the exact same file):</p>
  
  <pre><code>define([
      "dojo/_base/declare",
      "dojo/aspect",
      "https://blah.com/absolute/path/to/myFile.js"
  ], function(
      declare,
      aspect,
      myFile
  ) { ... 
  </code></pre>
  
  <p>I get the following error:</p>
  
  <blockquote>
    <p>"message": "Error: Script error for \"<a href="https://blah.com/absolute/path/to/myFile.js" rel="noreferrer">https://blah.com/absolute/path/to/myFile.js</a>\", needed by: /home/test_vds_jasmine/test/modules/myFile-spec4.js\nhttp://requirejs.org/docs/errors.html#scripterror\nat /home/node_modules/requirejs/require.js:168:17\n\nmakeError@/home/node_modules/requirejs/require.js:168:17\nnewContext/context.onScriptError@/home/node_modules/requirejs/require.js:1738:36\n"</p>
  </blockquote>
  
  <p>I've tried all manner of absolute path including with and without <code>https</code>, with and without the <code>.js</code> extension but am drawing a blank, the error message is not really helpful at all.</p>
  
  <p>Am I calling the absolute path in the wrong way? Has anyone had experience doing it this way?</p>
  
  <p>There's a valid reason why I have to call some files using absolute paths or I would just call all locally.</p>