I also talked to @jesstelford about hosting on Vercel and he said "Not all of it unfortunately - some of our dependencies wouldn't package correctly for deployment to serverless."

So I agree that this should be taken out of the docs unless it is possible. Maybe submit a PR @jacobdoran ?

fantastic! Thanks a ton

Hey Wes 👋,

I've added a few more questions and answers to the FAQ section of the Readme 🙂

Bumps next from 9.5.3 to 9.5.5. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vercel/next.js/releases">next's releases</a>.</em></p> <blockquote> <h2>v9.5.5</h2> <h3>Core Changes</h3> <ul> <li>Update to have default locale matched on root: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17669">#17669</a></li> <li>Handle css-loader file resolving change: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17724">#17724</a></li> <li>Update to generate auto static pages with all locales: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17730">#17730</a></li> </ul> <h3>Example Changes</h3> <ul> <li>Fix with-apollo example : <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17686">#17686</a></li> <li>Fix with-msw example: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17695">#17695</a></li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/HaNdTriX">@HaNdTriX</a>, and <a href="https://github.com/jensmeindertsma">@jensmeindertsma</a> for helping!</p> <h2>v9.5.5-canary.1</h2> <h3>Core Changes</h3> <ul> <li>Update to generate auto static pages with all locales: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17730">#17730</a></li> </ul> <h2>v9.5.5-canary.0</h2> <h3>Core Changes</h3> <ul> <li>Add initial changes for i18n support: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17370">#17370</a></li> <li>Update to have default locale matched on root: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17669">#17669</a></li> <li>Handle css-loader file resolving change: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17724">#17724</a></li> </ul> <h3>Example Changes</h3> <ul> <li>Fix with-apollo example : <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17686">#17686</a></li> <li>Fix with-msw example: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17695">#17695</a></li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/HaNdTriX">@HaNdTriX</a> and <a href="https://github.com/jensmeindertsma">@jensmeindertsma</a> for helping!</p> <h2>v9.5.4</h2> <p><strong>This upgrade is <em>completely backwards compatible and recommended for all users on versions below 9.5.4.</em> For future security related communications of our OSS projects, please <a href="https://vercel.com/security">join this mailing list</a>.</strong></p> <p>A security team from one of our partners noticed an issue in Next.js that allowed for open redirects to occur.</p> <p>Specially encoded paths could be used with the trailing slash redirect to allow an open redirect to occur to an external site.</p> <p>In general, this redirect does not directly harm users although can allow for phishing attacks by redirecting to an attackers domain from a trusted domain.</p> <p>We recommend upgrading to the latest version of Next.js to improve the overall security of your application.</p> <h2>How to Upgrade</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vercel/next.js/commit/e334c4ece8c97ea14fcd974b4510e580a11bcf84"><code>e334c4e</code></a> v9.5.5</li> <li><a href="https://github.com/vercel/next.js/commit/5e857097869c2d0d670623b4f9d85c4f4f349f32"><code>5e85709</code></a> v9.5.5-canary.1</li> <li><a href="https://github.com/vercel/next.js/commit/2170dfd1e3826c2f3ece4ccf06013f1ce48fb84b"><code>2170dfd</code></a> Update to generate auto static pages with all locales (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17730">#17730</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/62b9183e89d8aed5723830b1358c743f90ddfedc"><code>62b9183</code></a> v9.5.5-canary.0</li> <li><a href="https://github.com/vercel/next.js/commit/ec2ffb42444c5c46434df7c14fcdcc9541524ede"><code>ec2ffb4</code></a> Handle css-loader file resolving change (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17724">#17724</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/c021662d1e7bbdabd2b5cb9bea28ea05c11de7e0"><code>c021662</code></a> Fix with-msw example (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17695">#17695</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/bbc1a21c749c423e842586ab116889c9f9c7024e"><code>bbc1a21</code></a> Update to have default locale matched on root (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17669">#17669</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/a79bcfb73ad79a9898ee30580fab45379e7840bf"><code>a79bcfb</code></a> Fix with-apollo example (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17686">#17686</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/b2d1d87e7feed5535a05ec99d7558934dcbc82a5"><code>b2d1d87</code></a> Add initial changes for i18n support (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17370">#17370</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/658810815035e55a7031f27c5a6f3c01baa31ccf"><code>6588108</code></a> v9.5.4</li> <li>Additional commits viewable in <a href="https://github.com/vercel/next.js/compare/v9.5.3...v9.5.5">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps next from 9.5.3 to 9.5.4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vercel/next.js/releases">next's releases</a>.</em></p> <blockquote> <h2>v9.5.4</h2> <p><strong>This upgrade is <em>completely backwards compatible and recommended for all users on versions below 9.5.4.</em> For future security related communications of our OSS projects, please <a href="https://vercel.com/security">join this mailing list</a>.</strong></p> <p>A security team from one of our partners noticed an issue in Next.js that allowed for open redirects to occur.</p> <p>Specially encoded paths could be used with the trailing slash redirect to allow an open redirect to occur to an external site.</p> <p>In general, this redirect does not directly harm users although can allow for phishing attacks by redirecting to an attackers domain from a trusted domain.</p> <p>We recommend upgrading to the latest version of Next.js to improve the overall security of your application.</p> <h2>How to Upgrade</h2> <ul> <li>We have released patch versions for both the stable and canary channels of Next.js.</li> <li>To upgrade run <code>npm install next@latest --save</code></li> </ul> <h2>Impact</h2> <ul> <li><strong>Affected</strong>: Users of Next.js between 9.5.0 and 9.5.3</li> <li><strong>Not affected</strong>: Deployments on Vercel (<a href="https://vercel.com">https://vercel.com</a>) are not affected</li> <li><strong>Not affected</strong>: Deployments using <code>next export</code></li> </ul> <p>We recommend everyone to upgrade regardless of whether you can reproduce the issue or not.</p> <h3>How to Assess Impact</h3> <p>If you think users could have been affected, you can filter logs of affected sites by <code>%2F</code> with a 308 response.</p> <h2>What is Being Done</h2> <p>As Next.js has grown in popularity, it has received the attention of security teams and auditors. We are thankful to those that reached out for their investigation and discovery of the original bug and subsequent responsible disclosure.</p> <p>We've landed a patch that ensures encoding is handled properly for these types of redirects so the open redirect can no longer occur.</p> <p>Regression tests for this attack were added to the <a href="https://github.com/vercel/next.js/blob/canary/test/integration/production/test/security.js">security</a> integration test suite.</p> <ul> <li>We have notified known Next.js users in advance of this publication.</li> <li>A public CVE was released.</li> <li>If you want to stay on top of our security related news impacting Next.js or other Vercel projects, please <a href="https://zeit.co/security">join this mailing list</a>.</li> <li>We encourage responsible disclosure of future issues. Please email us at <strong><a href="https://github.com/vercel/next.js/blob/HEAD/mailto:[email protected]">[email protected]</a>.</strong> We are actively monitoring this mailbox.</li> </ul> <hr /> <h3>Core Changes</h3> <ul> <li>Make the image post-processor ignore SVG images: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16732">#16732</a></li> <li>Only update lookups for dev overlay if mounted: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16776">#16776</a></li> <li>Ensure interpolating dynamic href values works correctly: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16774">#16774</a></li> <li>Add automatic reloading when editing GS(S)P methods: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16744">#16744</a></li> <li>Update to show build indicator while re-fetching GS(S)P data in dev: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16789">#16789</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vercel/next.js/commit/658810815035e55a7031f27c5a6f3c01baa31ccf"><code>6588108</code></a> v9.5.4</li> <li><a href="https://github.com/vercel/next.js/commit/7108567b06bba6586296fe2bb7e6957410147c8f"><code>7108567</code></a> v9.5.4-canary.25</li> <li><a href="https://github.com/vercel/next.js/commit/5d79a8c0c4928d718e71707cf3305a51c9a5adc4"><code>5d79a8c</code></a> Update workflow step to restore cache (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17656">#17656</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/4c38e3ed8ec402862ea6b42b02297f8c28ab9b53"><code>4c38e3e</code></a> fix typo (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17653">#17653</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/241f38eaa8aa2199360dc28d76759c936f16cdd6"><code>241f38e</code></a> v9.5.4-canary.24</li> <li><a href="https://github.com/vercel/next.js/commit/7dec91175cb69f773fa623417e0e497acc606dc2"><code>7dec911</code></a> change anonymous functions to named in docs examples (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17510">#17510</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/1659e4da617db3effc63f1dd919ce628eb59e135"><code>1659e4d</code></a> Update migrating from Gatsby docs. (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17636">#17636</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/06a8b1ad67b07ffae68cba7863ba31b53fc8b95d"><code>06a8b1a</code></a> Add docs on how to migrate from Gatsby. (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17491">#17491</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/04234cc312b7b780a52ba6f9f63490d5699da4a3"><code>04234cc</code></a> Update to use hasNextSupport for custom-routes in next export check (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17630">#17630</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/742f5d9a46ed5244409ea0389d019fce375f28e3"><code>742f5d9</code></a> test(create-next-app): increase coverage (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17507">#17507</a>)</li> <li>Additional commits viewable in <a href="https://github.com/vercel/next.js/compare/v9.5.3...v9.5.4">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps next from 9.5.3 to 9.5.4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vercel/next.js/releases">next's releases</a>.</em></p> <blockquote> <h2>v9.5.4</h2> <p><strong>This upgrade is <em>completely backwards compatible and recommended for all users on versions below 9.5.4.</em> For future security related communications of our OSS projects, please <a href="https://vercel.com/security">join this mailing list</a>.</strong></p> <p>A security team from one of our partners noticed an issue in Next.js that allowed for open redirects to occur.</p> <p>Specially encoded paths could be used with the trailing slash redirect to allow an open redirect to occur to an external site.</p> <p>In general, this redirect does not directly harm users although can allow for phishing attacks by redirecting to an attackers domain from a trusted domain.</p> <p>We recommend upgrading to the latest version of Next.js to improve the overall security of your application.</p> <h2>How to Upgrade</h2> <ul> <li>We have released patch versions for both the stable and canary channels of Next.js.</li> <li>To upgrade run <code>npm install next@latest --save</code></li> </ul> <h2>Impact</h2> <ul> <li><strong>Affected</strong>: Users of Next.js between 9.5.0 and 9.5.3</li> <li><strong>Not affected</strong>: Deployments on Vercel (<a href="https://vercel.com">https://vercel.com</a>) are not affected</li> <li><strong>Not affected</strong>: Deployments using <code>next export</code></li> </ul> <p>We recommend everyone to upgrade regardless of whether you can reproduce the issue or not.</p> <h3>How to Assess Impact</h3> <p>If you think users could have been affected, you can filter logs of affected sites by <code>%2F</code> with a 308 response.</p> <h2>What is Being Done</h2> <p>As Next.js has grown in popularity, it has received the attention of security teams and auditors. We are thankful to those that reached out for their investigation and discovery of the original bug and subsequent responsible disclosure.</p> <p>We've landed a patch that ensures encoding is handled properly for these types of redirects so the open redirect can no longer occur.</p> <p>Regression tests for this attack were added to the <a href="https://github.com/vercel/next.js/blob/canary/test/integration/production/test/security.js">security</a> integration test suite.</p> <ul> <li>We have notified known Next.js users in advance of this publication.</li> <li>A public CVE was released.</li> <li>If you want to stay on top of our security related news impacting Next.js or other Vercel projects, please <a href="https://zeit.co/security">join this mailing list</a>.</li> <li>We encourage responsible disclosure of future issues. Please email us at <strong><a href="https://github.com/vercel/next.js/blob/HEAD/mailto:[email protected]">[email protected]</a>.</strong> We are actively monitoring this mailbox.</li> </ul> <hr /> <h3>Core Changes</h3> <ul> <li>Make the image post-processor ignore SVG images: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16732">#16732</a></li> <li>Only update lookups for dev overlay if mounted: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16776">#16776</a></li> <li>Ensure interpolating dynamic href values works correctly: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16774">#16774</a></li> <li>Add automatic reloading when editing GS(S)P methods: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16744">#16744</a></li> <li>Update to show build indicator while re-fetching GS(S)P data in dev: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16789">#16789</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vercel/next.js/commit/658810815035e55a7031f27c5a6f3c01baa31ccf"><code>6588108</code></a> v9.5.4</li> <li><a href="https://github.com/vercel/next.js/commit/7108567b06bba6586296fe2bb7e6957410147c8f"><code>7108567</code></a> v9.5.4-canary.25</li> <li><a href="https://github.com/vercel/next.js/commit/5d79a8c0c4928d718e71707cf3305a51c9a5adc4"><code>5d79a8c</code></a> Update workflow step to restore cache (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17656">#17656</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/4c38e3ed8ec402862ea6b42b02297f8c28ab9b53"><code>4c38e3e</code></a> fix typo (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17653">#17653</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/241f38eaa8aa2199360dc28d76759c936f16cdd6"><code>241f38e</code></a> v9.5.4-canary.24</li> <li><a href="https://github.com/vercel/next.js/commit/7dec91175cb69f773fa623417e0e497acc606dc2"><code>7dec911</code></a> change anonymous functions to named in docs examples (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17510">#17510</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/1659e4da617db3effc63f1dd919ce628eb59e135"><code>1659e4d</code></a> Update migrating from Gatsby docs. (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17636">#17636</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/06a8b1ad67b07ffae68cba7863ba31b53fc8b95d"><code>06a8b1a</code></a> Add docs on how to migrate from Gatsby. (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17491">#17491</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/04234cc312b7b780a52ba6f9f63490d5699da4a3"><code>04234cc</code></a> Update to use hasNextSupport for custom-routes in next export check (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17630">#17630</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/742f5d9a46ed5244409ea0389d019fce375f28e3"><code>742f5d9</code></a> test(create-next-app): increase coverage (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17507">#17507</a>)</li> <li>Additional commits viewable in <a href="https://github.com/vercel/next.js/compare/v9.5.3...v9.5.4">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps lodash from 4.17.15 to 4.17.20. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/ded9bc66583ed0b4e3b7dc906206d40757b4a90a"><code>ded9bc6</code></a> Bump to v4.17.20.</li> <li><a href="https://github.com/lodash/lodash/commit/63150ef7645ac07961b63a86490f419f356429aa"><code>63150ef</code></a> Documentation fixes.</li> <li><a href="https://github.com/lodash/lodash/commit/00f0f62a979d2f5fa0287c06eae70cf9a62d8794"><code>00f0f62</code></a> test.js: Remove trailing comma.</li> <li><a href="https://github.com/lodash/lodash/commit/846e434c7a5b5692c55ebf5715ed677b70a32389"><code>846e434</code></a> Temporarily use a custom fork of <code>lodash-cli</code>.</li> <li><a href="https://github.com/lodash/lodash/commit/5d046f39cbd27f573914768e3b36eeefcc4f1229"><code>5d046f3</code></a> Re-enable Travis tests on <code>4.17</code> branch.</li> <li><a href="https://github.com/lodash/lodash/commit/aa816b36d402a1ad9385142ce7188f17dae514fd"><code>aa816b3</code></a> Remove <code>/npm-package</code>.</li> <li><a href="https://github.com/lodash/lodash/commit/d7fbc52ee0466a6d248f047b5d5c3e6d1e099056"><code>d7fbc52</code></a> Bump to v4.17.19</li> <li><a href="https://github.com/lodash/lodash/commit/2e1c0f22f425e9c013815b2cd7c2ebd51f49a8d6"><code>2e1c0f2</code></a> Add npm-package</li> <li><a href="https://github.com/lodash/lodash/commit/1b6c282299f4e0271f932b466c67f0f822aa308e"><code>1b6c282</code></a> Bump to v4.17.18</li> <li><a href="https://github.com/lodash/lodash/commit/a370ac81408de2da77a82b3c4b61a01a3b9c2fac"><code>a370ac8</code></a> Bump to v4.17.17</li> <li>Additional commits viewable in <a href="https://github.com/lodash/lodash/compare/4.17.15...4.17.20">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~bnjmnt4n">bnjmnt4n</a>, a new releaser for lodash since your current version.</p> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps lodash from 4.17.15 to 4.17.20. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/ded9bc66583ed0b4e3b7dc906206d40757b4a90a"><code>ded9bc6</code></a> Bump to v4.17.20.</li> <li><a href="https://github.com/lodash/lodash/commit/63150ef7645ac07961b63a86490f419f356429aa"><code>63150ef</code></a> Documentation fixes.</li> <li><a href="https://github.com/lodash/lodash/commit/00f0f62a979d2f5fa0287c06eae70cf9a62d8794"><code>00f0f62</code></a> test.js: Remove trailing comma.</li> <li><a href="https://github.com/lodash/lodash/commit/846e434c7a5b5692c55ebf5715ed677b70a32389"><code>846e434</code></a> Temporarily use a custom fork of <code>lodash-cli</code>.</li> <li><a href="https://github.com/lodash/lodash/commit/5d046f39cbd27f573914768e3b36eeefcc4f1229"><code>5d046f3</code></a> Re-enable Travis tests on <code>4.17</code> branch.</li> <li><a href="https://github.com/lodash/lodash/commit/aa816b36d402a1ad9385142ce7188f17dae514fd"><code>aa816b3</code></a> Remove <code>/npm-package</code>.</li> <li><a href="https://github.com/lodash/lodash/commit/d7fbc52ee0466a6d248f047b5d5c3e6d1e099056"><code>d7fbc52</code></a> Bump to v4.17.19</li> <li><a href="https://github.com/lodash/lodash/commit/2e1c0f22f425e9c013815b2cd7c2ebd51f49a8d6"><code>2e1c0f2</code></a> Add npm-package</li> <li><a href="https://github.com/lodash/lodash/commit/1b6c282299f4e0271f932b466c67f0f822aa308e"><code>1b6c282</code></a> Bump to v4.17.18</li> <li><a href="https://github.com/lodash/lodash/commit/a370ac81408de2da77a82b3c4b61a01a3b9c2fac"><code>a370ac8</code></a> Bump to v4.17.17</li> <li>Additional commits viewable in <a href="https://github.com/lodash/lodash/compare/4.17.15...4.17.20">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~bnjmnt4n">bnjmnt4n</a>, a new releaser for lodash since your current version.</p> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps object-path from 0.11.4 to 0.11.5. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/mariocasciaro/object-path/commits">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps next from 9.5.3 to 9.5.4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vercel/next.js/releases">next's releases</a>.</em></p> <blockquote> <h2>v9.5.4</h2> <p><strong>This upgrade is <em>completely backwards compatible and recommended for all users on versions below 9.5.4.</em> For future security related communications of our OSS projects, please <a href="https://vercel.com/security">join this mailing list</a>.</strong></p> <p>A security team from one of our partners noticed an issue in Next.js that allowed for open redirects to occur.</p> <p>Specially encoded paths could be used with the trailing slash redirect to allow an open redirect to occur to an external site.</p> <p>In general, this redirect does not directly harm users although can allow for phishing attacks by redirecting to an attackers domain from a trusted domain.</p> <p>We recommend upgrading to the latest version of Next.js to improve the overall security of your application.</p> <h2>How to Upgrade</h2> <ul> <li>We have released patch versions for both the stable and canary channels of Next.js.</li> <li>To upgrade run <code>npm install next@latest --save</code></li> </ul> <h2>Impact</h2> <ul> <li><strong>Affected</strong>: Users of Next.js between 9.5.0 and 9.5.3</li> <li><strong>Not affected</strong>: Deployments on Vercel (<a href="https://vercel.com">https://vercel.com</a>) are not affected</li> <li><strong>Not affected</strong>: Deployments using <code>next export</code></li> </ul> <p>We recommend everyone to upgrade regardless of whether you can reproduce the issue or not.</p> <h3>How to Assess Impact</h3> <p>If you think users could have been affected, you can filter logs of affected sites by <code>%2F</code> with a 308 response.</p> <h2>What is Being Done</h2> <p>As Next.js has grown in popularity, it has received the attention of security teams and auditors. We are thankful to those that reached out for their investigation and discovery of the original bug and subsequent responsible disclosure.</p> <p>We've landed a patch that ensures encoding is handled properly for these types of redirects so the open redirect can no longer occur.</p> <p>Regression tests for this attack were added to the <a href="https://github.com/vercel/next.js/blob/canary/test/integration/production/test/security.js">security</a> integration test suite.</p> <ul> <li>We have notified known Next.js users in advance of this publication.</li> <li>A public CVE was released.</li> <li>If you want to stay on top of our security related news impacting Next.js or other Vercel projects, please <a href="https://zeit.co/security">join this mailing list</a>.</li> <li>We encourage responsible disclosure of future issues. Please email us at <strong><a href="https://github.com/vercel/next.js/blob/HEAD/mailto:[email protected]">[email protected]</a>.</strong> We are actively monitoring this mailbox.</li> </ul> <hr /> <h3>Core Changes</h3> <ul> <li>Make the image post-processor ignore SVG images: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16732">#16732</a></li> <li>Only update lookups for dev overlay if mounted: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16776">#16776</a></li> <li>Ensure interpolating dynamic href values works correctly: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16774">#16774</a></li> <li>Add automatic reloading when editing GS(S)P methods: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16744">#16744</a></li> <li>Update to show build indicator while re-fetching GS(S)P data in dev: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16789">#16789</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vercel/next.js/commit/658810815035e55a7031f27c5a6f3c01baa31ccf"><code>6588108</code></a> v9.5.4</li> <li><a href="https://github.com/vercel/next.js/commit/7108567b06bba6586296fe2bb7e6957410147c8f"><code>7108567</code></a> v9.5.4-canary.25</li> <li><a href="https://github.com/vercel/next.js/commit/5d79a8c0c4928d718e71707cf3305a51c9a5adc4"><code>5d79a8c</code></a> Update workflow step to restore cache (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17656">#17656</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/4c38e3ed8ec402862ea6b42b02297f8c28ab9b53"><code>4c38e3e</code></a> fix typo (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17653">#17653</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/241f38eaa8aa2199360dc28d76759c936f16cdd6"><code>241f38e</code></a> v9.5.4-canary.24</li> <li><a href="https://github.com/vercel/next.js/commit/7dec91175cb69f773fa623417e0e497acc606dc2"><code>7dec911</code></a> change anonymous functions to named in docs examples (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17510">#17510</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/1659e4da617db3effc63f1dd919ce628eb59e135"><code>1659e4d</code></a> Update migrating from Gatsby docs. (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17636">#17636</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/06a8b1ad67b07ffae68cba7863ba31b53fc8b95d"><code>06a8b1a</code></a> Add docs on how to migrate from Gatsby. (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17491">#17491</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/04234cc312b7b780a52ba6f9f63490d5699da4a3"><code>04234cc</code></a> Update to use hasNextSupport for custom-routes in next export check (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17630">#17630</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/742f5d9a46ed5244409ea0389d019fce375f28e3"><code>742f5d9</code></a> test(create-next-app): increase coverage (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17507">#17507</a>)</li> <li>Additional commits viewable in <a href="https://github.com/vercel/next.js/compare/v9.5.3...v9.5.4">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps next from 9.5.3 to 9.5.4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vercel/next.js/releases">next's releases</a>.</em></p> <blockquote> <h2>v9.5.4</h2> <p><strong>This upgrade is <em>completely backwards compatible and recommended for all users on versions below 9.5.4.</em> For future security related communications of our OSS projects, please <a href="https://vercel.com/security">join this mailing list</a>.</strong></p> <p>A security team from one of our partners noticed an issue in Next.js that allowed for open redirects to occur.</p> <p>Specially encoded paths could be used with the trailing slash redirect to allow an open redirect to occur to an external site.</p> <p>In general, this redirect does not directly harm users although can allow for phishing attacks by redirecting to an attackers domain from a trusted domain.</p> <p>We recommend upgrading to the latest version of Next.js to improve the overall security of your application.</p> <h2>How to Upgrade</h2> <ul> <li>We have released patch versions for both the stable and canary channels of Next.js.</li> <li>To upgrade run <code>npm install next@latest --save</code></li> </ul> <h2>Impact</h2> <ul> <li><strong>Affected</strong>: Users of Next.js between 9.5.0 and 9.5.3</li> <li><strong>Not affected</strong>: Deployments on Vercel (<a href="https://vercel.com">https://vercel.com</a>) are not affected</li> <li><strong>Not affected</strong>: Deployments using <code>next export</code></li> </ul> <p>We recommend everyone to upgrade regardless of whether you can reproduce the issue or not.</p> <h3>How to Assess Impact</h3> <p>If you think users could have been affected, you can filter logs of affected sites by <code>%2F</code> with a 308 response.</p> <h2>What is Being Done</h2> <p>As Next.js has grown in popularity, it has received the attention of security teams and auditors. We are thankful to those that reached out for their investigation and discovery of the original bug and subsequent responsible disclosure.</p> <p>We've landed a patch that ensures encoding is handled properly for these types of redirects so the open redirect can no longer occur.</p> <p>Regression tests for this attack were added to the <a href="https://github.com/vercel/next.js/blob/canary/test/integration/production/test/security.js">security</a> integration test suite.</p> <ul> <li>We have notified known Next.js users in advance of this publication.</li> <li>A public CVE was released.</li> <li>If you want to stay on top of our security related news impacting Next.js or other Vercel projects, please <a href="https://zeit.co/security">join this mailing list</a>.</li> <li>We encourage responsible disclosure of future issues. Please email us at <strong><a href="https://github.com/vercel/next.js/blob/HEAD/mailto:[email protected]">[email protected]</a>.</strong> We are actively monitoring this mailbox.</li> </ul> <hr /> <h3>Core Changes</h3> <ul> <li>Make the image post-processor ignore SVG images: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16732">#16732</a></li> <li>Only update lookups for dev overlay if mounted: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16776">#16776</a></li> <li>Ensure interpolating dynamic href values works correctly: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16774">#16774</a></li> <li>Add automatic reloading when editing GS(S)P methods: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16744">#16744</a></li> <li>Update to show build indicator while re-fetching GS(S)P data in dev: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/16789">#16789</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vercel/next.js/commit/658810815035e55a7031f27c5a6f3c01baa31ccf"><code>6588108</code></a> v9.5.4</li> <li><a href="https://github.com/vercel/next.js/commit/7108567b06bba6586296fe2bb7e6957410147c8f"><code>7108567</code></a> v9.5.4-canary.25</li> <li><a href="https://github.com/vercel/next.js/commit/5d79a8c0c4928d718e71707cf3305a51c9a5adc4"><code>5d79a8c</code></a> Update workflow step to restore cache (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17656">#17656</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/4c38e3ed8ec402862ea6b42b02297f8c28ab9b53"><code>4c38e3e</code></a> fix typo (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17653">#17653</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/241f38eaa8aa2199360dc28d76759c936f16cdd6"><code>241f38e</code></a> v9.5.4-canary.24</li> <li><a href="https://github.com/vercel/next.js/commit/7dec91175cb69f773fa623417e0e497acc606dc2"><code>7dec911</code></a> change anonymous functions to named in docs examples (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17510">#17510</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/1659e4da617db3effc63f1dd919ce628eb59e135"><code>1659e4d</code></a> Update migrating from Gatsby docs. (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17636">#17636</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/06a8b1ad67b07ffae68cba7863ba31b53fc8b95d"><code>06a8b1a</code></a> Add docs on how to migrate from Gatsby. (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17491">#17491</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/04234cc312b7b780a52ba6f9f63490d5699da4a3"><code>04234cc</code></a> Update to use hasNextSupport for custom-routes in next export check (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17630">#17630</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/742f5d9a46ed5244409ea0389d019fce375f28e3"><code>742f5d9</code></a> test(create-next-app): increase coverage (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/17507">#17507</a>)</li> <li>Additional commits viewable in <a href="https://github.com/vercel/next.js/compare/v9.5.3...v9.5.4">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps lodash from 4.17.15 to 4.17.20. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/ded9bc66583ed0b4e3b7dc906206d40757b4a90a"><code>ded9bc6</code></a> Bump to v4.17.20.</li> <li><a href="https://github.com/lodash/lodash/commit/63150ef7645ac07961b63a86490f419f356429aa"><code>63150ef</code></a> Documentation fixes.</li> <li><a href="https://github.com/lodash/lodash/commit/00f0f62a979d2f5fa0287c06eae70cf9a62d8794"><code>00f0f62</code></a> test.js: Remove trailing comma.</li> <li><a href="https://github.com/lodash/lodash/commit/846e434c7a5b5692c55ebf5715ed677b70a32389"><code>846e434</code></a> Temporarily use a custom fork of <code>lodash-cli</code>.</li> <li><a href="https://github.com/lodash/lodash/commit/5d046f39cbd27f573914768e3b36eeefcc4f1229"><code>5d046f3</code></a> Re-enable Travis tests on <code>4.17</code> branch.</li> <li><a href="https://github.com/lodash/lodash/commit/aa816b36d402a1ad9385142ce7188f17dae514fd"><code>aa816b3</code></a> Remove <code>/npm-package</code>.</li> <li><a href="https://github.com/lodash/lodash/commit/d7fbc52ee0466a6d248f047b5d5c3e6d1e099056"><code>d7fbc52</code></a> Bump to v4.17.19</li> <li><a href="https://github.com/lodash/lodash/commit/2e1c0f22f425e9c013815b2cd7c2ebd51f49a8d6"><code>2e1c0f2</code></a> Add npm-package</li> <li><a href="https://github.com/lodash/lodash/commit/1b6c282299f4e0271f932b466c67f0f822aa308e"><code>1b6c282</code></a> Bump to v4.17.18</li> <li><a href="https://github.com/lodash/lodash/commit/a370ac81408de2da77a82b3c4b61a01a3b9c2fac"><code>a370ac8</code></a> Bump to v4.17.17</li> <li>Additional commits viewable in <a href="https://github.com/lodash/lodash/compare/4.17.15...4.17.20">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~bnjmnt4n">bnjmnt4n</a>, a new releaser for lodash since your current version.</p> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Got this too, make sure you export keystone from your index.js:

