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

Bump esbuild, @vitejs/plugin-react-swc, @vitest/coverage-v8, @vitest/ui, vite and vitest #478

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

Bump esbuild, @vitejs/plugin-react-swc, @vitest/coverage-v8, @vitest/ui, vite and vitest #478

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 26, 2025

Bumps esbuild to 0.25.0 and updates ancestor dependencies esbuild, @vitejs/plugin-react-swc, @vitest/coverage-v8, @vitest/ui, vite and vitest. These dependencies need to be updated together.

Updates esbuild from 0.21.5 to 0.25.0

Release notes

Sourced from esbuild's releases.

v0.25.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.24.0 or ~0.24.0. See npm's documentation about semver for more information.

  • Restrict access to esbuild's development server (GHSA-67mh-4wv8-2f99)

    This change addresses esbuild's first security vulnerability report. Previously esbuild set the Access-Control-Allow-Origin header to * to allow esbuild's development server to be flexible in how it's used for development. However, this allows the websites you visit to make HTTP requests to esbuild's local development server, which gives read-only access to your source code if the website were to fetch your source code's specific URL. You can read more information in the report.

    Starting with this release, CORS will now be disabled, and requests will now be denied if the host does not match the one provided to --serve=. The default host is 0.0.0.0, which refers to all of the IP addresses that represent the local machine (e.g. both 127.0.0.1 and 192.168.0.1). If you want to customize anything about esbuild's development server, you can put a proxy in front of esbuild and modify the incoming and/or outgoing requests.

    In addition, the serve() API call has been changed to return an array of hosts instead of a single host string. This makes it possible to determine all of the hosts that esbuild's development server will accept.

    Thanks to @​sapphi-red for reporting this issue.

  • Delete output files when a build fails in watch mode (#3643)

    It has been requested for esbuild to delete files when a build fails in watch mode. Previously esbuild left the old files in place, which could cause people to not immediately realize that the most recent build failed. With this release, esbuild will now delete all output files if a rebuild fails. Fixing the build error and triggering another rebuild will restore all output files again.

  • Fix correctness issues with the CSS nesting transform (#3620, #3877, #3933, #3997, #4005, #4037, #4038)

    This release fixes the following problems:

    • Naive expansion of CSS nesting can result in an exponential blow-up of generated CSS if each nesting level has multiple selectors. Previously esbuild sometimes collapsed individual nesting levels using :is() to limit expansion. However, this collapsing wasn't correct in some cases, so it has been removed to fix correctness issues.

      /* Original code */
.parent {
  > .a,
  > .b1 > .b2 {
    color: red;
  }
}
/* Old output (with --supported:nesting=false) */
.parent > :is(.a, .b1 > .b2) {
color: red;
}
/* New output (with --supported:nesting=false) */
.parent > .a,
.parent > .b1 > .b2 {
color: red;
}

      Thanks to @​tim-we for working on a fix.

    • The & CSS nesting selector can be repeated multiple times to increase CSS specificity. Previously esbuild ignored this possibility and incorrectly considered && to have the same specificity as &. With this release, this should now work correctly:

      /* Original code (color should be red) */

... (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

    

  • e9174d6 publish 0.25.0 to npm
    • 

  • c27dbeb fix hosts in plugin-tests.js
    • 

  • 6794f60 fix hosts in node-unref-tests.js
    • 

  • de85afd Merge commit from fork
    • 

  • da1de1b fix #4065: bitwise operators can return bigints
    • 

  • f4e9d19 switch case liveness: default is always last
    • 

  • 7aa47c3 fix #4028: minify live/dead switch cases better
    • 

  • 22ecd30 minify: more constant folding for strict equality
    • 

  • 4cdf03c fix #4053: reordering of .tsx in node_modules
    • 

  • dc71977 fix #3692: 0 now picks a random ephemeral port
    • 

  • Additional commits viewable in compare view
    • 







Updates @vitejs/plugin-react-swc from 3.7.0 to 3.8.0



Release notes

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




v3.8.0


Add useAtYourOwnRisk_mutateSwcOptions option


The future of Vite is with OXC, and from the beginning this was a design choice to not exposed too many specialties from SWC so that Vite React users can move to another transformer later.
Also debugging why some specific version of decorators with some other unstable/legacy feature doesn't work is not fun, so we won't provide support for it, hence the name useAtYourOwnRisk.


react({
  useAtYourOwnRisk_mutateSwcOptions(options) {
    options.jsc.parser.decorators = true;
    options.jsc.transform.decoratorVersion = "2022-03";
  },
});


v3.7.2


Add Vite 6 to peerDependencies range #207


Thanks @​RobinTail


Revert throw when refresh runtime is loaded twice #237


Revert the 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.


This revert was done in the Babel plugin last year and I didn't port it back.


v3.7.1


Ignore directive sourcemap error #231







Changelog

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




3.8.0


Add useAtYourOwnRisk_mutateSwcOptions option


The future of Vite is with OXC, and from the beginning this was a design choice to not exposed too many specialties from SWC so that Vite React users can move to another transformer later.
Also debugging why some specific version of decorators with some other unstable/legacy feature doesn't work is not fun, so we won't provide support for it, hence the name useAtYourOwnRisk.


react({
  useAtYourOwnRisk_mutateSwcOptions(options) {
    options.jsc.parser.decorators = true;
    options.jsc.transform.decoratorVersion = "2022-03";
  },
});


3.7.2


Add Vite 6 to peerDependencies range #207


Thanks @​RobinTail


Revert throw when refresh runtime is loaded twice #237


Revert the 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.


This revert was done in the Babel plugin last year and I didn't port it back.


3.7.1


Ignore directive sourcemap error #231







Commits






Updates @vitest/coverage-v8 from 1.6.0 to 3.0.7



Release notes

Sourced from @​vitest/coverage-v8's releases.




v3.0.7


   🐞 Bug Fixes



   🏎 Performance



    View changes on GitHub


v3.0.6


   🐞 Bug Fixes



    View changes on GitHub


v3.0.5


This release includes security patches for:






... (truncated)





Commits






Updates @vitest/ui from 1.6.0 to 3.0.7



Release notes

Sourced from @​vitest/ui's releases.




v3.0.7


   🐞 Bug Fixes



   🏎 Performance



    View changes on GitHub


v3.0.6


   🐞 Bug Fixes



    View changes on GitHub


v3.0.5


This release includes security patches for:






... (truncated)





Commits






Updates vite from 5.4.6 to 6.2.0



Release notes

Sourced from vite's releases.




[email protected]


Please refer to CHANGELOG.md for details.


v6.2.0


Please refer to CHANGELOG.md for details.


v6.2.0-beta.1


Please refer to CHANGELOG.md for details.


v6.2.0-beta.0


Please refer to CHANGELOG.md for details.


[email protected]


Please refer to CHANGELOG.md for details.


v6.1.1


Please refer to CHANGELOG.md for details.


[email protected]


Please refer to CHANGELOG.md for details.


v6.1.0


Please refer to CHANGELOG.md for details.


v6.1.0-beta.2


Please refer to CHANGELOG.md for details.


v6.1.0-beta.1


Please refer to CHANGELOG.md for details.


v6.1.0-beta.0


Please refer to CHANGELOG.md for details.


v6.0.11


Please refer to CHANGELOG.md for details.


v6.0.10


Please refer to CHANGELOG.md for details.


v6.0.9


This version contains a breaking change due to security fixes. See GHSA-vg6x-rcgg-rjx6 for more details.


Please refer to CHANGELOG.md for details.


v6.0.8


Please refer to CHANGELOG.md for details.


v6.0.7


Please refer to CHANGELOG.md for details.





... (truncated)





Changelog

Sourced from vite's changelog.




6.2.0 (2025-02-25)



6.2.0-beta.1 (2025-02-21)


    

  • fix(css): temporary add ?. after this.getModuleInfo in vite:css-post (#19478) (12b0b8a), closes #19478
    • 



6.2.0-beta.0 (2025-02-21)



6.1.1 (2025-02-19)



6.1.0 (2025-02-05)


Features






... (truncated)





Commits






Updates vitest from 1.6.0 to 3.0.7



Release notes

Sourced from vitest's releases.




v3.0.7


   🐞 Bug Fixes



   🏎 Performance



    View changes on GitHub


v3.0.6


   🐞 Bug Fixes



    

  
  



      


          

          
  

    
  
    
    

  

  




          

        
      




  





       
            



      

  
        

  

      

  
  

  
          

  

    

      


  

      
        @dependabot
  




      

        
          Bump esbuild, @vitejs/plugin-react-swc, @vitest/coverage-v8, @vitest/…
        

          
                        
      


      

        

    
    
    

  

    


      


      

        

          

    
    
    

  

  

    
  



        

      


      

        
          b9ef5c0
        
      

    

  

    

      
…ui, vite and vitest

Bumps [esbuild](https://github.com/evanw/esbuild) to 0.25.0 and updates ancestor dependencies [esbuild](https://github.com/evanw/esbuild), [@vitejs/plugin-react-swc](https://github.com/vitejs/vite-plugin-react-swc), [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8), [@vitest/ui](https://github.com/vitest-dev/vitest/tree/HEAD/packages/ui), [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). These dependencies need to be updated together.


Updates `esbuild` from 0.21.5 to 0.25.0
- [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.0)

Updates `@vitejs/plugin-react-swc` from 3.7.0 to 3.8.0
- [Release notes](https://github.com/vitejs/vite-plugin-react-swc/releases)
- [Changelog](https://github.com/vitejs/vite-plugin-react-swc/blob/main/CHANGELOG.md)
- [Commits](vitejs/vite-plugin-react-swc@v3.7.0...v3.8.0)

Updates `@vitest/coverage-v8` from 1.6.0 to 3.0.7
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v3.0.7/packages/coverage-v8)

Updates `@vitest/ui` from 1.6.0 to 3.0.7
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v3.0.7/packages/ui)

Updates `vite` from 5.4.6 to 6.2.0
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/[email protected]/packages/vite)

Updates `vitest` from 1.6.0 to 3.0.7
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v3.0.7/packages/vitest)

---
updated-dependencies:
- dependency-name: esbuild
  dependency-type: indirect
- dependency-name: "@vitejs/plugin-react-swc"
  dependency-type: direct:development
- dependency-name: "@vitest/coverage-v8"
  dependency-type: direct:development
- dependency-name: "@vitest/ui"
  dependency-type: direct:development
- dependency-name: vite
  dependency-type: direct:development
- dependency-name: vitest
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <[email protected]>

    







  








      

  
            

    

      
    

    


      

          @dependabot
dependabot
bot



          added
  the 

  dependencies

  Pull requests that update a dependency file
 label


      Feb 26, 2025

    

  



  

  

    
  


  

      

  This was referenced Feb 26, 2025





  


  

      
   Closed

  






      






  


  

      
   Closed

  






  













  
  

    

      

  




    


    

      

              

  
    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








      

  

    

        

    Projects
  


        




    None yet




  



      


  

    
  

    Milestone
  


      No milestone





    
      
          
  

    

      

        
          

            
    

    Development
  



              


Successfully merging this pull request may close these issues.



  


        
      

    

  


      

    

  
      

  

    

      0 participants