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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@codesandbox/sandpack-react	^2.6.9 -> ^2.7.1
@types/node (source)	^20.6.0 -> ^20.6.1
antd (source)	^5.9.0 -> ^5.9.1
cypress	^13.1.0 -> ^13.2.0
jest (source)	^29.6.4 -> ^29.7.0
jest-environment-jsdom	^29.6.4 -> ^29.7.0

---

Release Notes

codesandbox/sandpack (@​codesandbox/sandpack-react)

v2.7.1

Compare Source

Bug Fixes

• node: fix issue with undefined startRoute in iframePreviewUrl (#​1002) (c457a53)

v2.7.0

Compare Source

Features

• add console hook to static template (#​909) (1a473e3)

2.6.9 (2023-06-20)

Bug Fixes

• lerna: remove experimental flag for workspaces (#​956) (dec34f0)

2.6.8 (2023-06-20)

Bug Fixes

• client: hard reload on module removal (d5dfdd1)

2.6.7 (2023-05-26)

Bug Fixes

• client: avoid concurrent compile step and init (#​946) (98a20e9)
• node: remove --force option from all Sandpack Vite templates (#​947) (4d1b576)

2.6.6 (2023-05-22)

Bug Fixes

• compile: create one TestRunner between sandbox compiles (5ada4e3)

2.6.5 (2023-05-19)

Bug Fixes

• package.json: update @​codesandbox/nodebox and outvariant versions (#​942) (e20d475)

2.6.4 (2023-05-11)

Bug Fixes

• runtime-client: disable loading state by default (#​935) (aee0e3d)
• types: deduplicate files type (#​932) (c1b19ee)
• vite templates: set specific version (#​934) (8ab934e)

2.6.3 (2023-05-05)

Bug Fixes

• client: work around solid refresh bugs (b11b5c7)

2.6.2 (2023-05-02)

Bug Fixes

• useClient: track all clients and update clients on runSandpack (#​923) (a7334ad)

2.6.1 (2023-04-17)

Bug Fixes

• sandpack-react: fix autoReload and honor showRunButton false (#​907) (63c89e3)

ant-design/ant-design (antd)

v5.9.1

Compare Source

• 🐞 Fix Select that controlHeightSM not work in small size. #​44859 @​MadCcc
• 🐞 Fix Rate that star transaform not at center. #​44855 @​MadCcc
• 🐞 Fix DatePicker that in dateTime mode switching input didn't trigger onCalendarChange. #​44845 @​Yuiai01
• 🐞 Fix Table virtual selection checkbox or radio not align in center. #​44786
• 🐞 Fix Select carbin align top bug when enable maxTagCount. #​44757
• 🐞 Fix Select alignment issue when label is Typography. #​44756
• 💄 Fix Table with virtual display issue about columns less than table size and some border & hover style missing. #​44818
• 💄 Fix wrong style of Select in Input addon. #​44825 @​MadCcc
• 💄 Fix Tree that Checkbox should be aligned with first line. #​44827 @​MadCcc
• 💄 Fix Card that Card.Grid has wrong style with left bottom corner. #​44801 @​Jason-huang66
• 💄 Fix Select/Cascader/TreeSelect style issue when customize their height. #​44753
• TypeScript
  • 🤖 Optimize ref type of Radio.Button. #​44747 @​LexiosAlex
  • 🤖 Optimize ref type of Checkbox. #​44746 @​LexiosAlex

---

• 🐞 修复小尺寸 Select 组件 controlHeightSM token 配置无效的问题。#​44859 @​MadCcc
• 🐞 修复 Rate 组件星星变换中心不在正中心的问题。#​44855 @​MadCcc
• 🐞 修复 DatePicker 组件 dateTime 模式切换输入框不会触发 onCalendarChange 的问题。#​44845 @​Yuiai01
• 🐞 修复 Table virtual 配置下，选择框没有居中对齐的问题。#​44786
• 🐞 修复 Select 开启 maxTagCount 时搜索光标偏上的问题。#​44757
• 🐞 修复 Select 的 label 为 Typography 组件时的选中文本对齐问题。#​44756
• 💄 修复 Table virtual 开启虚拟滚动时，当 columns 小于表格宽度会显示异常的问题以及部分边框、悬浮样式丢失的问题。#​44818
• 💄 修复 Select 组件在 Input addon 中使用时的样式错误。#​44825 @​MadCcc
• 💄 修复 Tree 组件样式，使 Checkbox 与文字第一行对齐。#​44827 @​MadCcc
• 💄 修复 Card 组件 Card.Grid 边缘样式问题。#​44801 @​Jason-huang66
• 💄 修复 Select/Cascader/TreeSelect 自定义高度时的样式问题。#​44753
• TypeScript
  • 🤖 优化 Radio.Button 的 ref 类型。#​44747 @​LexiosAlex
  • 🤖 优化 Checkbox 的 ref 类型。#​44746 @​LexiosAlex

cypress-io/cypress (cypress)

v13.2.0

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-2-0

jestjs/jest (jest)

v29.7.0

Compare Source

Features

• [create-jest] Add npm init / yarn create initialiser for Jest projects (#​14465)
• [jest-validate] Allow deprecation warnings for unknown options (#​14499)

Fixes

• [jest-resolver] Replace unmatched capture groups in moduleNameMapper with empty string instead of undefined (#​14507)
• [jest-snapshot] Allow for strings as well as template literals in inline snapshots (#​14465)
• [@jest/test-sequencer] Calculate test runtime if perStats.duration is missing (#​14473)

Performance

• [@jest/create-cache-key-function] Cache access of NODE_ENV and BABEL_ENV (#​14455)

Chore & Maintenance

• [jest-cli] Move internal config initialisation logic to the create-jest package (#​14465)

---

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	Comments	Updated (UTC)
blog	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 15, 2023 5:11pm

[github-actions]

Lighthouse Report

✨ https://blog-82kimyoja-sabertaz.vercel.app/

🚀 Vercel preview deployment
⚡ Lighthouse report

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

✨ https://blog-82kimyoja-sabertaz.vercel.app/posts

🚀 Vercel preview deployment
⚡ Lighthouse report

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

✨ https://blog-82kimyoja-sabertaz.vercel.app/tags

🚀 Vercel preview deployment
⚡ Lighthouse report

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

✨ https://blog-82kimyoja-sabertaz.vercel.app/books

🚀 Vercel preview deployment
⚡ Lighthouse report

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

✨ https://blog-82kimyoja-sabertaz.vercel.app/about

🚀 Vercel preview deployment
⚡ Lighthouse report

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

[pull-request-quantifier-deprecated]

This PR has 12 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       : +6 -6
Percentile : 4.8%

Total files changed: 2

Change summary by file extension:
.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.