profile
viewpoint
Wes Bos wesbos me Hamilton, Ontario www.wesbos.com I create courses that make learning things like JavaScript easy and fun 🔥

public-apis/public-apis 98715

A collective list of free APIs for use in software and web development.

gatsbyjs/gatsby 47599

Build blazing fast, modern apps and websites with React

wesbos/Advanced-React 2664

Starter Files and Solutions for Full Stack Advanced React and GraphQL

wesbos/aprilFools.css 1269

Harmlessly goof up your co-workers browser and chrome dev tools

wesbos/ama 280

Ask me anything!

wesbos/advanced-react-rerecord 191

Trying things out. Feel free to follow along

gf3/WAT 102

LOLWAT?

npm/roadmap 65

Public roadmap for npm

wesbos/app 31

👀

npm/feedback 30

Public feedback discussions for npm

issue commentkeystonejs/keystone

Documentation on KeystoneJs on AWS Lambda is misleading

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 ?

jacobdoran

comment created time in 2 hours

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha e471321e77b3d6f22db5e659c5a4f9b561de8284

settings

view details

push time in 3 hours

pull request commentwesbos/master-gatsby

Add more questions and answers to the FAQ section

fantastic! Thanks a ton

Asjas

comment created time in 7 hours

push eventwesbos/master-gatsby

A-J Roos

commit sha 75e89a6a7de9e4c9b907e01dac1fc39ced885ecb

update the FAQ section

view details

Wes Bos

commit sha 42daf9cfbf60bd2e449a7d19551397dee85558bb

Merge pull request #59 from Asjas/update-faq Add more questions and answers to the FAQ section

view details

push time in 7 hours

PR merged wesbos/master-gatsby

Add more questions and answers to the FAQ section

Hey Wes 👋,

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

+33 -1

0 comment

1 changed file

Asjas

pr closed time in 7 hours

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha 25b11dfdd72d7ed95b07b2f29b28a80e56a982eb

docs

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha a8569325448ed88ffeb3eed8a589a2049cf66d12

docs

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha 3fca86a1970788fae351a46d99d3f4126f368614

try DO fixes

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha 280eb5808de0180be86a6f0961436772c8565413

try DO fixes

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha 9d5977e1009146bc7f0550d7e6e0d1b7d092dbd4

api endpoint

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha ed9989d117f66ebe3cd17ce06ab4726dae103534

please work

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha 3ccf263b262a28149e100bb7451637376c20e769

endpoint

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha bd0a286296775819732d6980a55fdc5c514fdfd4

asdf

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha 039fe82359fbfb437195619bac55ed11484d0c25

uhasdafsdF

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha 15a1dde53d98d7d35a900c082c708382f49d71af

fffff

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha 420a8f3650f119a7715bd88f3db6e2498a47c710

geasdfasdF

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha af67c77402be9cc5a437fe23e5a1da872640d884

ushdiufhasldkgfhsdlkfjgh

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha fbcce83b72ec83a64c12bbca66a00dd9840d98e0

changes

view details

push time in 3 days

PR closed wesbos/advanced-react-rerecord

Bump next from 9.5.3 to 9.5.5 in /finished-files/backend dependencies

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 compatibility score

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>

+348 -307

0 comment

1 changed file

dependabot[bot]

pr closed time in 3 days

PR closed wesbos/advanced-react-rerecord

Bump next from 9.5.3 to 9.5.4 in /finished-files/frontend dependencies

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:security@zeit.co">security@vercel.com</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 compatibility score

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>

+395 -328

0 comment

2 changed files

dependabot[bot]

pr closed time in 3 days

PR closed wesbos/advanced-react-rerecord

Bump next from 9.5.3 to 9.5.4 in /finished-files/frontend-strapi dependencies

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:security@zeit.co">security@vercel.com</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 compatibility score

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>

+395 -328

0 comment

2 changed files

