search

DSsenegal / app-snpay

Intégrer des méthodes de paiement locales telles que Wave ou Orange Money dans Saleor
https://app-snpay.onrender.com
Other
1 stars 2 forks source link

[skip ci]: Bump the vite group across 1 directory with 3 updates #66

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 2 months ago

Bumps the vite group with 3 updates in the / directory: @vitejs/plugin-react, vite and vitest.

Updates @vitejs/plugin-react from 4.2.1 to 4.3.1

Release notes

Sourced from @​vitejs/plugin-react's releases.

v4.3.1

Fix support for React Compiler with React 18

The previous version made this assumption that the compiler was only usable with React 19, but it's possible to use it with React 18 and a custom runtimeModule: https://gist.github.com/poteto/37c076bf112a07ba39d0e5f0645fec43

When using a custom runtimeModule, the plugin will not try to pre-optimize react/compiler-runtime dependency.

Reminder: Vite expect code outside of node_modules to be ESM, so you will need to update the gist with import React from 'react'.

v4.3.0

Fix support for React compiler

Don't set retainLines: true when the React compiler is used. This creates whitespace issues and the compiler is modifying the JSX too much to get correct line numbers after that. If you want to use the React compiler and get back correct line numbers for tools like vite-plugin-react-click-to-component to work, you should update your config to something like:

export default defineConfig(({ command }) => {
  const babelPlugins = [['babel-plugin-react-compiler', {}]]
  if (command === 'serve') {
    babelPlugins.push(['@babel/plugin-transform-react-jsx-development', {}])
  }

return {
plugins: [react({ babel: { plugins: babelPlugins } })],
}
})

Support HMR for class components

This is a long overdue and should fix some issues people had with HMR when migrating from CRA.

Changelog

Sourced from @​vitejs/plugin-react's changelog.

4.3.1 (2024-06-10)

Fix support for React Compiler with React 18

The previous version made this assumption that the compiler was only usable with React 19, but it's possible to use it with React 18 and a custom runtimeModule: https://gist.github.com/poteto/37c076bf112a07ba39d0e5f0645fec43

When using a custom runtimeModule, the plugin will not try to pre-optimize react/compiler-runtime dependency.

Reminder: Vite expect code outside of node_modules to be ESM, so you will need to update the gist with import React from 'react'.

4.3.0 (2024-05-22)

Fix support for React compiler

Don't set retainLines: true when the React compiler is used. This creates whitespace issues and the compiler is modifying the JSX too much to get correct line numbers after that. If you want to use the React compiler and get back correct line numbers for tools like vite-plugin-react-click-to-component to work, you should update your config to something like:

export default defineConfig(({ command }) => {
  const babelPlugins = [['babel-plugin-react-compiler', {}]]
  if (command === 'serve') {
    babelPlugins.push(['@babel/plugin-transform-react-jsx-development', {}])
  }

return {
plugins: [react({ babel: { plugins: babelPlugins } })],
}
})

Support HMR for class components

This is a long overdue and should fix some issues people had with HMR when migrating from CRA.

Commits


Updates vite from 5.2.10 to 5.4.7

Release notes

Sourced from vite's releases.

create-vite@5.4.0

Please refer to CHANGELOG.md for details.

create-vite@5.3.0

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

5.4.7 (2024-09-20)

5.4.6 (2024-09-16)

5.4.5 (2024-09-13)

5.4.4 (2024-09-11)

5.4.3 (2024-09-03)

5.4.2 (2024-08-20)

... (truncated)

Commits


Updates vitest from 1.5.2 to 2.1.1

Release notes

Sourced from vitest's releases.

v2.1.1

   🐞 Bug Fixes

    View changes on GitHub

v2.1.0

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)

await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()


const [firstPost] = screen.getByRole('listitem').all()


await firstPost.getByRole('button', { name: 'Delete' }).click()


expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

Potential Breaking Change

  • workspace:
    • Correctly resolve workspace globs and file paths  -  by @​sheremet-va in vitest-dev/vitest#6316 (afdcb)
    • This changes how the custom glob pattern in the workspace config is treated. Any file matching the glob is considered a Vitest config file. Any folder matching the glob pattern is treated as a workspace project and is subject to the regular config resolution (single vitest.config.ts or vite.config.ts inside the folder)
    • For example, projects/* will match anything inside the projects folder. If it's a folder, we try to find the config inside that folder (if there is none, it is still treated as a project with the default config). If it's a file, it will be treated as a Vitest config. projects/**/* previously would assume that you only wanted to have folders as projects, but now it will match every single file insideprojects.
    • This change doesn't affect non-glob usage.

   🚀 Features

... (truncated)

Commits
  • 699055e chore: release v2.1.1
  • 36b5ace fix(workspace): resolve glob pattern once to avoid name collision (#6489)
  • 16aa76c fix(browser): make example test callbacks async (#6484)
  • 9f1fd18 chore: release v2.1.0
  • 94a186e fix(ui): render project name consistently (#6329)
  • ac698b1 fix: expect.getState().testPath always returns correct path (#6472)
  • b2be23e chore: release v2.1.0-beta.7
  • 0b44722 fix: ignore importer when resolving Vitest (#6469)
  • 97773e2 chore: fix edge case in license files bundling (#6460)
  • 7ab0f4a feat(browser): support --inspect-brk (#6434)
  • Additional commits viewable 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
dependabot[bot] commented 2 months ago

Superseded by #68.