Skip to content

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

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 7 updates #6

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Apr 13, 2025

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

Package From To
next 15.0.3 15.3.0
vitest 1.3.1 1.6.1
@vitest/coverage-v8 1.3.1 1.6.1
esbuild 0.21.5 0.25.2
@vitejs/plugin-react 4.2.1 4.3.4
@vitest/coverage-v8 1.6.1 3.1.1
vitest 1.6.1 3.1.1
nanoid 3.3.7 3.3.11
vite 5.4.11 6.2.6

Updates next from 15.0.3 to 15.3.0

Release notes

Sourced from next's releases.

v15.3.0

Core Changes

  • [dev-overlay] Customize <select> styling for consistency: #76973
  • Upgrade React from 029e8bd6-20250306 to 0ca3deeb-20250311: #76989
  • [metadata]: add pinterest meta tag: #76988
  • [dev-overlay] ensure stripping overlay bundle in prod build: #76976
  • Apply env inlining during generate build mode: #76990
  • Turbopack: Implement deploymentId: #76904
  • track persistent caching usage: #76996
  • [metadata] re-insert icons to head for streamed metadata: #76915
  • Upgrade React from 0ca3deeb-20250311 to 6aa8254b-20250312: #77033
  • Move static-env imports: #77035
  • [dev-overlay] Add size setting to preferences: #77027
  • Add config for only generating static env: #77038
  • chore(HMR clients): Clean up and share code between app and pages router: #76960
  • Add dev warning for cross-origin and stabilize allowedDevOrigins: #77044
  • unify allowed origin detection handling: #77053
  • Handle hash change in all files for static env: #77058
  • [dev-overlay] highlight errored code line for runtime errors: #77078
  • NFT: Ignore all of Webpack: #77081
  • Add experimental build mode flag for env: #77089
  • (feat) support client-side instrumentation: #76916
  • Fix JSDoc comment for 'seconds' cache life profile: #77084
  • refactor(HMR clients): Encapsulate some of the turbopack state tracking into a shared TurbopackHmr class: #76994
  • Slightly improve error handling for unknown server actions: #77135
  • Fix output standalone for alternative bundler: #76971
  • Add alternate bundler plugin information to next info: #77059
  • [metadata] remove the default segement check for metadata rendering: #77119
  • [dev-overlay] Fix stacking order of highlighted line: #77189
  • Upgrade React from 6aa8254b-20250312 to 5398b711-20250314: #77129
  • fix(styled-jsx): Pass useLightningcss option to styled-jsx correctly: #77008
  • log the instrumentation-client execution time: #77121
  • Turbopack: canary-gate production builds: #77146
  • [dev-overlay] remove special handling for missing tag error : #77147
  • chore(react-dev-overlay): Remove confusingly underscored variables in useErrorOverlayReducer: #77205
  • Update middleware request header: #77201
  • Update default allowed origins list: #77212
  • Ensure deploymentId is used for CSS preloads: #77210
  • chore(HMR clients): Fix a bunch of typescript errors by including the appropriate webpack type declarations: #77207
  • Update cache handler interface: #76687
  • Turbopack: don't include AMP optimizer in NFT: #77242
  • Server actions should not read stale data after calling revalidate*: #76885
  • [dev-overlay] Blur fader for scrollable container: #77196
  • Make revalidate* work when followed by a redirect in a route handler: #77090
  • feat: onNavigate for link: #77209
  • fix: pass telemetry plugin rspack tests: #77257
  • feat(eslint-plugin): add minimal built-in flat presets: #73873
  • [perf] skip loading client manifest for static metadata routes: #77260
  • Upgrade React from 5398b711-20250314 to c69a5fc5-20250318: #77249

... (truncated)

Commits

Updates vitest from 1.3.1 to 1.6.1

Release notes

Sourced from vitest's releases.

v1.6.1

This release includes security patches for:

   🐞 Bug Fixes

    View changes on GitHub

v1.6.0

   🚀 Features

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

v1.5.3

   🐞 Bug Fixes

... (truncated)

Commits

Updates @vitest/coverage-v8 from 1.3.1 to 1.6.1

Release notes

Sourced from @​vitest/coverage-v8's releases.

v1.6.1

This release includes security patches for:

   🐞 Bug Fixes

    View changes on GitHub

v1.6.0

   🚀 Features

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

v1.5.3

   🐞 Bug Fixes

... (truncated)

Commits

Updates esbuild from 0.21.5 to 0.25.2

Release notes

Sourced from esbuild's releases.

