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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@codesandbox/sandpack-react	^1.18.3 -> ^1.18.4
@types/react-dom (source)	^18.0.9 -> ^18.0.10
eslint-config-next	^13.0.7 -> ^13.1.1
framer-motion	^7.10.2 -> ^7.10.3
next-sitemap	^3.1.42 -> ^3.1.43
yarn	3.3.0 -> 3.3.1

---

Release Notes

codesandbox/sandpack

v1.18.4

Compare Source

Bug Fixes

• highlight inline error: make sure it highlight the correct file (#​671) (baaf2c5)

vercel/next.js

v13.1.1

Compare Source

Core Changes

• Exclude srcset from svg image: #​44308
• Fix CSS resource path not matched in __entry_css_files__: #​44310
• Fix next/image 404 when basePath and trailingSlash defined: #​44312

Documentation Changes

• Remove experimental for modularizeImports from docs and example: #​44311

Example Changes

• Updated dependencies for with-tailwindcss example: #​44289

Misc Changes

• Use turbo for packing files in test setup: #​44074

Credits

Huge thanks to @​JanKaifer, @​Nutlope, @​styfle, and @​chibicode for helping!

v13.1.0

Compare Source

Core Changes

• Fix windows slashes for app client entry: #​44052
• Hash both pitch and main loader for server CSS imports: #​44063
• Add tracing for testing tools: #​44046
• Run packing in tests in parallel: #​44048
• feat: app dir error-global component: #​44066
• Fix ignoring dev warning for preload component: #​44065
• refactor(next-swc): introduce next-binding to consolidate dependencies.: #​43473
• Add lodash to server components external packages: #​44022
• Fix dev session stopped handling: #​44112
• Add jsdoc/no-types eslint rule for TypeScript files: #​44049
• Revert "Remove useState from next/image (#​43587)": #​44094
• should not contain pages css in app dir: #​44151
• Upgrade undici to 5.14.0 to fix fetch redirect bug: #​44133
• build(cargo): fix turbopack + next-swc build: #​43983
• Align onRecoverableError callback between pages and app dir: #​44161
• build(cargo): update turbopack: #​44167
• Update styled-jsx: #​44070
• Fix crash in GraalVM: #​44176
• Also check error.message as digest for recoverable errors in pages: #​44185
• Move options to stable: #​44195
• Move transpilePackages out of experimental: #​44194
• Fix CSS resources being duplicated in app dir: #​44168
• Add telemetry for stable features: #​44201
• Add warning for experimental flags that have moved: #​44202
• build(cargo): bump up turbopack: #​44206
• Bump @vercel/[email protected]: #​44193
• Disable Image Optimization API when next.config.js has unoptimized: true: #​44205
• Honour distDir in type generation: #​44207
• Only once for the next/head usage in app dir: #​44233
• Enable allowMiddlewareResponseBody by default: #​44224
• Move modularizeImports out of experimental: #​44240
• Update config validation for latest turbopack changes: #​44223
• build(cargo): update turbopack: #​44241
• update turbopack for bugfixes: #​44251

Documentation Changes

• docs: Add explanation about font-display: #​44001
• Test that adding query can be detected by useSearchParams: #​43969
• Add static test for useSelectedLayoutSegments: #​43955
• Docs: Update deployment.md with Firebase, Amplify and Cloudflare: #​44092
• Add test for rewriting in middleware in app-dir: #​43971
• docs: Add missing type to import statement: #​44111
• docs: update next/dynamic docs: #​44067
• Update disabling-http-keep-alive.md for server-side only: #​43374
• docs: fix spelling error: #​44191
• Write tests for navigation between app-dir and pages: #​43881
• Add docs for middleware flags: #​44235

Example Changes

• Updates with-supertokens example: #​44042
• Fix styled-components setup in turbo example: #​44165
• update with-turbopack example for postcss/tailwind support: #​44261

Misc Changes

• Run packing in tests in parallel
• Revert "Run packing in tests in parallel"
• Remove extra turbo test: #​44073
• Implement new core test API: #​44086
• Refactor more tests to createNextDescribe: #​44104
• Add types as a default dependency into tests: #​44140
• Suggest contributors to use shallow clone: #​44158
• Update pnpm new-test to use createNextDescribe: #​44147
• Update README templates to include snippet on next/font: #​44088
• Wrap CSS variable in var: #​44153
• Ensure next.url is used instead of next.appPort: #​44163
• test: add test for notFound during streaming: #​44078
• Fix test template example: #​44170
• Remove devcontainer network host argument: #​44157
• Fix pnpm install on Azure: #​44179
• Enable ReactRefreshLogBox scss test: #​44180
• Increase recommended git clone depth: #​44181
• Document how chain works in BrowserInterface and chain to browser.eval: #​44085
• Remove browser.refresh in app tests: #​44186
• Move tests into their test folder: #​44183
• Add test checking that repeated edits won't cause hydration issues: #​44189
• Update labeler.json with current next.js team members: #​44231

Credits

Huge thanks to @​shuding, @​hanneslund, @​rishabhpoddar, @​JanKaifer, @​huozhi, @​timneutkens, @​kwonoj, @​IamManchanda, @​styfle, @​nyedidikeke, @​jaslong, @​jueungrace, @​longzheng, @​akshitsinha, @​Brooooooklyn, @​gish, and @​sokra for helping!

framer/motion

v7.10.3

Compare Source

Changed

• Firing animateChanges in useLayoutEffect rather than useEffect to ensure optimised appear animations are handed off before paint.

iamvishnusankar/next-sitemap

v3.1.43

Compare Source

Changes:

• a6374a9 Merge pull request #​546 from iamvishnusankar/dependabot/npm_and_yarn/next-13.0.7
• 73f8a65 Bump next from 13.0.6 to 13.0.7

This list of changes was auto generated.

yarnpkg/berry

v3.3.1

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 24, 2022 at 11:52AM (UTC)

[github-actions]

Lighthouse Report

✨ https://blog-56kerh5dd-sabertaz.vercel.app/

🚀 Vercel preview deployment
⚡ Lighthouse report

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

✨ https://blog-56kerh5dd-sabertaz.vercel.app/posts

🚀 Vercel preview deployment
⚡ Lighthouse report

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

✨ https://blog-56kerh5dd-sabertaz.vercel.app/tags

🚀 Vercel preview deployment
⚡ Lighthouse report

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

✨ https://blog-56kerh5dd-sabertaz.vercel.app/books

🚀 Vercel preview deployment
⚡ Lighthouse report

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

✨ https://blog-56kerh5dd-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 #1015 (90d93d3) into main (373011a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1015   +/-   ##
=======================================
  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.

[pull-request-quantifier-deprecated]

This PR has 14 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       : +7 -7
Percentile : 5.6%

Total files changed: 3

Change summary by file extension:
.yml : +1 -1
.json : +6 -6
.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.