module.exports.keystone = keystone;

thank you!

Description

This updates the show notes edit url to redirect to the edit page on GitHub.

Problem/Solution

The link for the Edit Show Notes had a stale URL, this PR updates it to have the /shows in the path to fix it.

Steps to reproduce

Go to the Vercel deploy preview (https://syntax-git-fix-show-notes-url.wesbos.vercel.app) and click on Edit Show Notes under an episode show, you should be redirected to the edit page on GitHub instead of a 404.

Screencast

Context

https://twitter.com/syntaxfm/status/1319040265882116099

Still waiting on the folks at Apollo, but they are working on a fix or a solution for us.

Just for reference the issue is this:

We have 4 items per page.

When I visit a page, those 4 items are slotted into the cache.

When you add or remove an item, that cache needs to be updated.

Now we can control the cache in two ways:

1. Each query has it's own cache:

allItems(limit:4, offset: 4)

2. All items in a single cache, this removes the limit and cache variables from the query and we manage the field ourselves with a typePolicy.

Both have an issue. Let's say we add an item:

1. With method 1, all the items need to be evicted or re-fetched

2. There is currently no way to evict all items of a type. You can either delete 1 item from the cache, or blow the entire apollo cache away.

3. With refetching queries, I'd need to supply an array of queries that need to be re-fetvched. But when an item is added, we don't know how many queries are in the cache, how many pages there are, what the offsets are etc.... And we could possibly have hundreds of pages in the cache

4. With method 2, we can put all the items in one cache, so this means when we delete or add an item, we simply just add or remove it from the cache in the slot it needs. Great! This actually works well, BUT this means we have to use a type policy for allItems, and then we aren't able to use the allItems query for anything else on the page. In our case we need it for search. So if I search for "shoes", the cache is now filled with items that match the search query and all our pagination data is gone.

So that's where we are at right now... I'm very open to having approached this absolutely wrong because I can't believe I'm the only one with this issue, but from talking to @kkemple it seems we are doing it right!

So that is where we are at! Huge thanks for the apollo folks for helping with this.

Once this is finished we are GOOD TO GOOOOOO

@JunaidQadirB is this your student? Seems they have an app and everything. Not allowed to use someone's likeness to promote something like this

dont use our photos you knob

Dear Wes,

Thank you very much for this awesome course, I'm learning a lot from it! I understand the video/code might not be updated in order to keep things consistent, but I'd still like to propose this small change. In the current version of the source code the order of items in the 'people' array is the same as that of the output of exercise 7, thus the difference is not quite visible, in my opinion. Maybe it would make sense even without a video update?

Thank you for your consideration!

Best, Lilla Pulay

<!-- 👋👋👋👋👋👋👋👋👋👋👋👋👋👋 👋👋👋Hello Friend!👋👋👋👋 👋👋👋👋👋👋👋👋👋👋👋👋👋👋

Thanks for Submitting a pull request. Before you hit that button please make sure:

These files are meant to be 1:1 copies of what is done in the video. If you found a better / different way to do things or fixed a small bug, that is great great, but I will be keeping them the same as the videos to avoid confusing.

Spelling mistakes / CSS updates / other clarifications are welcome as long as they don't change what is shown in the videos.

I encourage you to blog about your implementation and add the link to this repo - that way everyone can benefit from it.

-->

good idea! I like it. Thanks for this :)

