chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@commitlint/cli (source)	19.0.3 -> 19.2.1
@commitlint/config-conventional (source)	19.0.3 -> 19.1.0
@prisma/client (source)	5.10.2 -> 5.12.0
@types/node (source)	20.11.22 -> 20.12.3
@types/react (source)	18.2.60 -> 18.2.74
@types/react-dom (source)	18.2.19 -> 18.2.23
@typescript-eslint/eslint-plugin (source)	7.1.0 -> 7.5.0
@typescript-eslint/parser (source)	7.1.0 -> 7.5.0
autoprefixer	10.4.17 -> 10.4.19
dotenv-cli	7.3.0 -> 7.4.1
eslint-config-next (source)	14.1.0 -> 14.1.4
next (source)	14.1.0 -> 14.1.4
postcss (source)	8.4.35 -> 8.4.38
prettier-plugin-tailwindcss	0.5.11 -> 0.5.13
prisma (source)	5.10.2 -> 5.12.0
sass	1.71.1 -> 1.72.0
tailwindcss (source)	3.4.1 -> 3.4.3
typescript (source)	5.3.3 -> 5.4.3

---

Release Notes

conventional-changelog/commitlint (@​commitlint/cli)

v19.2.1

Compare Source

Note: Version bump only for package @​commitlint/cli

v19.2.0

Compare Source

Features

