Skip to content

Bump esbuild, @astrojs/react, astro, vite and vitest in /frontend - #862

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/frontend/multi-c407e1ddb8
Open

Bump esbuild, @astrojs/react, astro, vite and vitest in /frontend#862
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/frontend/multi-c407e1ddb8

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Apr 28, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps esbuild to 0.25.3 and updates ancestor dependencies esbuild, @astrojs/react, astro, vite and vitest. These dependencies need to be updated together.

Updates esbuild from 0.21.5 to 0.25.3

Release notes

Sourced from esbuild's releases.

v0.25.3

  • Fix lowered async arrow functions before super() (#4141, #4142)

    This change makes it possible to call an async arrow function in a constructor before calling super() when targeting environments without async support, as long as the function body doesn't reference this. Here's an example (notice the change from this to null):

    // Original code
class Foo extends Object {
  constructor() {
    (async () => await foo())()
    super()
  }
}
// Old output (with --target=es2016)
class Foo extends Object {
constructor() {
(() => __async(this, null, function* () {
return yield foo();
}))();
super();
}
}
// New output (with --target=es2016)
class Foo extends Object {
constructor() {
(() => __async(null, null, function* () {
return yield foo();
}))();
super();
}
}

    Some background: Arrow functions with the async keyword are transformed into generator functions for older language targets such as --target=es2016. Since arrow functions capture this, the generated code forwards this into the body of the generator function. However, JavaScript class syntax forbids using this in a constructor before calling super(), and this forwarding was problematic since previously happened even when the function body doesn't use this. Starting with this release, esbuild will now only forward this if it's used within the function body.

    This fix was contributed by @​magic-akari.

  • Fix memory leak with --watch=true (#4131, #4132)

    This release fixes a memory leak with esbuild when --watch=true is used instead of --watch. Previously using --watch=true caused esbuild to continue to use more and more memory for every rebuild, but --watch=true should now behave like --watch and not leak memory.

    This bug happened because esbuild disables the garbage collector when it's not run as a long-lived process for extra speed, but esbuild's checks for which arguments cause esbuild to be a long-lived process weren't updated for the new --watch=true style of boolean command-line flags. This has been an issue since this boolean flag syntax was added in version 0.14.24 in 2022. These checks are unfortunately separate from the regular argument parser because of how esbuild's internals are organized (the command-line interface is exposed as a separate Go API so you can build your own custom esbuild CLI).

    This fix was contributed by @​mxschmitt.

  • More concise output for repeated legal comments (#4139)

    Some libraries have many files and also use the same legal comment text in all files. Previously esbuild would copy each legal comment to the output file. Starting with this release, legal comments duplicated across separate files will now be grouped in the output file by unique comment content.

... (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 @astrojs/react from 3.6.3 to 4.2.5



Release notes

Sourced from @​astrojs/react's releases.




@​astrojs/react@​4.2.5


Patch Changes



@​astrojs/react@​4.2.4


Patch Changes



@​astrojs/react@​4.2.3


Patch Changes



@​astrojs/react@​4.2.2


Patch Changes








Changelog

Sourced from @​astrojs/react's changelog.




4.2.5


Patch Changes



4.2.4


Patch Changes



4.2.3


Patch Changes



4.2.2


Patch Changes



4.2.1


Patch Changes


    

  • #13323 80926fa Thanks @​ematipico! - Updates esbuild and vite to the latest to avoid false positives audits warnings caused by esbuild.
    • 



4.2.0


Minor Changes


    

  • 

    #13036 3c90d8f Thanks @​artmsilva! - Adds experimental support for disabling streaming
    

    This is useful to support libraries that are not compatible with streaming such as some CSS-in-JS libraries. To disable streaming for all React components in your project, set experimentalDisableStreaming: true as a configuration option for @astrojs/react:
    

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import react from '@astrojs/react';
export default defineConfig({
integrations: [
react({


 experimentalDisableStreaming: true,

}),
    • 








... (truncated)





Commits






Updates astro from 4.16.18 to 5.7.7



Release notes

Sourced from astro's releases.




astro@5.7.7


Patch Changes



astro@5.7.6


Patch Changes


    

  • 

    #13703 659904b Thanks @​florian-lefebvre! - Fixes a bug where empty fallbacks could not be provided when using the experimental fonts API
    

    • 

  • 

    #13680 18e1b97 Thanks @​florian-lefebvre! - Improves the UnsupportedExternalRedirect error message to include more details such as the concerned destination
    

    • 

  • 

    #13703 659904b Thanks @​ascorbic! - Simplifies styles for experimental responsive images
    

    ⚠️ BREAKING CHANGE FOR EXPERIMENTAL RESPONSIVE IMAGES ONLY ⚠️
    

    The generated styles for image layouts are now simpler and easier to override. Previously the responsive image component used CSS to set the size and aspect ratio of the images, but this is no longer needed. Now the styles just include object-fit and object-position for all images, and sets max-width: 100% for constrained images and width: 100% for full-width images.
    

    This is an implementation change only, and most users will see no change. However, it may affect any custom styles you have added to your responsive images. Please check your rendered images to determine whether any change to your CSS is needed.
    

    The styles now use the :where() pseudo-class, which has a specificity of 0, meaning that it is easy to override with your own styles. You can now be sure that your own classes will always override the applied styles, as will global styles on img.
    

    An exception is Tailwind 4, which uses cascade layers, meaning the rules are always lower specificity. Astro supports browsers that do not support cascade layers, so we cannot use this. If you need to override the styles using Tailwind 4, you must use !important classes. Do check if this is needed though: there may be a layout that is more appropriate for your use case.
    

    • 

  • 

    #13703 659904b Thanks @​ascorbic! - Adds warnings about using local font files in the publicDir when the experimental fonts API is enabled.
    

    • 

  • 

    #13703 659904b Thanks @​ascorbic! - Renames experimental responsive image layout option from "responsive" to "constrained"
    

    ⚠️ BREAKING CHANGE FOR EXPERIMENTAL RESPONSIVE IMAGES ONLY ⚠️
    

    The layout option called "responsive" is renamed to "constrained" to better reflect its behavior.
    

    The previous name was causing confusion, because it is also the name of the feature. The responsive layout option is specifically for images that are displayed at the requested size, unless they do not fit the width of their container, at which point they would be scaled down to fit. They do not get scaled beyond the intrinsic size of the source image, or the width prop if provided.
    

    It became clear from user feedback that many people (understandably) thought that they needed to set layout to responsive if they wanted to use responsive images. They then struggled with overriding styles to make the image scale up for full-width hero images, for example, when they should have been using full-width layout. Renaming the layout to constrained should make it clearer that this layout is for when you want to constrain the maximum size of the image, but allow it to scale-down.
    

    Upgrading
    

    If you set a default image.experimentalLayout in your astro.config.mjs, or set it on a per-image basis using the layout prop, you will need to change all occurences to constrained:
    

    • 






... (truncated)





Changelog

Sourced from astro's changelog.




5.7.7


Patch Changes



5.7.6


Patch Changes


    

  • 

    #13703 659904b Thanks @​ascorbic! - Fixes a bug where empty fallbacks could not be provided when using the experimental fonts API
    

    • 

  • 

    #13680 18e1b97 Thanks @​florian-lefebvre! - Improves the UnsupportedExternalRedirect error message to include more details such as the concerned destination
    

    • 

  • 

    #13703 659904b Thanks @​ascorbic! - Simplifies styles for experimental responsive images
    

    ⚠️ BREAKING CHANGE FOR EXPERIMENTAL RESPONSIVE IMAGES ONLY ⚠️
    

    The generated styles for image layouts are now simpler and easier to override. Previously the responsive image component used CSS to set the size and aspect ratio of the images, but this is no longer needed. Now the styles just include object-fit and object-position for all images, and sets max-width: 100% for constrained images and width: 100% for full-width images.
    

    This is an implementation change only, and most users will see no change. However, it may affect any custom styles you have added to your responsive images. Please check your rendered images to determine whether any change to your CSS is needed.
    

    The styles now use the :where() pseudo-class, which has a specificity of 0, meaning that it is easy to override with your own styles. You can now be sure that your own classes will always override the applied styles, as will global styles on img.
    

    An exception is Tailwind 4, which uses cascade layers, meaning the rules are always lower specificity. Astro supports browsers that do not support cascade layers, so we cannot use this. If you need to override the styles using Tailwind 4, you must use !important classes. Do check if this is needed though: there may be a layout that is more appropriate for your use case.
    

    • 

  • 

    #13703 659904b Thanks @​ascorbic! - Adds warnings about using local font files in the publicDir when the experimental fonts API is enabled.
    

    • 

  • 

    #13703 659904b Thanks @​ascorbic! - Renames experimental responsive image layout option from "responsive" to "constrained"
    

    ⚠️ BREAKING CHANGE FOR EXPERIMENTAL RESPONSIVE IMAGES ONLY ⚠️
    

    The layout option called "responsive" is renamed to "constrained" to better reflect its behavior.
    

    The previous name was causing confusion, because it is also the name of the feature. The responsive layout option is specifically for images that are displayed at the requested size, unless they do not fit the width of their container, at which point they would be scaled down to fit. They do not get scaled beyond the intrinsic size of the source image, or the width prop if provided.
    

    It became clear from user feedback that many people (understandably) thought that they needed to set layout to responsive if they wanted to use responsive images. They then struggled with overriding styles to make the image scale up for full-width hero images, for example, when they should have been using full-width layout. Renaming the layout to constrained should make it clearer that this layout is for when you want to constrain the maximum size of the image, but allow it to scale-down.
    

    Upgrading
    

    • 






... (truncated)





Commits






Updates vite from 5.4.14 to 6.3.3



Release notes

Sourced from vite's releases.




v6.3.3


Please refer to CHANGELOG.md for details.


v6.3.2


Please refer to CHANGELOG.md for details.


create-vite@6.3.1


Please refer to CHANGELOG.md for details.


v6.3.1


Please refer to CHANGELOG.md for details.


create-vite@6.3.0


Please refer to CHANGELOG.md for details.


v6.3.0


Please refer to CHANGELOG.md for details.


v6.3.0-beta.2


Please refer to CHANGELOG.md for details.


v6.3.0-beta.1


Please refer to CHANGELOG.md for details.


v6.3.0-beta.0


Please refer to CHANGELOG.md for details.


v6.2.6


Please refer to CHANGELOG.md for details.


v6.2.5


Please refer to CHANGELOG.md for details.


v6.2.4


Please refer to CHANGELOG.md for details.


v6.2.3


Please refer to CHANGELOG.md for details.


v6.2.2


Please refer to CHANGELOG.md for details.


create-vite@6.2.1


Please refer to CHANGELOG.md for details.


v6.2.1


Please refer to CHANGELOG.md for details.


create-vite@6.2.0


Please refer to CHANGELOG.md for details.





... (truncated)





Changelog

Sourced from vite's changelog.




6.3.3 (2025-04-24)


    

  • fix: ignore malformed uris in tranform middleware (#19853) (e4d5201), closes #19853
    • 

  • fix(assets): ensure ?no-inline is not included in the asset url in the production environment (#1949 (16a73c0), closes #19496
    • 

  • fix(css): resolve relative imports in sass properly on Windows (#19920) (ffab442), closes #19920
    • 

  • fix(deps): update all non-major dependencies (#19899) (a4b500e), closes #19899
    • 

  • fix(ssr): fix execution order of re-export (#19841) (ed29dee), closes #19841
    • 

  • fix(ssr): fix live binding of default export declaration and hoist exports getter (#19842) (80a91ff), closes #19842
    • 

  • perf: skip sourcemap generation for renderChunk hook of import-analysis-build plugin (#19921) (55cfd04), closes #19921
    • 

  • test(ssr): test ssrTransform re-export deps and test stacktrace with first line (#19629) (9399cda), closes #19629
    • 



6.3.2 (2025-04-18)



6.3.1 (2025-04-17)



6.3.0 (2025-04-16)



6.3.0-beta.2 (2025-04-11)






... (truncated)





Commits

    

  • db9eb97 release: v6.3.3
    • 

  • e4d5201 fix: ignore malformed uris in tranform middleware (#19853)
    • 

  • 55cfd04 perf: skip sourcemap generation for renderChunk hook of import-analysis-build...
    • 

  • ffab442 fix(css): resolve relative imports in sass properly on Windows (#19920)
    • 

  • 16a73c0 fix(assets): ensure ?no-inline is not included in the asset url in the produc...
    • 

  • 9399cda test(ssr): test ssrTransform re-export deps and test stacktrace with first ...
    • 

  • ed29dee fix(ssr): fix execution order of re-export (#19841)
    • 

  • 80a91ff fix(ssr): fix live binding of default export declaration and hoist exports ge...
    • 

  • a4b500e fix(deps): update all non-major dependencies (#19899)
    • 

  • 4bc17b4 release: v6.3.2
    • 

  • Additional commits viewable in compare view
    • 







Updates vitest from 1.6.0 to 3.1.2



Release notes

Sourced from vitest's releases.




v3.1.2


   🐞 Bug Fixes



   🏎 Performance



    View changes on GitHub


v3.1.1


   🐞 Bug Fixes



    View changes on GitHub


v3.1.0


🚀 Features






... (truncated)





Commits


    

  
  



      


          

          
  
  

    
  
    
    

  

  

  



                    

          
        





  





    



      

  
        

  

      

  
  

  
          

  

    

      


  

        
          @dependabot
  




      

        
          Bump esbuild, @astrojs/react, astro, vite and vitest in /frontend
        

          
                        
      


      

        

    
    
    

  

    


      


      

        

          

    
    
    

  

  

    
  



        

      


      

        
          f7e0951
        
      

    

  

    

      
Bumps [esbuild](https://github.com/evanw/esbuild) to 0.25.3 and updates ancestor dependencies [esbuild](https://github.com/evanw/esbuild), [@astrojs/react](https://github.com/withastro/astro/tree/HEAD/packages/integrations/react), [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro), [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.3
- [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.3)

Updates `@astrojs/react` from 3.6.3 to 4.2.5
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/integrations/react/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/@astrojs/react@4.2.5/packages/integrations/react)

Updates `astro` from 4.16.18 to 5.7.7
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/astro@5.7.7/packages/astro)

Updates `vite` from 5.4.14 to 6.3.3
- [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/v6.3.3/packages/vite)

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

---
updated-dependencies:
- dependency-name: esbuild
  dependency-version: 0.25.3
  dependency-type: indirect
- dependency-name: "@astrojs/react"
  dependency-version: 4.2.5
  dependency-type: direct:production
- dependency-name: astro
  dependency-version: 5.7.7
  dependency-type: direct:production
- dependency-name: vite
  dependency-version: 6.3.3
  dependency-type: indirect
- dependency-name: vitest
  dependency-version: 3.1.2
  dependency-type: direct:development
...

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


      Apr 28, 2025

    

  



  

  

    
  


  

      


  This was referenced Apr 28, 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
  
    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