thank you!

I noticed that on lesson 33 (SEO) the path for the image of the slicemaster was missing the fluid property before accessing the src.

Also, I added the optional chaining to help prevent issues when the image is missing. As suggested in the Pizza.js template

thanks!

This jsx-a11y/label-has-associated-control error can be fixed by asserting that it either respects both (control nested inside label), htmlFor (with the htmlFor attribute) or either one of them.

https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/issues/632

Thanks everyone -super helpful. I've begun work on typescript support for this package.

You can check it out on this branch: https://github.com/wesbos/eslint-config-wesbos/tree/typescript

Still early WIP, so no docs but will update when its ready to try out

The move / rename commands in the sidebar are super handy because they update import paths in JS and TS projects.

These commands aren't part of the command palette and make me break my workflow / reach for the mouse.

Could we get these commands in the command palette too? I currently use the "file utils" extension to do this, but they don't seem to update import paths like VS Code rename/move commands do.

In TS and JS files, if you rename or move a file, VS Code will update your imports that depend on that file.

This works if you:

1. Drag the file in the sidebar
2. right click, rename file

It doesn't seem to prompt you if you use the command palette file: rename or file: move.

Would we be able to see what commands VS Code is running for the sidebar UI and run them with rename and move commands?

Here is a 1 min video detailing the issue: https://wes.io/xQuA70rD

