⬆️ Updates gradient-string to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
gradient-string	^1.2.0 -> ^3.0.0

---

Release Notes

bokub/gradient-string (gradient-string)

v3.0.0

Compare Source

• gradient-string v3 is now written in TypeScript & pure ESM
• All dependencies are up-to-date, all security issues patched
• New super-fast unit tests made with Vitest
• Improved documentation

⚠️ v2 to v3 migration

Breaking changes

• gradient-string requires Node.js 14+ (instead of 10 before)
• You cannot require gradient-string anymore, you have to import it

  - const gradient = require('gradient-string');
  + import gradient, { rainbow } from 'gradient-string';

Deprecated

The following recommendations are not breaking changes, but you should migrate your code to avoid problems in the future.
N.B You may see @deprecated warnings or TypeScript errors/warnings if you decide not to.

// Don't use aliases like this
- import gradient from 'gradient-string';
- gradient.rainbow('Hello, World!');

// Import aliases separately instead
+ import { rainbow } from 'gradient-string';
+ rainbow('Hello, World!');

// Don't separate your colors in different arguments
- const coolGradient = gradient('red', 'blue')('Hello, World!');

// Use an array instead
+ const coolGradient = gradient(['red', 'blue'])('Hello, World!');

// Don't pass your options when you call your already initialized gradient
- const coolGradient = gradient(['red', 'blue'])
- coolGradient('Hello, World!', { interpolation: 'hsv' }); // Options were needed here
// Pass your options directly when you initialize it
+ const coolGradient = gradient(['red', 'blue'], { interpolation: 'hsv' }) // Pass them here
+ coolGradient('Hello, World!');

v2.0.2

Compare Source

• Upgrade dependencies to patch security issues

v2.0.1

Compare Source

• Upgrade dependencies to patch security issues

v2.0.0

Compare Source

• gradient-string now needs Node.js >=10. For older versions, please keep using version 1.2.0
• Updated dependencies, especially chalk, which massively improves performance , and brings a better color detection.

---

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Moscow, Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR is behind base branch, 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.

[github-actions]

Thanks for the PR!

This section of the codebase is owner by https://github.com/AlexRogalskiy/ - if they write a comment saying "LGTM" then it will be merged.

[github-actions]

Thanks for opening an issue! Make sure you've followed CONTRIBUTING.md.

[github-actions]

Hello from PR Helper

Is your PR ready for review and processing? Mark the PR ready by including #pr-ready in a comment.

If you still have work to do, even after marking this ready. Put the PR on hold by including #pr-onhold in a comment.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/gradient-string@3.0.0	None	+1	62.5 kB	bokub

🚮 Removed packages: npm/@tilt.dev/tilt-inspector@0.1.6, npm/gradient-string@1.2.0, npm/onchange@7.1.0, npm/opener@1.5.2, npm/prettier@2.8.8, npm/pretty-quick@3.3.1, npm/randomcolor@0.5.4, npm/remark-cli@9.0.0, npm/remark-lint-code-block-style@2.0.1, npm/remark-lint-ordered-list-marker-value@2.0.1, npm/remark-preset-davidtheclark@0.12.0, npm/remark-validate-links@10.0.4, npm/semantic-release@17.4.7, npm/ts-jest@27.1.5, npm/ts-node@10.9.2, npm/typedoc@0.21.10, npm/typescript@4.9.5, npm/validate-commit-msg@2.14.0

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	CI
Critical CVE	npm/lodash@2.4.2	CVE: GHSA-jf85-cpcp-j695 Prototype Pollution in lodash (CRITICAL) Affected versions: < 4.17.12 Patched version: 4.17.12	package.json	⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

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/lodash@2.4.2