Skip to content

chore(deps): bump the npm_and_yarn group across 4 directories with 9 updates#2433

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/npm_and_yarn-792f2f9915
Open

chore(deps): bump the npm_and_yarn group across 4 directories with 9 updates#2433
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/npm_and_yarn-792f2f9915

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot bot commented on behalf of github Mar 24, 2026 •
edited
Loading

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

Package From To
js-yaml 4.1.0 4.1.1
esbuild 0.20.2 0.25.0
storybook 8.6.14 8.6.17
next 14.2.29 15.5.14
bn.js 4.12.2 4.12.3
node-forge 1.3.1 1.3.3
rollup 4.41.0 4.60.0
undici 6.21.3 6.24.1
vite 5.4.19 5.4.21

Bumps the npm_and_yarn group with 1 update in the /account-kit/plugingen directory: esbuild.
Bumps the npm_and_yarn group with 1 update in the /examples/alchemy-privy-integration-example directory: next.
Bumps the npm_and_yarn group with 1 update in the /examples/ui-demo directory: next.

Updates js-yaml from 4.1.0 to 4.1.1

Changelog

Sourced from js-yaml's changelog.

[4.1.1] - 2025-11-12

Security

  • Fix prototype pollution issue in yaml merge (<<) operator.
Commits

Updates esbuild from 0.20.2 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 storybook from 8.6.14 to 8.6.17



Release notes

Sourced from storybook's releases.




v8.6.17


8.6.17


    

  • Harden websocket connection
    • 



v8.6.16


8.6.16


    

  • No-op release. No changes.
    • 



v8.6.15


8.6.15








Changelog

Sourced from storybook's changelog.




8.6.17


    

  • Harden websocket connection
    • 



8.6.16


    

  • No-op release. No changes.
    • 








Commits

    

  • c6e550a Bump version from "8.6.16" to "8.6.17" [skip ci]
    • 

  • 9cf9d89 Core: Require token for websocket connections
    • 

  • 7e51515 Bump version from "8.6.15" to "8.6.16" [skip ci]
    • 

  • 3812b43 Bump version from 8.6.14 to 8.6.15 MANUALLY
    • 

  • 4a04cb2 filter env vars from .env files
    • 

  • See full diff in compare view
    • 






Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for storybook since your current version.






Updates next from 14.2.29 to 15.5.14



Release notes

Sourced from next's releases.




v15.5.14




