Update dependency @emotion/is-prop-valid to v1 #9
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.
This PR contains the following updates:
0.8.8→1.4.0Release Notes
emotion-js/emotion (@emotion/is-prop-valid)
v1.4.0Compare Source
Minor Changes
dfae1cbThanks @EnzoAlbornoz! - Addspopover,popoverTargetandpopoverTargetActionto the list of allowed props.v1.3.1Compare Source
Patch Changes
532ff57Thanks @codejet, @DustinBrett! - AddsfetchpriorityandfetchPriorityto the list of allowed props.v1.3.0Compare Source
Minor Changes
a1e881bThanks @sarayourfriend! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.Patch Changes
7f8db2d]:v1.2.2Compare Source
Patch Changes
0bfa9786Thanks @nnguyen01! - AddsdisableRemotePlaybackto the list of allowed props.v1.2.1Compare Source
Patch Changes
#3029
eed5e6cfThanks @Andarist! - Fixed importing in Node ESMUpdated dependencies [
eed5e6cf]:v1.2.0Compare Source
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. It limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.Patch Changes
bbad8c79]:v1.1.3Compare Source
Patch Changes
isPropValidfromPropertyKeytostringin the TypeScript definitions.v1.1.2Compare Source
Patch Changes
d2531639Thanks @andreasmcdermott! - Addedabbrprop to the allowlist of forwardable props.v1.1.1Compare Source
Patch Changes
9861a18bThanks @fabb! - AddedenterKeyHintprop to the allowlist of forwardable props.v1.1.0Compare Source
Minor Changes
f3c2e81d#2232 Thanks @ka2jun8! - Addedoption&fallbackAMP props to the list of valid props.v1.0.0Compare Source
Major Changes
923ded01#1643 Thanks @JakeGinnivan! - AllowisPropValidto take anyPropertyKeyas an argument (instead of juststring).Minor Changes
69446cb5#1971 Thanks @mjcampagna! -translategot added to the list of the valid props.Patch Changes
a085003d#1613 Thanks @Andarist! - Add missing#__PURE__annotationsConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.