• VSCode Version: 1.50.0
• OS Version: Mac 10.15.6

There must be something in the API that brings back a thumbnail for when a video is tweeted

There must be something in the API that brings back a thumbnail for when a video is tweeted

Hey! Thanskf or offering to help.

Some easy wins: https://github.com/wesbos/wesbos/search?q=%3Ch3%3E

Some of the blog posts were written in HTML, converting them to markdown would be great.

<!--

Please read the requirements corresponding to your pull request before you submit. You can delete this before you PR

What's a Uses Page?

A /uses page lists a developer's setup, gear, software, and configs (what they use). It's a great reference for those looking to add to their library of tools or reconfigure ones they already use.

What Should I Include?

Include the hardware you use, such as your computer and other related equipment. Include your preferred terminal, text editors, tools, frameworks, and other related software you use. If you can, include configurations for software (such as fonts and themes). The more you have on your /uses page, the more interesting it'll be to those who view it - just keep it on-topic!

Adding Yourself

• Ensure you are linking to a /uses page, not just your website
• Ensure your data is formatted like other entries
• Do not add yourself to the end of the array (add yourself somewhere random instead)
• Ensure this PR has a title in the following format
  • ✅ Add Your Name
  • ✅ Add @twitterusername
  • ❌ Add myself
  • ❌ Adding myself!
  • ❌ Add Your Name @twitter @github

