Skip to content

Bump the npm_and_yarn group across 1 directory with 6 updates #125

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

Bump the npm_and_yarn group across 1 directory with 6 updates #125

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 15, 2025 •
edited
Loading

Bumps the npm_and_yarn group with 6 updates in the / directory:

Package From To
@babel/runtime 7.24.1 7.26.10
esbuild 0.21.5 0.25.1
vite 5.4.14 6.2.2
@vitejs/plugin-react 4.2.1 4.3.4
vite-plugin-svgr 4.2.0 4.3.0
vitest 2.1.9 3.0.8

Updates @babel/runtime from 7.24.1 to 7.26.10

Release notes

Sourced from @​babel/runtime's releases.

v7.26.10 (2025-03-11)

Thanks @​jordan-choi and @​mmmsssttt404 for your first PRs!

This release includes a fix for GHSA-968p-4wvh-cqc8, a security vulnerability which affects the .replace method of transpiled regular expressions that use named capturing groups.

👓 Spec Compliance

🐛 Bug Fix

  • babel-parser, babel-template
  • babel-core
  • babel-parser, babel-plugin-transform-typescript
  • babel-traverse
  • babel-generator
  • babel-parser
  • babel-helpers, babel-runtime, babel-runtime-corejs2, babel-runtime-corejs3

💅 Polish

  • babel-standalone

🏠 Internal

Committers: 6

v7.26.9 (2025-02-14)

🐛 Bug Fix

... (truncated)

Changelog

Sourced from @​babel/runtime's changelog.

v7.26.10 (2025-03-11)

👓 Spec Compliance

🐛 Bug Fix

  • babel-parser, babel-template
  • babel-core
  • babel-parser, babel-plugin-transform-typescript
  • babel-traverse
  • babel-generator
  • babel-parser
  • babel-helpers, babel-runtime, babel-runtime-corejs2, babel-runtime-corejs3

💅 Polish

  • babel-standalone

🏠 Internal

v7.26.9 (2025-02-14)

🐛 Bug Fix

🏠 Internal

v7.26.7 (2025-01-24)

🐛 Bug Fix

  • babel-helpers, babel-preset-env, babel-runtime-corejs3
  • babel-plugin-transform-typeof-symbol

... (truncated)

Commits

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 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 @vitejs/plugin-react from 4.2.1 to 4.3.4



Release notes

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




v4.3.4


Add Vite 6 to peerDependencies range


Vite 6 is highly backward compatible, not much to add!


Force Babel to output spec compliant import attributes #386


The default was an old spec (with type: "json"). We now enforce spec compliant (with { type: "json" })


v4.3.3


React Compiler runtimeModule option removed


React Compiler was updated to accept a target option and runtimeModule was removed. vite-plugin-react will still detect runtimeModule for backwards compatibility.


When using a custom runtimeModule or target !== '19', the plugin will not try to pre-optimize react/compiler-runtime dependency.


The react-compiler-runtime is now available on npm can be used instead of the local shim for people using the compiler with React < 19.


Here is the configuration to use the compiler with React 18 and correct source maps in development:


npm install babel-plugin-react-compiler react-compiler-runtime @babel/plugin-transform-react-jsx-development


export default defineConfig(({ command }) => {
  const babelPlugins = [['babel-plugin-react-compiler', { target: '18' }]]
  if (command === 'serve') {
    babelPlugins.push(['@babel/plugin-transform-react-jsx-development', {}])
  }
return {
plugins: [react({ babel: { plugins: babelPlugins } })],
}
})


v4.3.2


Ignore directive sourcemap error #369


v4.3.1


Fix support for React Compiler with React 18


The previous version made this assumption that the compiler was only usable with React 19, but it's possible to use it with React 18 and a custom runtimeModule: https://gist.github.com/poteto/37c076bf112a07ba39d0e5f0645fec43


When using a custom runtimeModule, the plugin will not try to pre-optimize react/compiler-runtime dependency.


Reminder: Vite expect code outside of node_modules to be ESM, so you will need to update the gist with import React from 'react'.


v4.3.0





... (truncated)





Changelog

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




4.3.4 (2024-11-26)


Add Vite 6 to peerDependencies range


Vite 6 is highly backward compatible, not much to add!


Force Babel to output spec compliant import attributes #386


The default was an old spec (with type: "json"). We now enforce spec compliant (with { type: "json" })


4.3.3 (2024-10-19)


React Compiler runtimeModule option removed


React Compiler was updated to accept a target option and runtimeModule was removed. vite-plugin-react will still detect runtimeModule for backwards compatibility.


When using a custom runtimeModule or target !== '19', the plugin will not try to pre-optimize react/compiler-runtime dependency.


The react-compiler-runtime is now available on npm can be used instead of the local shim for people using the compiler with React < 19.


Here is the configuration to use the compiler with React 18 and correct source maps in development:


npm install babel-plugin-react-compiler react-compiler-runtime @babel/plugin-transform-react-jsx-development


export default defineConfig(({ command }) => {
  const babelPlugins = [['babel-plugin-react-compiler', { target: '18' }]]
  if (command === 'serve') {
    babelPlugins.push(['@babel/plugin-transform-react-jsx-development', {}])
  }
return {
plugins: [react({ babel: { plugins: babelPlugins } })],
}
})


4.3.2 (2024-09-29)


Ignore directive sourcemap error #369


4.3.1 (2024-06-10)


