-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
feat(nextjs): Inject manifest into client for webpack builds #16857
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
size-limit report 📦
|
* | ||
* @default false | ||
*/ | ||
disableManifestInjection?: boolean; |
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.
l/feel free to ignore: I generally prefer enableX
with default true
over disableX
with default false
flag patterns but not sure if there's already precedence in other options here. To me the enableX pattern is a bit more intuitive from
- a user perspective because they can switch on/off a feature without having to invert it in their mind
- a dev perspective because I don't have to invert the ifs (i.e.
if enableX doX()
).
But again, this might be just me, so happy to leave this up to you and no objections to going withdisable
here.
ref #16683
This PR injects the manifest into client bundles for webpack.