• cli: introduce new --last flag, to stop recommending HEAD~1 (#​3916) (99f4f3f)

v19.1.0

Compare Source

Note: Version bump only for package @​commitlint/cli

19.0.3 (2024-02-28)

Note: Version bump only for package @​commitlint/cli

19.0.2 (2024-02-28)

Note: Version bump only for package @​commitlint/cli

19.0.1 (2024-02-27)

Bug Fixes

• drop resolve-from, resolve-global and import-fresh, resolve global packages correctly (#​3939) (8793c63), closes #​3938

conventional-changelog/commitlint (@​commitlint/config-conventional)

v19.1.0

Compare Source

Note: Version bump only for package @​commitlint/config-conventional

19.0.3 (2024-02-28)

Note: Version bump only for package @​commitlint/config-conventional

prisma/prisma (@​prisma/client)

v5.12.0

Compare Source

Today, we are excited to share the 5.12.0 stable release 🎉

🌟 Help us spread the word about Prisma by starring the repo or posting on X about the release.

Highlights

Cloudflare D1 (Preview)

This release brings Preview support for Cloudflare D1 with Prisma ORM 🥳

D1 is Cloudflare’s SQLite database that can be used when deploying applications with Cloudflare.

When using Prisma ORM with D1, you can continue to: model your database with Prisma schema language, specify sqlite as your database provider in your Prisma schema, and interact with your database using Prisma Client.

To use Prisma ORM and D1 on Cloudflare Workers or Cloudflare Pages, you need to set sqlite as your database provider and use the @prisma/adapter-d1 database adapter via the driverAdapters Preview feature, released back in version 5.4.0.

Here is an example of sending a query to your D1 database using Prisma Client in your Worker:

// src/index.ts file
import { PrismaClient } from '@​prisma/client'
import { PrismaD1 } from '@​prisma/adapter-d1'

// Add the D1Database to the Env interface
export interface Env {
// This must match the binding name defined in your wrangler.toml configuration
  DB: D1Database
}

export default {
  async fetch(
    request: Request,
    env: Env,
    ctx: ExecutionContext
  ): Promise<Response> {
    // Make sure the database name matches the binding name in wrangler.toml and Env interface
    const adapter = new PrismaD1(env.DB)
    // Instantiate PrismaClient using the PrismaD1 driver adapter
    const prisma = new PrismaClient({ adapter })

    const users = await prisma.user.findMany()
    const result = JSON.stringify(users)
    return new Response(result)
  },
}

📚 Documentation: Deploying a Cloudflare worker with D1 and Prisma ORM

✍️ Blog post: Build Applications at the Edge with Prisma ORM & Cloudflare D1 (Preview)

📣 Share your feedback: D1 Driver Adapter

🚀 Example project: Deploy a Cloudflare Worker with D1

createMany() for SQLite

Bringing support for createMany() in SQLite has been a long-awaited and highly requested feature ⭐

createMany() is a method on Prisma Client, released back in version 2.16.0, that lets you insert multiple records into your database at once. This can be really useful when seeding your database or inserting bulk data.

Here is an example of using createMany() to create new users:

const users = await prisma.user.createMany({
  data: [
    { name: 'Sonali', email: 'sonali@prisma.io' },
    { name: 'Alex', email: 'alex@prisma.io' },
    { name: 'Yewande', email: 'yewande@prisma.io' },
    { name: 'Angelina', email: 'angelina@prisma.io' },
  ],
})

Before this release, if you wanted to perform bulk inserts with SQLite, you would have most likely used $queryRawUnsafe to execute raw SQL queries. But now you don’t have to go through all that trouble 🙂

With SQLite, createMany() works exactly the same way from an API standpoint as it does with other databases except it does not support the skipDuplicates option. At the behavior level, SQLite will split createMany() entries into multiple INSERT queries when the model in your schema contains fields with attributes like @default(dbgenerated()) or @default(autoincrement()) and when the fields are not consistently provided with values across the entries.

📚Documentation: createMany() - Prisma Client API Reference

Fixes and Improvements

Prisma Client

• N+1 Issue with Decimal data type and combining queries (batching)
• Batched findUnique() error out when the field is of Boolean type
• relationJoins MySQL converts nested Decimal to float
• Unexpected query leading to querying full table when using batched findUnique()
• node-postgres (pg) errors with misleading P2010 PrismaClientKnownRequestError when using @prisma/adapter-pg with SSL (?sslmode=require)
• D1 DateTime type does not work

Credits

Huge thanks to @​yubrot, @​skyzh, @​anuraaga, @​onichandame, @​LucianBuzzo, @​RobertCraigie, @​arthurfiorette, @​elithrar for helping!

v5.11.0

Compare Source

Today, we are excited to share the 5.11.0 stable release 🎉

🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release.

Highlights

Edge function support for Cloudflare and Vercel (Preview)

We’re thrilled to announce that support for edge function deployments with Prisma ORM is now in Preview 🥳 As of this release, you can deploy your apps that are using Prisma ORM to:

• Vercel Edge Functions and Vercel Edge Middleware
• Cloudflare Workers and Cloudflare Pages

In order to deploy to an edge function, you’ll need to use a compatible database driver (along with its Prisma driver adapter):

• Neon Serverless Driver (for PostgreSQL databases hosted via Neon)
• PlanetScale Serverless Driver (for MySQL databases hosted via PlanetScale)
• pg driver (for traditional PostgreSQL databases)
• @libsql/client driver (for SQLite databases hosted via Turso)

Check out our documentation to learn how you can deploy an edge function using any combination of supported edge function provider and database.

Performance improvements in nested create operations

With Prisma ORM, you can create multiple new records in nested queries, for example:

const user = await prisma.user.update({
  where: { id: 9 },
  data: {
    name: 'Elliott',
    posts: {
      create: {
        data: [{ title: 'My first post' }, { title: 'My second post' }],
      },
    },
  },
})

In previous versions, Prisma ORM would translate this into multiple SQL INSERT queries, each requiring its own roundtrip to the database. As of this release, these nested create queries are optimized and the INSERT queries are sent to the database in bulk in a single roundtrip. These optimizations apply to one-to-many as well as many-to-many relations.

With this change, using the nested create option to create multiple records effectively becomes equivalent to using a nested createMany operation (except that createMany only works with one-to-many relations, whereas create works both with one-to-many and many-to-many).

Note: Only the deepest nested operation is optimized. If a user specified create (1) -> create (2) -> create (3) in their query, only create (3) will be optimized.

Fixes and improvements

Prisma Client

• Prisma errors when not using the major.minor.patch versioning system
• mongodb where condition resulted in combined $ne but should not be $eq
• Node hangs when console.log(new PrismaClient())
• Add wolfy linux to supported OS
• Support Linux Gentoo
• Know engines to download for Void Linux
• Engine does not support Linux distro "openeuler"
• Prisma Doesn't Recognize Crystal Linux distro
• Regression: Mapped enum throws error (collation cp1250_czech_cs or similar)
• NOT condition leaks out of its desired bounds
• The column does not exist in the current database.
• Logging PrismaClient object is slow
• Running prisma generate on Litespeed Web Server cPanel with ssh
• Prisma doesn't know which engines to download for the Linux distro "guttaos"
• Error in driver-adapter-utils with tsc: Cannot find namespace 'debug'.
• VS Code debugger freeze from time to time, when Prisma Client is involved
• push method still unimplemented for scalar lists in CockroachDB
• Invalid character error persists on 5.10.1 in Prisma Studio
• Add "Peppermint OS" to list of supported distros
• runtimeDescription is not defined error

Prisma Migrate

• Prisma with UOS or Deepin
• Warning: Linux distro "slackware"
• Error when run npx prisma db pull with DeepinOS 20.9GNU/LInux
• Add solus to list of known supported distros
• NixOS not recognised as a Linux distribution
• Prisma Warning on Ubuntu 20.04
• Let Prisma detect Artix Linux distro
• couldn't identify clear-linux-os
• Prisma doesn't know which engines to download with Linux Mint
• Error: Invalid character when schema.prisma includes Chinese/Non-ASCII characters in a comment

Prisma Engines

• [DA] Planetscale engine tests: aggregations
• [DA] Planetscale engine tests: json filtering
• [DA] Planetscale engine tests: order and pagination
• [DA] Planetscale engine tests: oids
• [DA] Planetscale engine tests: nested_createmany_fail_dups
• [DA] Planetscale engine tests: create_many_error_dups
• [DA] Planetscale engine tests: upsert_fails_if_filter_dont_match

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v7.5.0

Compare Source

🩹 Fixes

• eslint-plugin: [no-floating-promises] handle TaggedTemplateExpression

• eslint-plugin: [no-unnecessary-type-assertion] handle exactOptionalPropertyTypes compiler option

❤️ Thank You

• Brad Zacher
• Kim Sang Du
• Mark de Dios
• Naru
• YeonJuan

You can read about our versioning strategy and releases on our website.

v7.4.0

Compare Source

🚀 Features

• eslint-plugin: [consistent-type-imports] ignore files with decorators, experimentalDecorators, and emitDecoratorMetadata

• eslint-plugin: [no-unnecessary-type-arguments] handle tagged templates

• eslint-plugin: deprecate no-throw-literal and add a renamed only-throw-error

🩹 Fixes

• eslint-plugin: [prefer-optional-chain] address multipart nullish checks false positive

• eslint-plugin: [prefer-optional-chain] properly disambiguate between boolean and false

• eslint-plugin: [no-unnecessary-type-assertion] avoid remove const casting on template literals with expressions inside

❤️ Thank You

• Abraham Guo
• Brad Zacher
• Josh Goldberg ✨
• Kim Sang Du
• Kirk Waiblinger
• Marco Pasqualetti
• YeonJuan

You can read about our versioning strategy and releases on our website.

v7.3.1

Compare Source

🩹 Fixes

• eslint-plugin: [no-floating-promises] revert disable of ignoreVoid in strict config

❤️ Thank You

• Josh Goldberg ✨

You can read about our versioning strategy and releases on our website.

v7.3.0

Compare Source

🚀 Features

• eslint-plugin: [restrict-template-expressions] add allowArray option

• eslint-plugin: add meta.docs.recommended setting for strict config options

• eslint-plugin: add rule use-unknown-in-catch-callback-variables

• eslint-plugin: [prefer-reduce-type-parameter] supports tuple, union, intersection

🩹 Fixes

• correct engines.node constraints in package.json

• eslint-plugin: [unbound-method] check method definition in object literal using longhand form

• eslint-plugin: [consistent-type-imports] handle imports without specifiers

• eslint-plugin: [no-redundant-type-constituents] incorrectly marks & string as redundant

• eslint-plugin: [no-unnecessary-qualifier] handle merge namespace with enum

• eslint-plugin: [no-unused-expressions] false negatives when using assertions

• eslint-plugin: [ban-ts-comment] more accurate handling of multiline comments

• eslint-plugin: [explicit-function-return-type, explicit-module-boundary-types] improved checking for allowHigherOrderFunctions option

• eslint-plugin: [class-literal-property-style] ignore property assigned in constructor

• eslint-plugin: [no-unnecessary-type-assertion] fix false negative for const variable declarations

❤️ Thank You

• Abraham Guo
• Alexu
• Arka Pratim Chaudhuri
• auvred
• Derrick Isaacson
• fnx
• Josh Goldberg ✨
• Kirk Waiblinger
• Marta Cardoso
• Michaël De Boey
• Tristan Rasmussen
• YeonJuan

You can read about our versioning strategy and releases on our website.

v7.2.0

Compare Source

🚀 Features

• support TS 5.4

• eslint-plugin: [prefer-string-starts-ends-with] add allowSingleElementEquality option

🩹 Fixes

• eslint-plugin: expose *-type-checked-only configs for extension

• eslint-plugin: [member-ordering] report alphabetical sorting for all groups instead of just the first failing group

• eslint-plugin: [no-var-requires, no-require-imports] support template literal

• eslint-plugin: [no-useless-template-literals] detect TemplateLiteral

• eslint-plugin: [no-unnecessary-condition] handle union array and tuple type

• eslint-plugin: [prefer-find] support ternary branches in prefer-find

❤️ Thank You

• Arka Pratim Chaudhuri
• auvred
• Chris Plummer
• Fotis Papadogeorgopoulos
• Josh Goldberg ✨
• Kirk Waiblinger
• Wayne Zhang
• YeonJuan

You can read about our versioning strategy and releases on our website.

v7.1.1

Compare Source

This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v7.5.0

Compare Source

🩹 Fixes

• parser: disallow errorOnTypeScriptSyntacticAndSemanticIssues

❤️ Thank You

• Brad Zacher
• Kim Sang Du
• Mark de Dios
• Naru
• YeonJuan

You can read about our versioning strategy and releases on our website.

v7.4.0

Compare Source

v7.3.1

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v7.3.0

Compare Source

🩹 Fixes

• correct engines.node constraints in package.json

❤️ Thank You

• Abraham Guo
• Alexu
• Arka Pratim Chaudhuri
• auvred
• Derrick Isaacson
• fnx
• Josh Goldberg ✨
• Kirk Waiblinger
• Marta Cardoso
• Michaël De Boey
• Tristan Rasmussen
• YeonJuan

You can read about our versioning strategy and releases on our website.

v7.2.0

Compare Source

🚀 Features

• support TS 5.4

❤️ Thank You

• Arka Pratim Chaudhuri
• auvred
• Chris Plummer
• Fotis Papadogeorgopoulos
• Josh Goldberg ✨
• Kirk Waiblinger
• Wayne Zhang
• YeonJuan

You can read about our versioning strategy and releases on our website.

v7.1.1

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

postcss/autoprefixer (autoprefixer)

v10.4.19

Compare Source

• Removed end value has mixed support, consider using flex-end warning
  since end/start now have good support.

v10.4.18

Compare Source

• Fixed removing -webkit-box-orient on -webkit-line-clamp (@​Goodwine).

entropitor/dotenv-cli (dotenv-cli)

v7.4.1

Compare Source

v7.4.0: Release better variable usage (-v)

Compare Source

Releases https://github.com/entropitor/dotenv-cli/pull/105

vercel/next.js (eslint-config-next)

v14.1.4

Compare Source

v14.1.3

Compare Source

v14.1.2

Compare Source

v14.1.1

Compare Source

Core Changes

• Should not warn metadataBase missing if only absolute urls are present: https://github.com/vercel/next.js/pull/61898
• Fix trailing slash for canonical url: https://github.com/vercel/next.js/pull/62109
• Fix metadata json manifest convention: https://github.com/vercel/next.js/pull/62615
• Improve the Server Actions SWC transform: https://github.com/vercel/next.js/pull/61001
• Fix Server Reference being double registered: https://github.com/vercel/next.js/pull/61244
• Improve the Server Actions SWC transform (part 2): https://github.com/vercel/next.js/pull/62052
• Fix module-level Server Action creation with closure-closed values: https://github.com/vercel/next.js/pull/62437
• Fix draft mode invariant: https://github.com/vercel/next.js/pull/62121
• fix: babel usage with next/image: https://github.com/vercel/next.js/pull/61835
• Fix next/server api alias for ESM pkg: https://github.com/vercel/next.js/pull/61721
• Replace image optimizer IPC call with request handler: https://github.com/vercel/next.js/pull/61471
• chore: refactor image optimization to separate external/internal urls: https://github.com/vercel/next.js/pull/61172
• fix(image): warn when animated image is missing unoptimized prop: https://github.com/vercel/next.js/pull/61045
• fix(build-output): show stack during CSR bailout warning: https://github.com/vercel/next.js/pull/62594
• Fix extra swc optimizer applied to node_modules in browser layer: https://github.com/vercel/next.js/pull/62051
• fix(next-swc): Detect exports.foo from cjs_finder: https://github.com/vercel/next.js/pull/61795
• Fix attempted import error for react: https://github.com/vercel/next.js/pull/61791
• Add stack trace to client rendering bailout error: https://github.com/vercel/next.js/pull/61200
• fix router crash on revalidate + popstate: https://github.com/vercel/next.js/pull/62383
• fix loading issue when navigating to page with async metadata: https://github.com/vercel/next.js/pull/61687
• revert changes to process default routes at build: https://github.com/vercel/next.js/pull/61241
• fix parallel route top-level catch-all normalization logic to support nested explicit (non-catchall) slot routes: https://github.com/vercel/next.js/pull/60776
• Improve redirection handling: https://github.com/vercel/next.js/pull/62561
• Simplify node/edge server chunking some: https://github.com/vercel/next.js/pull/62424

Credits

Huge thanks to @​huozhi, @​shuding, @​Ethan-Arrowood, @​styfle, @​ijjk, @​ztanner, @​balazsorban44, @​kdy1, and @​williamli for helping!

vercel/next.js (next)

v14.1.4

Compare Source

v14.1.3

Compare Source

v14.1.2

Compare Source

v14.1.1

Compare Source

Note: this is a backport release for critical bug fixes -- this does not include all pending features/changes on canary

Core Changes

• Should not warn metadataBase missing if only absolute urls are present: https://github.com/vercel/next.js/pull/61898
• Fix trailing slash for canonical url: https://github.com/vercel/next.js/pull/62109
• Fix metadata json manifest convention: https://github.com/vercel/next.js/pull/62615
• Improve the Server Actions SWC transform: https://github.com/vercel/next.js/pull/61001
• Fix Server Reference being double registered: https://github.com/vercel/next.js/pull/61244
• Improve the Server Actions SWC transform (part 2): https://github.com/vercel/next.js/pull/62052
• Fix module-level Server Action creation with closure-closed values: https://github.com/vercel/next.js/pull/62437
• Fix draft mode invariant: https://github.com/vercel/next.js/pull/62121
• fix: babel usage with next/image: https://github.com/vercel/next.js/pull/61835
• Fix next/server api alias for ESM pkg: https://github.com/vercel/next.js/pull/61721
• Replace image optimizer IPC call with request handler: https://github.com/vercel/next.js/pull/61471
• chore: refactor image optimization to separate external/internal urls: https://github.com/vercel/next.js/pull/61172
• fix(image): warn when animated image is missing unoptimized prop: https://github.com/vercel/next.js/pull/61045
• fix(build-output): show stack during CSR bailout warning: https://github.com/vercel/next.js/pull/62594
• Fix extra swc optimizer applied to node_modules in browser layer: https://github.com/vercel/next.js/pull/62051
• fix(next-swc): Detect exports.foo from cjs_finder: https://github.com/vercel/next.js/pull/61795
• Fix attempted import error for react: https://github.com/vercel/next.js/pull/61791
• Add stack trace to client rendering bailout error: https://github.com/vercel/next.js/pull/61200
• fix router crash on revalidate + popstate: https://github.com/vercel/next.js/pull/62383
• fix loading issue when navigating to page with async metadata: https://github.com/vercel/next.js/pull/61687
• revert changes to process default routes at build: https://github.com/vercel/next.js/pull/61241
• fix parallel route top-level catch-all normalization logic to support nested explicit (non-catchall) slot routes: https://github.com/vercel/next.js/pull/60776
• Improve redirection handling: https://github.com/vercel/next.js/pull/62561
• Simplify node/edge server chunking some: https://github.com/vercel/next.js/pull/62424

Credits

Huge thanks to @​huozhi, @​shuding, @​Ethan-Arrowood, @​styfle, @​ijjk, @​ztanner, @​balazsorban44, @​kdy1, and @​williamli for helping!

postcss/postcss (postcss)

v8.4.38

Compare Source

• Fixed endIndex: 0 in errors and warnings (by @​romainmenke).

v8.4.37

Compare Source

• Fixed original.column are not numbers error in another case.

v8.4.36

Compare Source

• Fixed original.column are not numbers error on broken previous source map.

tailwindlabs/prettier-plugin-tailwindcss (prettier-plugin-tailwindcss)

v0.5.13

Compare Source

Added

• Add support for @zackad/prettier-plugin-twig-melody (#​255)

v0.5.12

Compare Source

Added

• Add support for prettier-plugin-sort-imports (#​241)
• Add support for Tailwind CSS v4.0 (#​249)

sass/dart-sass (sass)

v1.72.0

Compare Source

• Support adjacent /s without whitespace in between when parsing plain CSS
  expressions.

• Allow the Node.js pkg: importer to load Sass stylesheets for package.json
exports field entries without extensions.

• When printing suggestions for variables, use underscores in variable names
  when the original usage used underscores.

JavaScript API

• Properly resolve pkg: imports with the Node.js package importer when
  arguments are passed to the JavaScript process.

tailwindlabs/tailwindcss (tailwindcss)

v3.4.3

Compare Source

v3.4.2

Compare Source

Fixed

• Ensure max specificity of 0,0,1 for button and input Preflight rules (#​12735)
• Improve glob handling for folders with (, ), [ or ] in the file path (#​12715)
• Split :has rules when using experimental.optimizeUniversalDefaults (#​12736)
• Sort arbitrary properties alphabetically across multiple class lists (#​12911)
• Add mix-blend-plus-darker utility (#​12923)
• Ensure dashes are allowed in variant modifiers (#​13303)
• Fix crash showing completions in Intellisense when using a custom separator (#​13306)
• Transpile import.meta.url in config files (#​13322)
• Reset letter spacing for form elements (#​13150)
• Fix missing xx-large and remove double x-large absolute size (#​13324)
• Don't error when encountering nested CSS unless trying to @apply a class that uses nesting (#​13325)
• Ensure that arbitrary properties respect important configuration (#​13353)
• Change dark mode selector so @apply works correctly with pseudo elements (#​13379)

Microsoft/TypeScript (typescript)

v5.4.3: TypeScript 5.4.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.4.0 (Beta).
• fixed issues query for Typescript 5.4.1 (RC).
• fixed issues query for Typescript 5.4.2 (Stable).
• fixed issues query for Typescript 5.4.3 (Stable).

Downloads are available on:

• NuGet package

v5.4.2: TypeScript 5.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.4.0 (Beta).
• [fixed issues query for Typescript 5.4.1 (RC)](https://togithub.com/Microsoft/TypeScript/issues?u

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" in timezone Asia/Jakarta, 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.

👻 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)
link	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 2, 2024 11:03pm