dependabot[bot]

pr closed time in 3 days

PR closed wesbos/advanced-react-rerecord

Bump lodash from 4.17.15 to 4.17.20 in /finished-files/frontend dependencies

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 compatibility score

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>

+80 -52

0 comment

1 changed file

dependabot[bot]

pr closed time in 3 days

PR closed wesbos/advanced-react-rerecord

Bump lodash from 4.17.15 to 4.17.20 in /finished-files/frontend-strapi dependencies

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 compatibility score

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>

+3 -52

0 comment

1 changed file

dependabot[bot]

pr closed time in 3 days

PR closed wesbos/advanced-react-rerecord

Bump object-path from 0.11.4 to 0.11.5 in /backend-strapi dependencies

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 compatibility score

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>

+3 -3

5 comments

1 changed file

dependabot[bot]

pr closed time in 3 days

PR closed wesbos/advanced-react-rerecord

Bump next from 9.5.3 to 9.5.4 in /frontend dependencies

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:security@zeit.co">security@vercel.com</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 compatibility score

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>

+293 -276

5 comments

2 changed files

dependabot[bot]

pr closed time in 3 days

PR closed wesbos/advanced-react-rerecord

Bump next from 9.5.3 to 9.5.4 in /backend dependencies

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:security@zeit.co">security@vercel.com</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 compatibility score

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>

+280 -287

5 comments

1 changed file

dependabot[bot]

pr closed time in 3 days

PR closed wesbos/advanced-react-rerecord

Bump lodash from 4.17.15 to 4.17.20 in /frontend-strapi dependencies

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 compatibility score

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>

+3 -52

5 comments

1 changed file

dependabot[bot]

pr closed time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha b942e0560fa08c360acc5f4f0a5ccce963904ad9

change backend port

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha 10e68f8e7c71cc3a916299ef589b3d6199456777

pin node version, due to bug in 15

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha 90c653f9967e63c37019eb6e353004c55c73ecd7

change backend to 8080

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha 214c93cb38655b0d36a352e295cab308d812b1a6

change next prod port

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha 4d4c1e00c85c9be63e33eb82d7e2ded7d26bcb52

why was that there

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha f4dabf9b99203a4c5ed7690cb9508c5e3a1eace5

asdFAsdfaSDF

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha 2797465951b1b3af384f27691547f8c2ed7952f3

update package.lock

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha 977eb07554f6407685515444ce072cd9aaba0d57

remove backend

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha 03eb53e0ba499ca40779c7ba559e1a60cb2f062c

do

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha 6bd70dcb0337f067803e64ca33b7c37ff0a7cf14

revert serverless

view details

push time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha 2cd4f94c6d7d94ccb211df7e3d9be5f79c5d5a02

try serverless

view details

push time in 3 days

issue commentkeystonejs/keystone

Cannot boot in existing project: "TypeError: Cannot read property 'prepare' of undefined"

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

module.exports.keystone = keystone;

ra-external

comment created time in 3 days

push eventwesbos/advanced-react-rerecord

Wes Bos

commit sha b811a3fe6dff781bd2d97ffd49ff31f05411af30

moving folders

view details

push time in 3 days

push eventwesbos/javascript-verification-inputs

Wes Bos

commit sha 0492bc606cc8e65d43c43eed34ecd28adbab3435

add backspace challenge

view details

push time in 4 days

create barnchwesbos/javascript-verification-inputs

branch : master

created branch time in 4 days

created repositorywesbos/javascript-verification-inputs

created time in 4 days

pull request commentwesbos/Syntax

fix: update show notes edit url

thank you!

bntzio

comment created time in 4 days

push eventwesbos/Syntax

Enrique Benitez

commit sha 5803b134fbfa34f18d65e70d16ef9464d720403c

fix: update show notes edit url

view details

Wes Bos

commit sha c27340bfdca311e106fc2db29e8807fc7d9b022a

