Skip to content

Bump the npm_and_yarn group across 2 directories with 3 updates#2

Open
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/npm_and_yarn/frontend/npm_and_yarn-593c55524f
Open

Bump the npm_and_yarn group across 2 directories with 3 updates#2
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/npm_and_yarn/frontend/npm_and_yarn-593c55524f

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github Sep 11, 2025

Bumps the npm_and_yarn group with 3 updates in the /frontend directory: vite, esbuild and @sveltejs/vite-plugin-svelte.
Bumps the npm_and_yarn group with 2 updates in the /website/other/bezier-rs-demos directory: vite and esbuild.

Updates vite from 5.4.14 to 5.4.20

Release notes

Sourced from vite's releases.

v5.4.20

Please refer to CHANGELOG.md for details.

v5.4.19

Please refer to CHANGELOG.md for details.

v5.4.18

Please refer to CHANGELOG.md for details.

v5.4.17

Please refer to CHANGELOG.md for details.

v5.4.16

Please refer to CHANGELOG.md for details.

v5.4.15

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

5.4.20 (2025-09-08)

5.4.19 (2025-04-30)

5.4.18 (2025-04-10)

5.4.17 (2025-04-03)

5.4.16 (2025-03-31)

5.4.15 (2025-03-24)

Commits

Updates esbuild from 0.21.5 to 0.25.9

Release notes

Sourced from esbuild's releases.

