Closed cherylli closed 1 year ago
Name | Link |
---|---|
Latest commit | 5e649fcb8ff463387e03706e1ac060a4756eb433 |
Latest deploy log | https://app.netlify.com/sites/priceless-booth-2dfcaf/deploys/646edf0ee7ad370008214a78 |
Deploy Preview | https://deploy-preview-170--priceless-booth-2dfcaf.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
Great job, @cherylli ! The warning is gone on my end! 🎉
When you go to the blog page, do you also see this error related to the Tag styling? I wonder if it's caused by the missing styled-components options we're removing.
Now I remember why we need the styled-components in the config, it's needed for SSR mostly which we use in the blog page. I might try to use another way so we don't see the warning
it should run without error now but when/if we ever going to migrate to the new next.js app structure, we might have to redo this again, as they have another method in the beta docs
Have you updated the CHANGELOG.md file? If not, please do it.
yes
What is this change?
fix invalid next.config.js warnings due to changes in a newer next.js version
Were there any complications while making this change?
no
How did you verify this change?
run locally
When should this be merged?
after review