Code Modifications

• Ensure the code submitted is formatted similarly to existing code
• Ensure variable, method, function, and component names are clear and concise

Final Requirements

• You've read and understood the above

Add your name to verify: Rohit Gohri

-->

Remove dummy entry that got merged in #796 accidentally. The build will pass once a bot token has been added to the project as mentioned in https://github.com/wesbos/awesome-uses/pull/796#issuecomment-707514080.

<!--

Please read the requirements corresponding to your pull request before you submit. You can delete this before you PR

What's a Uses Page?

A /uses page lists a developer's setup, gear, software, and configs (what they use). It's a great reference for those looking to add to their library of tools or reconfigure ones they already use.

What Should I Include?

Include the hardware you use, such as your computer and other related equipment. Include your preferred terminal, text editors, tools, frameworks, and other related software you use. If you can, include configurations for software (such as fonts and themes). The more you have on your /uses page, the more interesting it'll be to those who view it - just keep it on-topic!

Adding Yourself

• Ensure you are linking to a /uses page, not just your website
• Ensure your data is formatted like other entries
• Do not add yourself to the end of the array (add yourself somewhere random instead)
• Ensure this PR has a title in the following format
  • ✅ Add Your Name
  • ✅ Add @twitterusername
  • ❌ Add myself
  • ❌ Adding myself!
  • ❌ Add Your Name @twitter @github

