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 }}
Repository navigation
fix(deps): update dependency react-live to v5 - #3747
#416b8bf7a0 - Fix the standalone Editor losing focus after the first keystroke. use-editable rebuilt its editing surface on the first edit's re-render, which reset contentEditable and dropped focus; Editor now settles that surface before it can be edited.
#418be53ccd - Support React 19 type definitions, add an exports map, drop engines, and raise the
output target.
LivePreview's overloads referenced the global JSX namespace, which @types/react@19
removed. Because those types are emitted into the published declarations, consumers on React
19 types failed to compile. They now use React.JSX, which resolves under both @types/react@18 and @types/react@19.
The package also gains an exports map with separate types for the ESM and CJS conditions.
Filenames are unchanged from 4.1.x (dist/index.js, dist/index.mjs, dist/index.d.ts), so main, module, and types resolve exactly as before. Subpaths other than ./package.json are no longer importable; only the package root was ever documented.
Output is now built for es2022 rather than es6, so the bundle may contain syntax such as
optional chaining that previous releases transpiled away.
The engines field is gone, along with the node: ">= 0.12.0" and npm: ">= 2.0.0" it
declared. Both were years out of date, and neither constrained anything real: this is browser
code, so the Node version that installs it has no bearing on whether it runs. npm will no
longer print an engine warning against those bounds.
None of this changes the public API -- same exports, same props, same react >=18 peer
range -- but the exports map and the raised output target are enough that a major release
is the honest way to ship them.
#421004b007 - Type the live prop that withLive injects, instead of Record<string, unknown>.
Wrapped components saw unknown for every key, so live.element could not be
rendered and live.error could not be read without casting first. The prop now
uses the same type the context is created with, which is the shape the docs
have always described: code, error, element, onError, onChange.
constPanel=withLive(({ live })=>{constResult=live.element;// was `unknown`, now a componentreturnResult ? <Result/> : <pre>{live.error}</pre>;});
Types only, with no runtime change. It is a narrowing, so a wrapped component
that reads a key outside that shape off live will now fail to compile.
Patch Changes
#418be53ccd - Forward the Editorprism prop to prism-react-renderer. It was typed but never passed through, so a custom Prism instance was silently ignored.
#418be53ccd - Stop emitting React's __self and __source debug props from transpiled code.
Sucrase adds these props to every element it compiles. They describe a source file, and there
is no source file here -- the code comes from a live editor rather than from disk, so the
filename sucrase emitted was always the empty string. React ignores both props, and React 19
additionally treats __self as the signature of an outdated JSX transform, logging
"Your app (or one of its dependencies) is using an outdated JSX transform" to the console of
every page rendering a LiveProvider.
Transpiling with sucrase's production option drops both props, and with them the _jsxFileName constant that the transform pipeline used to splice out and re-add solely to
keep __source resolvable.
#418be53ccd - Add getDerivedStateFromError to the internal error boundary, so a runtime error in live code no longer logs a React warning about it.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
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
dependenciesPull requests that update a dependency file
1 participant
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.
![renovate-approve[bot]](https://avatars.githubusercontent.com/in/7394?s=60&v=4){kind=small}
This PR contains the following updates:
^3.2.0→^5.0.0Release Notes
FormidableLabs/react-live (react-live)
v5.0.1Compare Source
Patch Changes
b8bf7a0- Fix the standaloneEditorlosing focus after the first keystroke.use-editablerebuilt its editing surface on the first edit's re-render, which resetcontentEditableand dropped focus;Editornow settles that surface before it can be edited.v5.0.0Compare Source
Major Changes
#418
be53ccd- Support React 19 type definitions, add anexportsmap, dropengines, and raise theoutput target.
LivePreview's overloads referenced the globalJSXnamespace, which@types/react@19removed. Because those types are emitted into the published declarations, consumers on React
19 types failed to compile. They now use
React.JSX, which resolves under both@types/react@18and@types/react@19.The package also gains an
exportsmap with separate types for the ESM and CJS conditions.Filenames are unchanged from 4.1.x (
dist/index.js,dist/index.mjs,dist/index.d.ts), somain,module, andtypesresolve exactly as before. Subpaths other than./package.jsonare no longer importable; only the package root was ever documented.Output is now built for
es2022rather thanes6, so the bundle may contain syntax such asoptional chaining that previous releases transpiled away.
The
enginesfield is gone, along with thenode: ">= 0.12.0"andnpm: ">= 2.0.0"itdeclared. Both were years out of date, and neither constrained anything real: this is browser
code, so the Node version that installs it has no bearing on whether it runs. npm will no
longer print an engine warning against those bounds.
None of this changes the public API -- same exports, same props, same
react >=18peerrange -- but the
exportsmap and the raised output target are enough that a major releaseis the honest way to ship them.
#421
004b007- Type theliveprop thatwithLiveinjects, instead ofRecord<string, unknown>.Wrapped components saw
unknownfor every key, solive.elementcould not berendered and
live.errorcould not be read without casting first. The prop nowuses the same type the context is created with, which is the shape
the docs
have always described:
code,error,element,onError,onChange.Types only, with no runtime change. It is a narrowing, so a wrapped component
that reads a key outside that shape off
livewill now fail to compile.Patch Changes
#418
be53ccd- Forward theEditorprismprop toprism-react-renderer. It was typed but never passed through, so a custom Prism instance was silently ignored.#418
be53ccd- Stop emitting React's__selfand__sourcedebug props from transpiled code.Sucrase adds these props to every element it compiles. They describe a source file, and there
is no source file here -- the code comes from a live editor rather than from disk, so the
filename sucrase emitted was always the empty string. React ignores both props, and React 19
additionally treats
__selfas the signature of an outdated JSX transform, logging"Your app (or one of its dependencies) is using an outdated JSX transform" to the console of
every page rendering a
LiveProvider.Transpiling with sucrase's
productionoption drops both props, and with them the_jsxFileNameconstant that the transform pipeline used to splice out and re-add solely tokeep
__sourceresolvable.#418
be53ccd- AddgetDerivedStateFromErrorto the internal error boundary, so a runtime error in live code no longer logs a React warning about it.v4.1.8Compare Source
What's Changed
Documentation Changes
New Contributors
Full Changelog: https://github.com/FormidableLabs/react-live/compare/react-live@4.1.7...react-live@4.1.8
v4.1.7Compare Source
Patch Changes
v4.1.6Compare Source
Patch Changes
v4.1.5Compare Source
Patch Changes
v4.1.4Compare Source
Patch Changes
v4.1.3Compare Source
Patch Changes
v4.1.2Compare Source
Patch Changes
v4.1.1Compare Source
Patch Changes
v4.1.0Compare Source
Minor Changes
Patch Changes
v4.0.1Compare Source
Patch Changes
v4.0.0Compare Source
Major Changes
Configuration
📅 Schedule: (UTC)
* 0-4,22-23 * * 1-5)* * * * 0,6)🚦 Automerge: Enabled.
♻ 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.