Repository navigation
chore(release): v3.1.0 - #279
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Merging this publishes react-helmet-async@3.1.0 to npm and creates the v3.1.0 GitHub release with these notes.
Added
react-helmet-async/package.jsonresolves again. Theexportsmap added in 3.0.0 had left it out.Changed
<Helmet>instances are merged again, as on React 16–18: the innermost<title>wins and uses the nearesttitleTemplateanddefaultTitle, and a tag that several<Helmet>s set, such as<meta name="description">, renders once, from the innermost one. Server rendering still outputs every<Helmet>'s tags, because instances only merge once they mount, and when hydrating React reuses only the first server-rendered<title>, so a second one stays in<head>.prioritizeSeoTags,<meta charset>moves fromhelmet.metato the start ofhelmet.priority, because browsers only honor a charset declared within the first 1024 bytes of the document. A template that printshelmet.metabut nothelmet.priorityno longer outputs it.<Helmet>throws for invalid children or a missing<HelmetProvider>are plainErrors, namedErrorinstead ofInvariant Violation.Removed
invariantandshallowequaldependencies.Fixed
<Helmet>with no<HelmetProvider>above it and nohelmetDataprop throws<Helmet> must be rendered inside a <HelmetProvider> or be given a helmetData prop. If it is, check that only one copy of react-helmet-async is bundled.instead ofTypeError: Cannot read properties of undefined (reading 'add').meta,link,script,styleandnoscriptprops that use React attribute names such asitemProp,charSetorhttpEquivare no longer dropped. Their React names are written as HTML attribute names, as for JSX children, sohttpEquivbecomeshttp-equivandclassNamebecomesclassin the DOM and intoString().<link>,<meta>,<noscript>,<script>and<style>tags inside a fragment are no longer dropped when<Helmet>has more than one fragment, or a fragment next to a tag of the same type.onLoadare attached as event handlers instead of being written as attributes that contain the function's source, andtoString()leaves them out. Handlers receive the nativeEvent, not a React synthetic event.lib/index.jsandlib/index.esm.jsare compiled to ES2018, so webpack 4, which Create React App 3 and 4 use, can parse them. Since 2.0.0 they contained class fields and optional chaining.deferon (the default), changes made while the tab is in the background are applied within about a second instead of when the tab is shown again.<base>with only atargetattribute is no longer dropped. The HTML spec allowshref,target, or both.Full changes: ba5d5fb...v3.1.0