leerob

leerob

Director of DevRel ▲ @vercel

Member Since 7 years ago

@Vercel, Des Moines, IA

Experience Points
4.5k
follower
Lessons Completed
0
follow
Lessons Completed
128
stars
Best Reply Awards
40
repos

2704 contributions in the last year

Pinned
⚡ The React Framework
⚡ ✨ My portfolio built with Next.js, Tailwind, Prisma, and Vercel.
⚡ ⚛️ Build applications from the the future, today.
⚡ Easily add user reviews, feedback, and comments to your website in one line of code.
⚡ A free video course for building static and server-side rendered applications with Next.js and React.
⚡ Example Next.js app to upload photos to an S3 bucket.
Activity
Jan
25
2 days ago
push

leerob push leerob/leerob.io

leerob
leerob

Bump nanoid from 3.1.30 to 3.2.0 (#440)

commit sha: 676de3f7f3469f04503618a7d7e21e155608fc10

push time in 1 day ago
Activity icon
delete

leerob in leerob/leerob.io delete branch dependabot/npm_and_yarn/nanoid-3.2.0

deleted time in 1 day ago
pull request

leerob pull request leerob/leerob.io

leerob
leerob

Bump nanoid from 3.1.30 to 3.2.0

Bumps nanoid from 3.1.30 to 3.2.0.

Changelog

Sourced from nanoid's changelog.

Change Log

This project adheres to Semantic Versioning.

3.2

  • Added --size and --alphabet arguments to binary (by Vitaly Baev).

3.1.32

  • Reduced async exports size (by Artyom Arutyunyan).
  • Moved from Jest to uvu (by Vitaly Baev).

3.1.31

  • Fixed collision vulnerability on object in size (by Artyom Arutyunyan).
Commits

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.


Dependabot commands and options

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.

Activity icon
issue

leerob issue comment RyanClementsHax/storybook-addon-next

leerob
leerob

Thank you! ❤️

Just wanted to say thank you for creating this - it's awesome!

leerob
leerob

Thoughts on merging one of your examples here back to with-storybook?

https://github.com/vercel/next.js/tree/canary/examples/with-storybook

Activity icon
issue

leerob issue RyanClementsHax/storybook-addon-next

leerob
leerob

Thank you! ❤️

Just wanted to say thank you for creating this - it's awesome!

pull request

leerob merge to vercel/next.js

leerob
leerob

Clarify `headers` config option description

Reading over this page, it wasn't immediately clear to me if these were headers which would get read off of the incoming request, or headers to be added to the outgoing response.

Documentation / Examples

  • Make sure the linting passes by running yarn lint
push

leerob push leerob/new-website

leerob
leerob

Update and rename now.json to vercel.json

commit sha: d3b8e4504c193c0bdb771c9106a03c8c6d6b5981

push time in 2 days ago
Activity icon
fork

leerob forked datocms/new-website

⚡ Next.js project powering our marketing page!
leerob Updated
fork time in 2 days ago
pull request

leerob pull request paulirish/lite-youtube-embed

leerob
leerob

Rename `now.json` to `vercel.json`

Closes https://github.com/paulirish/lite-youtube-embed/issues/114.

Single new line change from the GitHub GUI editor when renaming.

Activity icon
fork

leerob forked paulirish/lite-youtube-embed

⚡ A faster youtube embed.
leerob Updated
fork time in 2 days ago
Activity icon
issue

leerob issue datocms/nextjs-demo

leerob
leerob

Update dependencies

Hey! We recently updated the dependencies of this example in the Next.js repo - should they be copied here?

https://github.com/vercel/next.js/tree/canary/examples/cms-datocms

Activity icon
issue

leerob issue paulirish/lite-youtube-embed

leerob
leerob

Vercel Usage

Hey there! I saw you were still using a now.json file. Are you still utilizing Vercel? I'd be happy to make a PR to switch that over 😄

pull request

leerob merge to vercel/platforms

leerob
leerob

Secured API routes and consolidated all api routes for /post

open pull request

leerob wants to merge vercel/platforms

leerob
leerob

Secured API routes and consolidated all api routes for /post

pull request

leerob merge to vercel/platforms

leerob
leerob

Secured API routes and consolidated all api routes for /post

Jan
24
3 days ago
Activity icon
issue

leerob issue comment vercel/platforms

leerob
leerob

Add error toasts on login page

What

A nice improvement to offer out of the box would be error prompts for the login page (User can see if it's an issue with something they did, or a server-side issue, etc). Seeing as react-hot-toast is already used in other places, we could use that combined with next/router to check for any error parameters returned by next-auth

leerob
leerob

Yeah! That would be great.

If there's an error logging in, catch that error and display it with react-hot-toast 👍

Activity icon
issue

leerob issue vercel/platforms

leerob
leerob

Twitter Auth Essential Access error

I'm getting the following error.

[next-auth][error][OAUTH_V1_GET_ACCESS_TOKEN_ERROR] 
https://next-auth.js.org/errors#oauth_v1_get_access_token_error undefined {
  statusCode: 403,
  data: '{"errors":[{"message":"You currently have Essential access which includes access to Twitter API v2 endpoints only. If you need access to this endpoint, you’ll need to apply for Elevated access via the Developer Portal. You can learn more here: https://developer.twitter.com/en/docs/twitter-api/getting-started/about-twitter-api#v2-access-leve","code":453}]}\n'
}

I am following along with the blog post but things do look different for me. For example, my Twitter dev dashboard does not have "enable 3-legged" option. Just the options in the screenshot below

image

I can't even get the login button to prompt for Twitter oAuth without changing the callback URL in step 13 from the blog post suggestion of 'http://localhost:3000/api/auth/callback/twitter' (does not work) to 'http://app.localhost:3000/api/auth/callback/twitter' (prompts but get console error above)

If I follow the blog post exactly I get this

[next-auth][error][GET_AUTHORIZATION_URL_ERROR] 
https://next-auth.js.org/errors#get_authorization_url_error undefined {
  statusCode: 403,
  data: `<?xml version='1.0' encoding='UTF-8'?><errors><error code="415">Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings</error></errors>`
}
[next-auth][error][SIGNIN_OAUTH_ERROR] 
https://next-auth.js.org/errors#signin_oauth_error undefined {
  error: {
    statusCode: 403,
    data: `<?xml version='1.0' encoding='UTF-8'?><errors><error code="415">Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings</error></errors>`
  },
  provider: {
    id: 'twitter',
    name: 'Twitter (Legacy)',
    type: 'oauth',
    version: '1.0A',
    authorization: { url: 'https://api.twitter.com/oauth/authenticate', params: {} },
    accessTokenUrl: 'https://api.twitter.com/oauth/access_token',
    requestTokenUrl: 'https://api.twitter.com/oauth/request_token',
    profileUrl: 'https://api.twitter.com/1.1/account/verify_credentials.json?include_email=true',
    profile: [Function: profile],
    clientId: 'xxxx-removed-xxxx',
    clientSecret: 'xxxx-removed-xxxx',
    signinUrl: 'http://app.localhost:3000/api/auth/signin/twitter',
    callbackUrl: 'http://app.localhost:3000/api/auth/callback/twitter'
  },
  message: undefined
}

