# Cloudflare Pages

Coming soon

# GitHub Pages

Coming soon

# Orbiter

Coming soon

# Cloudflare Workers

Coming soon

bhvr is a framework used to build apps that are not tied down to a single provider, and each piece can be deployed in multiple places.

::::steps

### Create a New Project

To start using bhvr make sure you have [Bun](https://bun.sh) installed first, then run the following command.

```bash [terminal]

bun create bhvr@latest

```

The stack is composed of the following:

```

.

├── client/               # React frontend

├── server/               # Hono backend

├── shared/               # Shared TypeScript definitions

│   └── src/types/        # Type definitions used by both client and server

└── package.json          # Root package.json with workspaces

```

### Start Up Dev Server

Once you have created your project you can `cd` into it and run the dev server

```bash [terminal]

bun run dev

```

This will spin up dev servers for the `server`, `client`, and `shared` packages

Try updating the API endpoints in the `server` package

```typescript [server/src/index.ts]

import { Hono } from 'hono'

import { cors } from 'hono/cors'

import type { ApiResponse } from 'shared/dist'

const app = new Hono()

app.use(cors())

app.get('/', (c) => {

  return c.text('Hello Hono!')

})

app.get('/hello', async (c) => {

  const data: ApiResponse = {

    message: "Hello BHVR!",

    success: true

  }

  return c.json(data, { status: 200 })

})

export default app

```

Also try editing the React app in `client`

```tsx [client/src/App.tsx]

import { useState } from 'react'

import beaver from './assets/beaver.svg'

import { ApiResponse } from 'shared'

import './App.css'

const SERVER_URL = import.meta.env.VITE_SERVER_URL || "http://localhost:3000"

function App() {

  const [data, setData] = useState<ApiResponse | undefined>()

  async function sendRequest() {

    try {

      const req = await fetch(`${SERVER_URL}/hello`)

      const res: ApiResponse = await req.json()

      setData(res)

    } catch (error) {

      console.log(error)

    }

  }

  return (

    <>

      <div>

        <a href="https://github.com/stevedylandev/bhvr" target="_blank">

          <img src={beaver} className="logo" alt="beaver logo" />

        </a>

      </div>

      <h1>bhvr</h1>

      <h2>Bun + Hono + Vite + React</h2>

      <p>A typesafe fullstack monorepo</p>

      <div className="card">

        <button onClick={sendRequest}>

          Call API

        </button>

        {data && (

          <pre className='response'>

            <code>

            Message: {data.message} <br />

            Success: {data.success.toString()}

            </code>

          </pre>

        )}

      </div>

      <p className="read-the-docs">

        Click the beaver to learn more

      </p>

    </>

  )

}

export default App

```

### Build Project

Once you have your project ready to go you can use the build command to build the `client` and `shared` packages

```bash [terminal]

bun run build

```

From there you can select multiple [deployment options](/deployment/client/orbiter)

::::

# `client`

Coming soon

# `server`

Coming soon

# `shared`

Coming soon

# Why bhvr?

I get it. Why another typescript framework for web apps? Aren't we just heaping fuel to the already massive dumpster fire?

While that might be true, the reality is the web is continuing to be built on JavaScript, and generally written in TypeScript. While that reality stays true, there are some concerning pieces of our ecosystem that create more walled gardens and vendor lock-in. SSR is notorious for this as it prevents web apps from being portable, where you can easily host a piece of your stack somewhere else with little to no effort. That old age was more commonly known as Jamstack (Javascript APIs and Markdown), and in that period we saw a renasiance of web apps that were lightweight, efficient, and most importantly open and portable.

![image](https://dweb.mypinata.cloud/ipfs/bafybeiglk63npgshe6teogi5o5tljcmyx2ifddkwion4znbfpiceehnnn4)

The tides are turning and SSR is not always everyone's top pick these days. Developers from the Jamstack era long for the old times again, and new developers experience the frustration that comes with complicated frameworks such as Next.js. bhvr was built on a whim to fill the void Next.js leaves most developers, and it's mission now is to become a stack for the open web.

  logoUrl: "https://bhvr-docs.orbiter.website/icon-big.png",

          collapsed: true,

          collapsed: true,