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

Fixed no-img-element documentation snippet. #26154

Merged
merged 1 commit into from Jun 16, 2021
Merged

Fixed no-img-element documentation snippet. #26154

merged 1 commit into from Jun 16, 2021

Conversation

IvanKalinin
Copy link
Contributor

@IvanKalinin IvanKalinin commented Jun 16, 2021

Module "next/image" has no exported member 'Image'.
It must be import Image from "next/image"

Bug

  • Related issues linked using fixes #number
  • Integration tests added

Feature

  • Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
  • Related issues linked using fixes #number
  • Integration tests added
  • Documentation added
  • Telemetry added. In case of a feature if it's used or not.

Documentation / Examples

  • Make sure the linting passes

Module "next/image" has no exported member 'Image'.
It must be `import Image from "next/image"`
@timneutkens timneutkens merged commit c851da2 into vercel:canary Jun 16, 2021
@timneutkens
Copy link
Member

Thanks!

flybayer pushed a commit to blitz-js/next.js that referenced this pull request Jun 24, 2021
Module "next/image" has no exported member 'Image'.
It must be `import Image from "next/image"`
@vercel vercel locked as resolved and limited conversation to collaborators Jan 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants