Skip to content

Bump esbuild, @astrojs/mdx, @astrojs/starlight, @lorenzo_lewis/starlight-utils and astro #23

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 esbuild, @astrojs/mdx, @astrojs/starlight, @lorenzo_lewis/starlight-utils and astro #23

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Apr 8, 2025 •
edited
Loading

Bumps esbuild to 0.25.2 and updates ancestor dependencies esbuild, @astrojs/mdx, @astrojs/starlight, @lorenzo_lewis/starlight-utils and astro. These dependencies need to be updated together.

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 @astrojs/mdx from 3.1.9 to 4.2.3



Release notes

Sourced from @​astrojs/mdx's releases.




@​astrojs/mdx@​4.2.3


Patch Changes



@​astrojs/mdx@​4.2.2


Patch Changes



@​astrojs/mdx@​4.2.0


Minor Changes


    

  • 

    #13352 cb886dc Thanks @​delucis! - Adds support for a new experimental.headingIdCompat flag
    

    By default, Astro removes a trailing - from the end of IDs it generates for headings ending with
special characters. This differs from the behavior of common Markdown processors.
    

    You can now disable this behavior with a new configuration flag:
    

    // astro.config.mjs
import { defineConfig } from 'astro/config';
export default defineConfig({
experimental: {
headingIdCompat: true,
},
});
    

    This can be useful when heading IDs and anchor links need to behave consistently across your site
and other platforms such as GitHub and npm.
    

    If you are using the rehypeHeadingIds plugin directly, you can also pass this new option:
    

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import { rehypeHeadingIds } from '@astrojs/markdown-remark';
import { otherPluginThatReliesOnHeadingIDs } from 'some/plugin/source';
export default defineConfig({
markdown: {
rehypePlugins: [
[rehypeHeadingIds, { experimentalHeadingIdCompat: true }],
otherPluginThatReliesOnHeadingIDs,
],
},
});
    

    • 






... (truncated)





Changelog

Sourced from @​astrojs/mdx's changelog.




4.2.3


Patch Changes



4.2.2


Patch Changes



4.2.1


Patch Changes



4.2.0


Minor Changes


    

  • 

    #13352 cb886dc Thanks @​delucis! - Adds support for a new experimental.headingIdCompat flag
    

    By default, Astro removes a trailing - from the end of IDs it generates for headings ending with
special characters. This differs from the behavior of common Markdown processors.
    

    You can now disable this behavior with a new configuration flag:
    

    // astro.config.mjs
import { defineConfig } from 'astro/config';
export default defineConfig({
experimental: {
headingIdCompat: true,
},
});
    

    This can be useful when heading IDs and anchor links need to behave consistently across your site
and other platforms such as GitHub and npm.
    

    If you are using the rehypeHeadingIds plugin directly, you can also pass this new option:
    

    // astro.config.mjs
    

    • 






... (truncated)





Commits






Updates @astrojs/starlight from 0.28.2 to 0.33.0



Release notes

Sourced from @​astrojs/starlight's releases.




@​astrojs/starlight@​0.33.0


Minor Changes


    

  • 

    #3026 82deb84 Thanks @​HiDeoo! - Fixes a potential list styling issue if the last element of a list item is a <script> tag.
    

    ⚠️ BREAKING CHANGE:
    

    This release drops official support for Chromium-based browsers prior to version 105 (released 30 August 2022) and Firefox-based browsers prior to version 121 (released 19 December 2023). You can find a list of currently supported browsers and their versions using this browserslist query.
    

    With this release, Starlight-generated sites will still work fine on those older browsers except for this small detail in list item styling, but future releases may introduce further breaking changes for impacted browsers, including in patch releases.
    

    • 

  • 

    #3025 f87e9ac Thanks @​delucis! - Makes social configuration more flexible.
    

    ⚠️ BREAKING CHANGE: The social configuration option has changed syntax. You will need to update this in astro.config.mjs when upgrading.
    

    Previously, a limited set of platforms were supported using a shorthand syntax with labels built in to Starlight. While convenient, this approach was less flexible and required dedicated code for each social platform added.
    

    Now, you must specify the icon and label for each social link explicitly and you can use any of Starlight’s built-in icons for social links.
    

    The following example shows updating the old social syntax to the new:
    

    - social: {
-   github: 'https://github.com/withastro/starlight',
-   discord: 'https://astro.build/chat',
- },
+ social: [
+   { icon: 'github', label: 'GitHub', href: 'https://github.com/withastro/starlight' },
+   { icon: 'discord', label: 'Discord', href: 'https://astro.build/chat' },
+ ],
    

    • 

  • 

    #2927 c46904c Thanks @​HiDeoo! - Adds the head route data property which contains an array of all tags to include in the <head> of the current page.
    

    Previously, the <Head> component was responsible for generating a list of tags to include in the <head> of the current page and rendering them.
