<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I have searched the <a href="https://github.com/mui-org/material-ui/issues?utf8=%E2%9C%93&amp;q=is%3Aissue+is%3Aopen+fontSize">issues</a> of this repository and believe that this is not a duplicate.</li>
</ul>
<h2 dir="auto">Expected Behavior</h2>
<p dir="auto">There shouldn't be a warning when importing an svg icon. Or if there should be, please update docs to reflect the correct way of rendering the SVG icon in our code. Currently the docs don't show if any fontSize attribute needs to be passed in.</p>
<h2 dir="auto">Current Behavior</h2>
<p dir="auto">When importing any svg icon, I get a warning saying:</p>
<p dir="auto"><code class="notranslate">Warning: Received true for a non-boolean attribute fontSize. If you want to write it to the DOM, pass a string instead: fontSize="true" or fontSize={value.toString()}.</code></p>
<p dir="auto">I don't set a <code class="notranslate">fontSize</code> attribute in the tag, like how the <a href="https://material-ui-next.com/demos/buttons/#icon-buttons" rel="nofollow">docs</a> show. This is part of what my code looks like:</p>
<div class="highlight highlight-source-js notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="import IconButton from 'material-ui-next/IconButton';
import DeleteIcon from 'material-ui-icons/Delete';

&lt;IconButton onClick={() =&gt; this.setState({ openDialog: true })}&gt;
 &lt;DeleteIcon /&gt;
&lt;/IconButton&gt;"><pre class="notranslate"><span class="pl-k">import</span> <span class="pl-v">IconButton</span> <span class="pl-k">from</span> <span class="pl-s">'material-ui-next/IconButton'</span><span class="pl-kos">;</span>
<span class="pl-k">import</span> <span class="pl-v">DeleteIcon</span> <span class="pl-k">from</span> <span class="pl-s">'material-ui-icons/Delete'</span><span class="pl-kos">;</span>

<span class="pl-c1">&lt;</span><span class="pl-ent">IconButton</span> <span class="pl-c1">onClick</span><span class="pl-c1">=</span><span class="pl-kos">{</span><span class="pl-kos">(</span><span class="pl-kos">)</span> <span class="pl-c1">=&gt;</span> <span class="pl-smi">this</span><span class="pl-kos">.</span><span class="pl-en">setState</span><span class="pl-kos">(</span><span class="pl-kos">{</span> <span class="pl-c1">openDialog</span>: <span class="pl-c1">true</span> <span class="pl-kos">}</span><span class="pl-kos">)</span><span class="pl-kos">}</span><span class="pl-c1">&gt;</span>
 <span class="pl-c1">&lt;</span><span class="pl-ent">DeleteIcon</span> <span class="pl-c1">/</span><span class="pl-c1">&gt;</span>
<span class="pl-c1">&lt;</span><span class="pl-c1">/</span><span class="pl-ent">IconButton</span><span class="pl-c1">&gt;</span></pre></div>
<h2 dir="auto">Steps to Reproduce (for bugs)</h2>
<ol dir="auto">
<li>Import any icon from <code class="notranslate">material-ui-icons</code> package.</li>
<li>Render it.</li>
<li>See warning in console.</li>
</ol>
<p dir="auto">NOTE: I tried this in codesandbox but did not see the warning. But here is the link regardless:<br>
<a href="https://codesandbox.io/s/qvo302329q" rel="nofollow">https://codesandbox.io/s/qvo302329q</a></p>
<h2 dir="auto">Context</h2>
<p dir="auto">I'm currently in the processing of migrating all Button components from Material-UI v.0.20 to v.1 in my application at work. Currently, the way I'm avoiding getting this warning is by actually not using SVG icons at all and using, for instance <code class="notranslate">&lt;Icon&gt;delete&lt;/Icon&gt;</code> instead.</p>
<h2 dir="auto">Your Environment</h2>
<table role="table">
<thead>
<tr>
<th>Tech</th>
<th>Version</th>
</tr>
</thead>
<tbody>
<tr>
<td>Material-UI</td>
<td>1.0.0-beta.31</td>
</tr>
<tr>
<td>material-ui-icons</td>
<td>1.0.0-beta.17</td>
</tr>
<tr>
<td>React</td>
<td>16.2.0</td>
</tr>
<tr>
<td>browser</td>
<td>Chrome v63.0.3239.84</td>
</tr>
</tbody>
</table>
<p dir="auto">Is there any possibility that as part of the release process, the ES2015 Components can be included as part of the published NPM artifacts?</p>
<p dir="auto">I'm working in a large React app, which is already doing transpiling and I don't want the babel transform-runtime as part of every component (babel-polyfill is already in the bundle). My primary motivation is reducing bundle size. In other libraries (<a href="https://github.com/ReactTraining/react-router/blob/master/package.json#L20">react-router</a> the ES2015 is built into an <code class="notranslate">es</code> folder, which assumes you're using a bundler that can understand these modules.</p>
<p dir="auto">This might be as easy as writing a copy task from <code class="notranslate">src</code> to <code class="notranslate">es</code> although I haven't look into your build process too deeply.</p>