-
-
Notifications
You must be signed in to change notification settings - Fork 322
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
Fixing middleware-runtime.js error #325
Fixing middleware-runtime.js error #325
Conversation
@HT-Moh No, I'm finished, I just thought to add /server/pages/_middleware.js at the last minute, but not going to consider where eveyone might put this file so it will be up to everyone to add this line if they are using the new _middleware feature |
Lets get this merged! |
hi, when fix will be in npm release? |
Published 5.4.5 |
forgot about middleware-runtime.js.map |
After updating to 5.4.5 I still happen to experience the error, which was supposed to be fixed, however I have no idea why. Is it just me, or anyone else still encountering it? |
I actually fixed my problem by adding |
It's working fine here, hosting via ngrok, started with a fresh build using 5.4.5: 1: Delete sw.js and workbox-xxxxx.js from /public On my Android phone, I get the prompt in Chrome to add to homescreen. Not saying lighthouse is showing a false positive but don't see anything on the console.
|
@pascuflow I followed the same exact steps but stil end up with the console error : Also here is my next config file:
Anyone have any leads, insight, clue of why the exclude does not catch the "/_next/server/middleware-runtime.js.map" file ? Thanks |
Upgrade to latest version |
…error Fixing middleware-runtime.js error
Fixing this annoying middlware precaching errors that pops up.