From 5bd0d438ba7ce0194cc9d9b2cf17f27e5a47bf4a Mon Sep 17 00:00:00 2001 From: Andreas Deininger Date: Sat, 14 Mar 2026 21:38:33 +0100 Subject: [PATCH 1/2] Source map specification: fix broken link --- src/content/api.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/api.yml b/src/content/api.yml index 0d77ec5..0467e95 100644 --- a/src/content/api.yml +++ b/src/content/api.yml @@ -7464,7 +7464,7 @@ body: - h3: Sources content - p: > - [Source maps](#sourcemap) are generated using [version 3](https://sourcemaps.info/spec.html) + [Source maps](#sourcemap) are generated using [version 3](https://tc39.es/ecma426/) of the source map format, which is by far the most widely-supported variant. Each source map will look something like this: From d041dd7f0a9bf6ea987f3b8f2b94985bba60fb65 Mon Sep 17 00:00:00 2001 From: Andreas Deininger Date: Sat, 14 Mar 2026 21:41:38 +0100 Subject: [PATCH 2/2] Fix typos --- src/content/api.yml | 6 +++--- src/content/plugins.yml | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/content/api.yml b/src/content/api.yml index 0467e95..6b38594 100644 --- a/src/content/api.yml +++ b/src/content/api.yml @@ -5116,7 +5116,7 @@ body: - p: > By default esbuild assumes that JSX expressions are side-effect free, - which means they are annoated with [`/* @__PURE__ */` comments](#pure) and + which means they are annotated with [`/* @__PURE__ */` comments](#pure) and are removed during bundling when they are unused. This follows the common use of JSX for virtual DOM and applies to the vast majority of JSX libraries. However, some people have written JSX libraries that don't have this property @@ -7756,7 +7756,7 @@ body: - p: > This data can then be analyzed by other tools. For an interactive visualization, you can use esbuild's own [Bundle Size Analyzer](/analyze/). - For a quick textual analysis, you can use esbuild's build-in [analyze](#analyze) + For a quick textual analysis, you can use esbuild's built-in [analyze](#analyze) feature. Or you can write your own analysis which uses this information. - p: > @@ -8251,7 +8251,7 @@ body:
  • `undefined-composes-from`
    {{ FORMAT_MESSAGES({ 'example.module.css': '.foo { composes: bar from "lib.module.css"; zoom: 1; }', 'lib.module.css': '.bar { zoom: 2 }' }, { bundle: true }) }}
  • `unsupported-@charset`
    {{ FORMAT_MESSAGES('@charset "ASCII";', { sourcefile: 'example.css', loader: 'css' }) }}
  • `unsupported-@namespace`
    {{ FORMAT_MESSAGES('@namespace "ns";', { sourcefile: 'example.css', loader: 'css' }) }}
    • -
  • `unsupported-css-property`
    {{ FORMAT_MESSAGES('div { widht: 1px }', { sourcefile: 'example.css', loader: 'css' }) }}
    • +
  • `unsupported-css-property`
    {{ FORMAT_MESSAGES('div { width: 1px }', { sourcefile: 'example.css', loader: 'css' }) }}
  • `unsupported-css-nesting`
    {{ FORMAT_MESSAGES('a b {\n.foo & {\n}\n}', { sourcefile: 'example.css', loader: 'css', target: 'chrome50' }) }}

    • diff --git a/src/content/plugins.yml b/src/content/plugins.yml index 20cd362..1f182dd 100644 --- a/src/content/plugins.yml +++ b/src/content/plugins.yml @@ -1702,7 +1702,7 @@ body: `with`

    This is the [import attributes](https://github.com/tc39/proposal-import-attributes) - assocated with the import statement for this path. For example, a `with` value of + associated with the import statement for this path. For example, a `with` value of { type: 'json' } would be appropriate for a module imported using with { type: 'json' } attributes on the import statement. This information isn't used by esbuild but may be used by [on-resolve callbacks](#on-resolve).