fix(deps): update npm non-major dependencies #350

renovate · 2024-10-11T21:53:04Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@headlessui/react (source)	`2.1.10` -> `2.2.0`
@playwright/test (source)	`1.48.0` -> `1.48.2`
@remix-run/dev (source)	`2.12.1` -> `2.13.1`
@remix-run/express (source)	`2.12.1` -> `2.13.1`
@remix-run/node (source)	`2.12.1` -> `2.13.1`
@remix-run/react (source)	`2.12.1` -> `2.13.1`
@types/react (source)	`18.3.11` -> `18.3.12`
@types/web-push (source)	`3.6.3` -> `3.6.4`
@typescript-eslint/eslint-plugin (source)	`8.8.1` -> `8.12.2`
@typescript-eslint/parser (source)	`8.8.1` -> `8.12.2`
better-sqlite3	`11.3.0` -> `11.5.0`
compression	`1.7.4` -> `1.7.5`
drizzle-kit (source)	`^0.25.0` -> `^0.27.0`
drizzle-orm (source)	`^0.34.0` -> `^0.36.0`
eslint-plugin-jsx-a11y	`6.10.0` -> `6.10.2`
eslint-plugin-react	`7.37.1` -> `7.37.2`
knip (source)	`5.33.3` -> `5.36.1`
lucide-react (source)	`^0.451.0` -> `^0.454.0`
react-day-picker (source)	`9.1.3` -> `9.2.1`
react-easy-crop (source)	`5.0.8` -> `5.1.0`
remix-development-tools (source)	`4.7.3` -> `4.7.5`
slate	`0.103.0` -> `0.110.2`
slate-history	`0.109.0` -> `0.110.3`
slate-react	`0.110.1` -> `0.111.0`
tailwind-merge	`2.5.3` -> `2.5.4`
tailwindcss (source)	`3.4.13` -> `3.4.14`
tsx (source)	`4.19.1` -> `4.19.2`
vite (source)	`5.4.8` -> `5.4.10`

Release Notes

tailwindlabs/headlessui (@headlessui/react)

`v2.2.0`

Compare Source

Added

