chore(deps): update dependency @craco/craco to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@craco/craco (source)	^6.4.3 -> ^7.0.0

---

Release Notes

dilanx/craco (@​craco/craco)

v7.1.0

Compare Source

What's Changed

• Fix the github link in the docs on the top right by @​scottarver in https://github.com/dilanx/craco/pull/465
• fix signature for whenXX functions by @​liao02x in https://github.com/dilanx/craco/pull/468
• Update webpack.md by @​TerrySansom in https://github.com/dilanx/craco/pull/479
• Fix: proper return type by @​galbitz in https://github.com/dilanx/craco/pull/482
• Use Jest 27.x types by @​levrik in https://github.com/dilanx/craco/pull/464
• allow build script to use existing NODE_ENV value by @​Maikel-Nait in https://github.com/dilanx/craco/pull/480
• feat: Override CRA paths by @​attilapolakovics in https://github.com/dilanx/craco/pull/489
• update plugins by @​ponjs in https://github.com/dilanx/craco/pull/492
• docs: add plugin craco-css-modules by @​crazyurus in https://github.com/dilanx/craco/pull/494
• Fix broken link, fixing typos by @​deining in https://github.com/dilanx/craco/pull/496

New Contributors

• @​scottarver made their first contribution in https://github.com/dilanx/craco/pull/465
• @​liao02x made their first contribution in https://github.com/dilanx/craco/pull/468
• @​TerrySansom made their first contribution in https://github.com/dilanx/craco/pull/479
• @​galbitz made their first contribution in https://github.com/dilanx/craco/pull/482
• @​levrik made their first contribution in https://github.com/dilanx/craco/pull/464
• @​Maikel-Nait made their first contribution in https://github.com/dilanx/craco/pull/480
• @​attilapolakovics made their first contribution in https://github.com/dilanx/craco/pull/489
• @​ponjs made their first contribution in https://github.com/dilanx/craco/pull/492
• @​crazyurus made their first contribution in https://github.com/dilanx/craco/pull/494
• @​deining made their first contribution in https://github.com/dilanx/craco/pull/496

Full Changelog: dilanx/craco@v7.0.0...v7.1.0

v7.0.0

Compare Source

CRACO now supports Create React App 5.

The new documentation is live at https://craco.js.org.

v6.4.5

Compare Source

• Reverted to v6.4.3. #​425

v6.4.4

Compare Source

• Fixed undefined properties error in tests. #​425 #​432

---

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" in timezone Europe/Paris, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[socket-security]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
@craco/craco	6.4.3...7.1.0	None	+436/-98	66.8 MB	dilanx

[socket-security]

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

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

Issue	Package	Version	Note	Source
Install scripts	core-js-pure	3.31.0	Install script: postinstall Source: node -e "try{require('./postinstall')}catch(e){}"	@craco/[email protected] via package.json

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 package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore [email protected]