fix: restore WebAPI naming

Author: jderochervlk

README.md

@@ -20,11 +20,19 @@ and add `@rescript/webapi` to your `rescript.json`:
     "@rescript/webapi"
   ],
   "bsc-flags": [
-    "-open WebApi.DOM.Global"
+    "-open WebAPI.Global"
   ]
 }
 ```
 
+## Usage
+
+```rescript
+let location = window.location
+let href = location.href
+location->WebAPI.Location.reload
+```
+
 ## Documentation
 
 More information can be found on https://rescript-lang.github.io/experimental-rescript-webapi/

docs/content/docs/contributing/api-modelling.mdx

@@ -88,8 +88,8 @@ mutable fillStyle: fillStyle
 When we wish to read and write the `fillStyle` property, we can use a helper module to lift the type to an actual ReScript variant:
 
 export const fillStyleModule = `
-open WebApi.Canvas
-open WebApi.DOM
+open WebAPI.Canvas
+open WebAPI.DOM
 
 external fromString: string => fillStyle = "%identity"
 external fromCanvasGradient: canvasGradient => fillStyle = "%identity"

docs/content/docs/index.mdx

@@ -2,7 +2,7 @@
 title: Getting started
 description: Learn more about @rescript/webapi.
 hero:
-  title: "ReScript WebApi"
+  title: "ReScript WebAPI"
   tagline: ReScript bindings for everything you need in the browser.
   actions:
     - text: Let's go!
@@ -42,7 +42,7 @@ export const rescriptJson = `
     "@rescript/webapi"
   ],
   "bsc-flags": [
-    "-open WebApi.DOM.Global"
+    "-open WebAPI.Global"
   ]
 }
 `;
@@ -54,14 +54,14 @@ export const rescriptJson = `
 After installing the package , you can use bindings for the various Web APIs as defined in [MDN](https://developer.mozilla.org/en-US/docs/Web/API).
 
 export const rescriptSample = `
-// Note that this only works when you added the \`-open WebApi.DOM.Global\` bsc flag.
+// Note that this only works when you added the \`-open WebAPI.Global\` bsc flag.
 let location = window.location
 
 // Access properties using \`.\`
 let href = location.href
 
 // Invoke methods using the \`->TypeModule.method\`
-location->WebApi.DOM.Location.reload
+location->WebAPI.Location.reload
 `;
 
 export const compiledSample = `

docs/content/docs/philosophy.mdx

