search

shreyaskarnik / DistiLlama

Chrome Extension to Summarize or Chat with Web Pages/Local Documents Using locally running LLMs. Keep all of your data and conversations private. 🔐
MIT License
279 stars 28 forks source link

Bump vite and @vitejs/plugin-react #74

Closed dependabot[bot] closed 10 months ago

dependabot[bot] commented 10 months ago

Bumps vite and @vitejs/plugin-react. These dependencies needed to be updated together. Updates vite from 3.2.7 to 5.0.10

Release notes

Sourced from vite's releases.

create-vite@5.0.0

Please refer to CHANGELOG.md for details.

create-vite@5.0.0-beta.1

Please refer to CHANGELOG.md for details.

create-vite@5.0.0-beta.0

Please refer to CHANGELOG.md for details.

create-vite@4.4.1

Please refer to CHANGELOG.md for details.

create-vite@4.4.0

Please refer to CHANGELOG.md for details.

create-vite@4.3.2

Please refer to CHANGELOG.md for details.

create-vite@4.3.1

Please refer to CHANGELOG.md for details.

create-vite@4.3.0

Please refer to CHANGELOG.md for details.

create-vite@4.3.0-beta.0

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

5.0.10 (2023-12-15)

  • fix: omit protocol does not require pre-transform (#15355) (d9ae1b2), closes #15355
  • fix(build): use base64 for inline SVG if it contains both single and double quotes (#15271) (1bbff16), closes #15271

5.0.9 (2023-12-14)

5.0.8 (2023-12-12)

5.0.7 (2023-12-08)

5.0.6 (2023-12-06)

5.0.5 (2023-12-04)

... (truncated)

Commits


Updates @vitejs/plugin-react from 2.2.0 to 4.2.1

Release notes

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

v4.2.1

Remove generic parameter on Plugin to avoid type error with Rollup 4/Vite 5 and skipLibCheck: false.

I expect very few people to currently use this feature, but if you are extending the React plugin via api object, you can get back the typing of the hook by importing ViteReactPluginApi:

import type { Plugin } from 'vite'
import type { ViteReactPluginApi } from '@vitejs/plugin-react'

export const somePlugin: Plugin = {
name: 'some-plugin',
api: {
reactBabel: (babelConfig) => {
babelConfig.plugins.push('some-babel-plugin')
},
} satisfies ViteReactPluginApi,
}

v4.2.0

Update peer dependency range to target Vite 5

There were no breaking change that impacted this plugin, so any combination of React plugins and Vite core version will work.

Align jsx runtime for optimized dependencies

This will only affect people using internal libraries that contains untranspiled JSX. This change aligns the optimizer with the source code and avoid issues when the published source don't have React in the scope.

Reminder: While being partially supported in Vite, publishing TS & JSX outside of internal libraries is highly discouraged.

v4.1.1

  • Enable retainLines to get correct line numbers for jsxDev (fix #235)

v4.1.0

  • Add @types/babel__cores to dependencies (fix #211)
  • Improve build perf when not using Babel plugins by lazy loading @babel/core #212
  • Better invalidation message when an export is added & fix HMR for export of nullish values #215
  • Include non-dev jsx runtime in optimizeDeps & support HMR for JS files using the non dev runtime #224
  • The build output now contains a index.d.cts file so you don't get types errors when setting moduleResolution to node16 or nodenext in your tsconfig (we recommend using bundler which is more close to how Vite works)

v4.0.4

  • Fix #198: Enable Babel if presets list is not empty

v4.0.3

  • Revert #108: Remove throw when refresh runtime is loaded twice to enable usage in micro frontend apps. This was added to help fix setup usage, and this is not worth an annoying warning for others or a config parameter.

v4.0.2

  • Fix fast-refresh for files that are transformed into jsx (#188)

plugin-react@4.0.1

... (truncated)

Changelog

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

4.2.1 (2023-12-04)

Remove generic parameter on Plugin to avoid type error with Rollup 4/Vite 5 and skipLibCheck: false.

I expect very few people to currently use this feature, but if you are extending the React plugin via api object, you can get back the typing of the hook by importing ViteReactPluginApi:

import type { Plugin } from 'vite'
import type { ViteReactPluginApi } from '@vitejs/plugin-react'

export const somePlugin: Plugin = {
name: 'some-plugin',
api: {
reactBabel: (babelConfig) => {
babelConfig.plugins.push('some-babel-plugin')
},
} satisfies ViteReactPluginApi,
}

4.2.0 (2023-11-16)

Update peer dependency range to target Vite 5

There were no breaking change that impacted this plugin, so any combination of React plugins and Vite core version will work.

Align jsx runtime for optimized dependencies

This will only affect people using internal libraries that contains untranspiled JSX. This change aligns the optimizer with the source code and avoid issues when the published source don't have React in the scope.

Reminder: While being partially supported in Vite, publishing TS & JSX outside of internal libraries is highly discouraged.

4.1.1 (2023-11-02)

  • Enable retainLines to get correct line numbers for jsxDev (fix #235)

4.1.0 (2023-09-24)

  • Add @types/babel__cores to dependencies (fix #211)
  • Improve build perf when not using Babel plugins by lazy loading @babel/core #212
  • Better invalidation message when an export is added & fix HMR for export of nullish values #215
  • Include non-dev jsx runtime in optimizeDeps & support HMR for JS files using the non dev runtime #224
  • The build output now contains a index.d.cts file so you don't get types errors when setting moduleResolution to node16 or nodenext in your tsconfig (we recommend using bundler which is more close to how Vite works)

4.0.4 (2023-07-31)

  • Fix #198: Enable Babel if presets list is not empty

4.0.3 (2023-07-10)

... (truncated)

Commits


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 this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)