Merge pull request #555 from bntzio/fix/show-notes-url fix: update show notes edit url

view details

push time in 4 days

PR merged wesbos/Syntax

fix: update show notes edit url

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

syntax_notes_bug

Context

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

+1 -1

2 comments

1 changed file

bntzio

pr closed time in 4 days

issue commentwesbos/advanced-react-rerecord

Pagination with cache is still goofy

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)

  1. 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

wesbos

comment created time in 5 days

pull request commentkuldeep349/unl.finance

remove our photos from your website

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

wesbos

comment created time in 6 days

PR opened kuldeep349/unl.finance

remove our photos from your website

dont use our photos you knob

+1 -95

0 comment

1 changed file

pr created time in 6 days

push eventwesbos/unl.finance

Wes Bos

commit sha c2178110ad8cd3d31c7109bcb25162abd4fab7f8

remove our photos from your website

view details

push time in 6 days

push eventwesbos/dotfiles

Wes Bos

commit sha 195743693d585df07ee1f8a611c36b551f3ab1ac

Create javascript.snippets.json

view details

push time in 6 days

push eventwesbos/JavaScript30

Lilla Pulay

commit sha bf1d9148c4e3a24463ad1de6c943fde83ef9ebeb

Mixed the order of items in the 'people' array The original order was the same at the solution to exercise 7 in the file, thus I think the difference couldn't be seen properly.

view details

Lilla Pulay

commit sha 80ec67114e6f244a823052f2b2ae795608725fc2

Mixed the order of items in the 'people' array The original order was the same at the solution to exercise 7 in the file, thus I think the difference couldn't be seen properly.

view details

Wes Bos

commit sha ac5ce1a3ccc2255cec56ad07cd9e233a83030fc4

Merge pull request #406 from lillapulay/master Suggestion for 'people' array of day 4

view details

push time in 6 days

PR merged wesbos/JavaScript30

Suggestion for 'people' array of day 4

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.

-->

+16 -4

1 comment

2 changed files

lillapulay

pr closed time in 6 days

pull request commentwesbos/JavaScript30

Suggestion for 'people' array of day 4

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

lillapulay

comment created time in 6 days

pull request commentwesbos/master-gatsby

Update SEO on Slicemasters Template

thank you!

break7533

comment created time in 6 days

push eventwesbos/master-gatsby

Luis Lopes

commit sha af30da4c617dc2d11dde75c497a799b39f7ede8b

Update SEO 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

view details

Luis Lopes

commit sha 80b2b8e7123e9735254b56f0d07ccdf3c662d707

Update SEO on lesson 33 Also decided to update the stepped solution, in case it is important to have consistency between files. This will cause the solution to be different from the video, feel free to decline this change

view details

Wes Bos

commit sha b1138b93b240ba677268d0cb66ab8288d99fe199

Merge pull request #52 from break7533/patch-1 Update SEO on Slicemasters Template

view details

push time in 6 days

PR merged wesbos/master-gatsby

Update SEO on Slicemasters Template

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

+2 -2

0 comment

2 changed files

break7533

pr closed time in 6 days

pull request commentwesbos/eslint-config-wesbos

Add asset option for label-control fix

thanks!

adebiyial

comment created time in 7 days

push eventwesbos/eslint-config-wesbos

Adebiyi Adedotun

commit sha 003df34f618e627c59747ba81bab9e135beebac3

Add asser option for label-control fix

view details

Wes Bos

commit sha 35adb5b18aeba2083f6c88df71941cacb5bc5031

Merge pull request #65 from adebiyial/bugfix/label-associated-control Add asset option for label-control fix

view details

push time in 7 days

PR merged wesbos/eslint-config-wesbos

Add asset option for label-control fix

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

+6 -0

0 comment

1 changed file

adebiyial

pr closed time in 7 days

push eventwesbos/eslint-config-wesbos

mhesham32

