vevcom / projectNext

Project Next is Omegas new website coming soon
MIT License
7 stars 0 forks source link

chore(deps): bump the minor group with 12 updates #225

Closed dependabot[bot] closed 5 months ago

dependabot[bot] commented 5 months ago

Bumps the minor group with 12 updates:

Package From To
@fortawesome/fontawesome-svg-core 6.5.1 6.5.2
@fortawesome/free-brands-svg-icons 6.5.1 6.5.2
@fortawesome/free-solid-svg-icons 6.5.1 6.5.2
@prisma/client 5.11.0 5.12.1
sass 1.72.0 1.74.1
@types/node 20.12.2 20.12.5
@types/react 18.2.73 18.2.74
@types/react-dom 18.2.23 18.2.24
@typescript-eslint/eslint-plugin 7.4.0 7.6.0
@typescript-eslint/parser 7.4.0 7.6.0
prisma 5.11.0 5.12.1
typescript 5.4.3 5.4.4

Updates @fortawesome/fontawesome-svg-core from 6.5.1 to 6.5.2

Release notes

Sourced from @​fortawesome/fontawesome-svg-core's releases.

Release 6.5.2

Change log available at https://fontawesome.com/docs/changelog/

Commits


Updates @fortawesome/free-brands-svg-icons from 6.5.1 to 6.5.2

Release notes

Sourced from @​fortawesome/free-brands-svg-icons's releases.

Release 6.5.2

Change log available at https://fontawesome.com/docs/changelog/

Commits


Updates @fortawesome/free-solid-svg-icons from 6.5.1 to 6.5.2

Release notes

Sourced from @​fortawesome/free-solid-svg-icons's releases.

Release 6.5.2

Change log available at https://fontawesome.com/docs/changelog/

Commits


Updates @prisma/client from 5.11.0 to 5.12.1

Release notes

Sourced from @​prisma/client's releases.

5.12.1

Today, we are issuing the 5.12.1 patch release to fix two small problems with our new Cloudflare D1 support.

Fixes in Prisma CLI

Windows-only fix for new D1 specific flags for migrate diff and db pull

The flags --from-local-d1 and --to-local-d1 for migrate diff and --local-d1 to db pull we added in 5.12.0 were not working as expected when running on Windows only. This is now fixed.

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

New option for migrate diff: -o or --output

We added a new parameter --output to migrate diff that can be used to provide a filename into which the output of the command will be written. This is particularly useful for Windows users, using PowerShell, as using > to write into a file creates a UTF-16 LE file that can not be read by wrangler d1 migrations apply. Using this new option, this problem can be avoided:

npx prisma migrate diff --script --from-empty --to-schema-datamodel ./prisma/schema.prisma --output ./schema.sql

Related issues:

