fix(deps): update dependency @choc-ui/chakra-autocomplete to v5.5.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@choc-ui/chakra-autocomplete	5.2.9 -> 5.5.1

---

Release Notes

anubra266/choc-autocomplete (@​choc-ui/chakra-autocomplete)

v5.5.1

Compare Source

What's Changed

• Fix #​253 Changed scrollIntoView behaviour to fix scrolling issue when navigating with keyboard by @​EinarSnorrason in https://github.com/anubra266/choc-autocomplete/pull/255 (thanks for the research and PR!)

New Contributors

• @​EinarSnorrason made their first contribution in https://github.com/anubra266/choc-autocomplete/pull/255

Full Changelog: anubra266/choc-autocomplete@v5.5.0...v5.5.1

v5.5.0

Compare Source

What's Changed

• #​252 Expose matchWidth prop for Popover

Full Changelog: anubra266/choc-autocomplete@v5.4.1...v5.5.0

v5.4.1

Compare Source

This is a dependency only update just to keep current

Full Changelog: anubra266/choc-autocomplete@v5.4.0...v5.4.1

v5.4.0

Compare Source

What's Changed

• Fix #​241 named export error due to build issue by @​Kysluss in https://github.com/anubra266/choc-autocomplete/pull/250. Thanks to @​wcardosodev @​omniverse and @​ImExoOdeex for reporting and @​omniverse for a temporary workaround.

Full Changelog: anubra266/choc-autocomplete@v5.3.1...v5.4.0

v5.3.1

Compare Source

What's Changed

• Doc: Add form library integration documentation by @​Kysluss in https://github.com/anubra266/choc-autocomplete/pull/246
• Fix issues with removeItem by @​Kysluss in https://github.com/anubra266/choc-autocomplete/pull/248 reported by @​atandy and @​arieb

Full Changelog: anubra266/choc-autocomplete@v5.3.0...v5.3.1

v5.3.0

Compare Source

What's Changed

• Make prefocusFirstItem behavior configurable and consistent by @​chrisregner in https://github.com/anubra266/choc-autocomplete/pull/242
• Fix #​235 value prop does nothing reported by @​Kysluss in https://github.com/anubra266/choc-autocomplete/pull/244 Thank you to @​ThomasHickman for the bug report

New Contributors

• @​chrisregner made their first contribution in https://github.com/anubra266/choc-autocomplete/pull/242

Full Changelog: anubra266/choc-autocomplete@v5.2.10...v5.3.0

v5.2.10

Compare Source

Bug Fixes

• Fixes #​240 by @​ThomasHickman (thanks for your bug report!) - First item is selected when pressing enter and the AutoComplete is closed

Housekeeping

• Update dependencies to latest
• Update documentation and contributors

Full Changelog: anubra266/choc-autocomplete@v5.2.9...v5.2.10

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 has been generated by Mend Renovate. View repository job log here.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@choc-ui/chakra-autocomplete@5.5.1	Transitive: environment, filesystem, network, shell	+58	225 MB

🚮 Removed packages: npm/@choc-ui/chakra-autocomplete@5.2.9

View full report↗︎

[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.

Alert	Package	Note	Source
Install scripts	npm/esbuild@0.19.12	Install script: postinstall Source: node install.js	apps/frontend/package.json package-lock.json
Install scripts	npm/esbuild@0.19.2	Install script: postinstall Source: node install.js	Source
Install scripts	npm/esbuild@0.19.8	Install script: postinstall Source: node install.js	Source

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/esbuild@0.19.12
• @SocketSecurity ignore npm/esbuild@0.19.2
• @SocketSecurity ignore npm/esbuild@0.19.8