updates to fix netlify website build errors #4044
dylansAnnotations
12 errors and 10 warnings
|
lint:eslint:
packages/slate-react/src/components/editable.tsx#L138
Component definition is missing display name
|
|
lint:eslint:
packages/slate-react/src/components/text.tsx#L27
React Hook "useSlateStatic" may be executed more than once. Possibly because it is called in a loop. React Hooks must be called in the exact same order in every component render
|
|
lint:eslint:
packages/slate-react/src/components/text.tsx#L28
React Hook "useRef" may be executed more than once. Possibly because it is called in a loop. React Hooks must be called in the exact same order in every component render
|
|
lint:eslint:
packages/slate/test/interfaces/Editor/above/block-highest.tsx#L20
Missing "key" prop for element in array
|
|
lint:eslint:
packages/slate/test/interfaces/Editor/above/block-lowest.tsx#L22
Missing "key" prop for element in array
|
|
lint:eslint:
packages/slate/test/interfaces/Editor/above/inline.tsx#L21
Missing "key" prop for element in array
|
|
lint:eslint:
packages/slate/test/interfaces/Editor/above/point.tsx#L18
Missing "key" prop for element in array
|
|
lint:eslint:
packages/slate/test/interfaces/Editor/above/range.tsx#L26
Missing "key" prop for element in array
|
|
lint:eslint:
packages/slate/test/interfaces/Editor/levels/match.tsx#L22
Missing "key" prop for element in array
|
|
lint:eslint:
packages/slate/test/interfaces/Editor/levels/match.tsx#L27
Missing "key" prop for element in array
|
|
test:integration
The job was canceled because "lint_eslint" failed.
|
|
test:integration
The operation was canceled.
|
|
lint:eslint:
packages/slate-dom/src/utils/hotkeys.ts#L72
Assign object to a variable before exporting as module default
|
|
lint:eslint:
site/examples/js/images.jsx#L83
Image elements must have an alt prop, either with meaningful text, or an empty string for decorative images
|
|
lint:eslint:
site/examples/js/images.jsx#L102
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
lint:eslint:
site/examples/js/images.jsx#L102
img elements must have an alt prop, either with meaningful text, or an empty string for decorative images
|
|
lint:eslint:
site/examples/js/paste-html.jsx#L177
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
lint:eslint:
site/examples/js/paste-html.jsx#L177
img elements must have an alt prop, either with meaningful text, or an empty string for decorative images
|
|
lint:eslint:
site/examples/ts/images.tsx#L96
Image elements must have an alt prop, either with meaningful text, or an empty string for decorative images
|
|
lint:eslint:
site/examples/ts/images.tsx#L117
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
lint:eslint:
site/examples/ts/images.tsx#L117
img elements must have an alt prop, either with meaningful text, or an empty string for decorative images
|
|
lint:eslint:
site/examples/ts/paste-html.tsx#L200
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|