commit sha 2e05a892c7dae984f3a0bd5081ebeeff350a12f0

add "s" to window (fix typo) 🤞

view details

mhesham32

commit sha 2412e60b488fe3f8794fcb551e5a46242b7bff16

reuse single quotes

view details

Wes Bos

commit sha b31f01ff90f15803c8a73c56772fe5004dc88e17

Merge pull request #66 from mhesham32/master add "s" to window fix typo 🤞

view details

push time in 7 days

issue commentwesbos/eslint-config-wesbos

Using together with typescript?

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

kiprasmel

comment created time in 10 days

push eventwesbos/eslint-config-wesbos

Wes Bos

commit sha 9fcb7c0ad06738139529c9210f3a49816b038c9e

update deps

view details

push time in 10 days

create barnchwesbos/eslint-config-wesbos

branch : typescript

created branch time in 10 days

issue openedmicrosoft/vscode

Add file rename and move commands to the command palette

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.

created time in 10 days

issue openedsleistner/vscode-fileutils

Prompt to update imports when moving or renaming a file.

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

created time in 10 days

push eventwesbos/wesbos

Wes Bos

commit sha 9293dd32edbf4292057665ce829d6d3c0eb798cb

Fix broken mp4 thumbs. Fixes #123

view details

push time in 10 days

issue closedwesbos/wesbos

Thumbnail Broken in tweets when tweeting a video

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

image

closed time in 10 days

wesbos

issue openedwesbos/wesbos

Thumbnail Broken in tweets when tweeting a video

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

image

created time in 10 days

issue commentwesbos/wesbos

interested in contributing, what do you need?

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.

serahrono

comment created time in 12 days

push eventwesbos/awesome-uses

Rohit Gohri

commit sha d13b22f097a927bda29ac5b09e600587a561974d

remove invalid entry

view details

Wes Bos

commit sha 9399e346da7a2df94c86330f5aab1adc78246b2f

Merge pull request #997 from rohit-gohri/invalidEntry Remove invalid entry

view details

push time in 13 days

PR merged wesbos/awesome-uses

Remove invalid entry

<!--

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.

+0 -11

0 comment

1 changed file

rohit-gohri

pr closed time in 13 days

MemberEvent

PR closed wesbos/awesome-uses

Add Julius Dockwarder

<!--

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

-->

+20 -0

3 comments

1 changed file

dockwarder

pr closed time in 14 days

pull request commentwesbos/awesome-uses

Add Julius Dockwarder

please reopen when you are ready

dockwarder

comment created time in 14 days

push eventwesbos/awesome-uses

Rohit Gohri

commit sha c7691e320096b99e3e879553d31e8036b5d11036

chore: run validate script only when run directly

view details

Rohit Gohri

commit sha 9426b956e6321e9cea4473ed6350c10dbd8c57f0

ci: add danger-js and add validation dangerfile

view details

Rohit Gohri

commit sha 84e985bc94d1f379026c6da9417d672752e6cea2

ci: add danger step to workflow

view details

Rohit Gohri

commit sha bc624f15172f86b2a1695d101b659bc98f4fe81b

add dummy entry to trigger workflow

view details

Rohit Gohri

commit sha afced1a6b7c1f5d4b01b49205d599b0387ac4ef8

ci: delete old data-validate step

view details

Rohit Gohri

commit sha 2f2ce100fd1fa39b376b24570fcc3d4552d6869e

ci: show all errors in comment/log

view details

Rohit Gohri

commit sha 38464bf0653e3aeed5e958bef629946014d365e4

ci: Move comment creation to dangerfile

view details

Rohit Gohri

commit sha 3d2af7bc38e1cab25ecb96233531332885cf67e7

ci: use danger token

view details

Rohit Gohri

commit sha ef972cf38f1975d122578d6189bdd1f45339714d

ci: better formatted messages

view details

Rohit Gohri

