Put the favicons in an /image directory inside the /public directory and put the code below in your _app.js <Head> <link rel=”shortcut icon” href=”/images/favicon.ico” /> <link rel=”apple-touch-icon” sizes=”180×180″ href=”/images/apple-touch-icon.png” /> <link rel=”icon” type=”image/png” sizes=”32×32″ href=”/images/favicon-32×32.png”/> <link rel=”icon” type=”image/png” sizes=”16×16″ href=”/images/favicon-16×16.png”/> </Head>
I think, this might have to do with this weird hackfix that is being touted in a bunch of places that tells you to place next/babel in your eslint config file for some reason (e.g. here). It probably was a hackfix for an old bug in older next.js versions. But as of (at least) summer … Read more
Go to Project Settings Change Framework preset from Other to Next.js Redeploy the project.
Add a vercel.json file at the root of your project, and use “rewrites” to rewrite all incoming paths to refer to your index path. For example: { “rewrites”: [ {“source”: “/(.*)”, “destination”: “/”} ] } Check here for further information: https://vercel.com/docs/configuration#project/rewrites
This answer worked for me: https://stackoverflow.com/a/55541435/3051080 TL;DR; update git cache: git rm -r –cached . git add –all . git commit -a -m “Versioning untracked files” git push origin master
I ran into the same error a few days back. A few Points I would want to clarify: Build happens as per the pages and URLs of the browser. If you are seeing something like Export encountered errors on following paths: /about Then you should copy “/about” and paste it in front of the current … Read more
We started experiencing this issue on our build server without making significant changes last week and have not managed to find a fix yet but there are a few issues that have been created of other teams experiencing sudden issues related to this error. Check out this issue on the React GitHub page and this … Read more
I had the same issue where puppeteer was running okay on my local environment but when i deployed to AWS EC2 i face up the same error shared loading libraries Solution First check the version of nodejs you are running and if its not less than v14.0 or greater than v14.0. Upgrade or downgrade (recommended … Read more
use akamai setting images.loader to ‘imgix’ caused dev and build errors. i used this instead: // next.config.js module.exports = { images: { loader: ‘akamai’, path: ”, }, } it just works for all i care about. possible values for images.loader are: [ default, imgix, cloudinary, akamai, custom ] reference: https://nextjs.org/docs/api-reference/next/image#built-in-loaders