This data is now available as Astro.locals.starlightRoute.head instead and can be modified using route data middleware.
The <Head> component now only renders the tags provided in Astro.locals.starlightRoute.head.
    

    • 

  • 

    #2924 6a56d1b Thanks @​HiDeoo! - ⚠️ BREAKING CHANGE: Ensures that the <Badge> and <Icon> components no longer render with a trailing space.
    

    In Astro, components that include styles render with a trailing space which can prevent some use cases from working as expected, e.g. when using such components inlined with text. This change ensures that the <Badge> and <Icon> components no longer render with a trailing space.
    

    If you were previously relying on that implementation detail, you may need to update your code to account for this change. For example, considering the following code:
    

    <Badge text="New" />
Feature
    

    The rendered text would previously include a space between the badge and the text due to the trailing space automatically added by the component:
    

    • 






... (truncated)





Changelog

Sourced from @​astrojs/starlight's changelog.




0.33.0


Minor Changes


    

  • 

    #3026 82deb84 Thanks @​HiDeoo! - Fixes a potential list styling issue if the last element of a list item is a <script> tag.
    

    ⚠️ BREAKING CHANGE:
    

    This release drops official support for Chromium-based browsers prior to version 105 (released 30 August 2022) and Firefox-based browsers prior to version 121 (released 19 December 2023). You can find a list of currently supported browsers and their versions using this browserslist query.
    

    With this release, Starlight-generated sites will still work fine on those older browsers except for this small detail in list item styling, but future releases may introduce further breaking changes for impacted browsers, including in patch releases.
    

    • 

  • 

    #3025 f87e9ac Thanks @​delucis! - Makes social configuration more flexible.
    

    ⚠️ BREAKING CHANGE: The social configuration option has changed syntax. You will need to update this in astro.config.mjs when upgrading.
    

    Previously, a limited set of platforms were supported using a shorthand syntax with labels built in to Starlight. While convenient, this approach was less flexible and required dedicated code for each social platform added.
    

    Now, you must specify the icon and label for each social link explicitly and you can use any of Starlight’s built-in icons for social links.
    

    The following example shows updating the old social syntax to the new:
    

    - social: {
-   github: 'https://github.com/withastro/starlight',
-   discord: 'https://astro.build/chat',
- },
+ social: [
+   { icon: 'github', label: 'GitHub', href: 'https://github.com/withastro/starlight' },
+   { icon: 'discord', label: 'Discord', href: 'https://astro.build/chat' },
+ ],
    

    • 

  • 

    #2927 c46904c Thanks @​HiDeoo! - Adds the head route data property which contains an array of all tags to include in the <head> of the current page.
    

    Previously, the <Head> component was responsible for generating a list of tags to include in the <head> of the current page and rendering them.
This data is now available as Astro.locals.starlightRoute.head instead and can be modified using route data middleware.
The <Head> component now only renders the tags provided in Astro.locals.starlightRoute.head.
    

    • 

  • 

    #2924 6a56d1b Thanks @​HiDeoo! - ⚠️ BREAKING CHANGE: Ensures that the <Badge> and <Icon> components no longer render with a trailing space.
    

    In Astro, components that include styles render with a trailing space which can prevent some use cases from working as expected, e.g. when using such components inlined with text. This change ensures that the <Badge> and <Icon> components no longer render with a trailing space.
    

    If you were previously relying on that implementation detail, you may need to update your code to account for this change. For example, considering the following code:
    

    <Badge text="New" />
Feature
    

    • 






... (truncated)





Commits





Maintainer changes