Any help or suggestions is appreciated

Activity icon
issue

leerob issue comment vercel/platforms

leerob
leerob

Twitter Auth Essential Access error

I'm getting the following error.

[next-auth][error][OAUTH_V1_GET_ACCESS_TOKEN_ERROR] 
https://next-auth.js.org/errors#oauth_v1_get_access_token_error undefined {
  statusCode: 403,
  data: '{"errors":[{"message":"You currently have Essential access which includes access to Twitter API v2 endpoints only. If you need access to this endpoint, you’ll need to apply for Elevated access via the Developer Portal. You can learn more here: https://developer.twitter.com/en/docs/twitter-api/getting-started/about-twitter-api#v2-access-leve","code":453}]}\n'
}

I am following along with the blog post but things do look different for me. For example, my Twitter dev dashboard does not have "enable 3-legged" option. Just the options in the screenshot below

image

I can't even get the login button to prompt for Twitter oAuth without changing the callback URL in step 13 from the blog post suggestion of 'http://localhost:3000/api/auth/callback/twitter' (does not work) to 'http://app.localhost:3000/api/auth/callback/twitter' (prompts but get console error above)

If I follow the blog post exactly I get this

[next-auth][error][GET_AUTHORIZATION_URL_ERROR] 
https://next-auth.js.org/errors#get_authorization_url_error undefined {
  statusCode: 403,
  data: `<?xml version='1.0' encoding='UTF-8'?><errors><error code="415">Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings</error></errors>`
}
[next-auth][error][SIGNIN_OAUTH_ERROR] 
https://next-auth.js.org/errors#signin_oauth_error undefined {
  error: {
    statusCode: 403,
    data: `<?xml version='1.0' encoding='UTF-8'?><errors><error code="415">Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings</error></errors>`
  },
  provider: {
    id: 'twitter',
    name: 'Twitter (Legacy)',
    type: 'oauth',
    version: '1.0A',
    authorization: { url: 'https://api.twitter.com/oauth/authenticate', params: {} },
    accessTokenUrl: 'https://api.twitter.com/oauth/access_token',
    requestTokenUrl: 'https://api.twitter.com/oauth/request_token',
    profileUrl: 'https://api.twitter.com/1.1/account/verify_credentials.json?include_email=true',
    profile: [Function: profile],
    clientId: 'xxxx-removed-xxxx',
    clientSecret: 'xxxx-removed-xxxx',
    signinUrl: 'http://app.localhost:3000/api/auth/signin/twitter',
    callbackUrl: 'http://app.localhost:3000/api/auth/callback/twitter'
  },
  message: undefined
}

