Skip to content

Bump the npm_and_yarn group across 3 directories with 6 updates #15

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

Bump the npm_and_yarn group across 3 directories with 6 updates #15

dependabot wants to merge 1 commit into from

Conversation

@dependabot
Copy link

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

Bumps the npm_and_yarn group with 3 updates in the /api directory: esbuild, tsx and wrangler.
Bumps the npm_and_yarn group with 3 updates in the /scraper directory: esbuild, undici and form-data.
Bumps the npm_and_yarn group with 1 update in the /web directory: base-x.

Updates esbuild from 0.23.1 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 tsx from 4.19.2 to 4.20.5



Release notes

Sourced from tsx's releases.




v4.20.5


4.20.5 (2025-08-24)


Bug Fixes


    

  • handle ambiguous packages (796053a)
    • 





This release is also available on:



v4.20.4


4.20.4 (2025-08-12)


Bug Fixes





This release is also available on:



v4.20.3


4.20.3 (2025-06-13)


Bug Fixes





This release is also available on:



v4.20.2


4.20.2 (2025-06-12)


Bug Fixes





... (truncated)





Commits

    

  • e6d1a47 docs: obfuscate aside classname
    • 

  • de2719d style: remove unused variable
    • 

  • 13f2954 chore: upgrade docs deps
    • 

  • 0504525 chore: upgrade manten
    • 

  • 132fdd8 test: assert require.cache
    • 

  • f057e7d test: require loop
    • 

  • a6f8f9f refactor: getFormat to handle all formats
    • 

  • 796053a fix: handle ambiguous packages
    • 

  • 471997a test: CJS & ESM race condition
    • 

  • a639836 fix: override Node's native TS formats (#733)
    • 

  • Additional commits viewable in compare view
    • 







Updates wrangler from 4.7.2 to 4.34.0



Release notes

Sourced from wrangler's releases.




wrangler@4.34.0


Minor Changes


    

  • 

    #10478 cc47b51 Thanks @​danielrs! - Beta feature preview_urls is now disabled by default.
    

    This change makes preview_urls disabled by default when it's not provided, making
the feature opt-in instead of opt-out.
    

    • 



Patch Changes



wrangler@4.33.2


Patch Changes



wrangler@4.33.1





... (truncated)





Changelog

Sourced from wrangler's changelog.




4.34.0


Minor Changes


    

  • 

    #10478 cc47b51 Thanks @​danielrs! - Beta feature preview_urls is now disabled by default.
    

    This change makes preview_urls disabled by default when it's not provided, making
the feature opt-in instead of opt-out.
    

    • 



Patch Changes



4.33.2


Patch Changes






... (truncated)





Commits






Updates undici from 5.29.0 to 7.15.0



Release notes

Sourced from undici's releases.




v6.21.3


What's Changed



Full Changelog: nodejs/undici@v6.21.2...v6.21.3


v6.21.2


What's Changed



New Contributors



Full Changelog: nodejs/undici@v6.21.1...v6.21.2







Commits






Updates esbuild from 0.25.2 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 undici from 6.21.1 to 6.21.3



Release notes

Sourced from undici's releases.




v6.21.3


What's Changed



Full Changelog: nodejs/undici@v6.21.2...v6.21.3


v6.21.2


What's Changed



New Contributors



Full Changelog: nodejs/undici@v6.21.1...v6.21.2







Commits






Updates form-data from 4.0.1 to 4.0.4



Release notes

Sourced from form-data's releases.




v4.0.4


v4.0.4 - 2025-07-16


Commits


    

  • [meta] add auto-changelog 811f682
    • 

  • [Tests] handle predict-v8-randomness failures in node < 17 and node > 23 1d11a76
    • 

  • [Fix] Switch to using crypto random for boundary values 3d17230
    • 

  • [Tests] fix linting errors 5e34080
    • 

  • [meta] actually ensure the readme backup isn’t published 316c82b
    • 

  • [Dev Deps] update @ljharb/eslint-config 58c25d7
    • 

  • [meta] fix readme capitalization 2300ca1
    • 



v4.0.3


v4.0.3 - 2025-06-05


Fixed



Commits


    

  • [eslint] use a shared config 426ba9a
    • 

  • [eslint] fix some spacing issues 2094191
    • 

  • [Refactor] use hasown 81ab41b
    • 

  • [Fix] validate boundary type in setBoundary() method 8d8e469
    • 

  • [Tests] add tests to check the behavior of getBoundary with non-strings 837b8a1
    • 

  • [Dev Deps] remove unused deps 870e4e6
    • 

  • [meta] remove local commit hooks e6e83cc
    • 

  • [Dev Deps] update eslint 4066fd6
    • 

  • [meta] fix scripts to use prepublishOnly c4bbb13
    • 



v4.0.2


v4.0.2 - 2025-02-14


Merged



Fixed



Commits





... (truncated)





Changelog

Sourced from form-data's changelog.




v4.0.4 - 2025-07-16


Commits


    

  • [meta] add auto-changelog 811f682
    • 

  • [Tests] handle predict-v8-randomness failures in node < 17 and node > 23 1d11a76
    • 

  • [Fix] Switch to using crypto random for boundary values 3d17230
    • 

  • [Tests] fix linting errors 5e34080
    • 

  • [meta] actually ensure the readme backup isn’t published 316c82b
    • 

  • [Dev Deps] update @ljharb/eslint-config 58c25d7
    • 

  • [meta] fix readme capitalization 2300ca1
    • 



v4.0.3 - 2025-06-05


Fixed



