[v6]: remove Astro.glob() [i18nIgnore]

src/content/docs/en/guides/upgrade-to/v6.mdx

@@ -102,6 +102,33 @@ import { ClientRouter } from 'astro:transitions';
 
 <ReadMore>Read more about [view transitions and client-side routing in Astro](/en/guides/view-transitions/).</ReadMore>
 
+### Removed: `Astro.glob()`
+
+<SourcePR number="14421" title="feat!: remove Astro.glob"/>
+
+In Astro 5.0, `Astro.glob()` was deprecated in favor of using `getCollection()` to query your collections, and `import.meta.glob()` to query other source files in your project.
+
+Astro 6.0 removes `Astro.glob()` entirely. Update to `import.meta.glob()` to keep your current behavior.
+
+#### What should I do?
+
+Replace all use of `Astro.glob()` with `import.meta.glob()`. Note that `import.meta.glob()` no longer returns a `Promise`, so you may have to update your code accordingly. You should not require any updates to your [glob patterns](/en/guides/imports/#glob-patterns).
+
+```astro title="src/pages/blog.astro" del={2} ins={3}
+---
+const posts = await Astro.glob('./posts/*.md');
+const posts = Object.values(import.meta.glob('./posts/*.md', { eager: true }));
+---
+
+{posts.map((post) => <li><a href={post.url}>{post.frontmatter.title}</a></li>)}
+```
+
+Where appropriate, consider using [content collections](/en/guides/content-collections/) to organize your content, which has its own newer, more performant querying functions.
+
+You may also wish to consider using glob packages from NPM, such as [`fast-glob`](https://www.npmjs.com/package/fast-glob).
+
+<ReadMore>Learn more about [importing files with `import.meta.glob`](/en/guides/imports/#importmetaglob).</ReadMore>
+
 ## Changed Defaults
 
 Some default behavior has changed in Astro v5.0 and your project code may need updating to account for these changes.

src/content/docs/en/reference/api-reference.mdx

@@ -1048,118 +1048,3 @@ Loads a session by ID. In normal use, a session is loaded automatically from the
   </TabItem>
 
 </Tabs>
-
-
-### Deprecated object properties
-
-#### `Astro.glob()`
-
-:::caution[Deprecated in v5.0]
-Use [Vite's `import.meta.glob`](https://vite.dev/guide/features.html#glob-import) to query project files. 
-
-`Astro.glob('../pages/post/*.md')` can be replaced with:
-
-`Object.values(import.meta.glob('../pages/post/*.md', { eager: true }));`
-
-See the [imports guide](/en/guides/imports/#importmetaglob) for more information and usage.
-:::
-
-`Astro.glob()` is a way to load many local files into your static site setup.
-
-```astro
----
-// src/components/my-component.astro
-const posts = await Astro.glob('../pages/post/*.md'); // returns an array of posts that live at ./src/pages/post/*.md
----
-
-<div>
-{posts.slice(0, 3).map((post) => (
-  <article>
-    <h2>{post.frontmatter.title}</h2>
-    <p>{post.frontmatter.description}</p>
-    <a href={post.url}>Read more</a>
-  </article>
-))}
-</div>
-```
-
-`.glob()` only takes one parameter: a relative URL glob of which local files you'd like to import. It’s asynchronous and returns an array of the exports from matching files.
-
-`.glob()` can't take variables or strings that interpolate them, as they aren't statically analyzable. (See [the imports guide](/en/guides/imports/#supported-values) for a workaround.) This is because `Astro.glob()` is a wrapper of Vite's [`import.meta.glob()`](https://vite.dev/guide/features.html#glob-import).
-
-:::note
-You can also use `import.meta.glob()` itself in your Astro project. You may want to do this when:
-- You need this feature in a file that isn't `.astro`, like an API route. `Astro.glob()` is only available in `.astro` files, while `import.meta.glob()` is available anywhere in the project.
-- You don't want to load each file immediately. `import.meta.glob()` can return functions that import the file content, rather than returning the content itself. Note that this import includes all styles and scripts for any imported files. These will be bundled and added to the page whether or not a file is actually used, as this is decided by static analysis, not at runtime.
-- You want access to each file's path. `import.meta.glob()` returns a map of a file's path to its content, while `Astro.glob()` returns a list of content.
-- You want to pass multiple patterns; for example, you want to add a "negative pattern" that filters out certain files. `import.meta.glob()` can optionally take an array of glob strings, rather than a single string.
-
-Read more in the [Vite documentation](https://vite.dev/guide/features.html#glob-import).
-:::
-
-##### Markdown Files
-
-Markdown files loaded with `Astro.glob()` return the following `MarkdownInstance` interface:
-
-```ts
-export interface MarkdownInstance<T extends Record<string, any>> {
-  /* Any data specified in this file's YAML/TOML frontmatter */
-	frontmatter: T;
-  /* The absolute file path of this file */
-	file: string;
-  /* The rendered path of this file */
-	url: string | undefined;
-  /* Astro Component that renders the contents of this file */
-	Content: AstroComponentFactory;
-  /** (Markdown only) Raw Markdown file content, excluding layout HTML and YAML/TOML frontmatter */
-	rawContent(): string;
-  /** (Markdown only) Markdown file compiled to HTML, excluding layout HTML */
-	compiledContent(): string;
-  /* Function that returns an array of the h1...h6 elements in this file */
-	getHeadings(): Promise<{ depth: number; slug: string; text: string }[]>;
-	default: AstroComponentFactory;
-}
-```
-
-You can optionally provide a type for the `frontmatter` variable using a TypeScript generic.
-
-```astro
----
-interface Frontmatter {
-  title: string;
-  description?: string;
-}
-const posts = await Astro.glob<Frontmatter>('../pages/post/*.md');
----
-
-<ul>
-  {posts.map(post => <li>{post.frontmatter.title}</li>)}
-</ul>
-```
-
-##### Astro Files
-
-Astro files have the following interface:
-
-```ts
-export interface AstroInstance {
-  /* The file path of this file */
-  file: string;
-  /* The URL for this file (if it is in the pages directory) */
-	url: string | undefined;
-	default: AstroComponentFactory;
-}
-```
-
-##### Other Files
-
-Other files may have various different interfaces, but `Astro.glob()` accepts a TypeScript generic if you know exactly what an unrecognized file type contains.
-
-```ts
----
-interface CustomDataFile {
-  default: Record<string, any>;
-}
-const data = await Astro.glob<CustomDataFile>('../data/**/*.js');
----
-```

src/content/docs/en/reference/error-reference.mdx

@@ -64,15 +64,12 @@ The following reference is a complete list of the errors you may encounter while
 - [**AstroResponseHeadersReassigned**](/en/reference/errors/astro-response-headers-reassigned/)<br/>`Astro.response.headers` must not be reassigned.
 - [**MiddlewareCantBeLoaded**](/en/reference/errors/middleware-cant-be-loaded/)<br/>Can't load the middleware.
 - [**LocalImageUsedWrongly**](/en/reference/errors/local-image-used-wrongly/)<br/>Local images must be imported.
-- [**AstroGlobUsedOutside**](/en/reference/errors/astro-glob-used-outside/)<br/>Astro.glob() used outside of an Astro file.
-- [**AstroGlobNoMatch**](/en/reference/errors/astro-glob-no-match/)<br/>Astro.glob() did not match any files.
 - [**RedirectWithNoLocation**](/en/reference/errors/redirect-with-no-location/)<br/>A redirect must be given a location with the `Location` header.
 - [**UnsupportedExternalRedirect**](/en/reference/errors/unsupported-external-redirect/)<br/>Unsupported or malformed URL.
 - [**InvalidDynamicRoute**](/en/reference/errors/invalid-dynamic-route/)<br/>Invalid dynamic route.
 - [**MissingSharp**](/en/reference/errors/missing-sharp/)<br/>Could not find Sharp.
 - [**UnknownViteError**](/en/reference/errors/unknown-vite-error/)<br/>Unknown Vite Error.
 - [**FailedToLoadModuleSSR**](/en/reference/errors/failed-to-load-module-ssr/)<br/>Could not import file.
-- [**InvalidGlob**](/en/reference/errors/invalid-glob/)<br/>Invalid glob pattern.
 - [**FailedToFindPageMapSSR**](/en/reference/errors/failed-to-find-page-map-ssr/)<br/>Astro couldn't find the correct page to render
 - [**MissingLocale**](/en/reference/errors/missing-locale/)<br/>The provided locale does not exist.
 - [**MissingIndexForInternationalization**](/en/reference/errors/missing-index-for-internationalization/)<br/>Index page not found.