commit sha 61e1aeeb3674d29396285fec6b813deed91d35b9

ci: use danger diff to get master data

view details

Rohit Gohri

commit sha 48c717fb9579b4a232ad4b10a1667449a1f421e3

add different wrong data

view details

Rohit Gohri

commit sha c1c356e6229f511fc684eb30ba08c664c680eae2

chore: remove unused packages

view details

Wes Bos

commit sha fc27754ef4c0aba85e2da260f8059a1e7ae79288

Merge pull request #796 from rohit-gohri/danger Use DangerJS for commenting

view details

push time in 14 days

PR merged wesbos/awesome-uses

Use DangerJS for commenting

For Issue #478

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

+764 -188

2 comments

8 changed files

rohit-gohri

pr closed time in 14 days

pull request commentwesbos/awesome-uses

Use DangerJS for commenting

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

rohit-gohri

comment created time in 14 days

PR closed wesbos/awesome-uses

Adding Rafi Halilintar

<!--

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

-->

+860 -433

1 comment

2 changed files

masitings

pr closed time in 14 days

push eventokcoker/awesome-uses

Kieran Osgood

commit sha 8fdd090b16677306a73085b6970d2206f24d89cf

feat: add Kieran Osgood profile

view details

Sean Coker

commit sha 32a5ba6e84a5adf620964fa983235ef587cd660c

Add Sean Coker

view details

Gatare Libère

commit sha fc8b4c5083155d019f5d7907ca8b53f59a101519

Merge pull request #856 from okcoker/okcoker Add Sean Coker

view details

GitHub Action

commit sha f02697b00763b83001c16ff6c53d829795001fea

chore: generate `readme.md`, lint `src/data.js`

view details

Martin M

commit sha 1458502a7e2ff0163964fb249661a87d0a23a5ef

