<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">issues</a> of this repository and believe that this is not a duplicate.</li>
</ul>
<h2 dir="auto">Expected Behavior</h2>
<p dir="auto">Should not get deprecated warning when fresh install.</p>
<h2 dir="auto">Current Behavior</h2>
<p dir="auto">I am receiving deprecated warn:<br>
npm WARN deprecated node-uuid@1.4.8: Use uuid module instead</p>
<h2 dir="auto">Steps to Reproduce (for bugs)</h2>


<ol dir="auto">
<li>Go to this blog: <a href="https://zeit.co/blog/next4" rel="nofollow">https://zeit.co/blog/next4</a></li>
<li>Copy how to start: npm i next@latest react@latest react-dom@latest</li>
<li>Install and receive warning</li>
</ol>
<h2 dir="auto">Context</h2>
<p dir="auto">This warning didn't effect me but deprecated modules should be replaced.</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>4.1.4</td>
</tr>
<tr>
<td>node</td>
<td>8.9.0</td>
</tr>
<tr>
<td>OS</td>
<td>Linux Mint</td>
</tr>
<tr>
<td>browser</td>
<td>-</td>
</tr>
<tr>
<td>npm</td>
<td>5.5.1</td>
</tr>
</tbody>
</table>
<p dir="auto">In our application we have forms and want to prompt the user when they click the browser's Back or Forward buttons to notify them they will lose their data if they continue.</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">issues</a> of this repository and believe that this is not a duplicate.</li>
</ul>
<p dir="auto">Although it is similar in nature to <a href="https://github.com/zeit/next.js/issues/2236" data-hovercard-type="issue" data-hovercard-url="/vercel/next.js/issues/2236/hovercard">this issue</a> that has been marked as Exploration</p>
<h2 dir="auto">Expected Behavior</h2>
<p dir="auto">When user clicks back button, <code class="notranslate">window.onbeforeunload</code> function that is defined fires</p>
<h2 dir="auto">Current Behavior</h2>
<p dir="auto">Browser redirects user to previous page without triggering <code class="notranslate">window.onbeforeunload</code> action</p>
<h2 dir="auto">Special Notes</h2>
<p dir="auto">If I navigate directly to the page with the form by typing in the url, clicking the Back button <strong>correctly triggers</strong> <code class="notranslate">window.onbeforeunload</code>.</p>
<p dir="auto">If I navigate away from the page with the form by typing in the url for another page, the <code class="notranslate">window.onbeforeunload</code> event <strong>fires correctly</strong>.</p>
<p dir="auto">If I navigate to the page using links within the application, clicking the Back button <strong>does not trigger</strong> <code class="notranslate">window.onbeforeunload</code>.</p>
<p dir="auto">I <em>think</em> this has something to do with they way the browser is treating our application when the user navigates within the application using Next Links.  Instead of seeing each view as its own page and loading/unloading the page resources as the user navigates, it sees the entire application as just one page, thereby never loading/unloading resources and thus not triggering <code class="notranslate">window.onbeforeunload</code>.</p>