polen 0.10.0-next.3 → 0.10.0-next.4

package/README.md

@@ -2,34 +2,33 @@
 
 A framework for delightful GraphQL developer portals
 
-## Installation
+## What is Polen?
 
-```sh
-npm add polen
-```
+Polen transforms your GraphQL schema into a beautiful, interactive developer portal with zero configuration. It automatically generates:
 
-## Quickstart
+- 📖 **Schema Reference** - Interactive documentation for all types, fields, and operations
+- 📝 **Changelog** - Track schema evolution over time
+- 📄 **Custom Pages** - Add guides, tutorials, and API documentation with Markdown/MDX
+- 🎨 **Beautiful UI** - Modern, responsive design out of the box
+- 🚀 **Instant Deploy** - Static site generation for easy hosting anywhere
 
-1. Have a `schema.graphql` GraphQL schema file in your project directory.
+## Quick Start
 
-   ```graphql
-   type Query {
-     hello: String
-   }
-   ```
+```sh
+# Install Polen
+npm add polen
 
-2. Build your developer portal.
+# Create a GraphQL schema file
+echo "type Query { hello: String }" > schema.graphql
 
-   ```sh
-   npx polen build
-   ```
+# Build your developer portal
+npx polen build
 
-3. You now have a deployable developer portal. Try it locally
-   (http://localhost:3001):
+# Preview locally
+node build/app.js
+```
 
-   ```sh
-   node build/app.js
-   ```
+Visit http://localhost:3001 to see your developer portal!
 
 ## Live Demos
 
@@ -38,378 +37,52 @@ Experience Polen in action with our live documentation sites:
 ### 🌐 [View All Demos](https://the-guild-org.github.io/polen/)
 
 Featured examples:
