search

ant-design / pro-components

🏆 Use Ant Design like a Pro!
https://pro-components.antdigital.dev
MIT License
4.3k stars 1.36k forks source link

fix(layout): PageHeader style and breadcrumb.routes prop #8491

Closed ChuChencheng closed 4 months ago

ChuChencheng commented 4 months ago

Fixes #8479 Fixes #8490

  1. 如果背景默认透明是 by design，那 PageHeader ghost 就默认给个 true 吧
  2. 修复 has-breadcrumb, has-footer 样式不生效
  3. 修复 breadcrumb.routes 不生效导致面包屑空白
  4. 官网白屏可能是依赖的问题，我本地一开始也跑不起来，更新 lock 文件后就正常了
github-actions[bot] commented 4 months ago

😭 Deploy PR Preview failed.

socket-security[bot] commented 4 months ago

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/fast-deep-equal@3.1.3 None 0 13 kB esp
npm/lodash.merge@4.6.2 None 0 54.1 kB jdalton
npm/typescript@5.4.5 None 0 32.4 MB typescript-bot

View full report↗︎

socket-security[bot] commented 4 months ago

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package Note
Install scripts npm/@swc/core@1.4.2
  • Install script: postinstall
  • Source: node postinstall.js

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/@swc/core@1.4.2