<h1 dir="auto">Feature request</h1>
<p dir="auto">Currently, only the following meta tags can be duplicate as per the next/head logic</p>
<div class="highlight highlight-source-js notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="var ALLOWED_DUPLICATES = ['article:tag', 'og:image', 'og:image:alt', 'og:image:width', 'og:image:height', 'og:image:type', 'og:image:secure_url', 'og:image:url'];"><pre class="notranslate"><span class="pl-k">var</span> <span class="pl-c1">ALLOWED_DUPLICATES</span> <span class="pl-c1">=</span> <span class="pl-kos">[</span><span class="pl-s">'article:tag'</span><span class="pl-kos">,</span> <span class="pl-s">'og:image'</span><span class="pl-kos">,</span> <span class="pl-s">'og:image:alt'</span><span class="pl-kos">,</span> <span class="pl-s">'og:image:width'</span><span class="pl-kos">,</span> <span class="pl-s">'og:image:height'</span><span class="pl-kos">,</span> <span class="pl-s">'og:image:type'</span><span class="pl-kos">,</span> <span class="pl-s">'og:image:secure_url'</span><span class="pl-kos">,</span> <span class="pl-s">'og:image:url'</span><span class="pl-kos">]</span><span class="pl-kos">;</span></pre></div>
<p dir="auto">So, it is not allowing me to render multiple og:see_also tag in meta using next/head.</p>
<p dir="auto">It would be great if these ALLOWED_DUPLICATES can be configured/override using <a class="issue-link js-issue-link notranslate" rel="noopener noreferrer nofollow" href="https://linear.app/vercel/issue/WEB-pack">web-pack</a> config/environment variable/nextconfig.</p>
<p dir="auto">Please suggest.</p>
<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/zeit/next.js/issues?q=is%3Aissue">issues</a> of this repository and believe that this is not a duplicate.</li>
</ul>
<p dir="auto">Looking at this repo — <a href="https://github.com/dargue3/nextjs-v5-object-context">https://github.com/dargue3/nextjs-v5-object-context</a> — this line of code (in <code class="notranslate">pages/index.js</code> used to return the names of all the functions belonging to a React component class before upgrading to <code class="notranslate">next v5</code>.</p>
<p dir="auto"><code class="notranslate">Object.getOwnPropertyNames(Object.getPrototypeOf(context))</code></p>
<h2 dir="auto">Expected Behavior</h2>
<p dir="auto">It should print out <code class="notranslate">["constructor", "onClick", "otherFunction", "render", "componentDidMount", "componentWillUnmount"]</code></p>
<h2 dir="auto">Current Behavior</h2>
<p dir="auto">It prints out <code class="notranslate">["constructor", "render", "componentWillReceiveProps", "componentWillUpdate"]</code></p>
<h2 dir="auto">Steps to reproduce</h2>
<p dir="auto">Fire up the repo I pasted above and load <code class="notranslate">localhost:3000</code>. While rendering on the server, this works as expected. You can see the custom functions belonging to the class printing to the terminal. On the client however, any custom functions that you add to the React component will not show up. If you'd like to verify that this is related to <code class="notranslate">v5</code>, downgrade to <code class="notranslate">v4.2.2</code> and you should see the print statement showing up correct on both server and client.</p>
<h2 dir="auto">Your Environment</h2>
<table role="table">
<thead>
<tr>
<th>Tech</th>
<th>Version</th>
</tr>
</thead>
<tbody>
<tr>
<td>next</td>
<td>v5.0.0</td>
</tr>
<tr>
<td>node</td>
<td>v8.6.0</td>
</tr>
</tbody>
</table>
<p dir="auto">I can't really speak to whether or not this is a bug (or how the version of Next is even related to this change in expected behavior). Could someone shed some light on what changes to <code class="notranslate">v5</code> could have caused this?</p>