I am getting an error due to a update.hot-update.json
Unanswered
hermann17. posted this in #help-forum
So I build an app with next.js with the command npx create-next-app --template typescript.
I provided a name, set use typescript, use ESlint, Tailwind, use 'src/ directory', App Router, and no to import alias.
I aditionally added sanity to the project to have a cms part of the app.
My next configuration:
const nextConfig = {
images: {
remotePatterns: [
{
protocol: "https",
hostname: "lh3.googleusercontent.com"
},
{
protocol: "https",
hostname: "images.unsplash.com"
}
]
},
};
module.exports = nextConfig;
I am having a bug but not understanding exactly where it comes from.
The apps runs but if I access now the dev tools it crashes.
I get from the network tab: http://localhost:3000/_next/static/webpack/18c05b7f4eb7b7fc.webpack.hot-update.json
I have node v: 18.17.0
next v: ^14.2.5
I previously was using another version, but the log was requireing me to update node and next.
I have previously tried to check whether it is an issue related to the node_modules, but after removing the folder and reinstalling it I did not see any change. Deleting the .next folder has not helped much, I found out that perhaps the cache might have been related.
Anyhow at this point I am not sure what would be required for the bug I am facing.
Any thoughts?
I provided a name, set use typescript, use ESlint, Tailwind, use 'src/ directory', App Router, and no to import alias.
I aditionally added sanity to the project to have a cms part of the app.
My next configuration:
const nextConfig = {
images: {
remotePatterns: [
{
protocol: "https",
hostname: "lh3.googleusercontent.com"
},
{
protocol: "https",
hostname: "images.unsplash.com"
}
]
},
};
module.exports = nextConfig;
I am having a bug but not understanding exactly where it comes from.
The apps runs but if I access now the dev tools it crashes.
I get from the network tab: http://localhost:3000/_next/static/webpack/18c05b7f4eb7b7fc.webpack.hot-update.json
I have node v: 18.17.0
next v: ^14.2.5
I previously was using another version, but the log was requireing me to update node and next.
I have previously tried to check whether it is an issue related to the node_modules, but after removing the folder and reinstalling it I did not see any change. Deleting the .next folder has not helped much, I found out that perhaps the cache might have been related.
Anyhow at this point I am not sure what would be required for the bug I am facing.
Any thoughts?