[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.




Core Changes


    

  • feat(next/image): add lru disk cache and images.maximumDiskCacheSize (#91660)
    • 

  • Fix(pages-router): restore Content-Length and ETag for /_next/data/ JSON responses (#90304)
    • 



Credits


Huge thanks to @​styfle and @​lllomh for helping!


v15.5.13




[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.




Core Changes


    

  • fix: patch http-proxy to prevent request smuggling in rewrites (See: CVE-2026-29057)
    • 



Credits


Huge thanks to @​ztanner for helping!


v15.5.12




[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.




    

  • fix unlock in publish-native
    • 



This is a re-release of v15.5.11 applying the turbopack changes.


v15.5.11




[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.




Core Changes


    

  • Tracing: Fix memory leak in span map (#85529)
    • 

  • fix: ensure LRU cache items have minimum size of 1 to prevent unbounded growth (#89134)
    • 

  • Turbopack: fix NFT tracing of sharp 0.34 (#82340)
    • 

  • Turbopack: support pattern into exports field (#82757)
    • 

  • NFT tracing fixes (#84155 and #85323)
    • 

  • Turbopack: validate CSS without computing all paths (#83810)
    • 

  • feat: implement LRU cache with invocation ID scoping for minimal mode response cache (#89129)
    • 



Credits


Huge thanks to @​timneutkens, @​mischnic, @​ztanner, and @​wyattjoh for helping!







Commits

    

  • d7b012d v15.5.14
    • 

  • 2b05251 [backport] feat(next/image): add lru disk cache and `images.maximumDiskCacheS...
    • 

  • f88cee9 Backport: Fix(pages-router): restore Content-Length and ETag for /_next/data/...
    • 

  • cfd5f53 v15.5.13
    • 

  • 15f2891 [backport]: fix: patch http-proxy to prevent request smuggling in rewrites (#...
    • 

  • d23f41c v15.5.12
    • 

  • 8e75765 fix unlock in publish-native
    • 

  • 6cef992 [backport] normalize CRLF line endings in jscodeshift tests on Windows (#8800...
    • 

  • 7a94645 Apply needs for publishRelease
    • 

  • bbfd4e3 v15.5.11
    • 

  • Additional commits viewable in compare view
    • 







Updates bn.js from 4.12.2 to 4.12.3



Commits






Updates node-forge from 1.3.1 to 1.3.3



Changelog

Sourced from node-forge's changelog.




1.3.3 - 2025-12-02


Fixed


    

  • [pkcs12] Make digestAlgorithm parameters optional to fix PKCS#12/PFX issues
introduced in 1.3.2.
    • 



1.3.2 - 2025-11-25


Security


    

  • HIGH: ASN.1 Validator Desynchronization

      

    • An Interpretation Conflict (CWE-436) vulnerability in node-forge versions
1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1
structures to desynchronize schema validations, yielding a semantic
divergence that may bypass downstream cryptographic verifications and
security decisions.
      • 

    • Reported by Hunter Wodzenski.
      • 

    • CVE ID: CVE-2025-12816
      • 

    • GHSA ID: GHSA-5gfm-wpxj-wjgq
      • 

    

    • 

  • HIGH: ASN.1 Unbounded Recursion

      

    • An Uncontrolled Recursion (CWE-674) vulnerability in node-forge versions
1.3.1 and below enables remote, unauthenticated attackers to craft deep
ASN.1 structures that trigger unbounded recursive parsing. This leads to a
Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER
inputs.
      • 

    • Reported by Hunter Wodzenski.
      • 

    • CVE ID: CVE-2025-66031
      • 

    • GHSA ID: GHSA-554w-wpv2-vw27
      • 

    

    • 

  • MODERATE: ASN.1 OID Integer Truncation

      

    • An Integer Overflow (CWE-190) vulnerability in node-forge versions 1.3.1
and below enables remote, unauthenticated attackers to craft ASN.1
structures containing OIDs with oversized arcs. These arcs may be decoded
as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the
bypass of downstream OID-based security decisions.
      • 

    • Reported by Hunter Wodzenski.
      • 

    • CVE ID: CVE-2025-66030
      • 

    • GHSA ID: GHSA-65ch-62r8-g69g
      • 

    

    • 



Fixed


    

  • [asn1] Fix for vulnerability identified by CVE-2025-12816 PKCS#12 MAC
verification bypass due to missing macData enforcement and improper
asn1.validate routine.
    • 

  • [asn1] Add fromDer() max recursion depth check.

      

    • Add a asn1.maxDepth global configurable maximum depth of 256.
      • 

    • Add a asn1.fromDer() per-call maxDepth option.
      • 

    • NOTE: The default maximum is assumed to be higher than needed for valid
data. If this assumption is false then this could be a breaking change.
Please file an issue if there are use cases that need a higher maximum.
      • 

    • NOTE: The per-call maxDepth parameter has not been exposed up through
all of the API stack due to the complexities involved. Please file an issue
if there are use cases that require this instead of changing the default
      • 

    

    • 






... (truncated)





Commits






Updates rollup from 4.41.0 to 4.60.0



Release notes

Sourced from rollup's releases.




v4.60.0


4.60.0


2026-03-22


Features


    

  • Support source phase imports as long as they are external (#6279)
    • 



Pull Requests



v4.59.1


4.59.1


2026-03-21


Bug Fixes


    

  • Fix a crash when using lazy dynamic imports with moduleSideEffects:false (#6306)
    • 



Pull Requests



v4.59.0


4.59.0


2026-02-22





... (truncated)





Changelog

Sourced from rollup's changelog.




4.60.0


2026-03-22


Features


    

  • Support source phase imports as long as they are external (#6279)
    • 



Pull Requests



4.59.1


2026-03-21


Bug Fixes


    

  • Fix a crash when using lazy dynamic imports with moduleSideEffects:false (#6306)
    • 



Pull Requests



4.59.0


2026-02-22


Features


    

  • Throw when the generated bundle contains paths that would leave the output directory (#6276)
    • 






... (truncated)





Commits





Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for rollup since your current version.





Install script changes

This version modifies prepare script that runs during installation. Review the package contents before updating.






Updates undici from 6.21.3 to 6.24.1



Release notes

Sourced from undici's releases.




v6.24.1


Full Changelog: nodejs/undici@v6.24.0...v6.24.1


v6.24.0


Undici v6.24.0 Security Release Notes (LTS)


This release backports fixes for security vulnerabilities affecting the v6 line.


Upgrade guidance


All users on v6 should upgrade to v6.24.0 or later.


Fixed advisories



Not applicable to v6



Affected and patched ranges (v6)



References






... (truncated)





Commits

    

  • c0cf656 Bumped v6.24.1
    • 

  • f5a9f0c Fix v6 release workflow branch targeting
    • 

  • af2cb8f wqremove maxDecompressedMessageSize (#4891)
    • 

  • 8873c94 Bumped v6.24.0
    • 

  • 411bd01 test(websocket): use node:assert for Node 18 compatibility
    • 

  • 844bf59 test: fix http2 lint regressions in backport
    • 

  • a444e4f test: stabilize h2 and tls-cert-leak under current test runner
    • 

  • dc032a1 fix: h2 CI (#4395)
    • 

  • 4cd3f4b test: increase bitness in test/fixtures/*.pem (#3659)
    • 

  • 7df6442 fix: adapt websocket frame-limit handling for v6 parser
    • 

  • Additional commits viewable in compare view
    • 






Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for undici since your current version.






Updates vite from 5.4.19 to 5.4.21



Release notes

Sourced from vite's releases.




v5.4.21


Please refer to CHANGELOG.md for details.


v5.4.20


Please refer to CHANGELOG.md for details.







Changelog

Sourced from vite's changelog.




5.4.21 (2025-10-20)



5.4.20 (2025-09-08)








Commits






Updates esbuild from 0.20.2 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 next from 14.2.29 to 15.5.14



Release notes

Sourced from next's releases.




v15.5.14




[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.




Core Changes


    

  • feat(next/image): add lru disk cache and images.maximumDiskCacheSize (#91660)
    • 

  • Fix(pages-router): restore Content-Length and ETag for /_next/data/ JSON responses (#90304)
    • 



Credits


Huge thanks to @​styfle and @​lllomh for helping!


v15.5.13




[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.




Core Changes


    

  • fix: patch http-proxy to prevent request smuggling in rewrites (See: CVE-2026-29057)
    • 



Credits


Huge thanks to @​ztanner for helping!


v15.5.12




[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.




    

  • fix unlock in publish-native
    • 



This is a re-release of v15.5.11 applying the turbopack changes.


v15.5.11




[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.




Core Changes


    

  • Tracing: Fix memory leak in span map (#85529)
    • 

  • fix: ensure LRU cache items have minimum size of 1 to prevent unbounded growth (#89134)
    • 

  • Turbopack: fix NFT tracing of sharp 0.34 (#82340)
    • 

  • Turbopack: support pattern into exports field (#82757)
    • 

  • NFT tracing fixes (#84155 and #85323)
    • 

  • Turbopack: validate CSS without computing all paths (#83810)
    • 

  • feat: implement LRU cache with invocation ID scoping for minimal mode response cache (#89129)
    • 



Credits


Huge thanks to @​timneutkens, @​mischnic, @​ztanner, and @​wyattjoh for helping!







Commits

    

  • d7b012d v15.5.14
    • 

  • 2b05251 [backport] feat(next/image): add lru disk cache and `images.maximumDiskCacheS...
    • 

  • f88cee9 Backport: Fix(pages-router): restore Content-Length and ETag for /_next/data/...
    • 

  • cfd5f53 v15.5.13
    • 

  • 15f2891 [backport]: fix: patch http-proxy to prevent request smuggling in rewrites (#...
    • 

  • d23f41c v15.5.12
    • 


    

  
  



      


          

          
  
  

    
  
    
    

  

  

  



                    

          
        





  





    



      

  
            

    

      
    

    


      


          @dependabot
dependabot
bot



            added
      

  dependencies

  Pull requests that update a dependency file

      

  javascript

  Pull requests that update javascript code

  labels


      Mar 24, 2026

    

  



  
  

  

    
  


  

      


    @dependabot
dependabot
bot


    mentioned this pull request
    
      Mar 24, 2026
    





  


  

      
   Closed

  







  




  

  
  

  
      @dependabot
  dependabot
bot

        force-pushed
    the
        
      
  dependabot/npm_and_yarn/npm_and_yarn-792f2f9915


    
 branch
    from
    213b397    to
    bb7f5bb      
    Compare
  



    March 30, 2026 18:04    
    









      

  
        

  

      

  
  

  
          

  

    

      


  

      
        @dependabot
  




      

        
          chore(deps): bump the npm_and_yarn group across 4 directories with 9 …
        

          
                        
      


      

        

    
    
    

  

    


      


      

        

          

    
    
    

  

  

    
  



        

      


      

        
          6c6afaa
        
      

    

  

    

      
…updates

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

| Package | From | To |
| --- | --- | --- |
| [js-yaml](https://github.com/nodeca/js-yaml) | `4.1.0` | `4.1.1` |
| [esbuild](https://github.com/evanw/esbuild) | `0.20.2` | `0.25.0` |
| [storybook](https://github.com/storybookjs/storybook/tree/HEAD/code/core) | `8.6.14` | `8.6.17` |
| [next](https://github.com/vercel/next.js) | `14.2.29` | `15.5.14` |
| [bn.js](https://github.com/indutny/bn.js) | `4.12.2` | `4.12.3` |
| [node-forge](https://github.com/digitalbazaar/forge) | `1.3.1` | `1.3.3` |
| [rollup](https://github.com/rollup/rollup) | `4.41.0` | `4.60.0` |
| [undici](https://github.com/nodejs/undici) | `6.21.3` | `6.24.1` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `5.4.19` | `5.4.21` |

Bumps the npm_and_yarn group with 1 update in the /account-kit/plugingen directory: [esbuild](https://github.com/evanw/esbuild).
Bumps the npm_and_yarn group with 1 update in the /examples/alchemy-privy-integration-example directory: [next](https://github.com/vercel/next.js).
Bumps the npm_and_yarn group with 1 update in the /examples/ui-demo directory: [next](https://github.com/vercel/next.js).


Updates `js-yaml` from 4.1.0 to 4.1.1
- [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md)
- [Commits](nodeca/js-yaml@4.1.0...4.1.1)

Updates `esbuild` from 0.20.2 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.20.2...v0.25.0)

Updates `storybook` from 8.6.14 to 8.6.17
- [Release notes](https://github.com/storybookjs/storybook/releases)
- [Changelog](https://github.com/storybookjs/storybook/blob/v8.6.17/CHANGELOG.md)
- [Commits](https://github.com/storybookjs/storybook/commits/v8.6.17/code/core)

Updates `next` from 14.2.29 to 15.5.14
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v14.2.29...v15.5.14)

Updates `bn.js` from 4.12.2 to 4.12.3
- [Release notes](https://github.com/indutny/bn.js/releases)
- [Changelog](https://github.com/indutny/bn.js/blob/master/CHANGELOG.md)
- [Commits](indutny/bn.js@v4.12.2...v4.12.3)

Updates `node-forge` from 1.3.1 to 1.3.3
- [Changelog](https://github.com/digitalbazaar/forge/blob/main/CHANGELOG.md)
- [Commits](digitalbazaar/forge@v1.3.1...v1.3.3)

Updates `rollup` from 4.41.0 to 4.60.0
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](rollup/rollup@v4.41.0...v4.60.0)

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

Updates `vite` from 5.4.19 to 5.4.21
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v5.4.21/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v5.4.21/packages/vite)

Updates `esbuild` from 0.20.2 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.20.2...v0.25.0)

Updates `next` from 14.2.29 to 15.5.14
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v14.2.29...v15.5.14)

Updates `next` from 14.2.29 to 15.5.14
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v14.2.29...v15.5.14)

Updates `esbuild` from 0.20.2 to 0.27.4
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2024.md)
- [Commits](evanw/esbuild@v0.20.2...v0.25.0)

Updates `next` from 14.2.35 to 16.2.1
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v14.2.29...v15.5.14)

Updates `next` from 14.2.29 to 15.5.14
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v14.2.29...v15.5.14)

Updates `next` from 14.2.29 to 15.5.14
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v14.2.29...v15.5.14)

Updates `next` from 14.2.29 to 15.5.14
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v14.2.29...v15.5.14)

---
updated-dependencies:
- dependency-name: js-yaml
  dependency-version: 4.1.1
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: esbuild
  dependency-version: 0.25.0
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: storybook
  dependency-version: 8.6.17
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: next
  dependency-version: 15.5.14
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: bn.js
  dependency-version: 4.12.3
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: node-forge
  dependency-version: 1.3.3
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: rollup
  dependency-version: 4.60.0
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: undici
  dependency-version: 6.24.1
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: vite
  dependency-version: 5.4.21
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: esbuild
  dependency-version: 0.25.0
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: next
  dependency-version: 15.5.14
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: next
  dependency-version: 15.5.14
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: esbuild
  dependency-version: 0.27.4
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: next
  dependency-version: 16.2.1
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: next
  dependency-version: 15.5.14
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: next
  dependency-version: 15.5.14
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: next
  dependency-version: 15.5.14
  dependency-type: direct:production
  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-792f2f9915


    
 branch
    from
    bb7f5bb    to
    6c6afaa      
    Compare
  



    March 30, 2026 18:36    
    













  
  

    

      

  










  








  
      

  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment


  










      

  

    
    

    

  

    Reviewers
  


    


      

          


  
      @0xfourzerofour
  
    0xfourzerofour


                Awaiting requested review from 0xfourzerofour

                    0xfourzerofour is a code owner

        
      

      

          


  
      @dancoombs
  
    dancoombs


                Awaiting requested review from dancoombs

                    dancoombs is a code owner

        
      

      

          


  
      @niveda-krish
  
    niveda-krish


                Awaiting requested review from niveda-krish

                    niveda-krish is a code owner

        
      

      

          


  
      @pavelm
  
    pavelm


                Awaiting requested review from pavelm

                    pavelm is a code owner

        
      

      

          


  
      @jakehobbs
  
    jakehobbs


                Awaiting requested review from jakehobbs

                    jakehobbs is a code owner

        
      

      

          


  
      @florrdv
  
    florrdv


                Awaiting requested review from florrdv

                    florrdv is a code owner

        
      

      

          


  
      @Richard-Dang
  
    Richard-Dang


                Awaiting requested review from Richard-Dang

                    Richard-Dang is a code owner

        
      

      

          


  
      @clinder777
  
    clinder777


                Awaiting requested review from clinder777

                    clinder777 is a code owner

        
      

      

          


  
      @avarobinson
  
    avarobinson


                Awaiting requested review from avarobinson

                    avarobinson is a code owner

        
      

      

          


  
      @blakecduncan
  
    blakecduncan


                Awaiting requested review from blakecduncan

                    blakecduncan is a code owner

        
      

      

          


  
      @thebrianchen
  
    thebrianchen


                Awaiting requested review from thebrianchen

                    thebrianchen is a code owner

        
      

      

          


  
      @SahilAujla
  
    SahilAujla


                Awaiting requested review from SahilAujla

                    SahilAujla is a code owner

        
      


        

      At least 1 approving review is required to merge this pull request.
  








    
    
    

    

  


      
  

    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