fix(deps): update dependencies (non-major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@codesandbox/sandpack-react	^1.17.0 -> ^1.17.1
@types/node (source)	^18.11.9 -> ^18.11.10
@types/react (source)	^18.0.25 -> ^18.0.26
eslint-config-next	^13.0.5 -> ^13.0.6
framer-motion	^7.6.12 -> ^7.6.18

---

Release Notes

codesandbox/sandpack

v1.17.1

Compare Source

Bug Fixes

• vue template: support script setup template (#​648) (1ffb205)

vercel/next.js

v13.0.6

Compare Source

Core Changes

• test(integration): allow to run --turbo dev server tests dynamically : #​42967
• Ensure loaderFile is included in webpack cache key: #​43315
• Improve @​next/font error handling: #​43298
• Improve RSC plugin to provide better errors: #​42435
• fix appDir returning 404 in production with "output": "standalone": #​43268
• Fix outputting un-necessary trace files for edge functions: #​43304
• fix: apply default export interop to pages/_app: #​43335
• Fix package resolution issue in app dir: #​43349
• Get correct chunks in flight-manifest on Windows: #​43334
• Resolve RSC / HTML rendering errors in error overlay: #​43332
• App directory next/link dynamic href dev error: #​43074
• Add ref forwarding for next/image: #​43193
• Always transform styled-jsx for rsc and error with client-only condition: #​43386
• dynamic = 'error' should only throw if page didn't get exported: #​43377
• fix output: "standalone" returning 500 error on certain pages when built without pages/: #​43336
• Fix "apply() is only allowed in ready status (state: idle)" HMR errors: #​43242
• Add gSP and gSSP checks for both server and client layers in the SWC transform: #​43391
• Make sure the TS plugin works for src/app: #​43412
• Remove stack trace from full reload warning: #​43453
• Upgrade compiled undici: #​43481
• Fix missing cleanup process in flight plugin globals: #​43297
• Fix matchers in middleware manifest: #​43549
• rsc: bundle legacy head as client component: #​43425
• Remove useState from next/image: #​43587
• Group redirect status imports: #​43480
• Fix Failed to copy traced files for Edge functions and handle its files with middleware-manifest.json: #​43326
• Update next/link default legacyBehavior: #​42623
• fix: Dynamic Usage Error when using previewData with generateStaticParams and appDir: #​43395
• Minimized runtime errors in app dir: #​43511

Documentation Changes

• Add link back to font video in Font docs.: #​43440
• docs: update known Safari bug: #​43513
• Add yarn berry dependency upgrade example for Next 12 to 13 upgrade documentation.: #​43472
• Clarify that publicRuntimeConfig and serverRuntimeConfig do not work with Output File Tracing: #​43443
• adding note that edge api routes are not supported with ISR: #​43572
• Improve docs for URL Imports: #​43615

Example Changes

• chore(examples): Deprecate cms-strapi: #​43325
• Add example commands for creating reproductions: #​43375
• updates with-supertokens example: #​43379
• Fix with-docker-compose example: #​43419
• chore(examples): fix CLI commands for MobX examples: #​43534
• Simplify and convert with-vercel-fetch example to TypeScript: #​43403
• chore(examples): reference main prop in README.md in Firebase example: #​43434
• chore(examples): Update active-class-name example: #​43581
• Fix deploy button in with-xata example: #​43608

Misc Changes

• Avoid turbo cache miss on root package change: #​43309
• Add .pnpm-store to .gitignore: #​43366
• Update @​next/font/google fonts: #​43385
• Catch errors when calculating avg font width: #​43503
• chore: update issue verifier: #​43339
• chore: fix issue validator
• chore: move comments of issue validator
• chore: hardcode path for issue validator
• chore: add area dropdown to bug report template: #​43228
• chore: fix issue verifier issues
• Merge branch 'canary' of https://github.com/vercel/next.js into canary
• chore: fix issue verifier
• chore: don't comment twice
• chore: disable auto-labeling
• Fix "infer pnpm with example" test outside test suite: #​43487
• chore: add issue labeler: #​43599
• chore: fix issue labeler: #​43606
• Changed output mode on app directory test application: #​43607
• Fix output: standalone test for app directory: #​43618

Credits

Huge thanks to @​kwonoj, @​hanneslund, @​ijjk, @​shuding, @​DuCanhGH, @​chibicode, @​artechventure, @​JanKaifer, @​huozhi, @​colinking, @​rishabhpoddar, @​maxproske, @​wyattjoh, @​leerob, @​alantoa, @​Haschikeks, @​balazsorban44, @​matthew-heath, @​AaronJY, @​dtinth, @​styfle, @​leoortizz, @​ValentinH, @​brvnonascimento, @​joshuaslate, @​SferaDev, and @​timeyoutakeit for helping!

framer/motion

v7.6.18

Compare Source

Changed

• Removed popmotion as external dependency.

v7.6.17

Compare Source

Fixed

• Manually firing callback with latest callback when useOnChange is provided new motion value (affects useSpring).

v7.6.16

Compare Source

Fixed

• Fixing useOnChange to resubscribe when provided a new motion value (affects useSpring).

v7.6.15

Compare Source

Fixed

• Rounding tree scale to 1 to prevent unnecessary scale transforms.

v7.6.14

Compare Source

Fixed

• Nothing to see here.

v7.6.13

Compare Source

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
blog	✅ Ready (Inspect)	Visit Preview	Dec 2, 2022 at 5:44PM (UTC)

[pull-request-quantifier-deprecated]

This PR has 10 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +5 -5
Percentile : 4%

Total files changed: 2

Change summary by file extension:
.json : +5 -5
.lock : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[github-actions]

Lighthouse Report

✨ https://blog-htohf4x3w-sabertaz.vercel.app/

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	99
🟢 accessibility	100
🟢 best-practices	100
🟢 seo	100
🟢 pwa	100

✨ https://blog-htohf4x3w-sabertaz.vercel.app/posts

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	99
🟢 accessibility	100
🟢 best-practices	100
🟢 seo	100
🟢 pwa	100

✨ https://blog-htohf4x3w-sabertaz.vercel.app/tags

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	100
🟢 accessibility	100
🟢 best-practices	100
🟢 seo	100
🟢 pwa	100

✨ https://blog-htohf4x3w-sabertaz.vercel.app/books

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	100
🟢 accessibility	100
🟢 best-practices	100
🟢 seo	100
🟢 pwa	100

✨ https://blog-htohf4x3w-sabertaz.vercel.app/about

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	99
🟢 accessibility	100
🟢 best-practices	100
🟢 seo	100
🟢 pwa	100

[codecov]

Codecov Report

Merging #1005 (6e8943c) into main (82f8949) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1005   +/-   ##
=======================================
  Coverage   99.42%   99.42%           
=======================================
  Files         176      176           
  Lines        1039     1039           
  Branches       88       88           
=======================================
  Hits         1033     1033           
  Misses          5        5           
  Partials        1        1           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.