This version was pushed to npm by matthewp, a new releaser for @​astrojs/starlight since your current version.






Updates @lorenzo_lewis/starlight-utils from 0.2.0 to 0.3.2



Release notes

Sourced from @​lorenzo_lewis/starlight-utils's releases.




@​lorenzo_lewis/[email protected]


Patch Changes



@​lorenzo_lewis/[email protected]


Patch Changes



@​lorenzo_lewis/[email protected]


Minor Changes








Changelog

Sourced from @​lorenzo_lewis/starlight-utils's changelog.




0.3.2


Patch Changes



0.3.1


Patch Changes



0.3.0


Minor Changes








Commits






Updates astro from 4.16.18 to 5.6.1



Release notes

Sourced from astro's releases.




[email protected]


Patch Changes



[email protected]


Minor Changes


    

  • 

    #13403 dcb9526 Thanks @​yurynix! - Adds a new optional prerenderedErrorPageFetch option in the Adapter API to allow adapters to provide custom implementations for fetching prerendered error pages.
    

    Now, adapters can override the default fetch() behavior, for example when fetch() is unavailable or when you cannot call the server from itself.
    

    The following example provides a custom fetch for 500.html and 404.html, reading them from disk instead of performing an HTTP call:
    

    return app.render(request, {
  prerenderedErrorPageFetch: async (url: string): Promise<Response> => {
    if (url.includes("/500")) {
        const content = await fs.promises.readFile("500.html", "utf-8");
        return new Response(content, {
          status: 500,
          headers: { "Content-Type": "text/html" },
        });
    }
    const content = await fs.promises.readFile("404.html", "utf-8");
      return new Response(content, {
        status: 404,
        headers: { "Content-Type": "text/html" },
      });
});
    

    If no value is provided, Astro will fallback to its default behavior for fetching error pages.
    

    Read more about this feature in the Adapter API reference.
    

    • 

  • 

    #13482 ff257df Thanks @​florian-lefebvre! - Updates Astro config validation to also run for the Integration API. An error log will specify which integration is failing the validation.
    

    Now, Astro will first validate the user configuration, then validate the updated configuration after each integration astro:config:setup hook has run. This means updateConfig() calls will no longer accept invalid configuration.
    

    This fixes a situation where integrations could potentially update a project with a malformed configuration. These issues should now be caught and logged so that you can update your integration to only set valid configurations.
    

    • 

  • 

    #13405 21e7e80 Thanks @​Marocco2! - Adds a new eagerness option for prefetch() when using experimental.clientPrerender
    

    With the experimental clientPrerender flag enabled, you can use the eagerness option on prefetch() to suggest to the browser how eagerly it should prefetch/prerender link targets.
    

    • 






... (truncated)





Changelog

Sourced from astro's changelog.




5.6.1


Patch Changes



5.6.0


Minor Changes


    

  • 

    #13403 dcb9526 Thanks @​yurynix! - Adds a new optional prerenderedErrorPageFetch option in the Adapter API to allow adapters to provide custom implementations for fetching prerendered error pages.
    

    Now, adapters can override the default fetch() behavior, for example when fetch() is unavailable or when you cannot call the server from itself.
    

    The following example provides a custom fetch for 500.html and 404.html, reading them from disk instead of performing an HTTP call:
    

    return app.render(request, {
  prerenderedErrorPageFetch: async (url: string): Promise<Response> => {
    if (url.includes("/500")) {
        const content = await fs.promises.readFile("500.html", "utf-8");
        return new Response(content, {
          status: 500,
          headers: { "Content-Type": "text/html" },
        });
    }
    const content = await fs.promises.readFile("404.html", "utf-8");
      return new Response(content, {
        status: 404,
        headers: { "Content-Type": "text/html" },
      });
});
    

    If no value is provided, Astro will fallback to its default behavior for fetching error pages.
    

    Read more about this feature in the Adapter API reference.
    

    • 

  • 

    #13482 ff257df Thanks @​florian-lefebvre! - Updates Astro config validation to also run for the Integration API. An error log will specify which integration is failing the validation.
    

    Now, Astro will first validate the user configuration, then validate the updated configuration after each integration astro:config:setup hook has run. This means updateConfig() calls will no longer accept invalid configuration.
    

    This fixes a situation where integrations could potentially update a project with a malformed configuration. These issues should now be caught and logged so that you can update your integration to only set valid configurations.
    

    • 

  • 

    #13405 21e7e80 Thanks @​Marocco2! - Adds a new eagerness option for prefetch() when using experimental.clientPrerender
    

    • 






... (truncated)





Commits






You can trigger a rebase of this PR 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • 

  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • 

  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    
You can disable automated security fix PRs for this repo from the Security Alerts page.
    • 







Note

Automatic rebases have been disabled on this pull request as it has been open for over 30 days.



    

  
  



      


          

          
  
  

    
  
    
    

  

  

  



          

        
      




  




      

                  



      

  
            

    

      
    

    


      


          @dependabot
dependabot
bot



            added
      

  dependencies

  Pull requests that update a dependency file

      

  javascript

  Pull requests that update javascript code

  labels


      Apr 8, 2025

    

  



  

  
  

  
      @dependabot
  dependabot
bot

        force-pushed
    the
        
      
  dependabot/npm_and_yarn/multi-da57937042


    
 branch
    from
    0b0f4d4    to
    8229b55      
    Compare
  



    May 7, 2025 22:09    
    









      

  
        

  

      

  
  

  
          

  

    

      


  

      
        @dependabot
  




      

        
          Bump esbuild, @astrojs/mdx, @astrojs/starlight, @lorenzo_lewis/starli…
        

          
                        
      


      

        

    
    
    

  

    


      


      

        

          

    
    
    

  

  

    
  



        

      


      

        
          8a711f8
        
      

    

  

    

      
…ght-utils and astro

Bumps [esbuild](https://github.com/evanw/esbuild) to 0.25.2 and updates ancestor dependencies [esbuild](https://github.com/evanw/esbuild), [@astrojs/mdx](https://github.com/withastro/astro/tree/HEAD/packages/integrations/mdx), [@astrojs/starlight](https://github.com/withastro/starlight/tree/HEAD/packages/starlight), [@lorenzo_lewis/starlight-utils](https://github.com/lorenzolewis/starlight-utils/tree/HEAD/packages/starlight-utils) and [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro). These dependencies need to be updated together.


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 `@astrojs/mdx` from 3.1.9 to 4.2.3
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/integrations/mdx/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/@astrojs/[email protected]/packages/integrations/mdx)

Updates `@astrojs/starlight` from 0.28.2 to 0.33.0
- [Release notes](https://github.com/withastro/starlight/releases)
- [Changelog](https://github.com/withastro/starlight/blob/main/packages/starlight/CHANGELOG.md)
- [Commits](https://github.com/withastro/starlight/commits/@astrojs/[email protected]/packages/starlight)

Updates `@lorenzo_lewis/starlight-utils` from 0.2.0 to 0.3.2
- [Release notes](https://github.com/lorenzolewis/starlight-utils/releases)
- [Changelog](https://github.com/lorenzolewis/starlight-utils/blob/main/packages/starlight-utils/CHANGELOG.md)
- [Commits](https://github.com/lorenzolewis/starlight-utils/commits/@lorenzo_lewis/[email protected]/packages/starlight-utils)

Updates `astro` from 4.16.18 to 5.6.1
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/[email protected]/packages/astro)

---
updated-dependencies:
- dependency-name: esbuild
  dependency-version: 0.25.2
  dependency-type: indirect
- dependency-name: "@astrojs/mdx"
  dependency-version: 4.2.3
  dependency-type: direct:production
- dependency-name: "@astrojs/starlight"
  dependency-version: 0.33.0
  dependency-type: direct:production
- dependency-name: "@lorenzo_lewis/starlight-utils"
  dependency-version: 0.3.2
  dependency-type: direct:production
- dependency-name: astro
  dependency-version: 5.6.1
  dependency-type: direct:production
...

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

    







  








      

  
          

  
  

  
      @dependabot
  dependabot
bot

        force-pushed
    the
        
      
  dependabot/npm_and_yarn/multi-da57937042


    
 branch
    from
    8229b55    to
    8a711f8      
    Compare
  



    May 7, 2025 22:11    
    













  
  

    

      

  




      


    


    

      

        
      

  
    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