v0.25.2

  • Support flags in regular expressions for the API (#4121)

    The JavaScript plugin API for esbuild takes JavaScript regular expression objects for the filter option. Internally these are translated into Go regular expressions. However, this translation previously ignored the flags property of the regular expression. With this release, esbuild will now translate JavaScript regular expression flags into Go regular expression flags. Specifically the JavaScript regular expression /\.[jt]sx?$/i is turned into the Go regular expression `(?i)\.[jt]sx?$` internally inside of esbuild's API. This should make it possible to use JavaScript regular expressions with the i flag. Note that JavaScript and Go don't support all of the same regular expression features, so this mapping is only approximate.

  • Fix node-specific annotations for string literal export names (#4100)

    When node instantiates a CommonJS module, it scans the AST to look for names to expose via ESM named exports. This is a heuristic that looks for certain patterns such as exports.NAME = ... or module.exports = { ... }. This behavior is used by esbuild to "annotate" CommonJS code that was converted from ESM with the original ESM export names. For example, when converting the file export let foo, bar from ESM to CommonJS, esbuild appends this to the end of the file:

    // Annotate the CommonJS export names for ESM import in node:
0 && (module.exports = {
  bar,
  foo
});

    However, this feature previously didn't work correctly for export names that are not valid identifiers, which can be constructed using string literal export names. The generated code contained a syntax error. That problem is fixed in this release:

    // Original code
let foo
export { foo as "foo!" }
// Old output (with --format=cjs --platform=node)
...
0 && (module.exports = {
"foo!"
});
// New output (with --format=cjs --platform=node)
...
0 && (module.exports = {
"foo!": null
});

  • Basic support for index source maps (#3439, #4109)

    The source map specification has an optional mode called index source maps that makes it easier for tools to create an aggregate JavaScript file by concatenating many smaller JavaScript files with source maps, and then generate an aggregate source map by simply providing the original source maps along with some offset information. My understanding is that this is rarely used in practice. I'm only aware of two uses of it in the wild: ClojureScript and Turbopack.

    This release provides basic support for indexed source maps. However, the implementation has not been tested on a real app (just on very simple test input). If you are using index source maps in a real app, please try this out and report back if anything isn't working for you.

    Note that this is also not a complete implementation. For example, index source maps technically allows nesting source maps to an arbitrary depth, while esbuild's implementation in this release only supports a single level of nesting. It's unclear whether supporting more than one level of nesting is important or not given the lack of available test cases.

    This feature was contributed by @​clyfish.

v0.25.1

... (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 @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






Updates @vitest/coverage-v8 from 1.6.1 to 3.1.1



Release notes

Sourced from @​vitest/coverage-v8's releases.




v1.6.1


This release includes security patches for:



   🐞 Bug Fixes



    View changes on GitHub


v1.6.0


   🚀 Features



   🐞 Bug Fixes



   🏎 Performance



    View changes on GitHub


v1.5.3


   🐞 Bug Fixes






... (truncated)





Commits






Updates vitest from 1.6.1 to 3.1.1



Release notes

Sourced from vitest's releases.




v1.6.1


This release includes security patches for:



   🐞 Bug Fixes



    View changes on GitHub


v1.6.0


   🚀 Features



   🐞 Bug Fixes



    

  
  



      


          

          
  
  

    
  
    
    

  

  

  



          

        
      




  





       
            



      

  
        

  

      

  
  

  
          

  

    

      


  

      
        @dependabot
  




      

        
          Bump the npm_and_yarn group across 1 directory with 7 updates
        

          
                        
      


      

        

    
    
    

  

    


      


      

        

          

    
    
    

  

  

    
  



        

      


      

        
          9d77b59
        
      

    

  

    

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

| Package | From | To |
| --- | --- | --- |
| [next](https://github.com/vercel/next.js) | `15.0.3` | `15.3.0` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `1.3.1` | `1.6.1` |
| [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) | `1.3.1` | `1.6.1` |
| [esbuild](https://github.com/evanw/esbuild) | `0.21.5` | `0.25.2` |
| [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) | `4.2.1` | `4.3.4` |
| [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) | `1.6.1` | `3.1.1` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `1.6.1` | `3.1.1` |
| [nanoid](https://github.com/ai/nanoid) | `3.3.7` | `3.3.11` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `5.4.11` | `6.2.6` |



Updates `next` from 15.0.3 to 15.3.0
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v15.0.3...v15.3.0)

Updates `vitest` from 1.3.1 to 1.6.1
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v1.6.1/packages/vitest)

Updates `@vitest/coverage-v8` from 1.3.1 to 1.6.1
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v1.6.1/packages/coverage-v8)

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

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 `@vitest/coverage-v8` from 1.6.1 to 3.1.1
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v1.6.1/packages/coverage-v8)

Updates `vitest` from 1.6.1 to 3.1.1
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v1.6.1/packages/vitest)

Updates `nanoid` from 3.3.7 to 3.3.11
- [Release notes](https://github.com/ai/nanoid/releases)
- [Changelog](https://github.com/ai/nanoid/blob/main/CHANGELOG.md)
- [Commits](ai/nanoid@3.3.7...3.3.11)

Updates `vite` from 5.4.11 to 6.2.6
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v6.2.6/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v6.2.6/packages/vite)

---
updated-dependencies:
- dependency-name: next
  dependency-version: 15.3.0
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: vitest
  dependency-version: 1.6.1
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: "@vitest/coverage-v8"
  dependency-version: 1.6.1
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: esbuild
  dependency-version: 0.25.2
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: "@vitejs/plugin-react"
  dependency-version: 4.3.4
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: "@vitest/coverage-v8"
  dependency-version: 3.1.1
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: vitest
  dependency-version: 3.1.1
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: nanoid
  dependency-version: 3.3.11
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: vite
  dependency-version: 6.2.6
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <[email protected]>

    







  








      

  
            

    

      
    

    


      

          @dependabot
dependabot
bot



            added
      

  dependencies

  Pull requests that update a dependency file

      

  javascript

  Pull requests that update javascript code

  labels


      Apr 13, 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