Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

with-stripe-typescript has a typo: Unhhandled #56273

Closed
1 task done
hamirmahal opened this issue Oct 1, 2023 · 1 comment · Fixed by #56274
Closed
1 task done

with-stripe-typescript has a typo: Unhhandled #56273

hamirmahal opened this issue Oct 1, 2023 · 1 comment · Fixed by #56274
Labels
examples Issue/PR related to examples locked

Comments

@hamirmahal
Copy link
Contributor

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

$  npx --no-install next info

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Fri Jan 27 02:56:13 UTC 2023
Binaries:
  Node: 18.18.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 13.5.3
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.6
Next.js Config:
  output: N/A


warn  - Latest canary version not detected, detected: "13.5.3", newest: "13.5.4-canary.8".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue

Which example does this report relate to?

with-stripe-typescript

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Describe the Bug

unhandled is spelled incorrectly.

Expected Behavior

unhandled is spelled correctly.

To Reproduce

See

throw new Error(`Unhhandled event: ${event.type}`)
.

@hamirmahal hamirmahal added the examples Issue/PR related to examples label Oct 1, 2023
@kodiakhq kodiakhq bot closed this as completed in #56274 Oct 2, 2023
kodiakhq bot pushed a commit that referenced this issue Oct 2, 2023
@github-actions
Copy link
Contributor

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
examples Issue/PR related to examples locked
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant