Skip to content

chore(deps): bump next from 16.2.2 to 16.2.3 in /templates/nextjs-app #4258

chore(deps): bump next from 16.2.2 to 16.2.3 in /templates/nextjs-app

chore(deps): bump next from 16.2.2 to 16.2.3 in /templates/nextjs-app #4258

Triggered via pull request April 13, 2026 06:44
Status Success
Total duration 1m 1s
Artifacts

examples.yml

on: pull_request
Matrix: examples
Matrix: patterns
Matrix: templates
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
templates (nextjs-pages): templates/nextjs-pages/pages/index.tsx#L9
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
templates (nextjs-pages): templates/nextjs-pages/eslint.config.mjs#L8
'__dirname' is assigned a value but never used
examples (nextjs-pages): examples/nextjs-pages/eslint.config.mjs#L8
'__dirname' is assigned a value but never used
examples (nextjs-app): examples/nextjs-app/eslint.config.mjs#L8
'__dirname' is assigned a value but never used
templates (nextjs-app): templates/nextjs-app/eslint.config.mjs#L8
'__dirname' is assigned a value but never used
templates (nextjs-app): templates/nextjs-app/app/page.tsx#L9
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