Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(deps): update frontend dependencies (major) #1309

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

chore(deps): update frontend dependencies (major) #1309

wants to merge 1 commit into from

Conversation

ggrossetie
Copy link
Collaborator

@ggrossetie ggrossetie commented Feb 27, 2025 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
@welldone-software/why-did-you-render devDependencies major ~8.0 -> ~10.0.0
biblatex-csl-converter dependencies major ^1.11.0 -> ^3.0.0
clsx dependencies major ^1.2.1 -> ^2.0.0
downshift (source) dependencies major ^6.1.12 -> ^9.0.0
eslint (source) devDependencies major ^8.2.0 -> ^9.0.0
npm (source) volta major 10.9.2 -> 11.2.0
prettier (source) devDependencies major ^2.3.0 -> ^3.0.0
redux (source) dependencies major ^4.1.0 -> ^5.0.0
y-websocket dependencies major ^1.5.0 -> ^2.0.0

Release Notes

welldone-software/why-did-you-render (@​welldone-software/why-did-you-render)

v10.0.1

Compare Source

  • notifier was not exposing ownerDataMap despite the documentation saying it should.

v10.0.0: Why Did You Render v10 Supporting React 19! 🎉🍾

Compare Source

¯\(ツ)/¯ The version was bumped from v8 to v10 directly and 10.0.0 is actually the same as the next 10.0.1. Sorry, I had some npm publishing issues ¯\(ツ)/¯

[!NOTE]
I've joined the React team, specifically working on React tooling. This role has opened up exciting opportunities to enhance the developer experience for React users— and your input could offer valuable insights to help me with this effort. Please join the conversation in the discussion thread!

Breaking Changes

[!CAUTION]
The library was not tested with React Compiler at all. I believe it's completely incompatible with it.

[!CAUTION]
Not all re-renders are "bad". Sometimes shenanigan to reduce re-renders can either hurt your App's performance or have a neglagable effect, in which case it would be just a waste of your efforts, and complicate your code. Try to focus on heavier components when optimizing and use the React DevTools Profiler to measure the effects of any changes.

New Features
Internal
fiduswriter/biblatex-csl-converter (biblatex-csl-converter)

v3.0.1

Compare Source

v3.0.0

Compare Source

v2.1.0

Compare Source

v2.0.4

Compare Source

v2.0.2

Compare Source

v2.0.1

Compare Source

v2.0.0

Compare Source

lukeed/clsx (clsx)

v2.1.1

Compare Source

Patches

Chores

  • Add licenses.dev badge: 684509c
    This service recursively analyzes entire dependency graphs to ensure that a package (or your project) is using permissive licenses. For example, here's a results table for polka@next and a larger astro example.

Full Changelog: lukeed/clsx@v2.1.0...v2.1.1

v2.1.0

Compare Source

Features

  • Add new clsx/lite submodule for string-only usage: 1a49142

    This is a 140b version of clsx that is ideal for Tailwind and/or React contexts, which typically follow this clsx usage pattern:

    clsx('foo bar', props.maybe && 'conditional classes', props.className);

    Important: This clsx/lite module ignores all non-string arguments and is therefore not a 1:1 replacement for clsx itself!

    import { clsx } from 'clsx';
import { clsx as lite } from 'clsx/lite';

// strings-only usage is identical
clsx('foo', null, 'bar', true && 'baz'); //=> "foo bar baz"
lite('foo', null, 'bar', true && 'baz'); //=> "foo bar baz"

// clsx/lite ignores all non-strings
clsx('foo', { a: true, b: false, c: true }); //=> "foo a c"
lite('foo', { a: true, b: false, c: true }); //=> "foo"

Full Changelog: lukeed/clsx@v2.0.1...v2.1.0

v2.0.1

Compare Source