@@ -16,12 +16,13 @@ The bindings are generated from the [MDN Web API documentation](https://develope
 
 In other words, if you are searching for a specific JavaScript binding, begin your journey at the [MDN Web API documentation](https://developer.mozilla.org/en-US/docs/Web/API) and determine which module contains your sample. Ensure that the module is available in the bindings by checking the specific API. Please [open an issue](https://github.com/rescript-lang/experimental-rescript-webapi/issues/new/choose) if you require an API that is not yet present.
 
-Each feature is grouped under a `WebApi.<Feature>` module so related interfaces and helper modules stay together without relying on flat package-wide names.
+The bindings are exposed under the `WebAPI` namespace, with feature entry modules such as `WebAPI.DOM` available when you want to scope imports more narrowly.
 
 ```ReScript
-open WebApi.DOM.Global
+open WebAPI.Global
+// or WebAPI.DOM
 
-let myElement: WebApi.DOM.Types.element = document->WebApi.DOM.Document.createElement("div")
+let myElement: WebAPI.Element.t = document->WebAPI.Document.createElement("div")
 ```
 
 ## Interfaces
@@ -43,10 +44,11 @@ JavaScript supports function overloads, where a function can have multiple signa
 In some cases, type conversion will be required. Subtypes can safely be cast to their base type using conversion helpers within their module.
 
 ```ReScript
-open WebApi.DOM.Global
+open WebAPI.Global
+// or WebAPI.DOM
 
-let element: WebApi.DOM.Types.element = document->WebApi.DOM.Document.createElement("div")
-let node: WebApi.DOM.Types.node = element->WebApi.DOM.Element.asNode
+let element: WebAPI.Element.t = document->WebAPI.Document.createElement("div")
+let node: WebAPI.Node.t = element->WebAPI.Element.asNode
 ```
 
 Any other conversions should be treated as unsafe casts and used with caution, because the type system cannot guarantee they are valid at runtime.

docs/llm.js

@@ -108,10 +108,10 @@ function moduleNameForFile(relativePath) {
   const leafName = path.basename(fileName, ".res");
 
   if (leafName === spec.publicModule) {
-    return `WebApi.${spec.publicModule}`;
+    return `WebAPI.${spec.publicModule}`;
   }
 
-  return `WebApi.${spec.publicModule}.${publicNameForLeafModule(leafName, spec.internalPrefix)}`;
+  return `WebAPI.${spec.publicModule}.${publicNameForLeafModule(leafName, spec.internalPrefix)}`;
 }
 
 const pattern = "../src/*/**/*.res";
@@ -126,9 +126,9 @@ const packageJson = await fs.readFile(path.join(import.meta.dirname, "../package
 let version = JSON.parse(packageJson).version;
 const sha = await execAsync("git rev-parse --short HEAD").then(({ stdout }) => stdout.trim());
 const fullVersion = `${version}-experimental-${sha}`;
-const header = `Experimental ReScript WebApi Documentation ${fullVersion}
+const header = `Experimental ReScript WebAPI Documentation ${fullVersion}
 
-This is the API documentation for the experimental WebApi module version ${fullVersion}.
+This is the API documentation for the experimental WebAPI module version ${fullVersion}.
 More information can be found on https://rescript-lang.github.io/experimental-rescript-webapi/
 
 `;

docs/superpowers/specs/2026-04-22-unmonorepo-webapi-design.md

@@ -1,4 +1,4 @@
-# Unmonorepo WebApi Design
+# Unmonorepo WebAPI Design
 
 **Date:** 2026-04-22
 **Status:** Approved in conversation, written for review before implementation
@@ -7,15 +7,15 @@
 
 The repository was split into npm workspaces so each Web API area could build and publish independently from `packages/*`. The ReScript compiler now supports feature-gated source directories and feature-gated dependencies, so the package split is no longer required to support partial builds.
 
-The new target is a single published npm package, `@rescript/webapi`, with a unified internal build and an external API that still preserves feature-level boundaries such as `WebApi.DOM`, `WebApi.Fetch`, and `WebApi.Base`.
+The new target is a single published npm package, `@rescript/webapi`, with a unified internal build and an external API that still preserves feature-level boundaries such as `WebAPI.DOM`, `WebAPI.Fetch`, and `WebAPI.Base`.
 
 ## Goals
 
 - Remove the monorepo/workspace package split.
 - Move all feature sources from `packages/<Pkg>/src` to `src/<Pkg>`.
 - Delete every subpackage `package.json` and `rescript.json`.
 - Make the root `rescript.json` the single source of truth for sources, features, and ReScript dependencies.
-- Preserve the logical public API boundaries as `WebApi.<Feature>`.
+- Preserve the logical public API boundaries as `WebAPI.<Feature>`.
 - Keep internal helper modules private through the new `public` source setting.
 - Publish one npm package: `@rescript/webapi`.
 - Let internal builds and downstream consumers compile only the features they need.
@@ -62,13 +62,13 @@ Each former package source directory is listed as its own source entry. Example
     {
       "dir": "src/DOM",
       "subdirs": true,
-      "feature": "WebApi.DOM",
+      "feature": "WebAPI.DOM",
       "public": ["DOM"]
     },
     {
       "dir": "src/Fetch",
       "subdirs": true,
-      "feature": "WebApi.Fetch",
+      "feature": "WebAPI.Fetch",
       "public": ["Fetch"]
     },
     {
@@ -83,7 +83,7 @@ Each former package source directory is listed as its own source entry. Example
 Rules:
 
 - Every former package gets one root source entry.
-- The `feature` value matches the public module name, for example `"WebApi.DOM"` and `"WebApi.Fetch"`.
+- The `feature` value matches the public module name, for example `"WebAPI.DOM"` and `"WebAPI.Fetch"`.
 - The `public` list exposes only the feature entry module for that source directory.
 - Helper modules such as `DomTypes` and `DomGlobal` stay internal because they are not listed in `public`.
 - `tests` remains a dev-only source.
@@ -102,7 +102,7 @@ Example:
 {
   "dependencies": [
     "@plain/dep",
-    { "name": "@other/heavy", "features": ["WebApi.WebCrypto"] }
+    { "name": "@other/heavy", "features": ["WebAPI.WebCrypto"] }
   ]
 }
 ```
@@ -117,10 +117,10 @@ Migration rule:
 
 The public API remains feature-oriented:
 
-- `WebApi.Base`
-- `WebApi.DOM`
-- `WebApi.Fetch`
-- `WebApi.WebCrypto`
+- `WebAPI.Base`
+- `WebAPI.DOM`
+- `WebAPI.Fetch`
+- `WebAPI.WebCrypto`
 - and the rest of the former package surfaces
 
 The unified build must not expose raw internal file modules as first-class public API. Consumers should interact with a curated surface through the feature entry modules only.
@@ -240,7 +240,7 @@ The most important regression risks are:
 
 - Use a single package instead of npm workspaces.
 - Preserve feature boundaries in the external API.
-- Use `WebApi.*` spelling, not `WebAPI.*`.
-- Map feature names to public module names such as `"WebApi.DOM"`.
+- Use `WebAPI.*` spelling, not `WebApi.*`.
+- Map feature names to public module names such as `"WebAPI.DOM"`.
 - Rename generic internal modules to feature-qualified names.
 - Use source-level `public` settings so only the feature entry module is exposed.