Update data.js (#861)

view details

GitHub Action

commit sha 5f685e4673f96c97f7f7a06531c0b34675e7f891

chore: generate `readme.md`, lint `src/data.js`

view details

Narendra

commit sha 60690ff40c285f58f6aeae259ab526d2608c2b19

add Narendra (#865) * add Narendra * add Narendra

view details

GitHub Action

commit sha 641866b9c8ddaf3452ca0c5b3c8c5e525198f482

chore: generate `readme.md`, lint `src/data.js`

view details

Eric Blohm

commit sha 949d96fca51b85bbee57e58b9fac0d9466f4cbdd

add Eric Blohm (#866) Co-authored-by: Eric Blohm <eric@ericblohm.codes>

view details

Erik Kroes

commit sha 1665170bd66df944be6d3239d262385800d9deb9

add Erik Kroes (#867)

view details

GitHub Action

commit sha dffd82a25a360dff68dc9921631426b6c8b5f821

chore: generate `readme.md`, lint `src/data.js`

view details

Sergio Martín

commit sha 78531fc1c98cb254bba746ceeb6029bfc1e20389

Add Sergio Martin (#868)

view details

Amir Ghaffari

commit sha 54608d7fbafd53fa69e5a01e8dbac6347f0e91b3

add Amir Ghaffari (#869)

view details

Rizwan Mohamed Ibrahim

commit sha 62bd757d109976190ce222bbe3ed88d4b7da3700

adds rizwan's uses (#864) from https//blog.rizwan.dev/uses

view details

GitHub Action

commit sha 454aed7dee88bc351a0647b800d44e77e41ee4d2

chore: generate `readme.md`, lint `src/data.js`

view details

Philipp John

commit sha c9b76769bbadaa7ab4f5ed2bc56ec797179f3d02

Add Philipp John (#860)

view details

GitHub Action

commit sha a3873cebaa5d6b57c97d6c4863221322ff2c4eae

chore: generate `readme.md`, lint `src/data.js`

view details

Kieran Osgood

commit sha d404ccae3893feff57ba76ed04240277df45d63b

Merge branch 'master' into master

view details

Elio Struyf

commit sha b0802f68fef8868a79862ee375a00fe5cff59a67

Added myself 😃

view details

Gatare Libère

commit sha c9ab29ec3c18359fbb0e3e156073f5e915c260c1

Merge pull request #871 from estruyf/master Added Elio Struyf - @eliostruyf

view details

push time in 14 days

pull request commentwesbos/awesome-uses

feat: Clean up tags

thanks a ton! super helpful

okcoker

comment created time in 14 days

push eventwesbos/awesome-uses

Sean Coker

commit sha fca86d574eaccf2bbb5218b6c6308faa88231a61

Clean up tags data

view details

Wes Bos

commit sha d59fa315f96bcc78eb720acd874ecb44793a595a

Merge branch 'master' into feature/tag-normalization

view details

Wes Bos

commit sha d5a9c0b2bde661d3aa02f4a4173bc41d1c2dfb80

Merge pull request #857 from okcoker/feature/tag-normalization feat: Clean up tags

view details

push time in 14 days

PR merged wesbos/awesome-uses

feat: Clean up tags

<!--

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.

+58 -9

0 comment

2 changed files

okcoker

pr closed time in 14 days

PR closed wesbos/awesome-uses

add-phemmy

<!--

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

-->

+20 -0

0 comment

1 changed file

adexphem

pr closed time in 14 days

PR closed wesbos/awesome-uses

Added David Amunga

<!--

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

-->

+24 -0

0 comment

1 changed file

DavidAmunga

pr closed time in 14 days

PR closed wesbos/awesome-uses

Add Roland Szabó

<!--

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ó

-->

+22 -0

3 comments

1 changed file

RolandSzaboDesign

pr closed time in 14 days

pull request commentwesbos/awesome-uses

Add Roland Szabó

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

RolandSzaboDesign

comment created time in 14 days

push eventwesbos/awesome-uses

Dennis Mathenge

commit sha 3cd155ae63bf7a318b1a89dd556e4604f6a7fb0b

Add user Dennis

view details

Dennis Mathenge

commit sha 875a9f6192811b03fd3a69fb66ed41238ca4d3b6

update url

view details

Dennis Mathenge

commit sha cf444de83398fd41525205f2b99604a9bc5ee15a

update computer

view details

Dennis Mathenge

commit sha 5d716b26e67389847aa0fb663a8367ba523f45a8

update emoji

view details

Dennis Mathenge

commit sha c8eb325abfa650ec7fe614c8606f36885126f800

Change twitter handle

view details

Wes Bos

commit sha 6f394db65155ff14b4377bb98d8b4c3e2db4a38e

Merge pull request #927 from creativehubspace/master Add Dennis Mathenge

view details

push time in 14 days

PR merged wesbos/awesome-uses

Add 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: Dennis Mathenge

-->

+22 -0

2 comments

1 changed file

creativehubspace

pr closed time in 14 days

push eventwesbos/awesome-uses

Nico Bachner

commit sha 72519b3d08d30d0586d639e9b5cd6c84fff93f70

merged duplicate node.js tags

view details

Nico Bachner

commit sha 0ac3645fde726e855e41ee00258c3e3990d94ab1

Merge duplicate Node tags (typo correction) Co-authored-by: davidak <davidak@users.noreply.github.com>

view details

Nico Bachner

commit sha 956163f233fe2b1c6b85f0f8da5f7299e1d0235c

Merge branch 'master' into nodejs-tag-merge

view details

Nico Bachner

commit sha 5b93c5d545d911df30cb1435b89d6378c4757dad

convert Node tags to Node.js (PR wesbos/awesome-uses#962) (Issue wesbos/awesome-uses#637)

view details

Wes Bos

commit sha 344822a914febe69ba28692c7d64dadc918abae2

Merge branch 'master' into nodejs-tag-merge

view details

Wes Bos

commit sha c5c670894380c49cb8c46baa4841102431eb79f9

Merge pull request #962 from nico-bachner/nodejs-tag-merge Merge duplicate Node.js tags (Issue #637)

view details

push time in 14 days

PR merged wesbos/awesome-uses

Reviewers
Merge duplicate Node.js tags (Issue #637)

<!--

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

-->

+206 -208

3 comments

1 changed file

nico-bachner

pr closed time in 14 days

push eventnico-bachner/awesome-uses

Sheila Leon

commit sha cfcb63d81b77466a6013691509808d9d44a74dd5

Add Sheila Leon

view details

davidak

commit sha 32bb383287199197702e6dd159db7f4db95eaa25

Add davidak I finally made a uses page.

view details

Nico Bachner

commit sha 2dc92449a05e18af617a71831da66fcacd6e036e

merged duplicate jamstack tags

view details

Nico Bachner

commit sha 7f39dab6a302bfd1a760b5c3b056ef0ed7b72e51

merged duplicate oss tags

view details

Nico Bachner

commit sha cd16e4803e3cdec6d506c7a74aae3aceac519b14

merged duplicate front end tags

view details

Marc Berger

commit sha 00c503c38a5527b7d04dcc04413cf6206ae503cd

Update data.js Added my profile

view details

Marc Berger

commit sha b78de6d9c04487b5ce4e352a5c7ac9bb29eb351d

Add /uses/ to url

view details

Marc Berger

commit sha 8fb324df38393b7aa1075216660eb2f7a96005ef

Capitalize country

view details

Marc Berger

commit sha b87c7d221c3d77e50ef7f5318e16314aa075dc0a

Update uses url and country(emoji)

view details

Marc Berger

commit sha d031c79ce7e1fc35600168adc2a94c39d0ccda1d

Reset indentation

view details

Marc Berger

commit sha c86846d786f9ddd972288a9254d179658727af2f

Final change

view details

Marc Berger

commit sha 51b4934505aeb716c80daa81ef1688ee62b84062

Add comma

view details

Satyam1203

commit sha 3e3bd436f50d4a09e964744bae2a309f19a4958a

Merge duplicate DevOps tags

view details

Nico Bachner

commit sha 3d7779d482a045bf4a2b5eb1229d5d287cd40fb1

added flip phone (wesbos/awesome-uses#765)

view details

Pranesh

commit sha 71d90c42bff5c376c724d326a0d33518ad2ed401

Add Pranesh's uses

view details

aladin002dz

commit sha a1f8408939e22d16e9f2e3844f9df53f33a5afd3

Add Mahfoudh Arous

view details

aladin002dz

commit sha 0cf37adde1267220fa9b435eaad08c83d3ff8515

Add Mahfoudh Arous Details

view details

aladin002dz

commit sha b8620a40a47dfeafe9f39f6622e18bcceeec2e8d

fix url patterm

view details

aladin002dz

commit sha 9746634a251515440cd0e16641a1166633fe5aca

fix country code format

view details

aladin002dz

commit sha 1a180bd5c71a6ac8c097de15bc27f3468bd26b3d

fix country code format

view details

push time in 14 days

push eventwesbos/awesome-uses

Nico Bachner

commit sha cd16e4803e3cdec6d506c7a74aae3aceac519b14

merged duplicate front end tags

view details

Wes Bos

commit sha d793ec5ed77a59f89b46e7463d294ca1459e34f0

Merge branch 'master' into frontend-tag-merge

view details

Wes Bos

commit sha 3b155f94cebcd23331c08b863cb82514ac0bd035

Merge pull request #973 from nico-bachner/frontend-tag-merge Merge duplicate Front End tags (Issue #637)

view details

push time in 14 days

PR merged wesbos/awesome-uses

Merge duplicate Front End tags (Issue #637)

<!--

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

-->

+14 -14

0 comment

1 changed file

nico-bachner

pr closed time in 14 days

push eventnico-bachner/awesome-uses

Sheila Leon

commit sha cfcb63d81b77466a6013691509808d9d44a74dd5

Add Sheila Leon

view details

davidak

commit sha 32bb383287199197702e6dd159db7f4db95eaa25

Add davidak I finally made a uses page.

view details

Nico Bachner

commit sha 2dc92449a05e18af617a71831da66fcacd6e036e

merged duplicate jamstack tags

view details

Nico Bachner

commit sha 7f39dab6a302bfd1a760b5c3b056ef0ed7b72e51

merged duplicate oss tags

view details

Nico Bachner

commit sha 8056a0773f85b38a18c2d11f30826972cec034a4

merge duplicate full stack tags (wesbos/awesome-uses#637)

view details

Nico Bachner

commit sha ca89dfe290f417799270b9ae9c1730d88dd763a3

merged duplicate tailwindcss tags (wesbos/awesome-uses#637)

view details

Wes Bos

commit sha d1db4d75eebad3bfc2622b9bb2108398927b4d8e

Merge pull request #975 from nico-bachner/tailwind-tag-merge Merge duplicate Tailwind CSS tags (Issue #637)

view details

Wes Bos

commit sha 9be7184d19b80a1d8e5542f7f89ddab96e643f4a

Merge pull request #974 from nico-bachner/fullstack-tag-merge Merge duplicate Full Stack tags (Issue #637)

view details

Marc Berger

commit sha 00c503c38a5527b7d04dcc04413cf6206ae503cd

Update data.js Added my profile

view details

Marc Berger

commit sha b78de6d9c04487b5ce4e352a5c7ac9bb29eb351d

Add /uses/ to url

view details

Marc Berger

commit sha 8fb324df38393b7aa1075216660eb2f7a96005ef

Capitalize country

view details

Marc Berger

commit sha b87c7d221c3d77e50ef7f5318e16314aa075dc0a

Update uses url and country(emoji)

view details

Marc Berger

commit sha d031c79ce7e1fc35600168adc2a94c39d0ccda1d

Reset indentation

view details

Marc Berger

commit sha c86846d786f9ddd972288a9254d179658727af2f

Final change

view details

Marc Berger

commit sha 51b4934505aeb716c80daa81ef1688ee62b84062

Add comma

view details

Satyam1203

commit sha 3e3bd436f50d4a09e964744bae2a309f19a4958a

Merge duplicate DevOps tags

view details

Nico Bachner

commit sha 3d7779d482a045bf4a2b5eb1229d5d287cd40fb1

added flip phone (wesbos/awesome-uses#765)

view details

Matt Litzinger

commit sha 6fec7b84633a6a47a8c3ca92b4a6f07b2df511ff

Add Matt Litzinger (#979)

view details

Matthew Hughes

commit sha dfc930a6aff1d7627547f5197ae4afa6294f13f2

Update data.js (#956) added myself to the uses!

view details

Dhananjay Porwal

commit sha 94a8d3347dbcc0d127139881e6d0dab209d6e8be

Update data.js (#971) * Update data.js * Update data.js

view details

push time in 14 days

PR closed wesbos/awesome-uses

add @_iMeriem invalid

<!--

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

-->

+11 -0

0 comment

1 changed file

iMeriem

pr closed time in 14 days

push eventwesbos/awesome-uses

Sheila Leon

commit sha cfcb63d81b77466a6013691509808d9d44a74dd5

Add Sheila Leon

view details

Wes Bos

commit sha 4ce57c3229195625e307d893ada6edfaa811fefb

Merge pull request #933 from sheilaleon/master Add Sheila Leon

view details

push time in 14 days

PR merged wesbos/awesome-uses

Add Sheila Leon

Final Requirements

  • You've read and understood the above

**Add your name to verify: Sheila Leon

+20 -0

0 comment

1 changed file

sheilaleon

pr closed time in 14 days

more