@stone-js/starters 0.8.13 → 0.8.14

package/basic-react-declarative/package.json

@@ -20,16 +20,17 @@
   "dependencies": {
     "react": "^19.0.0",
     "react-dom": "^19.0.0",
-    "@stone-js/core": "^0.8.13",
-    "@stone-js/use-react": "^0.8.13",
-    "@stone-js/browser-adapter": "^0.8.13"
+    "@stone-js/core": "^0.8.14",
+    "@stone-js/use-react": "^0.8.14",
+    "@stone-js/browser-adapter": "^0.8.14"
   },
   "devDependencies": {
     "@babel/plugin-proposal-decorators": "^7.25.9",
     "@babel/preset-env": "^7.26.9",
     "@babel/preset-typescript": "^7.27.0",
-    "@stone-js/cli": "^0.8.13",
-    "@stone-js/testing": "^0.8.13",
+    "@stone-js/browser-core": "^0.8.14",
+    "@stone-js/cli": "^0.8.14",
+    "@stone-js/testing": "^0.8.14",
     "@types/node": "^24.0.7",
     "@types/react": "^19.0.7",
     "@types/react-dom": "^19.0.3",

package/basic-react-declarative/tests/Application.spec.ts

@@ -1,4 +1,5 @@
-import { createTestApp, makeIncomingHttpEvent } from '@stone-js/testing'
+import { createTestApp } from '@stone-js/testing'
+import { makeIncomingBrowserEvent } from '@stone-js/testing/browser'
 
 /**
  * The whole application, booted in memory and asked a real question.
@@ -12,7 +13,7 @@ describe('Pages', () => {
   it('renders the home page, data included', async () => {
     const app = await createTestApp()
 
-    const response = await app.send(makeIncomingHttpEvent({ method: 'GET', url: '/?name=Ada' }))
+    const response = await app.send(makeIncomingBrowserEvent({ url: '/?name=Ada' }))
 
     expect(response.statusCode).toBe(200)
     // A page is a handler, so a rendered page is a response whose body is HTML. Query that HTML with
@@ -23,7 +24,7 @@ describe('Pages', () => {
   it('renders without a name', async () => {
     const app = await createTestApp()
 
-    const response = await app.send(makeIncomingHttpEvent({ method: 'GET', url: '/' }))
+    const response = await app.send(makeIncomingBrowserEvent({ url: '/' }))
 
     expect(response.statusCode).toBe(200)
   })

package/basic-react-imperative/package.json

@@ -20,16 +20,17 @@
   "dependencies": {
     "react": "^19.0.0",
     "react-dom": "^19.0.0",
-    "@stone-js/core": "^0.8.13",
-    "@stone-js/use-react": "^0.8.13",
-    "@stone-js/browser-adapter": "^0.8.13"
+    "@stone-js/core": "^0.8.14",
+    "@stone-js/use-react": "^0.8.14",
+    "@stone-js/browser-adapter": "^0.8.14"
   },
   "devDependencies": {
     "@babel/plugin-proposal-decorators": "^7.25.9",
     "@babel/preset-env": "^7.26.9",
     "@babel/preset-typescript": "^7.27.0",
-    "@stone-js/cli": "^0.8.13",
-    "@stone-js/testing": "^0.8.13",
+    "@stone-js/browser-core": "^0.8.14",
+    "@stone-js/cli": "^0.8.14",
+    "@stone-js/testing": "^0.8.14",
     "@types/node": "^24.0.7",
     "@types/react": "^19.0.7",
     "@types/react-dom": "^19.0.3",

package/basic-react-imperative/tests/Application.spec.ts

@@ -1,4 +1,5 @@
-import { createTestApp, makeIncomingHttpEvent } from '@stone-js/testing'
+import { createTestApp } from '@stone-js/testing'
+import { makeIncomingBrowserEvent } from '@stone-js/testing/browser'
 
 /**
  * The whole application, booted in memory and asked a real question.
@@ -12,7 +13,7 @@ describe('Pages', () => {
   it('renders the home page, data included', async () => {
     const app = await createTestApp()
 
-    const response = await app.send(makeIncomingHttpEvent({ method: 'GET', url: '/?name=Ada' }))
+    const response = await app.send(makeIncomingBrowserEvent({ url: '/?name=Ada' }))
 
     expect(response.statusCode).toBe(200)
     // A page is a handler, so a rendered page is a response whose body is HTML. Query that HTML with
@@ -23,7 +24,7 @@ describe('Pages', () => {
   it('renders without a name', async () => {
     const app = await createTestApp()
 
-    const response = await app.send(makeIncomingHttpEvent({ method: 'GET', url: '/' }))
+    const response = await app.send(makeIncomingBrowserEvent({ url: '/' }))
 
     expect(response.statusCode).toBe(200)
   })

package/basic-react-native-declarative/README.md

@@ -106,36 +106,29 @@ the page that owns `/`, with `name` readable through `event.get('name')`. Change
 
 `App.tsx` renders `StoneNativeApp`, which shows the screen on top of the stack. That is the floor,
 not the ceiling: it is what makes the first run work with nothing installed. The platform's
-transitions, the swipe-back gesture, and a screen keeping its own state while another covers it are
-things only a native navigator gives you.
+transitions, the swipe-back gesture, the hardware back button, and a screen keeping its own state
+while another covers it are things only a native navigator gives you.
 
-The stack is public state, so a navigator drives itself from it:
+Two commands and one import away:
 
-```tsx
-import { useScreens } from '@stone-js/use-react-native'
-import { NavigationContainer } from '@react-navigation/native'
-import { createNativeStackNavigator } from '@react-navigation/native-stack'
+```sh
+npx expo install @react-navigation/native @react-navigation/native-stack \
+  react-native-screens react-native-safe-area-context
+```
 
-const Stack = createNativeStackNavigator()
+```tsx
+// App.tsx
+import { StoneNativeStack } from '@stone-js/use-react-native/navigation'
 
 export default function App () {
-  const screens = useScreens()
-
-  return (
-    <NavigationContainer>
-      <Stack.Navigator>
-        {screens.map((screen) => (
-          <Stack.Screen key={screen.key} name={screen.key} options={{ title: screen.title }}>
-            {() => screen.element}
-          </Stack.Screen>
-        ))}
-      </Stack.Navigator>
-    </NavigationContainer>
-  )
+  return <StoneNativeStack screenOptions={{ headerShown: true }} />
 }
 ```
 
-Nothing about your pages changes.
+Nothing about your screens changes. Each becomes a native one, keyed so the navigator keeps its
+state, and titled from the page's `head`. See the
+[renderer's README](https://www.npmjs.com/package/@stone-js/use-react-native) for how the two stacks
+stay in agreement, and for writing your own navigator instead.
 
 ## The imperative twin
 

package/basic-react-native-declarative/package.json

@@ -21,11 +21,11 @@
     "test:cvg": "npm run test -- --coverage"
   },
   "dependencies": {
-    "@stone-js/browser-core": "^0.8.13",
-    "@stone-js/core": "^0.8.13",
-    "@stone-js/react-native-adapter": "^0.8.13",
-    "@stone-js/router": "^0.8.13",
-    "@stone-js/use-react-native": "^0.8.13",
+    "@stone-js/browser-core": "^0.8.14",
+    "@stone-js/core": "^0.8.14",
+    "@stone-js/react-native-adapter": "^0.8.14",
+    "@stone-js/router": "^0.8.14",
+    "@stone-js/use-react-native": "^0.8.14",
     "expo": "~57.0.14",
     "expo-status-bar": "~57.0.1",
     "fast-text-encoding": "^1.0.6",
@@ -35,8 +35,8 @@
   },
   "devDependencies": {
     "@babel/plugin-proposal-decorators": "^7.28.0",
-    "@stone-js/cli": "^0.8.13",
-    "@stone-js/testing": "^0.8.13",
+    "@stone-js/cli": "^0.8.14",
+    "@stone-js/testing": "^0.8.14",
     "@types/react": "~19.2.2",
     "@vitest/coverage-v8": "^3.0.9",
     "babel-preset-expo": "^57.0.7",

package/basic-react-native-declarative/tests/HomeScreen.spec.ts

@@ -0,0 +1,36 @@
+import { createTestApp } from '@stone-js/testing'
+import { makeIncomingBrowserEvent } from '@stone-js/testing/browser'
+import { REACT_NATIVE_PLATFORM } from '@stone-js/react-native-adapter'
+
+/**
+ * The whole application, booted in memory and asked a real question.
+ *
+ * Nothing is mocked and nothing is listed: `createTestApp()` discovers `app/**`, and the event goes
+ * through the same kernel a phone runs. This is the same test the web starters ship, with one
+ * difference: the platform is named, and the event is the one a native application receives, which
+ * is how a deep link arrives.
+ *
+ * What it substitutes is the adapter, and that is the architecture rather than a concession to
+ * testing: the domain is written once and the context is chosen at run time, so under Node the
+ * context is a test adapter instead of React Native.
+ */
+describe('HomeScreen', () => {
+  it('resolves the home screen, data included', async () => {
+    const app = await createTestApp({ platform: REACT_NATIVE_PLATFORM })
+
+    const response = await app.send(makeIncomingBrowserEvent({ url: 'stone://app/?name=Ada' }))
+
+    expect(response.statusCode).toBe(200)
+    // The head is what a navigator shows in its header, and it proves the loader ran with the deep
+    // link's parameter.
+    expect((response.content as any).head.title).toBe('Ada · Welcome to Stone.js')
+  })
+
+  it('resolves without a name', async () => {
+    const app = await createTestApp({ platform: REACT_NATIVE_PLATFORM })
+
+    const response = await app.send(makeIncomingBrowserEvent({ url: 'stone://app/' }))
+
+    expect(response.statusCode).toBe(200)
+  })
+})

package/basic-react-native-declarative/tests/{Application.spec.ts → navigation.spec.ts}

@@ -5,18 +5,21 @@ import { ScreenStack } from '@stone-js/use-react-native'
 import { NavigationSource } from '@stone-js/react-native-adapter'
 
 /**
- * The whole application, booted under Node and asked real questions.
+ * Navigation, with the real adapter this time.
  *
- * Nothing is mocked. The kernel, the router, the adapter and the renderer are the ones a phone
- * runs; what a device adds is a screen to draw on, and this asserts what the framework resolved
- * before drawing. Two things are supplied rather than discovered, both through documented
- * configuration: the navigation source, so the test can send a deep link, and the screen stack, so
- * it can read what landed on it.
+ * `HomeScreen.spec.ts` asks what a route resolves to, which is the same question on every platform
+ * and needs no adapter. This asks the native question instead: what lands on the navigation stack,
+ * and in what order. So nothing is substituted here. The kernel, the router, the React Native adapter
+ * and the renderer are the ones a phone runs; what a device adds is a screen to draw on.
+ *
+ * Two things are supplied rather than discovered, both through documented configuration: the
+ * navigation source, so the test can send a deep link, and the screen stack, so it can read what
+ * landed on it.
  *
  * Screens are listed here because the generated manifest (`.stone/modules.ts`) is Metro's, written
  * when Metro starts. Under a test runner the modules are imported directly, which is the same set.
  */
-describe('Screens', () => {
+describe('Navigation', () => {
   const screens = ScreenStack.create()
   const navigation = NavigationSource.create({ baseUrl: 'stone://app' })
 

package/basic-react-native-declarative/vitest.config.ts

@@ -22,6 +22,12 @@ export default defineConfig({
     }
   },
   test: {
+    // `createTestApp()` discovers the application's modules by importing them at run time. Vitest
+    // externalises dependencies from `node_modules`, and an externalised module's `import()` is
+    // Node's, which cannot load a `.ts` file. Inlining the package puts those imports back through
+    // Vite's transform. `stone test` does this for you; a project running Vitest directly, as an
+    // Expo project does, states it here.
+    server: { deps: { inline: ['@stone-js/testing'] } },
     globals: true,
     environment: 'node',
     include: ['./tests/**/*.{test,spec}.?(c|m)[jt]s?(x)'],

package/basic-react-native-imperative/README.md

@@ -106,36 +106,29 @@ the page that owns `/`, with `name` readable through `event.get('name')`. Change
 
 `App.tsx` renders `StoneNativeApp`, which shows the screen on top of the stack. That is the floor,
 not the ceiling: it is what makes the first run work with nothing installed. The platform's
-transitions, the swipe-back gesture, and a screen keeping its own state while another covers it are
-things only a native navigator gives you.
+transitions, the swipe-back gesture, the hardware back button, and a screen keeping its own state
+while another covers it are things only a native navigator gives you.
 
-The stack is public state, so a navigator drives itself from it:
+Two commands and one import away:
 
-```tsx
-import { useScreens } from '@stone-js/use-react-native'
-import { NavigationContainer } from '@react-navigation/native'
-import { createNativeStackNavigator } from '@react-navigation/native-stack'
+```sh
+npx expo install @react-navigation/native @react-navigation/native-stack \
+  react-native-screens react-native-safe-area-context
+```
 
-const Stack = createNativeStackNavigator()
+```tsx
+// App.tsx
+import { StoneNativeStack } from '@stone-js/use-react-native/navigation'
 
 export default function App () {
-  const screens = useScreens()
-
-  return (
-    <NavigationContainer>
-      <Stack.Navigator>
-        {screens.map((screen) => (
-          <Stack.Screen key={screen.key} name={screen.key} options={{ title: screen.title }}>
-            {() => screen.element}
-          </Stack.Screen>
-        ))}
-      </Stack.Navigator>
-    </NavigationContainer>
-  )
+  return <StoneNativeStack screenOptions={{ headerShown: true }} />
 }
 ```
 
-Nothing about your pages changes.
+Nothing about your screens changes. Each becomes a native one, keyed so the navigator keeps its
+state, and titled from the page's `head`. See the
+[renderer's README](https://www.npmjs.com/package/@stone-js/use-react-native) for how the two stacks
+stay in agreement, and for writing your own navigator instead.
 
 ## The declarative twin
 

package/basic-react-native-imperative/package.json

@@ -21,11 +21,11 @@
     "test:cvg": "npm run test -- --coverage"
   },
   "dependencies": {
-    "@stone-js/browser-core": "^0.8.13",
-    "@stone-js/core": "^0.8.13",
-    "@stone-js/react-native-adapter": "^0.8.13",
-    "@stone-js/router": "^0.8.13",
-    "@stone-js/use-react-native": "^0.8.13",
+    "@stone-js/browser-core": "^0.8.14",
+    "@stone-js/core": "^0.8.14",
+    "@stone-js/react-native-adapter": "^0.8.14",
+    "@stone-js/router": "^0.8.14",
+    "@stone-js/use-react-native": "^0.8.14",
     "expo": "~57.0.14",
     "expo-status-bar": "~57.0.1",
     "fast-text-encoding": "^1.0.6",
@@ -35,8 +35,8 @@
   },
   "devDependencies": {
     "@babel/plugin-proposal-decorators": "^7.28.0",
-    "@stone-js/cli": "^0.8.13",
-    "@stone-js/testing": "^0.8.13",
+    "@stone-js/cli": "^0.8.14",
+    "@stone-js/testing": "^0.8.14",
     "@types/react": "~19.2.2",
     "@vitest/coverage-v8": "^3.0.9",
     "babel-preset-expo": "^57.0.7",

package/basic-react-native-imperative/tests/HomeScreen.spec.ts

@@ -0,0 +1,36 @@
+import { createTestApp } from '@stone-js/testing'
+import { makeIncomingBrowserEvent } from '@stone-js/testing/browser'
+import { REACT_NATIVE_PLATFORM } from '@stone-js/react-native-adapter'
+
+/**
+ * The whole application, booted in memory and asked a real question.
+ *
+ * Nothing is mocked and nothing is listed: `createTestApp()` discovers `app/**`, and the event goes
+ * through the same kernel a phone runs. This is the same test the web starters ship, with one
+ * difference: the platform is named, and the event is the one a native application receives, which
+ * is how a deep link arrives.
+ *
+ * What it substitutes is the adapter, and that is the architecture rather than a concession to
+ * testing: the domain is written once and the context is chosen at run time, so under Node the
+ * context is a test adapter instead of React Native.
+ */
+describe('HomeScreen', () => {
+  it('resolves the home screen, data included', async () => {
+    const app = await createTestApp({ platform: REACT_NATIVE_PLATFORM })
+
+    const response = await app.send(makeIncomingBrowserEvent({ url: 'stone://app/?name=Ada' }))
+
+    expect(response.statusCode).toBe(200)
+    // The head is what a navigator shows in its header, and it proves the loader ran with the deep
+    // link's parameter.
+    expect((response.content as any).head.title).toBe('Ada · Welcome to Stone.js')
+  })
+
+  it('resolves without a name', async () => {
+    const app = await createTestApp({ platform: REACT_NATIVE_PLATFORM })
+
+    const response = await app.send(makeIncomingBrowserEvent({ url: 'stone://app/' }))
+
+    expect(response.statusCode).toBe(200)
+  })
+})

package/basic-react-native-imperative/tests/{Application.spec.ts → navigation.spec.ts}

@@ -5,18 +5,21 @@ import { ScreenStack } from '@stone-js/use-react-native'
 import { NavigationSource } from '@stone-js/react-native-adapter'
 
 /**
- * The whole application, booted under Node and asked real questions.
+ * Navigation, with the real adapter this time.
  *
- * Nothing is mocked. The kernel, the router, the adapter and the renderer are the ones a phone
- * runs; what a device adds is a screen to draw on, and this asserts what the framework resolved
- * before drawing. Two things are supplied rather than discovered, both through documented
- * configuration: the navigation source, so the test can send a deep link, and the screen stack, so
- * it can read what landed on it.
+ * `HomeScreen.spec.ts` asks what a route resolves to, which is the same question on every platform
+ * and needs no adapter. This asks the native question instead: what lands on the navigation stack,
+ * and in what order. So nothing is substituted here. The kernel, the router, the React Native adapter
+ * and the renderer are the ones a phone runs; what a device adds is a screen to draw on.
+ *
+ * Two things are supplied rather than discovered, both through documented configuration: the
+ * navigation source, so the test can send a deep link, and the screen stack, so it can read what
+ * landed on it.
  *
  * Screens are listed here because the generated manifest (`.stone/modules.ts`) is Metro's, written
  * when Metro starts. Under a test runner the modules are imported directly, which is the same set.
  */
-describe('Screens', () => {
+describe('Navigation', () => {
   const screens = ScreenStack.create()
   const navigation = NavigationSource.create({ baseUrl: 'stone://app' })
 

package/basic-react-native-imperative/vitest.config.ts

@@ -22,6 +22,12 @@ export default defineConfig({
     }
   },
   test: {
+    // `createTestApp()` discovers the application's modules by importing them at run time. Vitest
+    // externalises dependencies from `node_modules`, and an externalised module's `import()` is
+    // Node's, which cannot load a `.ts` file. Inlining the package puts those imports back through
+    // Vite's transform. `stone test` does this for you; a project running Vitest directly, as an
+    // Expo project does, states it here.
+    server: { deps: { inline: ['@stone-js/testing'] } },
     globals: true,
     environment: 'node',
     include: ['./tests/**/*.{test,spec}.?(c|m)[jt]s?(x)'],

package/basic-service-declarative/package.json

@@ -18,15 +18,16 @@
     "test:cvg": "stone test --coverage"
   },
   "dependencies": {
-    "@stone-js/core": "^0.8.13",
-    "@stone-js/node-http-adapter": "^0.8.13"
+    "@stone-js/core": "^0.8.14",
+    "@stone-js/node-http-adapter": "^0.8.14"
   },
   "devDependencies": {
     "@babel/plugin-proposal-decorators": "^7.25.9",
     "@babel/preset-env": "^7.26.9",
     "@babel/preset-typescript": "^7.27.0",
-    "@stone-js/cli": "^0.8.13",
-    "@stone-js/testing": "^0.8.13",
+    "@stone-js/cli": "^0.8.14",
+    "@stone-js/http-core": "^0.8.14",
+    "@stone-js/testing": "^0.8.14",
     "@types/node": "^24.0.7",
     "@vitest/coverage-v8": "^3.0.9",
     "vitest": "^3.0.9"

package/basic-service-declarative/tests/Application.spec.ts

@@ -1,4 +1,5 @@
-import { createTestApp, makeIncomingHttpEvent } from '@stone-js/testing'
+import { createTestApp } from '@stone-js/testing'
+import { makeIncomingHttpEvent } from '@stone-js/testing/http'
 
 /**
  * The whole application, booted in memory and asked a real question.

package/basic-service-imperative/package.json

@@ -18,15 +18,16 @@
     "test:cvg": "stone test --coverage"
   },
   "dependencies": {
-    "@stone-js/core": "^0.8.13",
-    "@stone-js/node-http-adapter": "^0.8.13"
+    "@stone-js/core": "^0.8.14",
+    "@stone-js/node-http-adapter": "^0.8.14"
   },
   "devDependencies": {
     "@babel/plugin-proposal-decorators": "^7.25.9",
     "@babel/preset-env": "^7.26.9",
     "@babel/preset-typescript": "^7.27.0",
-    "@stone-js/cli": "^0.8.13",
-    "@stone-js/testing": "^0.8.13",
+    "@stone-js/cli": "^0.8.14",
+    "@stone-js/http-core": "^0.8.14",
+    "@stone-js/testing": "^0.8.14",
     "@types/node": "^24.0.7",
     "@vitest/coverage-v8": "^3.0.9",
     "vitest": "^3.0.9"

package/basic-service-imperative/tests/Application.spec.ts

@@ -1,4 +1,5 @@
-import { createTestApp, makeIncomingHttpEvent } from '@stone-js/testing'
+import { createTestApp } from '@stone-js/testing'
+import { makeIncomingHttpEvent } from '@stone-js/testing/http'
 
 /**
  * The whole application, booted in memory and asked a real question.

package/continuum-showcase/package.json

@@ -15,20 +15,20 @@
   "dependencies": {
     "react": "^19.0.0",
     "react-dom": "^19.0.0",
-    "@stone-js/core": "^0.8.13",
-    "@stone-js/router": "^0.8.13",
-    "@stone-js/use-react": "^0.8.13",
-    "@stone-js/http-core": "^0.8.13",
-    "@stone-js/pipeline": "^0.8.13",
-    "@stone-js/browser-adapter": "^0.8.13",
-    "@stone-js/node-http-adapter": "^0.8.13"
+    "@stone-js/core": "^0.8.14",
+    "@stone-js/router": "^0.8.14",
+    "@stone-js/use-react": "^0.8.14",
+    "@stone-js/http-core": "^0.8.14",
+    "@stone-js/pipeline": "^0.8.14",
+    "@stone-js/browser-adapter": "^0.8.14",
+    "@stone-js/node-http-adapter": "^0.8.14"
   },
   "devDependencies": {
     "@babel/plugin-proposal-decorators": "^7.25.9",
     "@babel/preset-env": "^7.26.9",
     "@babel/preset-typescript": "^7.27.0",
-    "@stone-js/cli": "^0.8.13",
-    "@stone-js/testing": "^0.8.13",
+    "@stone-js/cli": "^0.8.14",
+    "@stone-js/testing": "^0.8.14",
     "@types/node": "^24.0.7",
     "@types/react": "^19.0.7",
     "@types/react-dom": "^19.0.3",

package/continuum-showcase/tests/application.spec.ts

@@ -1,4 +1,5 @@
-import { createTestApp, makeIncomingHttpEvent } from '@stone-js/testing'
+import { createTestApp } from '@stone-js/testing'
+import { makeIncomingHttpEvent } from '@stone-js/testing/http'
 
 /**
  * The whole application, booted in memory and asked a real question.

package/full-react-declarative/package.json

@@ -18,14 +18,14 @@
     "test:cvg": "stone test --coverage"
   },
   "dependencies": {
-    "@stone-js/env": "^0.8.13",
-    "@stone-js/http-core": "^0.8.13",
-    "@stone-js/node-http-adapter": "^0.8.13",
-    "@stone-js/router": "^0.8.13",
-    "@stone-js/filesystem": "^0.8.13",
-    "@stone-js/core": "^0.8.13",
-    "@stone-js/use-react": "^0.8.13",
-    "@stone-js/browser-adapter": "^0.8.13",
+    "@stone-js/env": "^0.8.14",
+    "@stone-js/http-core": "^0.8.14",
+    "@stone-js/node-http-adapter": "^0.8.14",
+    "@stone-js/router": "^0.8.14",
+    "@stone-js/filesystem": "^0.8.14",
+    "@stone-js/core": "^0.8.14",
+    "@stone-js/use-react": "^0.8.14",
+    "@stone-js/browser-adapter": "^0.8.14",
     "axios": "^1.7.9",
     "react": "^19.0.0",
     "react-dom": "^19.0.0"
@@ -34,8 +34,8 @@
     "@babel/plugin-proposal-decorators": "^7.25.9",
     "@babel/preset-env": "^7.26.9",
     "@babel/preset-typescript": "^7.27.0",
-    "@stone-js/cli": "^0.8.13",
-    "@stone-js/testing": "^0.8.13",
+    "@stone-js/cli": "^0.8.14",
+    "@stone-js/testing": "^0.8.14",
     "@types/axios": "^0.14.4",
     "@types/node": "^24.0.7",
     "@types/react": "^19.0.7",

package/full-react-declarative/tests/application.spec.ts

@@ -1,4 +1,5 @@
-import { createTestApp, makeIncomingHttpEvent } from '@stone-js/testing'
+import { createTestApp } from '@stone-js/testing'
+import { makeIncomingHttpEvent } from '@stone-js/testing/http'
 
 /**
  * The whole application, booted in memory and asked a real question.

package/full-react-imperative/package.json

@@ -18,14 +18,14 @@
     "test:cvg": "stone test --coverage"
   },
   "dependencies": {
-    "@stone-js/env": "^0.8.13",
-    "@stone-js/http-core": "^0.8.13",
-    "@stone-js/node-http-adapter": "^0.8.13",
-    "@stone-js/router": "^0.8.13",
-    "@stone-js/filesystem": "^0.8.13",
-    "@stone-js/core": "^0.8.13",
-    "@stone-js/use-react": "^0.8.13",
-    "@stone-js/browser-adapter": "^0.8.13",
+    "@stone-js/env": "^0.8.14",
+    "@stone-js/http-core": "^0.8.14",
+    "@stone-js/node-http-adapter": "^0.8.14",
+    "@stone-js/router": "^0.8.14",
+    "@stone-js/filesystem": "^0.8.14",
+    "@stone-js/core": "^0.8.14",
+    "@stone-js/use-react": "^0.8.14",
+    "@stone-js/browser-adapter": "^0.8.14",
     "axios": "^1.7.9",
     "dayjs": "^1.11.13",
     "react": "^19.0.0",
@@ -35,8 +35,8 @@
     "@babel/plugin-proposal-decorators": "^7.25.9",
     "@babel/preset-env": "^7.26.9",
     "@babel/preset-typescript": "^7.27.0",
-    "@stone-js/cli": "^0.8.13",
-    "@stone-js/testing": "^0.8.13",
+    "@stone-js/cli": "^0.8.14",
+    "@stone-js/testing": "^0.8.14",
     "@types/axios": "^0.14.4",
     "@types/node": "^24.0.7",
     "@types/react": "^19.0.7",

package/full-react-imperative/tests/application.spec.ts

@@ -1,4 +1,5 @@
-import { createTestApp, makeIncomingHttpEvent } from '@stone-js/testing'
+import { createTestApp } from '@stone-js/testing'
+import { makeIncomingHttpEvent } from '@stone-js/testing/http'
 
 /**
  * The whole application, booted in memory and asked a real question.