Skip to content

chore(deps): bump the npm_and_yarn group across 1 directory with 4 updates #8

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
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): bump the npm_and_yarn group across 1 directory with 4 updates #8

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 22, 2025

Bumps the npm_and_yarn group with 4 updates in the / directory: esbuild, @vitest/ui, vite and vitest.

Updates esbuild from 0.21.5 to 0.25.1

Release notes

Sourced from esbuild's releases.

v0.25.1

  • Fix incorrect paths in inline source maps (#4070, #4075, #4105)

    This fixes a regression from version 0.25.0 where esbuild didn't correctly resolve relative paths contained within source maps in inline sourceMappingURL data URLs. The paths were incorrectly being passed through as-is instead of being resolved relative to the source file containing the sourceMappingURL comment, which was due to the data URL not being a file URL. This regression has been fixed, and this case now has test coverage.

  • Fix invalid generated source maps (#4080, #4082, #4104, #4107)

    This release fixes a regression from version 0.24.1 that could cause esbuild to generate invalid source maps. Specifically under certain conditions, esbuild could generate a mapping with an out-of-bounds source index. It was introduced by code that attempted to improve esbuild's handling of "null" entries in source maps (i.e. mappings with a generated position but no original position). This regression has been fixed.

    This fix was contributed by @​jridgewell.

  • Fix a regression with non-file source map paths (#4078)

    The format of paths in source maps that aren't in the file namespace was unintentionally changed in version 0.25.0. Path namespaces is an esbuild-specific concept that is optionally available for plugins to use to distinguish paths from file paths and from paths meant for other plugins. Previously the namespace was prepended to the path joined with a : character, but version 0.25.0 unintentionally failed to prepend the namespace. The previous behavior has been restored.

  • Fix a crash with switch optimization (#4088)

    The new code in the previous release to optimize dead code in switch statements accidentally introduced a crash in the edge case where one or more switch case values include a function expression. This is because esbuild now visits the case values first to determine whether any cases are dead code, and then visits the case bodies once the dead code status is known. That triggered some internal asserts that guard against traversing the AST in an unexpected order. This crash has been fixed by changing esbuild to expect the new traversal ordering. Here's an example of affected code:

    switch (x) {
  case '':
    return y.map(z => z.value)
  case y.map(z => z.key).join(','):
    return []
}

  • Update Go from 1.23.5 to 1.23.7 (#4076, #4077)

    This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain reports from vulnerability scanners that detect which version of the Go compiler esbuild uses.

    This PR was contributed by @​MikeWillCook.

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.

... (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 @vitest/ui from 2.1.9 to 3.0.9



Release notes

Sourced from @​vitest/ui's releases.




v3.0.9


   🐞 Bug Fixes



    View changes on GitHub


v3.0.8


   🐞 Bug Fixes



    View changes on GitHub


v3.0.7


   🐞 Bug Fixes






... (truncated)





Commits






Updates vite from 5.4.14 to 6.2.2



Release notes

Sourced from vite's releases.




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.


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.


create-vite@6.1.1


Please refer to CHANGELOG.md for details.


v6.1.1


Please refer to CHANGELOG.md for details.


create-vite@6.1.0


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.





... (truncated)





Changelog

Sourced from vite's changelog.




6.2.2 (2025-03-14)


    

  • fix: await client buildStart on top level buildStart (#19624) (b31faab), closes #19624
    • 

  • fix(css): inline css correctly for double quote use strict (#19590) (d0aa833), closes #19590
    • 

  • fix(deps): update all non-major dependencies (#19613) (363d691), closes #19613
    • 

  • fix(indexHtml): ensure correct URL when querying module graph (#19601) (dc5395a), closes #19601
    • 

  • fix(preview): use preview https config, not server (#19633) (98b3160), closes #19633
    • 

  • fix(ssr): use optional chaining to prevent "undefined is not an object" happening in `ssrRewriteStac (4309755), closes #19612
    • 

  • feat: show friendly error for malformed base (#19616) (2476391), closes #19616
    • 

  • feat(worker): show asset filename conflict warning (#19591) (367d968), closes #19591
    • 

  • chore: extend commit hash correctly when ambigious with a non-commit object (#19600) (89a6287), closes #19600
    • 



6.2.1 (2025-03-07)



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)





... (truncated)





Commits

    

  • b12911e release: v6.2.2
    • 

  • 98b3160 fix(preview): use preview https config, not server (#19633)
    • 

  • b31faab fix: await client buildStart on top level buildStart (#19624)
    • 

  • dc5395a fix(indexHtml): ensure correct URL when querying module graph (#19601)
    • 

  • 2476391 feat: show friendly error for malformed base (#19616)
    • 

  • 4309755 fix(ssr): use optional chaining to prevent "undefined is not an object" happe...
    • 

  • 363d691 fix(deps): update all non-major dependencies (#19613)
    • 

  • d0aa833 fix(css): inline css correctly for double quote use strict (#19590)
    • 

  • 367d968 feat(worker): show asset filename conflict warning (#19591)
    • 

  • 89a6287 chore: extend commit hash correctly when ambigious with a non-commit object (...
    • 

  • Additional commits viewable in compare view
    • 







Updates vitest from 2.1.9 to 3.0.9



Release notes

Sourced from vitest's releases.




v3.0.9


   🐞 Bug Fixes



    View changes on GitHub


v3.0.8


   🐞 Bug Fixes



    View changes on GitHub


v3.0.7


   🐞 Bug Fixes






... (truncated)





Commits

    

  • 8ea9e14 chore: release v3.0.9
    • 

  • 422ba66 fix(coverage): browser mode + coverage.all (#7597)
    • 

  • 3fdee3d chore: fix various typos (#7663)
    • 

  • 4b0451d chore(deps): update dependency @​antfu/eslint-config to v4 (#7407)
    • 

  • fcf3cf5 refactor: coverage types to avoid mixing node and runtime types (#7627)
    • 

  • 3fb3fbf fix: fix getState().testPath during collection with no isolation (#7640)
    • 

  • 7155aef chore: use pnpm catalog (#7590)
    • 

  • c0cf65f chore: use unplugin-isolated-decl with oxc-transform for dts build (#7609)
    • 

  • 5eb4cd1 fix(browser): fail playwright timeouts earlier than a test timeout (#7565)
    • 

  • b7f5526 fix: race condition in RPC filesystem cache. (#7531)
    • 

  • 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 <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
  




      

        
          chore(deps): bump the npm_and_yarn group across 1 directory with 4 up…
        

          
                        
      


      

        

    
    
    

  

    


      


      

        

          

    
    
    

  

  

    
  



        

      


      

        
          3db8c51
        
      

    

  

    

      
…dates

Bumps the npm_and_yarn group with 4 updates in the / directory: [esbuild](https://github.com/evanw/esbuild), [@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).


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

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

Updates `vite` from 5.4.14 to 6.2.2
- [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.2.2/packages/vite)

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

---
updated-dependencies:
- dependency-name: esbuild
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: "@vitest/ui"
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: vite
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: vitest
  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


      Mar 22, 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