Code Modifications

• Ensure the code submitted is formatted similarly to existing code
• Ensure variable, method, function, and component names are clear and concise

Final Requirements

• You've read and understood the above

Add your name to verify: Julius Dockwarder

-->

please reopen when you are ready

For Issue #478

Example for how a comment would look: https://github.com/rohit-gohri/awesome-uses/pull/1#issuecomment-623158310

sweet, just gonna yolo merge this and hope it works :)

<!--

Please read the requirements corresponding to your pull request before you submit. You can delete this before you PR

What's a Uses Page?

A /uses page lists a developer's setup, gear, software, and configs (what they use). It's a great reference for those looking to add to their library of tools or reconfigure ones they already use.

What Should I Include?

Include the hardware you use, such as your computer and other related equipment. Include your preferred terminal, text editors, tools, frameworks, and other related software you use. If you can, include configurations for software (such as fonts and themes). The more you have on your /uses page, the more interesting it'll be to those who view it - just keep it on-topic!

Adding Yourself

• Ensure you are linking to a /uses page, not just your website
• Ensure your data is formatted like other entries
• Do not add yourself to the end of the array (add yourself somewhere random instead)
• Ensure this PR has a title in the following format
  • ✅ Add Your Name
  • ✅ Add @twitterusername
  • ❌ Add myself
  • ❌ Adding myself!
  • ❌ Add Your Name @twitter @github

