-
-
Notifications
You must be signed in to change notification settings - Fork 338
Allows all PWA options to work #372
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
Conversation
theoludwig
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! 👍
Thanks, it solves the issue.
Just tested by manually editing my node_modules. 😄
|
Just subscribing so i know when this is merged. Having th same issue |
|
Just subscribing to know when this will merge, because having same issue |
digitaluprising
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
PicchiKevin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
I did the same test and it worked 😄 i'm using |
|
Just subscribing to know when this will merge |
|
+1 to changes in source code working via manual change to my node_modules |
d-strygwyr
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM !
|
For me, #381 is more the next.js way to fix it. |
I agree with this. #381 on the other hand is dealing with the config how next.js intented it (at least thats how I understood the next.js changes that lead to the situation we are in now) I suggest to merge #381 instead of this PR here. |
|
Having same issue, subscribing |
|
LGTM |
|
OK, I have read through the discussions and code changes in these PRs:
I will take this PR as it's minimal change and doesn't include format changes, will release a patch version Beside will make a new breaking change and release version |
In release 5.5.5 the disable option was broken. This fixes the option and allows it to work again.
Edit: Turns out all of the options specified do not work in 5.5.5. This should fix this.
Resolves: #371
Resolves: #370
Resolves: #378