v0.25.9

  • Better support building projects that use Yarn on Windows (#3131, #3663)

    With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the C: drive. The problem was as follows:

    1. Yarn in Plug'n'Play mode on Windows stores its global module cache on the C: drive
    2. Some developers put their projects on the D: drive
    3. Yarn generates relative paths that use ../.. to get from the project directory to the cache directory
    4. Windows-style paths don't support directory traversal between drives via .. (so D:\.. is just D:)
    5. I didn't have access to a Windows machine for testing this edge case

    Yarn works around this edge case by pretending Windows-style paths beginning with C:\ are actually Unix-style paths beginning with /C:/, so the ../.. path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.

  • Preserve parentheses around function expressions (#4252)

    The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.

    Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:

    // Original code
const fn0 = () => 0
const fn1 = (() => 1)
console.log(fn0, function() { return fn1() }())
// Old output
const fn0 = () => 0;
const fn1 = () => 1;
console.log(fn0, function() {
return fn1();
}());
// New output
const fn0 = () => 0;
const fn1 = (() => 1);
console.log(fn0, (function() {
return fn1();
})());

    Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.

  • Update Go from 1.23.10 to 1.23.12 (#4257, #4258)

    This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.

v0.25.8

  • Fix another TypeScript parsing edge case (#4248)

    This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2024

This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).

0.24.2

  • Fix regression with --define and import.meta (#4010, #4012, #4013)

    The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.

    This fix was contributed by @​sapphi-red.

0.24.1

  • Allow es2024 as a target in tsconfig.json (#4004)

    TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

    {
  "compilerOptions": {
    "target": "ES2024"
  }
}

    As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

    This fix was contributed by @​billyjanitsch.

  • Allow automatic semicolon insertion after get/set

    This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:

    class Foo {
  get
  *x() {}
  set
  *y() {}
}

    The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.

  • Allow quoted property names in --define and --pure (#4008)

    The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:

    

    • 






... (truncated)





Commits






Updates @sveltejs/vite-plugin-svelte from 3.1.2 to 6.2.0



Release notes

Sourced from @​sveltejs/vite-plugin-svelte's releases.




@​sveltejs/vite-plugin-svelte@​6.2.0


Minor Changes


    

  • feat(rolldown-vite): enable optimization.inlineConst by default to ensure treeshaking works with esm-env in svelte (#1207)
    • 



@​sveltejs/vite-plugin-svelte@​6.1.4


Patch Changes


    

  • 

    fix: allow preprocess plugin to run twice (#1206)
    

    • 

  • 

    fix(types): update urls to PreprocessorGroup and CompileOptions in type documention (#1203)
    

    • 

  • 

    replace kleur dependency with builtin node:utils styleText (#1210)
    

    • 



@​sveltejs/vite-plugin-svelte@​6.1.3


Patch Changes


    

  • fix(api): add api.filter and deprecate api.idFilter to avoid confusing filter.id = idFilter.id assignments when used as hybrid filter in other plugins (#1199)
    • 



@​sveltejs/vite-plugin-svelte@​6.1.2


Patch Changes


    

  • fix: ensure compiled css is returned when reloading during dev with ssr (e.g. SvelteKit) (#1194)
    • 



@​sveltejs/vite-plugin-svelte@​6.1.1


Patch Changes


    

  • fix: ensure compiled svelte css is loaded correctly when rebuilding in build --watch (#1189)
    • 



@​sveltejs/vite-plugin-svelte@​6.1.0


Minor Changes


    

  • feat: add support for the new experimental.async option and apply dynamicCompileOptions when compiling Svelte modules (#1176)
    • 



Patch Changes


    

  • 

    skip comment blocks when reporting compiler errors that might be caused by a preprocessor issue (#1166)
    

    • 

  • 

    increase logLevel to info for "no Svelte config found" message (#1179)
    

    • 



@​sveltejs/vite-plugin-svelte@​6.0.0


Major Changes


    

  • 

    drop support for node18 and update exports map to use default export. cjs is supported via require esm in node 20.19+ (#1129)
    

    • 

  • 

    Remove experimental "advanced raw queries" feature. Basic File.svelte?raw is still supported. (#1145)
    

    • 






... (truncated)





Changelog

Sourced from @​sveltejs/vite-plugin-svelte's changelog.




6.2.0


Minor Changes


    

  • feat(rolldown-vite): enable optimization.inlineConst by default to ensure treeshaking works with esm-env in svelte (#1207)
    • 



6.1.4


Patch Changes


    

  • 

    fix: allow preprocess plugin to run twice (#1206)
    

    • 

  • 

    fix(types): update urls to PreprocessorGroup and CompileOptions in type documention (#1203)
    

    • 

  • 

    replace kleur dependency with builtin node:utils styleText (#1210)
    

    • 



6.1.3


Patch Changes


    

  • fix(api): add api.filter and deprecate api.idFilter to avoid confusing filter.id = idFilter.id assignments when used as hybrid filter in other plugins (#1199)
    • 



6.1.2


Patch Changes


    

  • fix: ensure compiled css is returned when reloading during dev with ssr (e.g. SvelteKit) (#1194)
    • 



6.1.1


Patch Changes


    

  • fix: ensure compiled svelte css is loaded correctly when rebuilding in build --watch (#1189)
    • 



6.1.0


Minor Changes


    

  • feat: add support for the new experimental.async option and apply dynamicCompileOptions when compiling Svelte modules (#1176)
    • 



Patch Changes


    

  • 

    skip comment blocks when reporting compiler errors that might be caused by a preprocessor issue (#1166)
    

    • 

  • 

    increase logLevel to info for "no Svelte config found" message (#1179)
    

    • 






... (truncated)





Commits





Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​sveltejs/vite-plugin-svelte since your current version.






Updates vite from 5.4.20 to 7.1.5



Release notes

Sourced from vite's releases.




v5.4.20


Please refer to CHANGELOG.md for details.


v5.4.19


Please refer to CHANGELOG.md for details.


v5.4.18


Please refer to CHANGELOG.md for details.


v5.4.17


Please refer to CHANGELOG.md for details.


v5.4.16


Please refer to CHANGELOG.md for details.


v5.4.15


Please refer to CHANGELOG.md for details.







Changelog

Sourced from vite's changelog.




5.4.20 (2025-09-08)



5.4.19 (2025-04-30)



5.4.18 (2025-04-10)



5.4.17 (2025-04-03)



5.4.16 (2025-03-31)



5.4.15 (2025-03-24)








Commits






Updates vite from 5.4.14 to 5.4.20



Release notes

Sourced from vite's releases.




v5.4.20


Please refer to CHANGELOG.md for details.


v5.4.19


Please refer to CHANGELOG.md for details.


v5.4.18


Please refer to CHANGELOG.md for details.


v5.4.17


Please refer to CHANGELOG.md for details.


v5.4.16


Please refer to CHANGELOG.md for details.


v5.4.15


Please refer to CHANGELOG.md for details.







Changelog

Sourced from vite's changelog.




5.4.20 (2025-09-08)



5.4.19 (2025-04-30)



5.4.18 (2025-04-10)



5.4.17 (2025-04-03)



5.4.16 (2025-03-31)



5.4.15 (2025-03-24)








Commits






Updates esbuild from 0.21.5 to 0.25.9



Release notes

Sourced from esbuild's releases.




v0.25.9


    

  • 

    Better support building projects that use Yarn on Windows (#3131, #3663)
    

    With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the C: drive. The problem was as follows:
    

      

    1. Yarn in Plug'n'Play mode on Windows stores its global module cache on the C: drive
      2. 

    2. Some developers put their projects on the D: drive
      3. 

    3. Yarn generates relative paths that use ../.. to get from the project directory to the cache directory
      4. 

    4. Windows-style paths don't support directory traversal between drives via .. (so D:\.. is just D:)
      5. 

    5. I didn't have access to a Windows machine for testing this edge case
      6. 

    

    Yarn works around this edge case by pretending Windows-style paths beginning with C:\ are actually Unix-style paths beginning with /C:/, so the ../.. path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.
    

    • 

  • 

    Preserve parentheses around function expressions (#4252)
    

    The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.
    

    Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:
    

    // Original code
const fn0 = () => 0
const fn1 = (() => 1)
console.log(fn0, function() { return fn1() }())
// Old output
const fn0 = () => 0;
const fn1 = () => 1;
console.log(fn0, function() {
return fn1();
}());
// New output
const fn0 = () => 0;
const fn1 = (() => 1);
console.log(fn0, (function() {
return fn1();
})());
    

    Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.
    

    • 

  • 

    Update Go from 1.23.10 to 1.23.12 (#4257, #4258)
    

    This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.
    

    • 



v0.25.8


    

  • 

    Fix another TypeScript parsing edge case (#4248)
    

    This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:
    

    • 






... (truncated)





Changelog

Sourced from esbuild's changelog.




Changelog: 2024


This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).


0.24.2


    

  • 

    Fix regression with --define and import.meta (#4010, #4012, #4013)
    

    The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.
    

    This fix was contributed by @​sapphi-red.
    

    • 



0.24.1


    

  • 

    Allow es2024 as a target in tsconfig.json (#4004)
    

    TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:
    

    {
  "compilerOptions": {
    "target": "ES2024"
  }
}
    

    As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.
    

    This fix was contributed by @​billyjanitsch.
    

    • 

  • 

    Allow automatic semicolon insertion after get/set
    

    This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:
    

    class Foo {
  get
  *x() {}
  set
  *y() {}
}
    

    The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.
    

    • 

  • 

    Allow quoted property names in --define and --pure (#4008)
    

    The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:
    

    

    • 






... (truncated)





Commits






Updates vite from 5.4.20 to 7.1.5



Release notes

Sourced from vite's releases.




v5.4.20


Please refer to CHANGELOG.md for details.


v5.4.19


Please refer to CHANGELOG.md for details.


v5.4.18


Please refer to CHANGELOG.md for details.


v5.4.17


Please refer to CHANGELOG.md for details.


v5.4.16


Please refer to CHANGELOG.md for details.


v5.4.15


Please refer to CHANGELOG.md for details.







Changelog

Sourced from vite's changelog.




5.4.20 (2025-09-08)



5.4.19 (2025-04-30)



5.4.18 (2025-04-10)



5.4.17 (2025-04-03)



5.4.16 (2025-03-31)



5.4.15 (2025-03-24)








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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
    • 

  • @dependabot ignore <dependency name> 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 <dependency name> 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 <dependency name> 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 <dependency name> will remove all of the ignore conditions of the specified dependency
    • 

  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
    
You can disable automated security fix PRs for this repo from the Security Alerts page.
    • 




    

  
  



      


          

          
  
  

    
  
    
    

  

  

  



                    

          
        





  





    



      

  
        

  

      

  
  

  
          

  

    

      


  

      
        @dependabot
  




      

        
          Bump the npm_and_yarn group across 2 directories with 3 updates
        

          
                        
      


      

        

    
    
    

  

    


      


      

        

          

    
    
    

  

  

    
  



        

      


      

        
          8e0fc1a
        
      

    

  

    

      
Bumps the npm_and_yarn group with 3 updates in the /frontend directory: [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite), [esbuild](https://github.com/evanw/esbuild) and [@sveltejs/vite-plugin-svelte](https://github.com/sveltejs/vite-plugin-svelte/tree/HEAD/packages/vite-plugin-svelte).
Bumps the npm_and_yarn group with 2 updates in the /website/other/bezier-rs-demos directory: [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) and [esbuild](https://github.com/evanw/esbuild).


Updates `vite` from 5.4.14 to 5.4.20
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v5.4.20/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v5.4.20/packages/vite)

Updates `esbuild` from 0.21.5 to 0.25.9
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2024.md)
- [Commits](evanw/esbuild@v0.21.5...v0.25.9)

Updates `@sveltejs/vite-plugin-svelte` from 3.1.2 to 6.2.0
- [Release notes](https://github.com/sveltejs/vite-plugin-svelte/releases)
- [Changelog](https://github.com/sveltejs/vite-plugin-svelte/blob/main/packages/vite-plugin-svelte/CHANGELOG.md)
- [Commits](https://github.com/sveltejs/vite-plugin-svelte/commits/@sveltejs/vite-plugin-svelte@6.2.0/packages/vite-plugin-svelte)

Updates `vite` from 5.4.20 to 7.1.5
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v5.4.20/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v5.4.20/packages/vite)

Updates `vite` from 5.4.14 to 5.4.20
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v5.4.20/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v5.4.20/packages/vite)

Updates `esbuild` from 0.21.5 to 0.25.9
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2024.md)
- [Commits](evanw/esbuild@v0.21.5...v0.25.9)

Updates `vite` from 5.4.20 to 7.1.5
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v5.4.20/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v5.4.20/packages/vite)

---
updated-dependencies:
- dependency-name: vite
  dependency-version: 5.4.20
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: esbuild
  dependency-version: 0.25.9
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: "@sveltejs/vite-plugin-svelte"
  dependency-version: 6.2.0
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: vite
  dependency-version: 7.1.5
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: vite
  dependency-version: 5.4.20
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: esbuild
  dependency-version: 0.25.9
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: vite
  dependency-version: 7.1.5
  dependency-type: direct:development
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>

    







  








      

  
            

    

      
    

    


      


          @dependabot
dependabot
bot



            added
      

  dependencies

  Pull requests that update a dependency file

      

  javascript

  Pull requests that update javascript code

  labels


      Sep 11, 2025

    

  












  
  

    

      

  










  








  
      

  
    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
  



    

      

    dependencies

  Pull requests that update a dependency file
  

    javascript

  Pull requests that update javascript code








      

  

    

        

    Projects
  


        




    None yet




  



      


  

    
  

    Milestone
  


      No milestone





    
      
          


  

    

      
        

          
  

    Development
  



            


Successfully merging this pull request may close these issues.





  
  



      
    

  




      

    

  
      

  

    

      0 participants