Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Link Fash Refresh warning to codemod #16495

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.

Sign up for GitHub

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

Jump to bottom
Closed
lfades opened this issue Aug 23, 2020 · 1 comment · Fixed by #16496
Closed

Link Fash Refresh warning to codemod #16495

lfades opened this issue Aug 23, 2020 · 1 comment · Fixed by #16496
Assignees
@lfades
Labels
type: next
Milestone
iteration 8

Comments

@lfades
Copy link
Member

lfades commented Aug 23, 2020 •
edited
Loading

Update the Fast Refresh warning to include a link to the next-codemod: https://nextjs.org/docs/advanced-features/codemods#name-default-component
@lfades lfades self-assigned this Aug 23, 2020
@lfades lfades changed the title Update Fash Refresh warning Link Fash Refresh warning to codemod Aug 23, 2020
@lfades lfades mentioned this issue Aug 23, 2020
Merged
@kodiakhq kodiakhq bot closed this as completed in #16496 Aug 24, 2020
kodiakhq bot pushed a commit that referenced this issue Aug 24, 2020
@lfades
Update Fast Refresh warning (#16496)
735aab6 
Fixes #16495

Terminal:

![image](https://user-images.githubusercontent.com/4278345/90984442-96421b00-e53a-11ea-9939-44b00cba87cf.png)

Browser: 

![image](https://user-images.githubusercontent.com/4278345/90984456-a9ed8180-e53a-11ea-86da-d9f28e9c2fdd.png)

The link https://nextjs.link/codemod-ndc used for the warning links to a currently 404 docs page, that will be available in the next stable release.

Tests not added as the warning has tests already.
@Timer Timer added this to the iteration 8 milestone Aug 24, 2020
@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@lfades lfades

Labels
type: next
Projects
None yet
Milestone
iteration 8
Development

Successfully merging a pull request may close this issue.

Update Fast Refresh warning vercel/next.js
3 participants
@Timer @lfades @balazsorban44