You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 4, 2022. It is now read-only.
Hello folks,
First off, kudos to such a powerful library for analyzing the readability and seo scores.
I am currently using the yoastseo package in a react app using the Worker API as described in here: https://github.com/Yoast/javascript/blob/develop/packages/yoastseo/README.md#usage
However, I see that my bundle build size (production) is about ~2.4MB which is very large considering my requirement.
On further observation of the bundle, I noticed that the bundle includes lots of language specific code (transitionWords etc.).
Would like to understand if the following is possible:
Anything I can do to reduce the bundle size?
I currently use only few languages (en, de, es, pt, fr, it). Is there a way I can specify the bundle to include only the code for the these languages via a config param.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Explanation
Hello folks,
First off, kudos to such a powerful library for analyzing the readability and seo scores.
I am currently using the
yoastseo
package in a react app using the Worker API as described in here: https://github.com/Yoast/javascript/blob/develop/packages/yoastseo/README.md#usageHowever, I see that my bundle build size (production) is about ~2.4MB which is very large considering my requirement.
On further observation of the bundle, I noticed that the bundle includes lots of language specific code (transitionWords etc.).
Would like to understand if the following is possible:
en
,de
,es
,pt
,fr
,it
). Is there a way I can specify the bundle to include only the code for the these languages via a config param.The text was updated successfully, but these errors were encountered: