universal-json-schema
universal-json-schema copied to clipboard
fix(deps): update dependency slate-react to v0.117.1
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| slate-react | 0.22.9 -> 0.117.1 |
Release Notes
ianstormtaylor/slate (slate-react)
v0.117.1
Patch Changes
v0.116.0
Minor Changes
- #5871
fb87646eThanks @12joan! - - Implement experimental chunking optimization (disabled by default, see https://docs.slatejs.org/walkthroughs/09-performance).- Add
useElementanduseElementIfhooks to get the current element. - BREAKING CHANGE: Decorations are no longer recomputed when a node's parent re-renders, only when the node itself re-renders or when the
decoratefunction is changed.- Ensure that
decorateis a pure function of the node passed into it. Depending on the node's parent may result in decorations not being recomputed when you expect them to be. - If this change impacts you, consider changing your
decoratefunction to work on the node's parent instead. - For example, if your
decoratefunction decorates acode-linebased on the parentcode-block's language, decorate thecode-blockinstead. - This is unlikely to result in any performance detriment, since in previous versions of
slate-react, the decorations of all siblings were recomputed when one sibling was modified.
- Ensure that
- Increase minimum
slate-domversion to0.116.0. - Deprecate the
useSlateWithVhook - PERF: Use subscribable pattern for
useSlate,useSelectedand decorations to reduce re-renders.
- Add
v0.115.0
v0.114.2
Patch Changes
v0.114.0
Minor Changes
- #5850
22a3dda3Thanks @zbeyens! - - UpdateText.decorationsto return the positions in addition to the leaf nodes:{ leaf: Text, position?: { start: number, end: number, isFirst: boolean, isLast: boolean } }[].
v0.113.0
v0.112.1
Patch Changes
- #5795
f456dfbfThanks @12joan! - Ignore selectionchange events originating from input and textarea elements (addresses Chrome bug https://issues.chromium.org/issues/389368412)
v0.112.0
Patch Changes
-
#5763
644ebdc8Thanks @TyMick! - Use extendedEditortype inuseSlateWithVreturn type -
#5741
90fbcdefThanks @AdrienPoupa! - Fix ReactEditor.toDOMRange crash in setDomSelection
v0.111.0
Minor Changes
- #5734
9a212512Thanks @bmingles! - Split out slate-dom package
v0.110.3
Patch Changes
- #5746
e97a9f88Thanks @DustinMackintosh! - Invalidate node maps when nodes change until next react paint
v0.110.2
Patch Changes
-
#5737
cd21bb1fThanks @WindRunnerMax! - fix: sync built-in state on undo when editor is unfocused -
#5727
335c5418Thanks @hernansartorio! - Call unref on pathRefs created for move_node to remove memory leak
v0.110.1
Patch Changes
v0.110.0
Minor Changes
v0.109.0
Minor Changes
v0.108.0
Minor Changes
v0.107.1
Patch Changes
- #5677
a9a70405Thanks @WindrunnerMax! - fix unexpected event triggered when usingReactEditor.focus
v0.107.0
Minor Changes
- #5676
ec9e5f0aThanks @ivan-sysoi! - Changed behaviour of ReactEditor.findDocumentOrShadowRoot. It returns shadow root or document without checking for the existence of the getSelection method.
v0.106.0
Minor Changes
- #5659
e6254f70Thanks @MahmoudElsayad! - Enable Shadow DOM fix for all Safari versions.
Patch Changes
- #5664
0016f984Thanks @12joan! - Fix:state.isDraggingInternallyis stale if a drop handler outside the editor causes the dragged DOM element to unmount
v0.105.0
Minor Changes
- #5654
2a8b4e95Thanks @alex-starostin! - Make capitalizing work for iOS
v0.104.0
Minor Changes
- #5648
0bb7be54Thanks @MahmoudElsayad! - Fix Safari selection inside Shadow DOM.
v0.102.0
Minor Changes
- #5543
3aaf3b51Thanks @mainhanu! - Transform.insertNodes & Transform.insertFragment performance optimize
v0.101.6
Patch Changes
- #5593
54594d0fThanks @12joan! - Fix: CallingReactEditor.focusdoesn't updateuseFocusedwhen running in @testing-library/react
v0.101.5
Patch Changes
- #5316
8ba3a9c0Thanks @GeneralChauhan! - Punctuation Mark "+" Support Added
v0.101.3
Patch Changes
- #5576
8ce52fd4Thanks @qirong77! - fix onCompositionEnd update error.
v0.101.2
Patch Changes
- #5567
07f59e36Thanks @timagixe! - Fix cursor position on selection collapse for RTL direction
v0.101.1
Patch Changes
- #5562
91400a8eThanks @YaoKaiLun! - Fix the 'select' parameter of the insertNodes function has been overridden
v0.101.0
Minor Changes
- #5527
fc081816Thanks @skogsmaskin! - Fixes a bug withReactEditor.focuswhere it would throw an error if the editor was in the middle of applying pending operations. With this change, setting focus will be retried until the editor no longer has any pending operations. CallingReactEditor.focuson a editor without a current selection, will now make a selection in the top of the document.
Patch Changes
-
#5549
f9cca97fThanks @12joan! - Firefox compat: Fix incorrect focus.offset when text node ends with \n
v0.100.1
Patch Changes
- #5542
8688ed5cThanks @hellsan631! - Fix Memory Leak when switching between focused editables
v0.100.0
Minor Changes
v0.99.0
Minor Changes
- #5516
300dc57aThanks @josephmr! - Retain editor selection when using ReactEditor.focus()
Patch Changes
- #5514
ff7db221Thanks @YaoKaiLun! - Fix move_node triggers nodes re-render
v0.98.4
Patch Changes
- #5510
13c7d271Thanks @e1himself! - Remove an unused React ref
v0.98.3
Patch Changes
- #5503
e308cd66Thanks @janpaepke! - bugfix: slate breaks on load on safari < 16.4
v0.98.2
Patch Changes
- #5497
76ba3759Thanks @Dimitri-WEI-Lingfeng! - fix the bug that user cannot input chinese on mac wechat browser.
v0.98.1
Patch Changes
- #5491
a5576e56Thanks @WcaleNieWolny! - Fix firefox table selection if table is contentedtiable
v0.98.0
Minor Changes
- #5486
8b548fb5Thanks @WcaleNieWolny! - Fix invalid usage of the selection API in firefox
v0.97.2
Patch Changes
-
#5462
a6b606d8Thanks @Ben-Wormald! - Update hotkeys util to use isHotkey for better support for non-latin keyboards -
#5470
4bd15ed3Thanks @josephmr! - Fix Android caret placement regression when inputting into empty editor
v0.97.1
Patch Changes
v0.97.0
Minor Changes
- #5451
12ff246eThanks @gtluszcz! - Fixed occasional crashes when selecting void elements in Chrome
Patch Changes
- #5453
cde0a155Thanks @Shiba-ligo! - fix regular expression for testing Webkit based browser.
v0.96.0
Minor Changes
- #5437
3ad13d60Thanks @josephmr! - Detect all WebKit based browsers for COMPAT behavior
Patch Changes
- #5443
eb7f5987Thanks @OldDream! - fix wrong caret position during composition.
v0.95.0
Minor Changes
-
#5422
0b179909Thanks @Chudesnov! - Prevents default focus styles from being removed in Editable -
#5421
91e388ecThanks @e1himself! - Rename<Slate>component prop fromvaluetoinitialValueto emphasize uncontrolled nature of it
v0.94.2
Patch Changes
- #5423
042bca16Thanks @horacioh! - fix placeholder position in Safari 16.x
v0.94.0
Minor Changes
-
#5307
3243c7e3Thanks @zbeyens! - New Features:- All
EditorandTransformsmethods now calleditormethods. For example:Transforms.insertBreaknow callseditor.insertBreak. editor.setNodesnow callssetNodes, an exported function that implements the default editor behavior.- You can now override
editor.setNodeswith your own implementation. - You can use either
Editor.setNodesoreditor.setNodesin your code, and both will use your overridden behavior.
The
editorobject now has many more methods:export interface BaseEditor { // Core state. children: Descendant[] selection: Selection operations: Operation[] marks: EditorMarks | null // Overrideable core methods. apply: (operation: Operation) => void getDirtyPaths: (operation: Operation) => Path[] getFragment: () => Descendant[] isElementReadOnly: (element: Element) => boolean isSelectable: (element: Element) => boolean markableVoid: (element: Element) => boolean normalizeNode: ( entry: NodeEntry, options?: { operation?: Operation } ) => void onChange: (options?: { operation?: Operation }) => void shouldNormalize: ({ iteration, dirtyPaths, operation, }: { iteration: number initialDirtyPathsLength: number dirtyPaths: Path[] operation?: Operation }) => boolean // Overrideable core transforms. addMark: OmitFirstArg<typeof Editor.addMark> collapse: OmitFirstArg<typeof Transforms.collapse> delete: OmitFirstArg<typeof Transforms.delete> deleteBackward: (unit: TextUnit) => void deleteForward: (unit: TextUnit) => void deleteFragment: OmitFirstArg<typeof Editor.deleteFragment> deselect: OmitFirstArg<typeof Transforms.deselect> insertBreak: OmitFirstArg<typeof Editor.insertBreak> insertFragment: OmitFirstArg<typeof Transforms.insertFragment> insertNode: OmitFirstArg<typeof Editor.insertNode> insertNodes: OmitFirstArg<typeof Transforms.insertNodes> insertSoftBreak: OmitFirstArg<typeof Editor.insertSoftBreak> insertText: OmitFirstArg<typeof Transforms.insertText> liftNodes: OmitFirstArg<typeof Transforms.liftNodes> mergeNodes: OmitFirstArg<typeof Transforms.mergeNodes> move: OmitFirstArg<typeof Transforms.move> moveNodes: OmitFirstArg<typeof Transforms.moveNodes> normalize: OmitFirstArg<typeof Editor.normalize> removeMark: OmitFirstArg<typeof Editor.removeMark> removeNodes: OmitFirstArg<typeof Transforms.removeNodes> select: OmitFirstArg<typeof Transforms.select> setNodes: <T extends Node>( props: Partial<T>, options?: { at?: Location match?: NodeMatch<T> mode?: MaximizeMode hanging?: boolean split?: boolean voids?: boolean compare?: PropsCompare merge?: PropsMerge } ) => void setNormalizing: OmitFirstArg<typeof Editor.setNormalizing> setPoint: OmitFirstArg<typeof Transforms.setPoint> setSelection: OmitFirstArg<typeof Transforms.setSelection> splitNodes: OmitFirstArg<typeof Transforms.splitNodes> unsetNodes: OmitFirstArg<typeof Transforms.unsetNodes> unwrapNodes: OmitFirstArg<typeof Transforms.unwrapNodes> withoutNormalizing: OmitFirstArg<typeof Editor.withoutNormalizing> wrapNodes: OmitFirstArg<typeof Transforms.wrapNodes> // Overrideable core queries. above: <T extends Ancestor>( options?: EditorAboveOptions<T> ) => NodeEntry<T> | undefined after: OmitFirstArg<typeof Editor.after> before: OmitFirstArg<typeof Editor.before> edges: OmitFirstArg<typeof Editor.edges> elementReadOnly: OmitFirstArg<typeof Editor.elementReadOnly> end: OmitFirstArg<typeof Editor.end> first: OmitFirstArg<typeof Editor.first> fragment: OmitFirstArg<typeof Editor.fragment> getMarks: OmitFirstArg<typeof Editor.marks> hasBlocks: OmitFirstArg<typeof Editor.hasBlocks> hasInlines: OmitFirstArg<typeof Editor.hasInlines> hasPath: OmitFirstArg<typeof Editor.hasPath> hasTexts: OmitFirstArg<typeof Editor.hasTexts> isBlock: OmitFirstArg<typeof Editor.isBlock> isEdge: OmitFirstArg<typeof Editor.isEdge> isEmpty: OmitFirstArg<typeof Editor.isEmpty> isEnd: OmitFirstArg<typeof Editor.isEnd> isInline: OmitFirstArg<typeof Editor.isInline> isNormalizing: OmitFirstArg<typeof Editor.isNormalizing> isStart: OmitFirstArg<typeof Editor.isStart> isVoid: OmitFirstArg<typeof Editor.isVoid> last: OmitFirstArg<typeof Editor.last> leaf: OmitFirstArg<typeof Editor.leaf> levels: <T extends Node>( options?: EditorLevelsOptions<T> ) => Generator<NodeEntry<T>, void, undefined> next: <T extends Descendant>( options?: EditorNextOptions<T> ) => NodeEntry<T> | undefined node: OmitFirstArg<typeof Editor.node> nodes: <T extends Node>( options?: EditorNodesOptions<T> ) => Generator<NodeEntry<T>, void, undefined> parent: OmitFirstArg<typeof Editor.parent> path: OmitFirstArg<typeof Editor.path> pathRef: OmitFirstArg<typeof Editor.pathRef> pathRefs: OmitFirstArg<typeof Editor.pathRefs> point: OmitFirstArg<typeof Editor.point> pointRef: OmitFirstArg<typeof Editor.pointRef> pointRefs: OmitFirstArg<typeof Editor.pointRefs> positions: OmitFirstArg<typeof Editor.positions> previous: <T extends Node>( options?: EditorPreviousOptions<T> ) => NodeEntry<T> | undefined range: OmitFirstArg<typeof Editor.range> rangeRef: OmitFirstArg<typeof Editor.rangeRef> rangeRefs: OmitFirstArg<typeof Editor.rangeRefs> start: OmitFirstArg<typeof Editor.start> string: OmitFirstArg<typeof Editor.string> unhangRange: OmitFirstArg<typeof Editor.unhangRange> void: OmitFirstArg<typeof Editor.void> }Note:
- None of these method implementations have changed.
getMarksis an exception, as there is alreadyeditor.marksthat stores the current marks.Transforms.insertTexthas not been moved toeditoryet: there is already aneditor.insertTextmethod with extended behavior. This may change in a future release, but this release is trying to avoid any breaking changes.editor.insertTexthas a new argument (third):options?: TextInsertTextOptionsto matchTransforms.insertText.
Bug Fixes:
- Moving JSDoc's to the interface type to allow IDEs access to the interface methods.
- All
Patch Changes
- #5396
bc945eb1Thanks @Moerphy! - Correct core normalization that could cause wrong nodes to be removed
v0.93.0
Minor Changes
-
#5374
b52e08b0Thanks @12joan! - - AddisSelectabletoeditor(default true). A non-selectable element is skipped over when navigating using arrow keys.- Add
ignoreNonSelectabletoEditor.nodes,Editor.positions,Editor.afterandEditor.before(default false) Transforms.moveignores non-selectable elements
- Add
-
#5374
b52e08b0Thanks @12joan! - - AddisElementReadOnlytoeditor. A read-only element behaves much like a void with regard to selection and deletion, but renders itschildrenthe same as any other non-void node.
v0.92.0
Minor Changes
-
#5363
d42cd005Thanks @aciccarello! - update dependencies on react hooks to be more senstive to changesThe code should now meet eslint react hook standards
This could result in more renders
closes #3886
Patch Changes
- #5369
556a4565Thanks @alex-vladut! - Allow copying from editable void input
v0.91.11
Patch Changes
-
#5362
43999356Thanks @jason0x43! - Fix an issue where pastes in Safari wouldn't include application/x-slate-fragment data -
#5359
9825d29bThanks @jason0x43! - Fix an issue on Android where content containing a newline wouldn't be pasted properly
v0.91.10
Patch Changes
-
#5346
a5e833f6Thanks @edhager! - Fix a problem with Editable not calling the decorate function passed as a prop when it should. -
#5343
f7f02a8bThanks @12joan! - Fix error when triple-clicking a word preceding acontenteditable="false"DOM node in Chrome
v0.91.9
Patch Changes
- #5339
62f8ddd9Thanks @12joan! - Fixes #5335. To prevent performance issues, make sure to wrap customrenderPlaceholdervalues inuseCallback.
v0.91.8
Patch Changes
-
#5325
af3f828bThanks @clauderic! - Fix edge-cases in the Android input manager when text leaf nodes are deleted, such as when deleting text leaf nodes adjacent to inline void nodes. -
#5327
4205e0f0Thanks @YasinChan! - Fix the issue of composition API and beforeinput event triggering between Chrome versions 60-75 on the Android platform.
v0.91.7
Patch Changes
v0.91.6
Patch Changes
-
#5315
5784a38bThanks @clauderic! - TheRestoreDOMmanager that is used Android no longer restores the DOM to its previous state for text mutations. This allows the editor state to be reconciled during a composition without interrupting the composition, as programatically updating thetextContentof a text node ends the current composition. -
#5315
5784a38bThanks @clauderic! - Fixed consumer definedonInputevent handler not being invoked when passed to the<Editable>component.
v0.91.5
Patch Changes
-
#5313
3bf568edThanks @edhager! - Some code clean-up in Editable. -
#5306
213edbbfThanks @clauderic! - Use memoization to avoid unnecessarytextContentupdates in<TextString>component.
v0.91.4
Patch Changes
- #5311
0ac72a62Thanks @zbeyens! - Fix #5295 regression.editor.shouldNormalizenew option:initialDirtyPathsLength: number
v0.91.3
Patch Changes
-
#5295
84f811a7Thanks @zbeyens! - Neweditormethod that can be overridden to control when the normalization should stop. Default behavior (unchanged) is to throw an error when it iterates over 42 times the dirty paths length.shouldNormalize: ({ iteration, dirtyPaths, operation, }: { iteration: number dirtyPaths: Path[] operation?: Operation }) => booleaneditor.onChangesignature change:(options?: { operation?: Operation }) => voidwhereoperationis triggering the function.editor.normalizeNodesignature change:(entry: NodeEntry, options?: { operation?: Operation }) => voidwhereoperationis triggering the function.EditorNormalizeOptionsnew optionoperation?: Operationwhereoperationis triggering the function.
v0.91.2
Patch Changes
- #5297
967d99ebThanks @edhager! - Fix memory leaks by adding clean-up code that looks for ref resets in Editable and Text.
v0.91.1
Patch Changes
- #5251
6fa4b954Thanks @YaoKaiLun! - Fix the cursor jump to an unexpected position after deleting in android
v0.91.0
Minor Changes
-
#5267
463edbd2Thanks @ilya2204! - Allow to change clipboard fragment format name -
#5271
9635b992Thanks @dsvgit! - If TextComponent decorations keep the same offsets and only paths are changed, prevent re-rendering because only decoration offsets matter when leaves are calculated.
v0.90.0
Patch Changes
- #5278
9c4097a2Thanks @kylemclean! - Revert to using inline styles for default editor styles
v0.89.0
Minor Changes
Patch Changes
- #5265
3cf51f4dThanks @kylemclean! - Improve compatibility for browsers that do not support ResizeObserver or :where selector
v0.88.2
Patch Changes
-
#5259
d7de564dThanks @Jacfem! - Updates the selection correctly in readonly shadowdom -
#5252
179d5c92Thanks @frellica! - remove qq browser frombeforeinputcompat list because it had updated its chromium core to version 94
v0.88.0
Minor Changes
- #5226
0141f683Thanks @laufeyrut! - Check if getBoundingClientRect exist before trying to call bind on it. Makes unit testing experience agains Editable nicer
v0.87.1
Patch Changes
- #5223
120437d6Thanks @alex-vladut! - Fix issue preventing editing and copy/paste into editable voids
v0.87.0
Minor Changes
- #5206
96b7fcdbThanks @kylemclean! - Use stylesheet for default styles on Editable components
v0.86.0
Patch Changes
-
#5189
fbc9838fThanks @SmilinBrian! - Add hanging option to unsetNodes so it matches setNodes -
#5193
6909a8f7Thanks @SmilinBrian! - Stops Editor.unhangRange() from adjusting the range in some cases when it was not actually hanging -
#5186
e416d00bThanks @SmilinBrian! - Report marks applied to a markableVoid if selection is collapsed
v0.83.2
Patch Changes
- #5148
a2b6786dThanks @ksimons! - Ensure the min-height for placeholders is set on the correct editor - #5155
1b14de5Thanks @jameshfisher - Revert insertText breaking change that deletes fragment
v0.83.1
Patch Changes
- #5143
347865caThanks @BitPhinix! - Fix scrollIntoView when selection is collapsed inside mark placeholder
v0.83.0
Minor Changes
- #5123
0eb37e79Thanks @laufeyrut! - Make it possible to delete block elements with backspace in Chrome and Safari
Patch Changes
- #5127
341041f0Thanks @BitPhinix! - Cleanup and fix insertion placeholder mark compare
v0.82.2
Patch Changes
-
#5120
9815bdabThanks @hueyhe! - Fix editor selection out of sync in readonly mode -
#5100
8eb1972bThanks @KittyGiraudel! - Addaria-multilineattribute to textbox editor -
#5105
55b95740Thanks @yume-chan! - ChangeElementcomponent to use callback-style ref to reliably track DOM node of rendered custom elements
v0.82.1
Patch Changes
- #5069
46d113feThanks @krenzke! - Expose getDirtyPaths method on Editor object to allow for customization
v0.82.0
Patch Changes
- #4988
fbab6331Thanks @BitPhinix! - Android input handling rewrite, replace composition insert prefixes with decoration based mark placeholders
v0.81.0
Minor Changes
- #4999
fe13a8f9Thanks @alexandercampbell! - Add new Slate.Scrubber interface to allow scrubbing end user data from exception text. The default behavior remains unchanged.
v0.80.0
Minor Changes
- #4892 [
d2fc25c3](https://redirect.github.com/ianstormtaylor
Configuration
📅 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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.
🔍 Inspect: https://vercel.com/github56/react-jsonschema-form-material-ui/7W5Z9Ceqf4VhTYAitNtsukWHMF5L
✅ Preview: https://react-jsonschema-form-material-ui-git-renovate-2be56b-github56.vercel.app
Deployment failed with the following error:
Resource is limited - try again after in 4 hours (more than 100, code: "api-deployments-free-per-day").
Deployment failed with the following error:
Resource is limited - try again after in 8 hours (more than 100, code: "api-deployments-free-per-day").
Deployment failed with the following error:
Resource is limited - try again after in 6 hours (more than 100, code: "api-deployments-free-per-day").
Deployment failed with the following error:
Resource is limited - try again after in 12 hours (more than 100, code: "api-deployments-free-per-day").
Deployment failed with the following error:
Resource is limited - try again after in 10 hours (more than 100, code: "api-deployments-free-per-day").
:warning: Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
:recycle: Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you check the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/slate
npm ERR! slate@"0.47.9" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer slate@">=0.55.0" from [email protected]
npm ERR! node_modules/slate-react
npm ERR! slate-react@"0.62.1" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /tmp/renovate-cache/others/npm/_logs/2021-05-06T00_16_14_123Z-debug.log
⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻️ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you check the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/slate
npm ERR! slate@"0.47.9" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer slate@">=0.55.0" from [email protected]
npm ERR! node_modules/slate-react
npm ERR! slate-react@"0.65.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /tmp/renovate-cache/others/npm/_logs/2021-06-01T20_13_52_177Z-debug.log
Deployment failed with the following error:
Resource is limited - try again after in 13 hours (more than 100, code: "api-deployments-free-per-day").
Deployment failed with the following error:
Resource is limited - try again after in 2 hours (more than 100, code: "api-deployments-free-per-day").
Deployment failed with the following error:
Resource is limited - try again after in 2 minutes (more than 100, code: "api-deployments-free-per-day").
Deployment failed with the following error:
Resource is limited - try again after in 4 seconds (more than 100, code: "api-deployments-free-per-day").
Deployment failed with the following error:
Resource is limited - try again after in 29 seconds (more than 100, code: "api-deployments-free-per-day").
Deployment failed with the following error:
Resource is limited - try again after in 37 minutes (more than 100, code: "api-deployments-free-per-day").
Deployment failed with the following error:
Resource is limited - try again after in 1 hour (more than 100, code: "api-deployments-free-per-day").
Deployment failed with the following error:
Resource is limited - try again after in 16 hours (more than 100, code: "api-deployments-free-per-day").
⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/slate
npm ERR! slate@"0.47.9" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer slate@">=0.65.3" from [email protected]
npm ERR! node_modules/slate-react
npm ERR! slate-react@"0.70.2" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /tmp/renovate-cache/others/npm/_logs/2021-11-21T20_06_18_219Z-debug.log
Codecov Report
Merging #159 (0d3d3ee) into main (ea88d30) will not change coverage. The diff coverage is
n/a.
@@ Coverage Diff @@
## main #159 +/- ##
=======================================
Coverage 85.05% 85.05%
=======================================
Files 66 66
Lines 1619 1619
Branches 570 570
=======================================
Hits 1377 1377
Misses 237 237
Partials 5 5
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update ea88d30...0d3d3ee. Read the comment docs.
Deployment failed with the following error:
Resource is limited - try again after in 18 hours (more than 100, code: "api-deployments-free-per-day").
Deployment failed with the following error:
Resource is limited - try again after in 23 minutes (more than 100, code: "api-deployments-free-per-day").
Deployment failed with the following error:
Resource is limited - try again after in 15 hours (more than 100, code: "api-deployments-free-per-day").
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| react-jsonschema-form-material-ui | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Feb 7, 2024 0:33am |
Deployment failed with the following error:
Resource is limited - try again in 1 hour (more than 100, code: "api-deployments-free-per-day").
Deployment failed with the following error:
Resource is limited - try again in 7 hours (more than 100, code: "api-deployments-free-per-day").
Deployment failed with the following error:
Resource is limited - try again in 9 hours (more than 100, code: "api-deployments-free-per-day").
Deployment failed with the following error:
Resource is limited - try again in 8 hours (more than 100, code: "api-deployments-free-per-day").