Skip to content

Fix Copy Markdown button 500 error on docs pages #150

Fix Copy Markdown button 500 error on docs pages

Fix Copy Markdown button 500 error on docs pages #150

Re-run triggered February 1, 2026 13:40
Status Success
Total duration 32s
Artifacts

lint.yml

on: pull_request
Run ESLint and Prettier
26s
Run ESLint and Prettier
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
Run ESLint and Prettier: src/components/user/Showcase.tsx#L48
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
Run ESLint and Prettier: src/app/docs/layout.tsx#L12
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
Run ESLint and Prettier: src/app/(home)/page.tsx#L805
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
Run ESLint and Prettier: src/app/(home)/page.tsx#L781
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
Run ESLint and Prettier: src/app/(home)/page.tsx#L676
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
Run ESLint and Prettier: src/app/(home)/page.tsx#L424
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
Run ESLint and Prettier: postcss.config.mjs#L1
Assign object to a variable before exporting as module default