5.12.0

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 { </tr></table>

... (truncated)

Commits
  • af7b771 chore(deps): update engines to 5.12.0-21.473ed3124229e22d881cb7addf559799deba...
  • 671a742 chore(deps): update dependency @​libsql/client to v0.6.0 (#23658)
  • e7b60d1 chore(deps): update dependency @​cloudflare/workers-types to v4.20240329.0 (#2...
  • 7d1162b chore(deps): update engines to 5.12.0-19.473ed3124229e22d881cb7addf559799deba...
  • 09f640d fix(adapter-d1): Correctly treat CURRENT_TIMESTAMP result as date (#23649)
  • dfac408 chore(deps): update engines to 5.12.0-17.12fad4795eef0c21ed444646215f274961d9...
  • b6efac2 chore(deps): update definitelytyped (#23550)
  • d8ee9b2 chore(deps): update dependency @​types/node to v16.18.91 (#23464)
  • 85f43be chore(deps): update engines to 5.12.0-14.ac6cd787ad122596242218dca95c086051e2...
  • 0566ebb chore(deps): update engines to 5.12.0-13.582bc82c6e2ef356990286ce3082af371dd7...
  • Additional commits viewable in compare view


Updates sass from 1.72.0 to 1.74.1

Release notes

Sourced from sass's releases.

Dart Sass 1.74.1

To install Sass 1.74.1, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

  • No user-visible changes.

See the full changelog for changes in earlier releases.

Changelog

Sourced from sass's changelog.

1.74.1

  • No user-visible changes.

1.74.0

JS API

  • Add a new top-level deprecations object, which contains various Deprecation objects that define the different types of deprecation used by the Sass compiler and can be passed to the options below.

  • Add a new fatalDeprecations compiler option that causes the compiler to error if any deprecation warnings of the provided types are encountered. You can also pass in a Version object to treat all deprecations that were active in that Dart Sass version as fatal.

  • Add a new futureDeprecations compiler option that allows you to opt-in to certain deprecations early (currently just import).

  • Add a new silenceDeprecations compiler option to ignore any deprecation warnings of the provided types.

Command-Line Interface

  • Add a new --silence-deprecation flag, which causes the compiler to ignore any deprecation warnings of the provided types.

  • Previously, if a future deprecation was passed to --fatal-deprecation but not --future-deprecation, it would be treated as fatal despite not being enabled. Both flags are now required to treat a future deprecation as fatal with a warning emitted if --fatal-deprecation is passed without --future-deprecation, matching the JS API's behavior.

Dart API

  • The compile methods now take in a silenceDeprecations parameter, which causes the compiler to ignore any deprecation warnings of the provided types.

  • Add Deprecation.obsoleteIn to match the JS API. This is currently null for all deprecations, but will be used once some deprecations become obsolete in Dart Sass 2.0.0.

  • Potentially breaking bug fix: Fix a bug where compileStringToResultAsync ignored fatalDeprecations and futureDeprecations.

  • The behavior around making future deprecations fatal mentioned in the CLI section above has also been changed in the Dart API.

1.73.0

... (truncated)

Commits


Updates @types/node from 20.12.2 to 20.12.5

Commits


Updates @types/react from 18.2.73 to 18.2.74

Commits


Updates @types/react-dom from 18.2.23 to 18.2.24

Commits


Updates @typescript-eslint/eslint-plugin from 7.4.0 to 7.6.0

Release notes

Sourced from @​typescript-eslint/eslint-plugin's releases.

v7.6.0

7.6.0 (2024-04-08)

🚀 Features

  • add name field to shared configs and flat config types (#8863)
  • bump npm dependency ranges (#8860)
  • utils: add types for both flat and legacy eslint classes (#8861)

🩹 Fixes

  • typescript-eslint: fix type errors when using exactOptionalPropertyTypes (#8786)

❤️ Thank You

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

v7.5.0

7.5.0 (2024-04-01)

🩹 Fixes

  • eslint-plugin: [no-floating-promises] handle TaggedTemplateExpression (#8758)
  • eslint-plugin: [no-unnecessary-type-assertion] handle exactOptionalPropertyTypes compiler option (#8770)
  • parser: disallow errorOnTypeScriptSyntacticAndSemanticIssues (#8784)
  • typescript-eslint: improve support for legacy configs (#8812)

❤️ Thank You

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

Changelog

Sourced from @​typescript-eslint/eslint-plugin's changelog.

7.6.0 (2024-04-08)

🚀 Features

  • bump npm dependency ranges

❤️ Thank You

  • Abraham Guo
  • auvred
  • Brad Zacher

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

7.5.0 (2024-04-01)

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

Commits
  • e1db872 chore(release): publish 7.6.0
  • a6ab2cb feat: bump npm dependency ranges (#8860)
  • 4bac40c docs: fix incorrect tab item values in prefer-optional-chain (#8867)
  • a7bdd1c test(eslint-plugin): render snapshots of ESLint output for each code example ...
  • 41d893f docs(eslint-plugin): [consistent-return] add warning section use noImplicitRe...
  • d063275 docs: feature-freeze member-ordering, naming-convention, sort-type-constituen...
  • a14ba9d chore(release): publish 7.5.0
  • ecb6b55 docs: add homepage (#8742)
  • f0b1c4f fix(eslint-plugin): [no-unnecessary-type-assertion] handle exactOptionalPrope...
  • 5707268 fix(eslint-plugin): [no-floating-promises] handle TaggedTemplateExpression (#...
  • Additional commits viewable in compare view


Updates @typescript-eslint/parser from 7.4.0 to 7.6.0

Release notes

Sourced from @​typescript-eslint/parser's releases.

v7.6.0

7.6.0 (2024-04-08)

🚀 Features

  • add name field to shared configs and flat config types (#8863)
  • bump npm dependency ranges (#8860)
  • utils: add types for both flat and legacy eslint classes (#8861)

🩹 Fixes

  • typescript-eslint: fix type errors when using exactOptionalPropertyTypes (#8786)

❤️ Thank You

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

v7.5.0

7.5.0 (2024-04-01)

🩹 Fixes

  • eslint-plugin: [no-floating-promises] handle TaggedTemplateExpression (#8758)
  • eslint-plugin: [no-unnecessary-type-assertion] handle exactOptionalPropertyTypes compiler option (#8770)
  • parser: disallow errorOnTypeScriptSyntacticAndSemanticIssues (#8784)
  • typescript-eslint: improve support for legacy configs (#8812)

❤️ Thank You

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

Changelog

Sourced from @​typescript-eslint/parser's changelog.

7.6.0 (2024-04-08)

🚀 Features

  • bump npm dependency ranges

❤️ Thank You

  • Abraham Guo
  • auvred
  • Brad Zacher

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

7.5.0 (2024-04-01)

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

Commits


Updates prisma from 5.11.0 to 5.12.1

Release notes

Sourced from prisma's releases.

5.12.1

Today, we are issuing the 5.12.1 patch release to fix two small problems with our new Cloudflare D1 support.

Fixes in Prisma CLI

Windows-only fix for new D1 specific flags for migrate diff and db pull

The flags --from-local-d1 and --to-local-d1 for migrate diff and --local-d1 to db pull we added in 5.12.0 were not working as expected when running on Windows only. This is now fixed.

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

New option for migrate diff: -o or --output

We added a new parameter --output to migrate diff that can be used to provide a filename into which the output of the command will be written. This is particularly useful for Windows users, using PowerShell, as using > to write into a file creates a UTF-16 LE file that can not be read by wrangler d1 migrations apply. Using this new option, this problem can be avoided:

npx prisma migrate diff --script --from-empty --to-schema-datamodel ./prisma/schema.prisma --output ./schema.sql

Related issues:

5.12.0

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 { </tr></table>

... (truncated)

Commits


Updates typescript from 5.4.3 to 5.4.4

Release notes

Sourced from typescript's releases.

TypeScript 5.4.4

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

Commits
  • 8eb3367 Bump version to 5.4.4 and LKG
  • de9096b 🤖 Pick PR #57871 (Divide-and-conquer strategy for int...) into release-5.4 (#...
  • 06aae98 🤖 Pick PR #57973 (Compare package.json paths with cor...) into release-5.4 (#...
  • 6d8134e 🤖 Pick PR #57637 (Fixed a regression related to deter...) into release-5.4 (#...
  • 1c25c7f 🤖 Pick PR #57968 (Normalize slashes for paths in watc...) into release-5.4 (#...
  • 3caec2c Cherry pick PR 57887 into release-5.4 (#57898)
  • 896947e 🤖 Pick PR #57938 (Directories dont check modified tim...) into release-5.4 (#...
  • 521d3fb 🤖 Pick PR #57950 (Watch events enhancements) into release-5.4 (#57967)
  • See full diff in compare view


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions