reset alpha to latest code

DEVELOPMENT.md

@@ -15,7 +15,7 @@ git submodule update --recursive --init
 Software that needs installing to work with this library:
 
 - Rust
-  ```
+  ```sh
   curl -so rust.sh https://sh.rustup.rs && sh rust.sh -y
   restart shell or run source $HOME/.cargo/env
   ```

create-wit-bindings.sh

@@ -0,0 +1,3 @@
+#!/usr/bin/env bash
+
+~/.cargo/bin/wit-bindgen c --out-dir runtime/fastedge/host-api/bindings --world bindings runtime/fastedge/host-api/wit

docs/examples/variables-and-secrets.js

@@ -0,0 +1,13 @@
+import { getEnv } from 'fastedge::env';
+import { getSecret } from 'fastedge::secret';
+
+async function eventHandler(event) {
+  const username = getEnv('USERNAME');
+  const password = getSecret('PASSWORD');
+
+  return new Response(`Username: ${username}, Password: ${password}`);
+}
+
+addEventListener('fetch', (event) => {
+  event.respondWith(eventHandler(event));
+});

docs/src/content/docs/examples/main-examples.mdx

@@ -7,14 +7,13 @@ import { LinkCard, CardGrid } from '@astrojs/starlight/components';
 
 This is a brief list of examples, demonstrating the basic usage of FastEdge compute.
 
-More examples will be added to the
+More examples will be added to the examples-repo as we build out more functionality.
 
-<a href='https://github.com/G-Core/FastEdge-sdk-js/tree/main/docs/examples' target='_blank'>
-  repo
+<a href='https://github.com/G-Core/FastEdge-examples/tree/main/javascript' target='_blank'>
+  examples-repo
 </a>
-as we build out more functionality.
 
-## Some Examples
+## Some Basic Examples
 
 <CardGrid>
   <LinkCard title='Basic example' href='/FastEdge-sdk-js/examples/basic/' />
@@ -27,4 +26,8 @@ as we build out more functionality.
     title='Header manipulation with environment variables'
     href='/FastEdge-sdk-js/examples/headers/'
   />
+  <LinkCard
+    title='Environment variables and secrets'
+    href='/FastEdge-sdk-js/examples/variables-and-secrets/'
+  />
 </CardGrid>

docs/src/content/docs/examples/variables-and-secrets.mdx

@@ -0,0 +1,12 @@
+---
+title: Environment Variables and Secrets
+description: An example using environment variables and secrets.
+prev:
+  link: /FastEdge-sdk-js/examples/main-examples/
+  label: Back to examples
+---
+
+import { Code } from '@astrojs/starlight/components';
+import importedCode from '/examples/variables-and-secrets.js?raw';
+
+<Code code={importedCode} lang='js' title='docs/examples/variables-and-secrets.js' />

docs/src/content/docs/reference/fastedge::secret/getSecret.md

@@ -0,0 +1,38 @@
+---
+title: getSecret
+description: How to use FastEdge secret variables.
+---
+
+### Secret Variables
+
+To access secret variables, set during deployment on the FastEdge network.
+
+```js
+import { getSecret } from 'fastedge::secret';
+
+async function eventHandler(event) {
+  const secretToken = getSecret('MY_SECRET_TOKEN');
+  return new Response({ secretToken });
+}
+
+addEventListener('fetch', (event) => {
+  event.respondWith(eventHandler(event));
+});
+```
+
+```js title="SYNTAX"
+getSecret(secretName);
+```
+
+##### Parameters
+
+- `secretName` (required)
+
+  A string containing the name of the key you want to retrieve the value of.
+
+##### Return Value
+
+A string containing the value of the key. If the key does not exist, null is returned.
+
+**Note**: If the secret contains multiple `secret_slots` you will always receive the MAX `slot`
+value.

docs/src/content/docs/reference/fastedge::secret/getSecretEffectiveAt.md

@@ -0,0 +1,117 @@
+---
+title: getSecretEffectiveAt
+description: How to use FastEdge secret variables.
+---
+
+### Secret Variables
+
+To access slot specific secret variables, set during deployment on the FastEdge network.
+
+```js
+import { getSecretEffectiveAt } from 'fastedge::secret';
+
+async function eventHandler(event) {
+  const secretToken = getSecretEffectiveAt('MY_SECRET_TOKEN', 1);
+  return new Response({ secretToken });
+}
+
+addEventListener('fetch', (event) => {
+  event.respondWith(eventHandler(event));
+});
+```
+
+```js title="SYNTAX"
+getSecretEffectiveAt(secretName, 0);
+```
+
+##### Parameters
+
+- `secretName` (required)
+
+  A string containing the name of the key you want to retrieve the value of.
+
+- `effectiveAt` (required)
+
+  A number representing the slot you wish to access.
+
+##### Return Value
+
+A string containing the value of the key. If the key does not exist, null is returned.
+
+### Slots and secret rollover
+
+Using `getSecretEffectiveAt()` to access different slots within a given secret and how to use slots.
+
+The concept of slots allows you to manage secret rollover within your own applications in many
+different ways.
+
+##### Example 1 (Slots as indices)
+
+Validating a token against a specific version of a secret.
+
+Having created a secret:
+
+```json
+{
+  "secret": {
+    "comment": "The password to validate the token has been signed with",
+    "id": 168,
+    "name": "token-secret",
+    "secret_slots": [
+      {
+        "slot": 0,
+        "value": "original_password"
+      },
+      {
+        "slot": 5,
+        "value": "updated_password"
+      }
+    ]
+  }
+}
+```
+
+It would now be easy enough to also provide the `slot` value within the tokens claims as to which
+password it should validate against. This would allow you to slowly rollover from one password to
+another and keep all users able to refresh their tokens without issues, as each users token also
+carries the data to know which password was still in use when it was issued.
+
+It always returns `effectiveAt >= secret_slots.slot`
+
+So a request to:
+
+- `getSecretEffectiveAt("token-secret", 0)` would return `original_password`
+- `getSecretEffectiveAt("token-secret", 3)` would return `original_password`
+- `getSecretEffectiveAt("token-secret", 5)` would return `updated_password`
+- `getSecretEffectiveAt("token-secret", 7)` would return `updated_password`
+
+This `>=` logic makes it very easy to implement the following example.
+
+##### Example 2 (Slots as timestamps)
+
+Validating a token against a specific version of a secret using timestamps:
+
+```json
+{
+  "secret": {
+    "comment": "The password to validate the token has been signed with",
+    "id": 168,
+    "name": "token-secret",
+    "secret_slots": [
+      {
+        "slot": 0,
+        "value": "original_password"
+      },
+      {
+        "slot": 1741790697, // Wed Mar 12 2025 14:44:57
+        "value": "new_password"
+      }
+    ]
+  }
+}
+```
+
+As you can see any token being validated with an `iat` claim time before 1741790697 would use the
+`original_password` and any token after this time would start to use the `new_password`
+
+This is as simple as using `getSecretEffectiveAt("token-secret", claims.iat)`

docs/src/content/docs/reference/headers.md

@@ -0,0 +1,28 @@
+---
+title: Headers
+description: Response / Request Headers.
+---
+
+TThe Headers() constructor creates a new Headers object.
+
+```js
+new Headers();
+new Headers(init);
+```
+
+##### Parameters
+
+- `init` (optional)
+
+  An object containing any HTTP headers you want to prepopulate your `Headers` object with. This can
+  be a simple object literal with String values, an array of name-value pairs, where each pair is a
+  2-element string array; or an existing Headers object. In the last case, the new Headers object
+  copies its data from the existing Headers object.
+
+:::note[INFO]
+
+Request and Response Headers are immutable. This means, if you need to modify Request headers for
+downstream fetch requests, or modify Response headers prior to returning a Response. You will need
+to create a `new Headers()` object.
+
+:::

docs/src/content/docs/reference/overview.md

@@ -18,7 +18,7 @@ This Javascript SDK is not yet fully fledged, but it is growing quickly.
 As we test and write more functionality we will endeavour to keep adding to this reference guide.
 
 At present there is all the basic javascript functionality provided by
-<a href="https://spidermonkey.dev/" target="_blank">SpiderMonkey</a>. This is the engine our
-Javascript product is embedded with.
+<a href="https://github.com/bytecodealliance/StarlingMonkey" target="_blank">StarlingMonkey</a>.
+This is the engine our Javascript product is embedded with.
 
 We will continue to add more, so please check back often!

docs/src/content/docs/reference/request.md

@@ -0,0 +1,37 @@
+---
+title: Request
+description: Request object definition.
+---
+
+The Request() constructor creates a new Request object.
+
+```js
+new Request(input);
+new Request(input, options);
+```
+
+##### Parameters
+
+- `input`
+
+  Defines the resource you wish to fetch. Can be one of the following:
+
+  - A string containing the resource you wish to fetch.
+  - `Request` object, effectively creating a copy.
+
+- `options` (optional)
+
+  An options object containing any other data to associate with the Request
+
+  - method: (optional)
+
+    e.g. `GET`, `POST`, `PUT`, `DELETE`. (Default is `GET`)
+
+  - headers: (optional)
+
+    An object: containing either a `Headers` object or object literal with `String` key/value pairs.
+
+  - body: (optional)
+
+    Any body that you want to add to your request: this can be an `ArrayBuffer`, a `TypedArray`, a
+    `DataView`, a `URLSearchParams`, string object or literal, or a `ReadableStream` object.

docs/src/content/docs/reference/response.md

@@ -15,7 +15,16 @@ new Response(body, options);
 
 - `body` (optional)
 
-  A string defining the body of a response. This can be `null` that is the default.
+  A object defining the body of a response. This can be `null` (which is the default) or one of the
+  following:
+
+  - ArrayBuffer
+  - TypedArray
+  - DataView
+  - ReadableStream
+  - URLSearchParams
+  - String
+  - string literal
 
 - `options` (optional)
 
@@ -25,6 +34,10 @@ new Response(body, options);
 
     A number representing the http status code. e.g. `200`
 
+  - statusText: (optional)
+
+    The status message associated with the status code, e.g. `OK`.
+
   - headers: (optional)
 
     An object: containing either a `Headers` object or object literal with `String` key/value pairs.

package.json

@@ -38,8 +38,7 @@
     "build:monkey:prod": "./runtime/fastedge/build.sh",
     "build:libs": "node esbuild/fastedge-libs.js",
     "build:types": "tsc -p ./src/static-server/tsconfig.json",
-    "FIX:build:wasm": "node build-examples-config.js",
-    "FIX:generate:wit-world": "make -j8 -C fastedge-runtime/cbindings generate-wit-bindgen",
+    "generate:wit-world": "./create-wit-bindings.sh",
     "lint": "npx eslint -c ./config/eslint/repo/.eslintrc.cjs .",
     "semantic-release": "semantic-release",
     "test:solo": "NODE_ENV=test jest -c ./config/jest/jest.config.js --",

runtime/fastedge/build.sh

@@ -26,5 +26,5 @@ HOST_API=$(realpath host-api) cmake -B $BUILD_PATH -DCMAKE_BUILD_TYPE=$BUILD_TYP
 # cmake --build $BUILD_PATH --parallel 16
 cmake --build $BUILD_PATH --parallel 8
 # Copy the built WebAssembly module to the parent directory
-mv $BUILD_PATH/starling.wasm/starling.wasm ../../lib/fastedge-runtime.wasm
-mv $BUILD_PATH/starling.wasm/preview1-adapter.wasm ../../lib/preview1-adapter.wasm
+mv $BUILD_PATH/starling-raw.wasm/starling-raw.wasm ../../lib/fastedge-runtime.wasm
+mv $BUILD_PATH/starling-raw.wasm/preview1-adapter.wasm ../../lib/preview1-adapter.wasm