Any help or suggestions is appreciated

leerob
leerob

Hey there, sorry about this. There has been a number of issues with the Twitter API, and the number of steps to get it working, so we're going to switch to GitHub OAuth instead.

https://github.com/vercel/platforms/issues/23

Activity icon
issue

leerob issue vercel/platforms

leerob
leerob

Access control on API ?

I might be missing something, but it seems to me that the API is insecure, the api routes don’t check anything, so anyone can issue requests to delete or modify any existing content from other spaces for example.

Activity icon
issue

leerob issue comment vercel/platforms

leerob
leerob

Access control on API ?

I might be missing something, but it seems to me that the API is insecure, the api routes don’t check anything, so anyone can issue requests to delete or modify any existing content from other spaces for example.

open pull request

leerob wants to merge vercel/platforms

leerob
leerob

Secured API routes and consolidated all api routes for /post

leerob
leerob

Should postId have been removed?

pull request

leerob merge to vercel/platforms

leerob
leerob

Secured API routes and consolidated all api routes for /post

leerob
leerob

I see a get-post-data still - should we move that to a GET similar to these?

pull request

leerob merge to vercel/platforms

leerob
leerob

Secured API routes and consolidated all api routes for /post

leerob
leerob

I see a get-post-data still - should we move that to a GET similar to these?

Activity icon
issue

leerob issue comment vercel/examples

leerob
leerob

Update to all examples.

Update to all examples

Bumps all safe versions in every example/solution. Next on our todo is running an script weekly to automatize this process.

leerob
leerob

Should we close all the dependabot PRs for this one?

pull request

leerob merge to vercel/next.js

leerob
leerob

add new tailwindcss prettier plugin to example

Documentation / Examples

  • Make sure the linting passes by running yarn lint

This PR adds the new official plugin for class sorting from Tailwind Labs to the Tailwind example. Rel: https://tailwindcss.com/blog/automatic-class-sorting-with-prettier

open pull request

leerob wants to merge vercel/next.js

leerob
leerob

[Docs] Explain errors in background regeneration for ISR.

This was raised by a customer on Twitter, which made me realize there wasn't a great explanation of this in the docs.

leerob
leerob

Updated - tried to make it more clear they still have the option of manually handling the error case.

pull request

leerob merge to vercel/next.js

leerob
leerob

[Docs] Explain errors in background regeneration for ISR.

This was raised by a customer on Twitter, which made me realize there wasn't a great explanation of this in the docs.