Commits


    

  • [eslint] use a shared config 426ba9a
    • 

  • [eslint] fix some spacing issues 2094191
    • 

  • [Refactor] use hasown 81ab41b
    • 

  • [Fix] validate boundary type in setBoundary() method 8d8e469
    • 

  • [Tests] add tests to check the behavior of getBoundary with non-strings 837b8a1
    • 

  • [Dev Deps] remove unused deps 870e4e6
    • 

  • [meta] remove local commit hooks e6e83cc
    • 

  • [Dev Deps] update eslint 4066fd6
    • 

  • [meta] fix scripts to use prepublishOnly c4bbb13
    • 



v4.0.2 - 2025-02-14


Merged



Fixed



Commits


    

  • Merge tags v2.5.3 and v3.0.3 92613b9
    • 

  • [Tests] migrate from travis to GHA 806eda7
    • 

  • [Tests] migrate from travis to GHA 8fdb3bc
    • 






... (truncated)





Commits

    

  • 41996f5 v4.0.4
    • 

  • 316c82b [meta] actually ensure the readme backup isn’t published
    • 

  • 2300ca1 [meta] fix readme capitalization
    • 

  • 811f682 [meta] add auto-changelog
    • 

  • 5e34080 [Tests] fix linting errors
    • 

  • 1d11a76 [Tests] handle predict-v8-randomness failures in node < 17 and node > 23
    • 

  • 58c25d7 [Dev Deps] update @ljharb/eslint-config
    • 

  • 3d17230 [Fix] Switch to using crypto random for boundary values
    • 

  • d8d67dc v4.0.3
    • 

  • e6e83cc [meta] remove local commit hooks
    • 

  • Additional commits viewable in compare view
    • 







Updates base-x from 3.0.10 to 3.0.11



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



Description has been truncated

    

  
  



      


          

          
  
  

    
  
    
    

  

  

  



          

        
      




  




      

       
            



      

  
        

  

      

  
  

  
          

  

    

      


  

      
        @dependabot
  




      

        
          Bump the npm_and_yarn group across 3 directories with 6 updates
        

          
                        
      


      

        

    
    
    

  

    


      


      

        

          

    
    
    

  

  

    
  



        

      


      

        
          171c203
        
      

    

  

    

      
Bumps the npm_and_yarn group with 3 updates in the /api directory: [esbuild](https://github.com/evanw/esbuild), [tsx](https://github.com/privatenumber/tsx) and [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler).
Bumps the npm_and_yarn group with 3 updates in the /scraper directory: [esbuild](https://github.com/evanw/esbuild), [undici](https://github.com/nodejs/undici) and [form-data](https://github.com/form-data/form-data).
Bumps the npm_and_yarn group with 1 update in the /web directory: [base-x](https://github.com/cryptocoinjs/base-x).


Updates `esbuild` from 0.23.1 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.23.1...v0.25.9)

Updates `tsx` from 4.19.2 to 4.20.5
- [Release notes](https://github.com/privatenumber/tsx/releases)
- [Changelog](https://github.com/privatenumber/tsx/blob/master/release.config.cjs)
- [Commits](privatenumber/tsx@v4.19.2...v4.20.5)

Updates `wrangler` from 4.7.2 to 4.34.0
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Changelog](https://github.com/cloudflare/workers-sdk/blob/main/packages/wrangler/CHANGELOG.md)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.34.0/packages/wrangler)

Updates `undici` from 5.29.0 to 7.15.0
- [Release notes](https://github.com/nodejs/undici/releases)
- [Commits](nodejs/undici@v6.21.1...v6.21.3)

Updates `esbuild` from 0.25.2 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.23.1...v0.25.9)

Updates `undici` from 6.21.1 to 6.21.3
- [Release notes](https://github.com/nodejs/undici/releases)
- [Commits](nodejs/undici@v6.21.1...v6.21.3)

Updates `form-data` from 4.0.1 to 4.0.4
- [Release notes](https://github.com/form-data/form-data/releases)
- [Changelog](https://github.com/form-data/form-data/blob/master/CHANGELOG.md)
- [Commits](form-data/form-data@v4.0.1...v4.0.4)

Updates `base-x` from 3.0.10 to 3.0.11
- [Commits](cryptocoinjs/base-x@v3.0.10...v3.0.11)

---
updated-dependencies:
- dependency-name: esbuild
  dependency-version: 0.25.9
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: tsx
  dependency-version: 4.20.5
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: wrangler
  dependency-version: 4.34.0
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: undici
  dependency-version: 7.15.0
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: esbuild
  dependency-version: 0.25.9
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: undici
  dependency-version: 6.21.3
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: form-data
  dependency-version: 4.0.4
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: base-x
  dependency-version: 3.0.11
  dependency-type: indirect
  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 7, 2025

    

  








      

  
      



  

  @cloudflare-workers-and-pages






  



    

      

  

    

      

          
    
    

  


        
            
  
      
              Copy link

  

        
      

    


    

        



        

    

  


  

    

      
          
      

      
            cloudflare-workers-and-pages
  bot

      

      

      commented


        Sep 7, 2025


      
    


  





      


        



  
    

      
          
Deploying rageagain with  Cloudflare Pages  Cloudflare Pages


Latest commit: 
171c203



Status: ✅  Deploy successful!


Preview URL:
https://460da401.rageagain.pages.dev



Branch Preview URL:
https://dependabot-npm-and-yarn-api-cdxa.rageagain.pages.dev





View logs


      		
    

  





        


            

            
            

              
            

        

      


      

            
  
  

    
  
    
    

  

  

  


    
















  
  

    

      

  




      


    


    

      

        
      

  
    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