Fix support for React Compiler with React 18


The previous version made this assumption that the compiler was only usable with React 19, but it's possible to use it with React 18 and a custom runtimeModule: https://gist.github.com/poteto/37c076bf112a07ba39d0e5f0645fec43


When using a custom runtimeModule, the plugin will not try to pre-optimize react/compiler-runtime dependency.





... (truncated)





Commits

    

  • 2e368a6 release: plugin-react@4.3.4
    • 

  • bde1ad6 feat: add Vite 6 to peerDependencies range (#390)
    • 

  • 45a727c fix(deps): update all non-major dependencies (#373)
    • 

  • 5d2b6c6 fix: force non-legacy import attributes babel output (#386)
    • 

  • b61592a release: plugin-react@4.3.3
    • 

  • e8a923f fix: add react-dom in optimizeOps to handle CJS script. (#375)
    • 

  • 7a7e339 feat: support new React Compiler target option (#374)
    • 

  • 63b2e38 release: plugin-react@4.3.2
    • 

  • fdf6ce4 fix(deps): update all non-major dependencies (#273)
    • 

  • 4544e97 feat: update refresh utils for React Router 7 support (#363)
    • 

  • Additional commits viewable in compare view
    • 







Updates vite-plugin-svgr from 4.2.0 to 4.3.0



Commits






Updates vitest from 2.1.9 to 3.0.8



Release notes

Sourced from vitest's releases.




v3.0.8


   🐞 Bug Fixes



    View changes on GitHub


v3.0.7


   🐞 Bug Fixes



   🏎 Performance



    View changes on GitHub


v3.0.6


   🐞 Bug Fixes






... (truncated)





Commits

    

  • 814d5df chore: release v3.0.8
    • 

  • 57c3234 chore: remove hijackVitePluginInject (#7613)
    • 

  • 1a88b1b chore(deps): update dependency strip-literal to v3 (#7601)
    • 

  • 4325ac6 fix: correctly split the argv string (#7533)
    • 

  • 7f7ff11 fix: remove vestigial spy stub, import directly from @vitest/spy (#7575)
    • 

  • fee90d8 fix(browser): print related test file and potential test in unhandled errors ...
    • 

  • 1a8b433 fix: fix fetch cache multiple writes (#7546)
    • 

  • 358cccf chore: release v3.0.7
    • 

  • 365ffe6 fix(deps): update all non-major dependencies (#7543)
    • 

  • aaa5855 perf(browser): do wdio context switching only once per file (#7549)
    • 

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



Description has been truncated

    

  
  



      


          

          
  
  

    
  
    
    

  

  

  



          

        
      




  




      

       
            



      

  
            

    

      
    

    


      


          @dependabot
dependabot
bot



            added
      

  dependencies

  Pull requests that update a dependency file

      

  javascript

  Pull requests that update javascript code

  labels


      Mar 15, 2025

    

  








      

  
      



  

  @odarbelaeze





  



    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      

  
  Member


      

  


  

    

  





      


        



  
    

      
          
@dependabot rebase

      		
    

  





        


            

            
            

              
            

        

      


      

            
  
  

    
  
    
    

  

  

  


    












      

  
        

  

      

  
  

  
          

  

    

      


  

      
        @dependabot
  




      

        
          Bump the npm_and_yarn group across 1 directory with 6 updates
        

          
                        
      


      

        

    
    
    

  

    


      


      

        

          

    
    
    

  

  

    
  



        

      


      

        
          efbfb99
        
      

    

  

    

      
Bumps the npm_and_yarn group with 6 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@babel/runtime](https://github.com/babel/babel/tree/HEAD/packages/babel-runtime) | `7.24.1` | `7.26.10` |
| [esbuild](https://github.com/evanw/esbuild) | `0.21.5` | `0.25.1` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `5.4.14` | `6.2.2` |
| [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) | `4.2.1` | `4.3.4` |
| [vite-plugin-svgr](https://github.com/pd4d10/vite-plugin-svgr) | `4.2.0` | `4.3.0` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `2.1.9` | `3.0.8` |



Updates `@babel/runtime` from 7.24.1 to 7.26.10
- [Release notes](https://github.com/babel/babel/releases)
- [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md)
- [Commits](https://github.com/babel/babel/commits/v7.26.10/packages/babel-runtime)

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 `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 `@vitejs/plugin-react` from 4.2.1 to 4.3.4
- [Release notes](https://github.com/vitejs/vite-plugin-react/releases)
- [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite-plugin-react/commits/v4.3.4/packages/plugin-react)

Updates `vite-plugin-svgr` from 4.2.0 to 4.3.0
- [Release notes](https://github.com/pd4d10/vite-plugin-svgr/releases)
- [Commits](pd4d10/vite-plugin-svgr@v4.2.0...v4.3.0)

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

---
updated-dependencies:
- dependency-name: "@babel/runtime"
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: esbuild
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: vite
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: "@vitejs/plugin-react"
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: vite-plugin-svgr
  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

        force-pushed
    the
        
      
  dependabot/npm_and_yarn/npm_and_yarn-db59caa4a5


    
 branch
    from
    2aa7329    to
    efbfb99      
    Compare
  



    March 23, 2025 12:26    
    













  
  

    

      

  




      


    


    

      

        
      

  
    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.





  
  



      
    

  




      

    

  
      

  

    

      1 participant
    

    

        
          @odarbelaeze