title: Laravel Mix and SASS changing font directory
body: <p>I'm using Laravel 5.4 and Laravel Mix to output SASS files.</p>
  
  <p>In my font definitions I'm configuring them so that when the CSS is output it will point to files such as <code>public/assets/fnt/font-name/filename.ext</code> but the processor changes the output so that it will instead point to <code>public/fonts/filename.ext</code>. Is there a way to stop it from changing the output paths?</p>
  
  <p>It makes little sense to me that it would do something like this by default.</p>
  
  <p><strong>Edit</strong></p>
  
  <p>I've seen that the defaults they're using in Mix are the culprit:</p>
  
  <pre><code>module.exports.module = {
      rules: [
          // ...
          {
              test: /\.(woff2?|ttf|eot|svg|otf)$/,
              loader: 'file-loader',
              options: {
                  name: 'fonts/[name].[ext]?[hash]',
                  publicPath: '/'
              }
          }
      ]
  };
  </code></pre>
  
  <p>I've tried using <code>null-loader</code> instead of <code>file-loader</code> but instead it causes it to fail because it can't find the files in <code>node_modules</code> which is not where it should be looking in the first place.</p>
  
  <p>Removing the rule in question results in a flood of errors from trying to open and evaluate the font files in question:</p>
  
  <pre><code> error  in ./public/assets/fnt/fanfare-jf/fanfare-jf.ttf
  
  Module parse failed: DIRECTORY\public\assets\fnt\fanfare-jf\fanfare-jf.ttf Unexpected character '' (1:0)
  You may need an appropriate loader to handle this file type.
  (Source code omitted for this binary file)
  
   @ ./~/css-loader!./~/postcss-loader!./~/resolve-url-loader!./~/sass-loader?sourceMap&amp;precision=8!./resources/assets/sass/app.scss 6:2525-2590
   @ ./resources/assets/sass/app.scss
   @ multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss
  </code></pre>
  
  <p>I can at least add <code>emitFiles: false</code> to <code>options</code> to prevent it from making copies of the file, but the paths are still being altered.</p>