-
 - **[Pokemon GraphQL API](https://the-guild-org.github.io/polen/latest/pokemon/)** - Explore a fun GraphQL API with rich schema documentation
 - **GitHub GraphQL API** (Coming soon) - Browse GitHub's extensive GraphQL API documentation
 
-### Demo Versions
-
-Our demos are available at different stability levels, matching npm's dist tags:
+## Documentation
 
-- **Stable Release** (`latest`): [/polen/latest/pokemon](https://the-guild-org.github.io/polen/latest/pokemon/)
-  - The most recent stable version (e.g., `1.0.0`)
-  - Same as `npm install polen`
+- **[Getting Started](./docs/getting-started.md)** - Installation and quick start guide
+- **[Schema Configuration](./docs/guide/schema.md)** - Configure your GraphQL schema
+- **[Custom Pages](./docs/guide/pages.md)** - Add documentation with Markdown and MDX
+- **[Build & Deploy](./docs/guide/build.md)** - Build configuration and deployment options
+- **[CLI Reference](./docs/cli/index.md)** - All available commands
+- **[Package API](./docs/api/package.md)** - Programmatic usage
 
-- **Pre-release** (`next`): [/polen/next/pokemon](https://the-guild-org.github.io/polen/next/pokemon/)
-  - The latest pre-release version (e.g., `1.1.0-beta.1`)
-  - Same as `npm install polen@next`
+### Features
 
-- **Tagged Versions**: Access any specific release
-  - e.g., [/polen/1.0.0/pokemon](https://the-guild-org.github.io/polen/1.0.0/pokemon/)
-  - Same as `npm install polen@1.0.0`
-
-> [!TIP]
-> The correspondence between demo URLs and npm versions makes it easy to test features before upgrading. If you're using `polen@1.0.0`, visit `/polen/1.0.0/pokemon` to see exactly how your docs will look!
+- **[Static Rebase](./docs/features/static-rebase.md)** - Update base paths without rebuilding
+- **[Syntax Highlighting](./docs/features/syntax-highlighting.md)** - Beautiful code blocks with language support
 
 ## Examples
 
-Find the source code for these demos and more in the [examples](./examples) directory.
-
-## Guide
-
-### Schema Reference
-
-If you [provide Polen with a schema](#providing-a-schema), Polen will
-automatically render reference documentation for it.
-
-If you provide multiple versions of your schema then the reference is based on
-the schema with the latest date.
-
-### Schema Changelog
-
-Polen can render a changelog for your schema.
-
-This feature is automatically enabled when you provide multiple versions of your
-schema. Refer to [Provide a Schema](#providing-a-schema) for details on how to
-do that.
-
-### Schema Augmentations
-
-#### Descriptions
-
-You can append/prepend/replace descriptions of types and fields in your schema.
-
-Any Markdown syntax in your content will be automatically rendered.
-
-```ts
-import { Polen } from 'polen'
-
-export default Polen.defineConfig({
-  templateVariables: {
-    title: `Pokemon Developer Portal`,
-  },
-  schemaAugmentations: [
-    {
-      type: `description`,
-      on: {
-        type: `TargetType`,
-        name: `Query`,
-      },
-      placement: `over`,
-      content:
-        `**Content from [Polen](https://github.com/the-guild-org/polen)**.`,
-    },
-  ],
-})
-```
-
-### Providing a Schema
-
-You can provide a GraphQL schema to Polen in various ways.
-
-#### File
-
-Have a single `schema.graphql` SDL file in your project directory. Example:
-
-```
-schema.graphql
-```
-
-#### Directory
-
-Have a `schema` directory in your project directory with multiple versions of
-your schema as SDL files named using format: `YYYY-MM-DD.graphql`. Example:
-
-```
-schema/
-  2023-01-13.graphql
-  2020-09-26.graphql
-```
-
-This approach allows Polen to render a changelog for your schema. Refer to
-[Changelog](#changelog).
-
-#### Memory
-
-You can provide a schema to Polen in memory via configuration.
-
-You have control to provide one or multiple schemas, with or without dates.
-
-If no dates are given then the current time is assumed.
-
-If you provide multiple versions then Polen can render a changelog for you.
-Refer to [Changelog](#changelog).
-
-Basic example:
-
-```ts
-// polen.config.ts
-import { Polen } from 'polen'
-
-export default Polen.defineConfig({
-  schema: {
-    useDataSources: `memory`,
-    dataSources: {
-      memory: {
-        versions: [
-          {
-            date: new Date('2023-01-13'),
-            value: `type Query { hello: String }`,
-          },
-        ],
-      },
-    },
-  },
-})
-```
-
-### Pages
-
-You can add pages to your developer portal by adding markdown (`.md`) or MDX (`.mdx`) files to a
-`pages` directory.
-
-#### Routing
-
-- A file becomes a page.
-- The relative (to `pages` directory) file path becomes the web path.
-- _Navigation Bar_
-  - Top level pages are listed in the navigation bar.
-- _Index Pages_
-  - A file named `index` is an index page.
-  - The file name is elided in the route. For example `foo/index.md` becomes
-    route `/foo` .
-  - Details:
-    - If both `foo/index.md` and `foo.md` exist, then the former is used, latter
-      ignored, and a warning is raised.
-
-Example:
-
-| File                  | Route      | Navigation Bar Title |
-| --------------------- | ---------- | -------------------- |
-| `pages/foo.md`        | `/foo`     | `Foo`                |
-| `pages/foo.mdx`       | `/foo`     | `Foo`                |
-| `pages/foo/index.md`  | `/foo`     | `Foo`                |
-| `pages/foo/index.mdx` | `/foo`     | `Foo`                |
-| `pages/foo/bar.md`    | `/foo/bar` | `Foo`                |
-| `pages/foo/bar.mdx`   | `/foo/bar` | `Foo`                |
-
-#### Page Ordering
-
-You can control the order of pages in the sidebar by prefixing file names with numbers followed by `_` or `-`. The numeric prefix affects only the sidebar ordering - it does not appear in the page URL or title.
-
-- _Syntax_
-  - Format: `<number>_<name>.md` or `<number>-<name>.md`
-  - Examples: `01_intro.md`, `10_getting-started.md`, `20-configuration.md`
-- _Ordering_
-  - Pages with numeric prefixes appear before pages without prefixes
-  - Pages are sorted by their numeric value (not alphabetically)
-  - Pages without prefixes are sorted alphabetically after numbered pages
-- _Collisions_
-  - If multiple files have the same name after removing the prefix (e.g., `10_about.md` and `20_about.md`), the file with the higher number is used
-  - A warning is shown for collision conflicts
-
-Example:
-
-| File                          | Route              | Sidebar Title     | Order |
-| ----------------------------- | ------------------ | ----------------- | ----- |
-| `pages/10_getting-started.md` | `/getting-started` | `Getting Started` | 1st   |
-| `pages/20_configuration.md`   | `/configuration`   | `Configuration`   | 2nd   |
-| `pages/30_advanced.md`        | `/advanced`        | `Advanced`        | 3rd   |
-| `pages/api-reference.md`      | `/api-reference`   | `Api Reference`   | 4th   |
-| `pages/troubleshooting.md`    | `/troubleshooting` | `Troubleshooting` | 5th   |
-
-#### Markdown
-
-Markdown files (`.md`) are supported using [remark](https://remark.js.org/). This is the same underlying engine as [MDX](https://mdxjs.com/) thus you can rely on consistent behavior between your `.md` and `.mdx` files.
-
-Polen supports:
-
-- [CommonMark](https://commonmark.org/).
-- [GitHub Flavored Markdown](https://github.github.com/gfm/).
-
-In the future you will be able to extend Polen in your project with additional [Remark plugins](https://github.com/remarkjs/remark/blob/main/doc/plugins.md#list-of-plugins). Track this feature in [#64](https://github.com/the-guild-org/polen/issues/64).
+Find complete example projects in the [examples](./examples) directory:
 
-If you're new to Markdown, here are some great resources to get started:
+- `pokemon` - Fun Pokemon API documentation
+- `github` - GitHub GraphQL API (coming soon)
+- `minimal` - Minimal setup example
 
-- **[CommonMark Tutorial](https://commonmark.org/help/)** - Interactive 10-minute tutorial
-- **[Markdown Guide](https://www.markdownguide.org/)** - Comprehensive reference and cheat sheets
-- **[GitHub's Markdown Guide](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)** - Practical guide with examples
+## Why Polen?
 
-Syntax features available to you include:
+- **Zero Configuration** - Works out of the box with just a GraphQL schema
+- **Developer Focused** - Built specifically for GraphQL API documentation
+- **Modern Stack** - React, TypeScript, and Vite for fast builds
+- **Flexible** - Customize everything from branding to page structure
+- **Static or Server** - Deploy as static files or run as a Node.js server
 
-**Via CommonMark:**
+## Contributing
 
-- Headers, paragraphs, and line breaks
-- Bold, italic, and code formatting
-- Lists (ordered and unordered)
-- Links and images
-- Code blocks with syntax highlighting
-- Blockquotes
-- Horizontal rules
-
-**Via GitHub Flavored Markdown:**
-
-- Tables
-- Task lists
-- Strikethrough text
-- Autolinks
-
-#### MDX
-
-MDX begins where [Markdown](#markdown) ends. So everything stated there such as regarding supported Markdown flavours applies here too.
-
-MDX files (`.mdx`) allow you to use JSX/React components within your markdown content. This enables
-interactive documentation with live examples, custom components, and more.
-
-Example MDX page:
-
-```mdx
-# Interactive Documentation
-
-import { Button } from "@radix-ui/themes";
-
-This page demonstrates MDX features.
-
-<Button onClick={() => alert("Hello from MDX!")}>Click me!</Button>
-
-## Code Examples
-
-You can mix markdown with React components for powerful documentation:
-
-export const CodeExample = ({ language, code }) => (
-  <pre>
-    <code className={`language-${language}`}>{code}</code>
-  </pre>
-);
-
-<CodeExample
-  language="graphql"
-  code={`
-    query GetUser($id: ID!) {
-      user(id: $id) {
-        name
-        email
-      }
-    }
-  `}
-/>
-```
-
-### Build
-
-When you build you may choose between SSG and SSR. The default is SSG.
-
-#### SSG
-
-```sh
-npx polen build --type ssg
-```
-
-Deploy the contents of the `./build` directory on your favourite static site provider.
-
-#### SSR
-
-In the future Polen will have features that motivate using a server, but for now there is no particular benefit. Use `SSG` instead.
-
-#### Base Path Configuration
-
-Polen supports deploying to subdirectories through the `build.base` configuration option. This is useful for:
-
-- GitHub Pages project sites (e.g., `/my-project/`)
-- PR preview deployments (e.g., `/pr-123/`)
-- Hosting multiple Polen sites on one domain
-
-```ts
-// polen.config.ts
-import { Polen } from 'polen'
-
-export default Polen.defineConfig({
-  build: {
-    base: '/my-project/', // Must start and end with /
-  },
-})
-```
-
-When configured, Polen will output differently:
-
-- For SSG architecture:
-  - Generate static files that work in the subdirectory
-- For SSR architecture:
-  - A server that serves static assets from the correct path
-
-You can also set the base path via CLI:
-
-```bash
-npx polen build --base /my-project/
-npx polen dev --base /my-project/
-```
-
-The CLI flag takes precedence over the config file setting.
-
-#### Custom Logo
-
-You can provide a custom logo for your developer portal by placing a `logo.svg` file in your project's `public` directory:
-
-```
-public/
-  logo.svg
-```
-
-Polen will automatically use this logo in the navigation bar instead of the default Polen logo.
-
-### Package
-
-#### ESM
-
-Polen is an ESM only package. If you are using CJS, then you need
-[NodeJS version `>=22.0.0` to `require` it](https://nodejs.org/api/modules.html#loading-ecmascript-modules-using-require).
-
-#### Exports
-
-You can import a `Polen` namespace from `polen`. You can import its bare exports
-from `polen/polen`.
-
-```ts
-import { Polen } from 'polen'
-import { defineConfig } from 'polen/polen'
-
-console.log(Polen.defineConfig === defineConfig) // true
-```
-
-### Instant Schema Explorer
-
-Polen comes with a light-weight command to instantly view any GraphQL schema.
-
-Example:
-
-```sh
-npx polen open --name github
-```
-
-See docs for more details
-
-```sh
-npx polen open --help
-```
+We welcome contributions! See [DEVELOPMENT.md](./DEVELOPMENT.md) for:
 
-## Other
+- Development setup
+- Architecture overview
+- Testing guidelines
+- Contribution process
 
-### Changelog
+## Changelog
 
-Refer to
-[releases on this repo](https://github.com/the-guild-org/polen/releases).
+See [releases](https://github.com/the-guild-org/polen/releases) for a detailed changelog.
 
-### Development
+## License
 
-If you are working on Polen itself, then refer to
-[DEVELOPMENT.md](./DEVELOPMENT.md) for details about workflow, testing, etc.
+MIT © [The Guild](https://the-guild.dev)

package/build/api/api.d.ts

@@ -1,4 +1,5 @@
 export * from './builder/index.ts';
 export * from './config-resolver/index.ts';
 export * from './config/index.ts';
+export * from './static/index.ts';
 //# sourceMappingURL=api.d.ts.map

package/build/api/api.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"api.d.ts","sourceRoot":"","sources":["../../src/api/api.ts"],"names":[],"mappings":"AAAA,cAAc,oBAAoB,CAAA;AAClC,cAAc,4BAA4B,CAAA;AAC1C,cAAc,mBAAmB,CAAA"}
+{"version":3,"file":"api.d.ts","sourceRoot":"","sources":["../../src/api/api.ts"],"names":[],"mappings":"AAAA,cAAc,oBAAoB,CAAA;AAClC,cAAc,4BAA4B,CAAA;AAC1C,cAAc,mBAAmB,CAAA;AACjC,cAAc,mBAAmB,CAAA"}

package/build/api/api.js

@@ -1,4 +1,5 @@
 export * from "./builder/index.js";
 export * from "./config-resolver/index.js";
 export * from "./config/index.js";
+export * from "./static/index.js";
 //# sourceMappingURL=api.js.map

package/build/api/api.js.map

@@ -1 +1 @@
-{"version":3,"file":"api.js","sourceRoot":"","sources":["../../src/api/api.ts"],"names":[],"mappings":"AAAA,cAAc,oBAAoB,CAAA;AAClC,cAAc,4BAA4B,CAAA;AAC1C,cAAc,mBAAmB,CAAA"}
+{"version":3,"file":"api.js","sourceRoot":"","sources":["../../src/api/api.ts"],"names":[],"mappings":"AAAA,cAAc,oBAAoB,CAAA;AAClC,cAAc,4BAA4B,CAAA;AAC1C,cAAc,mBAAmB,CAAA;AACjC,cAAc,mBAAmB,CAAA"}

package/build/api/static/index.d.ts

@@ -0,0 +1,2 @@
+export * as Static from './static.ts';
+//# sourceMappingURL=index.d.ts.map

package/build/api/static/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/api/static/index.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,MAAM,MAAM,aAAa,CAAA"}

package/build/api/static/index.js

@@ -0,0 +1,2 @@
+export * as Static from "./static.js";
+//# sourceMappingURL=index.js.map

package/build/api/static/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/api/static/index.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,MAAM,MAAM,aAAa,CAAA"}

package/build/api/static/manifest.d.ts

@@ -0,0 +1,18 @@
+import { Resource } from '@wollybeard/kit';
+import { z } from 'zod/v4';
+export declare const PolenBuildManifestSchema: z.ZodObject<{
+    type: z.ZodEnum<{
+        ssr: "ssr";
+        ssg: "ssg";
+    }>;
+    version: z.ZodString;
+    basePath: z.ZodString;
+}, z.core.$loose>;
+export type PolenBuildManifest = z.infer<typeof PolenBuildManifestSchema>;
+export declare const buildManifest: Resource.Resource<"polen-build-manifest", {
+    [x: string]: unknown;
+    type: "ssr" | "ssg";
+    version: string;
+    basePath: string;
+}>;
+//# sourceMappingURL=manifest.d.ts.map

package/build/api/static/manifest.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"manifest.d.ts","sourceRoot":"","sources":["../../../src/api/static/manifest.ts"],"names":[],"mappings":"AAAA,OAAO,EAAS,QAAQ,EAAE,MAAM,iBAAiB,CAAA;AACjD,OAAO,EAAE,CAAC,EAAE,MAAM,QAAQ,CAAA;AAE1B,eAAO,MAAM,wBAAwB;;;;;;;iBAI3B,CAAA;AAEV,MAAM,MAAM,kBAAkB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,wBAAwB,CAAC,CAAA;AAEzE,eAAO,MAAM,aAAa;;;;;EAIxB,CAAA"}

package/build/api/static/manifest.js

@@ -0,0 +1,13 @@
+import { Codec, Resource } from '@wollybeard/kit';
+import { z } from 'zod/v4';
+export const PolenBuildManifestSchema = z.object({
+    type: z.enum(['ssg', 'ssr']),
+    version: z.string(),
+    basePath: z.string(),
+}).loose();
+export const buildManifest = Resource.create({
+    name: 'polen-build-manifest',
+    path: '.polen/build.json',
+    codec: Codec.fromZod(PolenBuildManifestSchema),
+});
+//# sourceMappingURL=manifest.js.map

package/build/api/static/manifest.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"manifest.js","sourceRoot":"","sources":["../../../src/api/static/manifest.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,KAAK,EAAE,QAAQ,EAAE,MAAM,iBAAiB,CAAA;AACjD,OAAO,EAAE,CAAC,EAAE,MAAM,QAAQ,CAAA;AAE1B,MAAM,CAAC,MAAM,wBAAwB,GAAG,CAAC,CAAC,MAAM,CAAC;IAC/C,IAAI,EAAE,CAAC,CAAC,IAAI,CAAC,CAAC,KAAK,EAAE,KAAK,CAAC,CAAC;IAC5B,OAAO,EAAE,CAAC,CAAC,MAAM,EAAE;IACnB,QAAQ,EAAE,CAAC,CAAC,MAAM,EAAE;CACrB,CAAC,CAAC,KAAK,EAAE,CAAA;AAIV,MAAM,CAAC,MAAM,aAAa,GAAG,QAAQ,CAAC,MAAM,CAAC;IAC3C,IAAI,EAAE,sBAAsB;IAC5B,IAAI,EAAE,mBAAmB;IACzB,KAAK,EAAE,KAAK,CAAC,OAAO,CAAC,wBAAwB,CAAC;CAC/C,CAAC,CAAA"}

package/build/api/static/rebase.d.ts

@@ -0,0 +1,14 @@
+export type RebasePlan = RebaseOverwritePlan | RebaseCopyPlan;
+export interface RebaseOverwritePlan {
+    changeMode: 'mutate';
+    newBasePath: string;
+    sourcePath: string;
+}
+export interface RebaseCopyPlan {
+    changeMode: 'copy';
+    newBasePath: string;
+    sourcePath: string;
+    targetPath: string;
+}
+export declare const rebase: (plan: RebasePlan) => Promise<void>;
+//# sourceMappingURL=rebase.d.ts.map

package/build/api/static/rebase.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"rebase.d.ts","sourceRoot":"","sources":["../../../src/api/static/rebase.ts"],"names":[],"mappings":"AAKA,MAAM,MAAM,UAAU,GAAG,mBAAmB,GAAG,cAAc,CAAA;AAE7D,MAAM,WAAW,mBAAmB;IAClC,UAAU,EAAE,QAAQ,CAAA;IACpB,WAAW,EAAE,MAAM,CAAA;IACnB,UAAU,EAAE,MAAM,CAAA;CACnB;AAED,MAAM,WAAW,cAAc;IAC7B,UAAU,EAAE,MAAM,CAAA;IAClB,WAAW,EAAE,MAAM,CAAA;IACnB,UAAU,EAAE,MAAM,CAAA;IAClB,UAAU,EAAE,MAAM,CAAA;CACnB;AAED,eAAO,MAAM,MAAM,GAAU,MAAM,UAAU,KAAG,OAAO,CAAC,IAAI,CAiC3D,CAAA"}

package/build/api/static/rebase.js

@@ -0,0 +1,110 @@
+import { TinyGlobby } from '#dep/tiny-globby/index';
+import { Fs, Path } from '@wollybeard/kit';
+import { Err } from '@wollybeard/kit';
+import { buildManifest } from "./manifest.js";
+export const rebase = async (plan) => {
+    // 1. Validate source is a Polen build
+    const manifestResult = await buildManifest.read(plan.sourcePath);
+    if (Err.is(manifestResult)) {
+        throw new Error(`Polen build manifest not found at: ${Path.join(plan.sourcePath, '.polen', 'build.json')}`);
+    }
+    const manifest = manifestResult;
+    // 2. Validate newBasePath is valid URL path
+    if (!isValidUrlPath(plan.newBasePath)) {
+        throw new Error(`Invalid base path: ${plan.newBasePath}`);
+    }
+    // 3. Handle copy vs mutate
+    let workingPath;
+    if (plan.changeMode === 'copy') {
+        if (await Fs.exists(plan.targetPath)) {
+            const isEmpty = await Fs.isEmptyDir(plan.targetPath);
+            if (!isEmpty) {
+                throw new Error(`Target path already exists and is not empty: ${plan.targetPath}`);
+            }
+        }
+        await Fs.copyDir({ from: plan.sourcePath, to: plan.targetPath });
+        workingPath = plan.targetPath;
+    }
+    else {
+        workingPath = plan.sourcePath;
+    }
+    // 4. Update HTML files with new base path
+    await updateHtmlFiles(workingPath, manifest.basePath, plan.newBasePath);
+    // 5. Update manifest
+    await updateManifest(workingPath, { basePath: plan.newBasePath });
+};
+//
+//
+//
+//
+// ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ • Local Helpers
+//
+//
+// TODO: this is very generic, factor out to kit-temp
+const isValidUrlPath = (path) => {
+    // URL path should start with / and not contain invalid characters
+    if (!path.startsWith('/'))
+        return false;
+    if (!path.endsWith('/'))
+        return false;
+    // Basic validation - no spaces, proper URL characters
+    const urlPathRegex = /^\/[a-zA-Z0-9\-._~:/?#[\]@!$&'()*+,;=%]*\/$/;
+    return urlPathRegex.test(path);
+};
+const updateHtmlFiles = async (buildPath, oldBasePath, newBasePath) => {
+    // Find all HTML files recursively
+    const htmlFiles = await findHtmlFiles(buildPath);
+    for (const htmlFile of htmlFiles) {
+        await updateHtmlFile(htmlFile, oldBasePath, newBasePath);
+    }
+};
+const findHtmlFiles = async (dir) => {
+    return await TinyGlobby.glob('**/*.html', {
+        absolute: true,
+        cwd: dir,
+        onlyFiles: true,
+    });
+};
+const updateHtmlFile = async (filePath, oldBasePath, newBasePath) => {
+    const content = await Fs.read(filePath);
+    if (content === null) {
+        throw new Error(`Could not read HTML file: ${filePath}`);
+    }
+    // Simple regex-based approach to update base tag
+    // Look for existing base tag first
+    const baseTagRegex = /<base\s+href\s*=\s*["']([^"']*)["'][^>]*>/i;
+    let updatedContent;
+    if (baseTagRegex.test(content)) {
+        // Update existing base tag
+        updatedContent = content.replace(baseTagRegex, `<base href="${newBasePath}">`);
+    }
+    else {
+        // Insert new base tag in head
+        const headRegex = /<head[^>]*>/i;
+        const headMatch = content.match(headRegex);
+        if (headMatch) {
+            const insertPosition = headMatch.index + headMatch[0].length;
+            updatedContent = content.slice(0, insertPosition)
+                + `\n  <base href="${newBasePath}">`
+                + content.slice(insertPosition);
+        }
+        else {
+            throw new Error(`Could not find <head> tag in HTML file: ${filePath}`);
+        }
+    }
+    await Fs.write({ path: filePath, content: updatedContent });
+};
+const updateManifest = async (buildPath, updates) => {
+    const manifestPath = Path.join(buildPath, '.polen', 'build.json');
+    const manifestResult = await buildManifest.read(buildPath);
+    if (Err.is(manifestResult)) {
+        throw new Error(`Polen build manifest not found at: ${manifestPath}`);
+    }
+    const currentManifest = manifestResult;
+    const updatedManifest = { ...currentManifest, ...updates };
+    await Fs.write({
+        path: manifestPath,
+        content: JSON.stringify(updatedManifest, null, 2),
+    });
+};
+//# sourceMappingURL=rebase.js.map