Code Modifications

• Ensure the code submitted is formatted similarly to existing code
• Ensure variable, method, function, and component names are clear and concise

Final Requirements

• You've read and understood the above

Add your name to verify: Name

-->

thanks a ton! super helpful

<!--

Code Modifications

• Ensure the code submitted is formatted similarly to existing code
• Ensure variable, method, function, and component names are clear and concise

Final Requirements

• You've read and understood the above

Add your name to verify: Sean Coker

-->

This normalizes and cleans up the tags on the page in 2 ways:

• Merges "case-varying" tags like "JavaScript" and "Javascript" to be merged into whatever tag is the most popular
• Adds a manual transformation for things that aren't necessarily case-varying like "Full Stack" vs "Fullstack" or "React" vs "React.js". I've manually added the replacement rules here based on the current count live on the site but it can be altered as you see fit (or not at all)

This means people can still enter a tag like "Javascript" and it will be changed to "JavaScript" (not because it's correct, but because it's the most popular) at build time.

<!--

Please read the requirements corresponding to your pull request before you submit. You can delete this before you PR

What's a Uses Page?

A /uses page lists a developer's setup, gear, software, and configs (what they use). It's a great reference for those looking to add to their library of tools or reconfigure ones they already use.

What Should I Include?

Include the hardware you use, such as your computer and other related equipment. Include your preferred terminal, text editors, tools, frameworks, and other related software you use. If you can, include configurations for software (such as fonts and themes). The more you have on your /uses page, the more interesting it'll be to those who view it - just keep it on-topic!

Adding Yourself

• Ensure you are linking to a /uses page, not just your website
• Ensure your data is formatted like other entries
• Do not add yourself to the end of the array (add yourself somewhere random instead)
• Ensure this PR has a title in the following format
  • ✅ Add Your Name
  • ✅ Add @twitterusername
  • ❌ Add myself
  • ❌ Adding myself!
  • ❌ Add Your Name @twitter @github

Code Modifications

• Ensure the code submitted is formatted similarly to existing code
• Ensure variable, method, function, and component names are clear and concise

Final Requirements

• You've read and understood the above

Add your name to verify: Name

-->

<!--

Please read the requirements corresponding to your pull request before you submit. You can delete this before you PR

What's a Uses Page?

A /uses page lists a developer's setup, gear, software, and configs (what they use). It's a great reference for those looking to add to their library of tools or reconfigure ones they already use.

What Should I Include?

Include the hardware you use, such as your computer and other related equipment. Include your preferred terminal, text editors, tools, frameworks, and other related software you use. If you can, include configurations for software (such as fonts and themes). The more you have on your /uses page, the more interesting it'll be to those who view it - just keep it on-topic!

Adding Yourself

• Ensure you are linking to a /uses page, not just your website
• Ensure your data is formatted like other entries
• Do not add yourself to the end of the array (add yourself somewhere random instead)
• Ensure this PR has a title in the following format
  • ✅ Add Your Name
  • ✅ Add @twitterusername
  • ❌ Add myself
  • ❌ Adding myself!
  • ❌ Add Your Name @twitter @github

Code Modifications

