next-seo
next-seo copied to clipboard
Tree Shaking Support
Hello! I'd like to import NextSEO
into my project without including all of the JSON LD functions I'm not using. At the moment next-seo
is taking up a significant amount of my bundle size for all pages.
I tried following @joeyorlando's steps here: https://github.com/garmeeh/next-seo/issues/75#issuecomment-705152810, to no avail. Is there a supported way to implement tree shaking?
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Yep! I'd love a response to understand if anyone has had any luck tree shacking the JSON LD code from next-seo
.
Couldn't get any of the steps working either, so +1
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Definitely still relevant!
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Definitely still relevant!
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Still relevant 💯
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Definitely still relevant!
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Yes! still relevant. Maybe migrating to webpack 5 would help here? I'm not sure.
Should this be re-opened? It's still relevant.
Yes apologies @schlosser. I need to disable stale bot 🤦♂️
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Still relevant!
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Is this still relevant?
Yep
hi @garmeeh , thanks for this great library,
have you tried already setting "sideEffects": false,
in the package.json
?
assuming there are no sideEffects that would help I guess, otherwise you can list those files which do have sideEffects in an array,
see webpack docs
cheers
I'm also interested in tree shaking support.
Yeah, same! It'd be really useful to have tree shaking support.