title: sass migrator problems - absolute paths and node_modules
body: <p>Sorry for overloading this post, but my questions are (somewhat) releated.</p>
  <p><strong>Absolute Paths</strong></p>
  <p>I'm migrating a themed bootstrap app that uses absolute paths for all imports  (intellij has path settings for js, but not for sass and it automatically changes imports to absolute paths when refactoring scss files).</p>
  <p>gulp-sass works fine with absolute paths.</p>
  <p>But sass-migrator can't find imported partials and errors out:
  Error: Could not find Sass file at 'src\theme\scss\variables-other'.</p>
  <p><strong>Question</strong> - Is there a path reference standard that I missed when I went to sass class and do I need to reset all my scss imports to use relative paths for imports?</p>
  <p><strong>Node Modules</strong>
  I'm currently using bootstrap 5.0.1 (and other modules that are not compliant with the new sass standards).</p>
  <p>It seems sass-migrator is attempting to &quot;migrate&quot; node modules, since I'm getting the above-mentioned path errors on bootstrap scss (and other node modules). I don't think this is kosher, since IMO the preferred way to remedy sass-compliance issues is to upgrade node mules directly (I'm in the process of updating bootstrap to 5.0.2, which is compliant).</p>
  <p><strong>Question</strong> - is there any flag to suppress migrating node modules? Or...is sass-migrator simply evaluating node modules so it can convert @import to @use?</p>