Releases: birdofpreyru/react-helmet
v3.1.0
v3.0.6
Contributors
Assets 2
v3.0.5
- [#11][#12] Fixes
prioritizeSeoTagsfeature support on the front-end side. - Update of dependencies.
v3.0.4
v3.0.3
v3.0.2
-
New: MetaTags component — a helper for easier rendering of page title, description, and meta-data (Open Graph, Twitter (X) Cards) for search engines, and social graphs (i.e. previews of linked pages in social networks, messengers, etc.).
-
Update of dependencies.
v3.0.1
- Update of dependencies.
v3.0.0
Beware
Entire library codebase, and its build setup have been heavily refactored for this release. While the aim was to keep API and behavior of the library unchanged (with exception of a few points listed below), and the refactored library passes the original unit tests, assume some nuances may have been overlooked, be vigilant, report any issues.
Breaking Changes
-
Removed
HelmetDataclass, and the possibility to use<Helmet>components without context. You must use<Helmet>components within a sub-tree of<HelmetProvider>, there is no excuse to do it differently, and the legacy implementation of that possibility led to (a) over-complicated code, (b) some nuanced differences in the actual library behavior when the same<Helmet>component was used within or without<HelmetProvider>context; thus, it just was not a good library design to have it. -
Removed
canUseDOMfield ofHelmetProviderexport. It was not necessary; from this version if the library detects DOM in the environment, it will operate on its<head>, and ifcontextis provided to<HelmetProvider>, it will be populated with methods necessary for server-side rendering (or other purposes you may need it for). Both may have work simultaneously, no real need to switch between them exclusively. -
Requires all attributes of managed head elements to be valid JSX props. The legacy implementation required to use HTML attribute names (
accesskey,charset,class,contenteditable,contextmenu,http-equiv,itemprop,tabindex) instead of the corresponding JSX props (accessKey,charSet,className,contentEditable,contextMenu,httpEquiv,itemProp,tabIndex). If you use TypeScript, correctly configured, it should highlight all these wrong attribute names as errors, making it easy to replace them. Otherwise, for now, the runtime actually supports both old (attribute names) and new (JSX props) for these correctly, and it prints warning messages to console about the need to replace them. The plan is to drop support of old attribute names in future releases.
v2.0.4
- Initial release.