Patches

  • (perf) Cache arguments.length & array.length for 6% performance gain (#​26): deff09b
    Adds 5 bytes (+2%) for ~3% avg performance gain
    Thank you @​jalalazimi

Chores

Full Changelog: lukeed/clsx@v2.0.0...v2.0.1

v2.0.0

Compare Source

Breaking

  • Add "exports" map for native ESM support (#​57): 3ec8e9f, 0949868
    Also supports TypeScript's node16/nodenext module resolution
    Maintains CommonJS support (with fixed TS definitions)
    Thank you @​remcohaszing~!

Chores

Full Changelog: lukeed/clsx@v1.2.1...v2.0.0

downshift-js/downshift (downshift)

v9.0.8

Compare Source

Bug Fixes

v9.0.7

Compare Source

Bug Fixes

v9.0.6

Compare Source

Bug Fixes

v9.0.5

Compare Source

Bug Fixes

v9.0.4

Compare Source

Bug Fixes

v9.0.3

Compare Source

Bug Fixes

v9.0.2

Compare Source

Bug Fixes

v9.0.1

Compare Source

Bug Fixes

v9.0.0

Compare Source

Features
BREAKING CHANGES
  • Release Downshift v9.

Why:
Release the changes in:

Closes https://github.com/downshift-js/downshift/issues/1322.
Closes https://github.com/downshift-js/downshift/issues/1244.
Closes https://github.com/downshift-js/downshift/issues/1227
Closes https://github.com/downshift-js/downshift/issues/1225.

How:
Merged the PRs in this branch.

Checklist:

  • Documentation
  • Tests
  • TypeScript Types
  • Flow Types
  • Ready to be merged

v8.5.0

Compare Source

Features

v8.4.0

Compare Source

Features

v8.3.3

Compare Source

Bug Fixes
  • fixes issue causing combobox to grab focus on render (#​1575) (59366d9)

v8.3.2

Compare Source

Bug Fixes

v8.3.1

Compare Source

Bug Fixes

v8.3.0

Compare Source

Features

v8.2.4

Compare Source

Bug Fixes

v8.2.3

Compare Source

Bug Fixes

v8.2.2

Compare Source

Bug Fixes
  • typescript: add onPress to toggle button props parameter (#​1548) (fd6ab68)

v8.2.1

Compare Source

Bug Fixes
  • defaultProps: use undefined environment on React Native (#​1546) (7d8c32d)
  • useSelect: preventDefault on item props onMouseDown (b24f2e6)
  • useSelect: preventDefault on item props onMouseDown (#​1547) (05ffa9c)

v8.2.0

Compare Source

Features

v8.1.1

Compare Source

Bug Fixes
  • typescript: missing generic parameter of React.RefObject (#​1536) (bc7639c)

v8.1.0

Compare Source

Features

v8.0.2

Compare Source

Bug Fixes

v8.0.1

Compare Source

Bug Fixes

v8.0.0

Compare Source

Features
BREAKING CHANGES
  • Release Downshift v8.

PRs included:

https://github.com/downshift-js/downshift/pull/1440
https://github.com/downshift-js/downshift/pull/1445
https://github.com/downshift-js/downshift/pull/1463
https://github.com/downshift-js/downshift/pull/1510
https://github.com/downshift-js/downshift/pull/1482

Changes

These changes will also be covered in the V8 migration guide.

isItemDisabled

Both useCombobox and useSelect now support the isItemDisabled function. This new API is used to mark menu items as disabled, and as such remove the from the navigation and prevent them from being selected. The old API required passing the disabled prop to the getItemProps function. This old API has been removed and you will receive a console warning if you are trying to use the disabled prop in getItemProps.

Example of API migration:

Old:

const items = [{value: 'item1'}, {value: 'item2'}]

const {getInputProps, ...rest} = useCombobox({items})

return (
  // ... rest
  <li {...getItemProps({item, disabled: item.value === 'item2'})}>
)

New:

const items = [{value: 'item1'}, {value: 'item2'}]

const {getInputProps, ...rest} = useCombobox({items, isItemDisabled(item, _index) { return item.value === 'item2' }})

return (
  // ... rest
  <li {...getItemProps({item})}>
)

The API for Downshift remains unchange.

useCombobox input click

ARIA 1.2 recommends to toggle the menu open state at input click. Previously, in v7, the menu was opened on receiving focus, from both mouse and keyboard. Starting with v8, input focus will not trigger any state change anymore. Only the input click event will be handled and will trigger a menu toggle. Consequently:

  • getInputProps will not return any Focus event handler.
  • getInputProps will return a Click event handler.
  • useCombobox.stateChangeTypes.InputFocus has been removed.
  • useCombobox.stateChangeTypes.InputClick has been added instead.

We recommend having the default toggle on input click behaviour as it's part of the official ARIA combobox 1.2 spec, but if you wish to override it and not toggle the menu on click, use the stateReducer:

function stateReducer(state, actionAndChanges) {
  const {changes, type} = actionAndChanges
  switch (type) {
    case useCombobox.stateChangeTypes.InputClick:
      return {
        ...changes,
        isOpen: state.isOpen, // do not toggle the menu when input is clicked.
      }
    default:
      return changes
  }
}

If you want to return to the v7 behaviour and open the menu on focus, keep the reducer above so you remove the toggle behaviour, and call the openMenu imperative function, returned by useCombobox, in a onFocus handler passed to
getInputProps:

<input
  {...getInputProps({
    onFocus() {
      openMenu()
    },
  })}
/>

Consider to use the default 1.2 ARIA behaviour provided by default in order to align your widget to the accessibility official spec. This behaviour consistency improves the user experience, since all comboboxes should behave the same and
there won't be need for any additional guess work done by your users.

Getter props return value types

Previously, the return value from the getter props returned by both Downshift and the hooks was any. In v8 we improved the types in order to reflect what is actually returned: the default values return by the getter prop function and
whatever else the user passes as arguments. The type changes are done in this PR, make sure you adapt your TS code, if applicable.

Also, in the Downshift component, the return values for some getter prop values have changed from null to undefined, since that is what HTML elements expect (value or undefined). These values are also reflected in the TS types.

  • getRootProps: 'aria-owns': isOpen ? this.menuId : nullundefined,
  • getInputProps:
    • 'aria-controls': isOpen ? this.menuId : nullundefined
    • 'aria-activedescendant': isOpen && typeof highlightedIndex === 'number' &&
      highlightedIndex >= 0 ? this.getItemId(highlightedIndex) : nullundefined
  • getMenuProps: props && props['aria-label'] ? nullundefined : this.labelId,
environment propTypes

The environment prop is useful when you are using downshift in a context
different than regular DOM. Its TS type has been updated to contain Node and
the propTypes have also been updated to reflect the properties which are
required by downshift from environment.

v7.6.2

Compare Source

Bug Fixes

v7.6.1

Compare Source

Bug Fixes

v7.6.0

Compare Source

Features
  • getter prop with aria-label will not add aria-labelledby (#​1488) (20314b5)

v7.5.0

Compare Source

Features

v7.4.1

Compare Source

Bug Fixes
  • useCombobox: Ensure highlighted index is not selected on browser tab change (#​1484) (4ff1385), closes #​1471

v7.4.0

Compare Source

Features

v7.3.4

Compare Source

Bug Fixes
  • defaultProps: only select if there are items and one is highlighted (#​1467) (108c1ba)

v7.3.3

Compare Source

Bug Fixes
  • hooks: correctly compute item and index in getter function (#​1473) (7471fba)

v7.3.2

Compare Source

Bug Fixes

v7.3.1

Compare Source

Bug Fixes

v7.3.0

Compare Source

Features

v7.2.2

Compare Source

Bug Fixes

v7.2.1

Compare Source

Bug Fixes
  • hooks: do not add mouse and touch events in React native (#​1472) (694f2af)

v7.2.0

Compare Source

Features

v7.1.2

Compare Source

Bug Fixes

v7.1.1

Compare Source

Bug Fixes
  • useMultipleSelection: prevent adding items on Backspace/Delete without activeIndex (#​1458) (d1a7f67)

v7.1.0

Compare Source

Features
  • useSelect: improve highlight by character keys algorithm (#​1456) (d822530)

v7.0.5

Compare Source

Bug Fixes
  • add clean up to avoid effect firing twice in strict mode (#​1436) (25a673b)

v7.0.4

Compare Source

Bug Fixes

v7.0.3

Compare Source

Bug Fixes

v7.0.1

Compare Source

Bug Fixes

v7.0.0

Compare Source

Features
BREAKING CHANGES
  • updates to useCombobox and useSelect to adhere to the 1.2 version of the ARIA Combobox pattern.

Migration guide is available in this file.

Closes https://github.com/downshift-js/downshift/issues/1365.
Closes https://github.com/downshift-js/downshift/issues/1239.
Contains changes from https://github.com/downshift-js/downshift/pull/1149.

eslint/eslint (eslint)

v9.22.0

Compare Source

Features
  • 7ddb095 feat: Export defineConfig, globalIgnores (#​19487) (Nicholas C. Zakas)
Bug Fixes
  • 19c0127 fix: improve message for no-console suggestions (#​19483) (Francesco Trotta)
  • 49e624f fix: improve error message for falsy parsed JS AST (#​19458) (Josh Goldberg ✨)
Documentation
  • 86c5f37 docs: Update README (GitHub Actions Bot)
  • fbdeff0 docs: Update README (GitHub Actions Bot)
  • c9e8510 docs: generate deprecation notice in TSDoc comments from rule metadata (#​19461) (Francesco Trotta)
  • 2f386ad docs: replace var with const in rule examples (#​19469) (Tanuj Kanti)
  • 0e688e3 docs: Update README (GitHub Actions Bot)
  • 06b596d docs: Restore the carrot to the position where the search input was lost (#​19459) (Amaresh S M)
Chores

v9.21.0

Compare Source

Features
Bug Fixes
  • db5340d fix: update missing plugin message template (#​19445) (Milos Djermanovic)
  • d8ffdd4 fix: do not exit process on rule crash (#​19436) (Francesco Trotta)
Documentation
  • c5561ea docs: Update README (GitHub Actions Bot)
  • 80b0485 docs: replace var with let and const in rule example (#​19434) (Tanuj Kanti)
  • f67d5e8 docs: Update README (GitHub Actions Bot)
  • 75afc61 docs: Update README (GitHub Actions Bot)
  • 0636cab docs: Update Eleventy from v2 to v3 (#​19415) (Amaresh S M)
  • dd7d930 docs: Update README (GitHub Actions Bot)
Chores
  • a8c9a9f chore: update @eslint/eslintrc and @eslint/js (#​19453) (Francesco Trotta)
  • 265e0cf chore: package.json update for @​eslint/js release (Jenkins)
  • 3401b85 test: add test for Rule.ReportDescriptor type (#​19449) (Francesco Trotta)
  • e497aa7 chore: update rewrite dependencies (#​19448) (Francesco Trotta)
  • dab5478 chore: better error message for missing plugin in config (#​19402) (Tanuj Kanti)
  • ebfe2eb chore: set js language for bug report issue config block (#​19439) (Josh Goldberg ✨)
  • 5fd211d test: processors can return subpaths (#​19425) (Milos Djermanovic)

v9.20.1

Compare Source

Bug Fixes
Documentation
  • fe3ccb2 docs: allow typing in search box while dropdown is open (#​19424) (Amaresh S M)
  • 93c78a5 docs: Add instructions for pnpm compat (#​19422) (Nicholas C. Zakas)
  • b476a93 docs: Fix Keyboard Navigation for Search Results (#​19416) (Amaresh S M)
  • ccb60c0 docs: Update README (GitHub Actions Bot)

v9.20.0

Compare Source

Features
  • e89a54a feat: change behavior of inactive flags (#​19386) (Milos Djermanovic)
Bug Fixes
  • 91d4d9f fix: Bring types in sync with @​eslint/core (#​19157) (Nicholas C. Zakas)
  • fa25c7a fix: Emit warning when empty config file is used (#​19399) (Nicholas C. Zakas)
  • 31a9fd0 fix: Clearer error message for wrong plugin format (#​19380) (Nicholas C. Zakas)
  • 61d99e3 fix: Better error message for unserializable parser (#​19384) (Nicholas C. Zakas)
  • db1b9a6 fix: Ensure module scope is checked for references in consistent-this (#​19383) (Nicholas C. Zakas)
  • 8bcd820 fix: arrow-body-style crash with single-token body (#​19379) (Milos Djermanovic)
Documentation
  • b7012c8 docs: rewrite examples with var using let and const (#​19407) (Mueez Javaid Hashmi)
  • 6406376 docs: Update README (GitHub Actions Bot)
  • 350f2b9 docs: rewrite some examples with var using let and const (#​19404) (Mueez Javaid Hashmi)
  • 93c325a docs: rewrite examples with var using let and const (#​19398) (Mueez Javaid Hashmi)
  • 56ff404 docs: replace var with let or const in rules docs (#​19396) (Daniel Harbrueger)
  • 4053226 docs: change sourceType in no-eval examples (#​19393) (Milos Djermanovic)
  • 1324af0 docs: replace var with let and const in rules docs (#​19392) (Daniel Harbrueger)
  • 8b87e00 docs: replace var with const and let in rules (#​19389) (Tanuj Kanti)
  • 758c66b docs: Explain what frozen rules mean (#​19382) (Nicholas C. Zakas)
  • 0ef8bb8 docs: additional checks for rule examples (#​19358) (Milos Djermanovic)
  • 58ab2f6 docs: fix order of installation steps in getting started (#​19326) (Tanuj Kanti)
Chores

v9.19.0

Compare Source

Features
  • 1637b8e feat: add --report-unused-inline-configs (#​19201) (Josh Goldberg ✨)
Bug Fixes
  • aae6717 fix: sync rule type header comments automatically (#​19276) (Francesco Trotta)
Documentation

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 Renovate Bot.

@netlify Netlify
Copy link

netlify bot commented Feb 27, 2025 •
edited
Loading

✅ Deploy Preview for stylo-docs canceled.

Name Link
🔨 Latest commit 71bb031
🔍 Latest deploy log https://app.netlify.com/sites/stylo-docs/deploys/67c90aa570440a00082debcd

@thom4parisot
Copy link
Member

Pour yjs ça nous intéresse au moins pour setContentInitializor().

@ggrossetie ggrossetie force-pushed the renovate/major-frontend-dependencies branch from a3c140f to 71bb031 Compare March 6, 2025 02:38
@ggrossetie
Copy link
Collaborator Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: front/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @ecrituresnumerique/stylo-front@3.2.15
npm error Found: react@18.3.1
npm error node_modules/react
npm error   react@"~18.3" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"^19" from @welldone-software/why-did-you-render@10.0.1
npm error node_modules/@welldone-software/why-did-you-render
npm error   dev @welldone-software/why-did-you-render@"~10.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-03-06T02_38_25_445Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-03-06T02_38_25_445Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@ggrossetie @thom4parisot