Add React 19 support (#3543)

microsoft/playwright (@playwright/test)

Browser Versions

Chromium 130.0.6723.19
Mozilla Firefox 130.0
WebKit 18.0

This version was also tested against the following stable channels:

Google Chrome 129
Microsoft Edge 129

remix-run/remix (@remix-run/dev)

`v2.13.1`

Compare Source

Patch Changes

Revert future.v3_optimizeDeps back to future.unstable_optimizeDeps as it was not intended to stabilize in Remix v2 (#10099)
Updated dependencies:
- @remix-run/[email protected]
- @remix-run/[email protected]

`v2.13.0`

Compare Source

Minor Changes

Stabilize the future.unstable_optimizeDeps flag into future.v3_optimizeDeps (#10092)
Stabilize React Router APIs in Remix (#9980)
- Adopt stabilized React Router APIs internally
  - Single Fetch: unstable_dataStrategy -> dataStrategy
  - Lazy Route Discovery: unstable_patchRoutesOnNavigation -> patchRoutesOnNavigation
- Stabilize public-facing APIs
  - Single Fetch: unstable_data() -> data()
  - unstable_viewTransition -> viewTransition (Link, Form, navigate, submit)
  - unstable_flushSync> -> <Link viewTransition> (Link, Form, navigate, submit, useFetcher)
Stabilize future flags (#10072)
- future.unstable_singleFetch -> future.v3_singleFetch
- future.unstable_lazyRouteDiscovery -> future.v3_lazyRouteDiscovery

Patch Changes

Stop passing request.signal as the renderToReadableStream signal to abort server rendering for cloudflare/deno runtimes because by the time that request is aborted, aborting the rendering is useless because there's no way for React to flush down the unresolved boundaries (#10047)
- This has been incorrect for some time, but only recently exposed due to a bug in how we were aborting requests when running via remix vite:dev because we were incorrectly aborting requests after successful renders - which was causing us to abort a completed React render, and try to close an already closed ReadableStream.
- This has likely not shown up in any production scenarios because cloudflare/deno production runtimes are (correctly) not aborting the request.signal on successful renders
- The built-in entry.server files no longer pass a signal to renderToReadableStream because adding a timeout-based abort signal to the default behavior would constitute a breaking change
- Users can configure this abort behavior via their own entry.server via remix reveal entry.server, and the template entry.server files have been updated with an example approach for newly created Remix apps
Fix adapter logic for aborting request.signal so we don't incorrectly abort on the close event for successful requests (#10046)
Updated dependencies:
- @remix-run/[email protected]
- @remix-run/[email protected]

remix-run/remix (@remix-run/express)

`v2.13.1`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/[email protected]

`v2.13.0`

Compare Source

Patch Changes

Fix adapter logic for aborting request.signal so we don't incorrectly abort on the close event for successful requests (#10046)
Updated dependencies:
- @remix-run/[email protected]

remix-run/remix (@remix-run/node)

`v2.13.1`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/[email protected]

`v2.13.0`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/[email protected]

remix-run/remix (@remix-run/react)

`v2.13.1`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/[email protected]

`v2.13.0`

Compare Source

Minor Changes

Stabilize React Router APIs in Remix (#9980)
- Adopt stabilized React Router APIs internally
  - Single Fetch: unstable_dataStrategy -> dataStrategy
  - Lazy Route Discovery: unstable_patchRoutesOnNavigation -> patchRoutesOnNavigation
- Stabilize public-facing APIs
  - Single Fetch: unstable_data() -> data()
  - unstable_viewTransition -> viewTransition (Link, Form, navigate, submit)
  - unstable_flushSync> -> <Link viewTransition> (Link, Form, navigate, submit, useFetcher)
Stabilize future flags (#10072)
- future.unstable_singleFetch -> future.v3_singleFetch
- future.unstable_lazyRouteDiscovery -> future.v3_lazyRouteDiscovery

Patch Changes

Fix bug with clientLoader.hydrate in a layout route when hydrating with bubbled errors (#10063)
Updated dependencies:
- @remix-run/[email protected]

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

`v8.12.2`

Compare Source

🩹 Fixes

eslint-plugin: [switch-exhaustiveness-check] invert considerDefaultExhaustiveForUnions (#10223)

❤️ Thank You

Kirk Waiblinger @kirkwaiblinger

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

`v8.12.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.

`v8.12.0`

Compare Source

🚀 Features

eslint-plugin: [no-base-to-string] handle String() (#10005)
eslint-plugin: [switch-exhaustiveness-check] add allowDefaultCaseMatchUnionMember option (#9954)
eslint-plugin: [consistent-indexed-object-style] report mapped types (#10160)
eslint-plugin: [prefer-nullish-coalescing] add support for assignment expressions (#10152)

❤️ Thank You

Abraham Guo
Kim Sang Du @developer-bandi
Kirk Waiblinger @kirkwaiblinger
YeonJuan @yeonjuan

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

`v8.11.0`

Compare Source

🚀 Features

eslint-plugin: [no-unnecessary-type-parameters] add suggestion fixer (#10149)
eslint-plugin: [no-base-to-string] add support for catching toLocaleString (#10138)

🩹 Fixes

eslint-plugin: [class-literal-property-style] don't report nodes with override keyword (#10135)

❤️ Thank You

Kirk Waiblinger @kirkwaiblinger
Yukihiro Hasegawa @y-hsgw

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

`v8.10.0`

Compare Source

🚀 Features

support TypeScript 5.6 (#9972)

❤️ Thank You

Josh Goldberg ✨

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

`v8.9.0`

Compare Source

🩹 Fixes

eslint-plugin: [no-unnecessary-type-parameters] cannot assume variables are either type or value
scope-manager: [no-use-before-define] do not treat nested namespace aliases as variable references
eslint-plugin: [return-await] sync the behavior with await-thenable
eslint-plugin: [prefer-literal-enum-member] report a different error message when allowBitwiseExpressions is enabled
eslint-plugin: [no-loop-func] sync from upstream base rule
eslint-plugin: [no-unused-vars] never report the naming of an enum member
eslint-plugin: correct use-at-your-own-risk type definitions
eslint-plugin: handle unions in await...for

❤️ Thank You

Abraham Guo
Anna Bocharova
Arya Emami
auvred
Joshua Chen
Kirk Waiblinger
Lotfi Meklati
mdm317
Ronen Amiel
Sukka
YeonJuan

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

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

`v8.12.2`

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.

`v8.12.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.

`v8.12.0`

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.

`v8.11.0`

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.

`v8.10.0`

Compare Source

🚀 Features

support TypeScript 5.6 (#9972)

❤️ Thank You

Josh Goldberg ✨

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

`v8.9.0`

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.

WiseLibs/better-sqlite3 (better-sqlite3)

`v11.5.0`

Compare Source

What's Changed

Added NodeJS 23 Support by @neoxpert in https://github.com/WiseLibs/better-sqlite3/pull/1283
Update SQLite to version 3.47.0 by @mceachen in https://github.com/WiseLibs/better-sqlite3/pull/1284

Full Changelog: WiseLibs/better-sqlite3@v11.4.0...v11.5.0

`v11.4.0`

Compare Source

What's Changed

Prebuild for Electron 33 by @oliverschwendener in https://github.com/WiseLibs/better-sqlite3/pull/1279

New Contributors

@oliverschwendener made their first contribution in https://github.com/WiseLibs/better-sqlite3/pull/1279

Full Changelog: WiseLibs/better-sqlite3@v11.3.0...v11.4.0

expressjs/compression (compression)

`v1.7.5`

Compare Source

==========

deps: Replace accepts with negotiator@~0.6.4
- Add preference option
deps: [email protected]
- Add petabyte (pb) support
- Fix "thousandsSeparator" incorrecting formatting fractional part
- Fix return value for un-parsable strings
deps: compressible@~2.0.18
- Mark font/ttf as compressible
- Remove compressible from multipart/mixed
- deps: mime-db@'>= 1.43.0 < 2'
deps: [email protected]

drizzle-team/drizzle-orm (drizzle-kit)

`v0.27.1`

Compare Source

🎉 Added support for Neon HTTP driver

import { neon, neonConfig } from '@&#8203;neondatabase/serverless';
import { drizzle } from 'drizzle-orm/neon-http';

neonConfig.fetchConnectionCache = true;

const sql = neon(process.env.DRIZZLE_DATABASE_URL!);
const db = drizzle(sql);

db.select(...)

`v0.27.0`

Compare Source

Correct behavior when installed in a monorepo (multiple Drizzle instances)

Replacing all instanceof statements with a custom is() function allowed us to handle multiple Drizzle packages interacting properly.

It also fixes one of our biggest Discord tickets: maximum call stack exceeded 🎉

You should now use is() instead of instanceof to check if specific objects are instances of specific Drizzle types. It might be useful if you are building something on top of the Drizzle API.

import { is, Column } from 'drizzle-orm'

if (is(value, Column)) {
  // value's type is narrowed to Column
}

`distinct` clause support

await db.selectDistinct().from(usersDistinctTable).orderBy(
  usersDistinctTable.id,
  usersDistinctTable.name,
);

Also, distinct on clause is available for PostgreSQL:

await db.selectDistinctOn([usersDistinctTable.id]).from(usersDistinctTable).orderBy(
  usersDistinctTable.id,
);

await db.selectDistinctOn([usersDistinctTable.name], { name: usersDistinctTable.name }).from(
  usersDistinctTable,
).orderBy(usersDistinctTable.name);

`bigint` and `boolean` support for SQLite

Contributed by @MrRahulRamkumar (#558), @raducristianpopa (#411) and @meech-ward (#725)

const users = sqliteTable('users', {
  bigintCol: blob('bigint', { mode: 'bigint' }).notNull(),
  boolCol: integer('bool', { mode: 'boolean' }).notNull(),
});

DX improvements

Added verbose type error when relational queries are used on a database type without a schema generic
Fix where callback in RQB for tables without relations

Various docs improvements

Fix joins docs typo (#522) by @arjunyel
Add Supabase guide to readme (#690) by @saltcod
Make the column type in sqlite clearer (#717) by @shairez

`v0.26.2`

Compare Source

Updated internal versions for the drizzle-kit and drizzle-orm packages. Changes were introduced in the last minor release, and you are required to upgrade both packages to ensure they work as expected

`v0.26.1`

Compare Source

Fix data is malformed for views

`v0.26.0`

Compare Source

While writing this update, we found one bug that may occur with views in MySQL and SQLite, so please use the [email protected] release

New Features

Checks support in `drizzle-kit`

You can use drizzle-kit to manage your check constraint defined in drizzle-orm schema definition

For example current drizzle table:

import { sql } from "drizzle-orm";
import { check, pgTable } from "drizzle-orm/pg-core";

export const users = pgTable(
  "users",
  (c) => ({
    id: c.uuid().defaultRandom().primaryKey(),
    username: c.text().notNull(),
    age: c.integer(),
  }),
  (table) => ({
    checkConstraint: check("age_check", sql`${table.age} > 21`),
  })
);

will be generated into

CREATE TABLE IF NOT EXISTS "users" (
  "id" uuid PRIMARY KEY DEFAULT gen_random_uuid() NOT NULL,
  "username" text NOT NULL,
  "age" integer,
  CONSTRAINT "age_check" CHECK ("users"."age" > 21)
);

The same is supported in all dialects

Limitations

generate will work as expected for all check constraint changes.
push will detect only check renames and will recreate the constraint. All other changes to SQL won't be detected and will be ignored.

So, if you want to change the constraint's SQL definition using only push, you would need to manually comment out the constraint, push, then put it back with the new SQL definition and push one more time.

Views support in `drizzle-kit`

You can use drizzle-kit to manage your views defined in drizzle-orm schema definition. It will work with all existing dialects and view options

PostgreSQL

For example current drizzle table:

import { sql } from "drizzle-orm";
import {
  check,
  pgMaterializedView,
  pgTable,
  pgView,
} from "drizzle-orm/pg-core";

export const users = pgTable(
  "users",
  (c) => ({
    id: c.uuid().defaultRandom().primaryKey(),
    username: c.text().notNull(),
    age: c.integer(),
  }),
  (table) => ({
    checkConstraint: check("age_check", sql`${table.age} > 21`),
  })
);

export const simpleView = pgView("simple_users_view").as((qb) =>
  qb.select().from(users)
);

export const materializedView = pgMaterializedView(
  "materialized_users_view"
).as((qb) => qb.select().from(users));

will be generated into

CREATE TABLE IF NOT EXISTS "users" (
  "id" uuid PRIMARY KEY DEFAULT gen_random_uuid() NOT NULL,
  "username" text NOT NULL,
  "age" integer,
  CONSTRAINT "age_check" CHECK ("users"."age" > 21)
);

CREATE VIEW "public"."simple_users_view" AS (select "id", "username", "age" from "users");

CREATE MATERIALIZED VIEW "public"."materialized_users_view" AS (select "id", "username", "age" from "users");

Views supported in all dialects, but materialized views are supported only in PostgreSQL

Limitations

generate will work as expected for all view changes
push limitations:

If you want to change the view's SQL definition using only push, you would need to manually comment out the view, push, then put it back with the new SQL definition and push one more time.

Updates for PostgreSQL enums behavior

We've updated enum behavior in Drizzle with PostgreSQL:

Add value after or before in enum: With this change, Drizzle will now respect the order of values in the enum and allow adding new values after or before a specific one.
Support for dropping a value from an enum: In this case, Drizzle will attempt to alter all columns using the enum to text, then drop the existing enum and create a new one with the updated set of values. After that, all columns previously using the enum will be altered back to the new enum.

If the deleted enum value was used by a column, this process will result in a database error.

Support for dropping an enum
Support for moving enums between schemas
Support for renaming enums

jsx-eslint/eslint-plugin-jsx-a11y (eslint-plugin-jsx-a11y)

`v6.10.2`

Compare Source

Fixed

[patch] no-redundandant-roles: allow <img src="*.svg" role="img" /> #936

Commits

[meta] fix changelog URLs 0d01a1a
[Refactor] remove no-longer-needed es-iterator-helpers aa075bd
[Refactor] avoid spreading things that are already arrays d15d3ab
[Dev Deps] update @babel/cli, @babel/core, @babel/eslint-parser, @babel/plugin-transform-flow-strip-types, @babel/register 5dad7c4
[Tests] aria-role: Add valid test for <svg role="img" /> daba189
[Docs] label-has-associated-control: add line breaks for readability 0bc6378
[Tests] label-has-associated-control: add additional test cases 30d2318
[Tests] Add tests to reinforce required attributes for role="heading" d92446c

`v6.10.1`

Compare Source

Commits

[Fix] handle interactive/noninteractive changes from aria-query 4925ba8
[Docs] Use consistent spelling of 'screen reader' cb6788c
[Dev Deps] update @babel/cli, @babel/core, @babel/eslint-parser, @babel/plugin-transform-flow-strip-types, @babel/register, auto-changelog, eslint-plugin-import, tape 518a77e
[Deps] update es-iterator-helpers, string.prototype.includes eed03a3
[meta] package.json - Update jscodeshift & remove babel-jest 2ee940c
[Docs] Remove accidental whitespace in CONTRIBUTING.md a262131
[Deps] unpin aria-query e517937

jsx-eslint/eslint-plugin-react (eslint-plugin-react)

`v7.37.2`

Compare Source

Fixed

[destructuring-assignment]: fix false negative when using typeof props.a (#3835 @golopot)

Changed

[Refactor] [destructuring-assignment]: use getParentStatelessComponent (#3835 @golopot)

webpro-nl/knip (knip)

`v5.36.1`

Compare Source

`v5.36.0`

Compare Source

Add disclosure reporter (c5f0ee6)

`v5.35.1`

Compare Source

`v5.35.0`

Compare Source

`v5.34.4`

Compare Source

`v5.34.3`

Compare Source

`v5.34.2`

Compare Source

Highlight package name in specifier in symbols reporter (eca123b)
Fix binary extraction from specifier (c881d78)
Rename util to get-referenced-inputs.ts (62b10ba)
(TypeScript plugin): Add references path of tsconf

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

renovate bot enabled auto-merge (rebase) October 11, 2024 21:53

renovate bot force-pushed the renovate/npm-minor-patch branch 11 times, most recently from e774364 to d51f412 Compare October 21, 2024 20:19

renovate bot force-pushed the renovate/npm-minor-patch branch 9 times, most recently from 5be8d6f to 9246986 Compare October 25, 2024 17:02

renovate bot changed the title ~~chore(deps): update npm non-major dependencies~~ fix(deps): update npm non-major dependencies Oct 25, 2024

renovate bot force-pushed the renovate/npm-minor-patch branch 8 times, most recently from 82772ab to 0266f02 Compare October 29, 2024 00:38

renovate bot force-pushed the renovate/npm-minor-patch branch 8 times, most recently from ff4a593 to 02dd7a9 Compare October 31, 2024 22:28

fix(deps): update npm non-major dependencies

c935214

renovate bot force-pushed the renovate/npm-minor-patch branch from 02dd7a9 to c935214 Compare November 1, 2024 18:57

lasseklovstad added 2 commits November 2, 2024 10:59

Fix

6dc923c

Fix en gang til

c3abfa8

renovate bot merged commit 6c7e289 into main Nov 2, 2024
3 checks passed

renovate bot deleted the renovate/npm-minor-patch branch November 2, 2024 10:08

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update npm non-major dependencies #350

fix(deps): update npm non-major dependencies #350

renovate bot commented Oct 11, 2024 •

edited

Loading

fix(deps): update npm non-major dependencies #350

fix(deps): update npm non-major dependencies #350

Conversation

renovate bot commented Oct 11, 2024 • edited Loading

Release Notes

Added

Highlights

Browser Versions

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

🩹 Fixes

❤️ Thank You

🚀 Features

❤️ Thank You

🚀 Features

🩹 Fixes

❤️ Thank You

🚀 Features

❤️ Thank You

🩹 Fixes

❤️ Thank You

🚀 Features

❤️ Thank You

What's Changed

What's Changed

New Contributors

Correct behavior when installed in a monorepo (multiple Drizzle instances)

distinct clause support

bigint and boolean support for SQLite

DX improvements

Various docs improvements

New Features

Checks support in drizzle-kit

Limitations

Views support in drizzle-kit

PostgreSQL

Limitations

Updates for PostgreSQL enums behavior

Fixed

Commits

Commits

Fixed

Changed

Configuration

renovate bot commented Oct 11, 2024 •

edited

Loading

`distinct` clause support

`bigint` and `boolean` support for SQLite

Checks support in `drizzle-kit`

Views support in `drizzle-kit`