• Ensure the code submitted is formatted similarly to existing code
• Ensure variable, method, function, and component names are clear and concise

Final Requirements

• You've read and understood the above

Add your name to verify: Name

-->

<!--

Please read the requirements corresponding to your pull request before you submit. You can delete this before you PR

What's a Uses Page?

A /uses page lists a developer's setup, gear, software, and configs (what they use). It's a great reference for those looking to add to their library of tools or reconfigure ones they already use.

What Should I Include?

Include the hardware you use, such as your computer and other related equipment. Include your preferred terminal, text editors, tools, frameworks, and other related software you use. If you can, include configurations for software (such as fonts and themes). The more you have on your /uses page, the more interesting it'll be to those who view it - just keep it on-topic!

Adding Yourself

• Ensure you are linking to a /uses page, not just your website
• Ensure your data is formatted like other entries
• Do not add yourself to the end of the array (add yourself somewhere random instead)
• Ensure this PR has a title in the following format
  • ✅ Add Your Name
  • ✅ Add @twitterusername
  • ❌ Add myself
  • ❌ Adding myself!
  • ❌ Add Your Name @twitter @github

Code Modifications

• Ensure the code submitted is formatted similarly to existing code
• Ensure variable, method, function, and component names are clear and concise

Final Requirements

• You've read and understood the above

Add your name to verify: Roland Szabó

-->

sorry this got goofed, can you reopen another PR or rebase

<!--

Please read the requirements corresponding to your pull request before you submit. You can delete this before you PR

What's a Uses Page?

A /uses page lists a developer's setup, gear, software, and configs (what they use). It's a great reference for those looking to add to their library of tools or reconfigure ones they already use.

What Should I Include?

Include the hardware you use, such as your computer and other related equipment. Include your preferred terminal, text editors, tools, frameworks, and other related software you use. If you can, include configurations for software (such as fonts and themes). The more you have on your /uses page, the more interesting it'll be to those who view it - just keep it on-topic!

Adding Yourself

• Ensure you are linking to a /uses page, not just your website
• Ensure your data is formatted like other entries
• Do not add yourself to the end of the array (add yourself somewhere random instead)
• Ensure this PR has a title in the following format
  • ✅ Add Your Name
  • ✅ Add @twitterusername
  • ❌ Add myself
  • ❌ Adding myself!
  • ❌ Add Your Name @twitter @github

Code Modifications

• Ensure the code submitted is formatted similarly to existing code
• Ensure variable, method, function, and component names are clear and concise

Final Requirements

• You've read and understood the above

Add your name to verify: Dennis Mathenge

-->

<!--

Please read the requirements corresponding to your pull request before you submit. You can delete this before you PR

What's a Uses Page?

A /uses page lists a developer's setup, gear, software, and configs (what they use). It's a great reference for those looking to add to their library of tools or reconfigure ones they already use.

What Should I Include?

Include the hardware you use, such as your computer and other related equipment. Include your preferred terminal, text editors, tools, frameworks, and other related software you use. If you can, include configurations for software (such as fonts and themes). The more you have on your /uses page, the more interesting it'll be to those who view it - just keep it on-topic!

Adding Yourself

• Ensure you are linking to a /uses page, not just your website
• Ensure your data is formatted like other entries
• Do not add yourself to the end of the array (add yourself somewhere random instead)
• Ensure this PR has a title in the following format
  • ✅ Add Your Name
  • ✅ Add @twitterusername
  • ❌ Add myself
  • ❌ Adding myself!
  • ❌ Add Your Name @twitter @github

Code Modifications

• Ensure the code submitted is formatted similarly to existing code
• Ensure variable, method, function, and component names are clear and concise

Final Requirements

• You've read and understood the above

Add your name to verify: Name

-->

<!--

Please read the requirements corresponding to your pull request before you submit. You can delete this before you PR

What's a Uses Page?

A /uses page lists a developer's setup, gear, software, and configs (what they use). It's a great reference for those looking to add to their library of tools or reconfigure ones they already use.

What Should I Include?

Include the hardware you use, such as your computer and other related equipment. Include your preferred terminal, text editors, tools, frameworks, and other related software you use. If you can, include configurations for software (such as fonts and themes). The more you have on your /uses page, the more interesting it'll be to those who view it - just keep it on-topic!

Adding Yourself

• Ensure you are linking to a /uses page, not just your website
• Ensure your data is formatted like other entries
• Do not add yourself to the end of the array (add yourself somewhere random instead)
• Ensure this PR has a title in the following format
  • ✅ Add Your Name
  • ✅ Add @twitterusername
  • ❌ Add myself
  • ❌ Adding myself!
  • ❌ Add Your Name @twitter @github

Code Modifications

• Ensure the code submitted is formatted similarly to existing code
• Ensure variable, method, function, and component names are clear and concise

Final Requirements

• You've read and understood the above

Add your name to verify: Name

-->

<!--

Please read the requirements corresponding to your pull request before you submit. You can delete this before you PR

What's a Uses Page?

A /uses page lists a developer's setup, gear, software, and configs (what they use). It's a great reference for those looking to add to their library of tools or reconfigure ones they already use.

What Should I Include?

Include the hardware you use, such as your computer and other related equipment. Include your preferred terminal, text editors, tools, frameworks, and other related software you use. If you can, include configurations for software (such as fonts and themes). The more you have on your /uses page, the more interesting it'll be to those who view it - just keep it on-topic!

Adding Yourself

• Ensure you are linking to a /uses page, not just your website
• Ensure your data is formatted like other entries
• Do not add yourself to the end of the array (add yourself somewhere random instead)
• Ensure this PR has a title in the following format
  • ✅ Add Your Name
  • ✅ Add @twitterusername
  • ❌ Add myself
  • ❌ Adding myself!
  • ❌ Add Your Name @twitter @github

Code Modifications

• Ensure the code submitted is formatted similarly to existing code
• Ensure variable, method, function, and component names are clear and concise

Final Requirements

• You've read and understood the above

Add your name to verify: Name

-->

Final Requirements

• You've read and understood the above

**Add your name to verify: Sheila Leon