---
# System prepended metadata

title: BWE Alpha Test

---

# Internal Notes (will be removed before sharing)

Date: Feb 26th

- polish matters— this will be the first time most participants see BWE in action. Time spent on beautifying demo components and creating nice documentation has impact
- two flows: web sandbox and bos-loader
- although we will be adding wallet support, we may want to add a disclaimer that we recommend using test accounts instead of connecting valuable near addresses
    - concern is lack of security audit at this point in time
- collective effort to catch bugs week before alpha

## Intended Participants

- internal teams: FastAuth, near.org squad
- proximity
- BOS power users: 
    - Eugene the Dream
    - Vadim (Proximity)
    - Mike Purvis (Proximity -> Working on VM Cosmos integrations)
    - Zahid (Jutsu)
    - Frol (DevHub)
    - Mario (Orderly)
    - Luis (Mintbase)
    - Elliot (Everything.dev)
    - James Waugh (NEAR Builders DAO)
    - Code (Banyan / Web3 Plug)
    - More on spreadsheet
- non-BOS web developers
    - how do we find these?

## Goals

- BWE exposure to a wider variety of component code to discover perforance/capability shortcomings
- socialization of BWE with prolific BOS developers
- feedback on migration path from vanilla React to BWE and from Discovery VM to BWE
- feedback on syntax / DevX
- inform roadmap to production availability
- gather opinion of BWE from non-BOS devs
- kick off security audit efforts
- inform type of npm modules that are desired to be supported
- use feedback to re-evaluate priority on all backlog items

The most consequential feedback from the test will be whether there are any shortcomings of the engine which require significant rework to what has already been implemented


(shared with participants)
vvvvvvvvvvvvvvvvvvvvvvvvv

# BOS Web Engine Alpha Test 
> ℹ️ Purpose of this section: We will share this to all invitees of the alpha test to outline how the test will be conducted, feedback we are looking for, expectations of the state of BWE, and links to relevant resources

Thanks so much for participating in the alpha test of BOS Web Engine, an improved execution layer for NEAR's decentralized front-end components.

## Timeline

The alpha test will begin on Feb 26 and run for several weeks as we perform rigorous testing both internally and with community members such as yourself. 🙏 


## How to get involved 

Head to our staging site and try any of the following:
- Writing components that aren't possible to build using the current VM
- Writing components that test the limits of BWE
- Migrating your existing components from the VM to BWE
- Migrating vanilla React components to BWE

## Support from BWE team

The BWE team will be available via Telegram (:exclamation: TODO link) and GitHub Discussions (:exclamation: TODO link) to answer questions and assist in troubleshooting

## Feedback

We are looking for feedback in the following areas:
- Performance
- Syntax
- Overall developer experience (DevX)
- Documentation
- Level of effort to migrate components to BWE
- Missing capabilities

### Avenues of Feedback

### Bugs / Performance Issues / Feature Requests

Please create a GitHub issue describing what you are experiencing. The more info the better, but don't let that be a blocker from filing an issue. If you only have time to file something quick, please do so and we can follow up for more details later :slightly_smiling_face: 
(:exclamation: TODO appropriate labels)

### Opinions on Syntax and DevX

You can start a GitHub Discussion (:exclamation: TODO instructions) or let us know through this form (:exclamation: TODO link)

## What to expect

( :exclamation: TODO andy to work on this section. link to component examples? )

### Should work
- npm dependencies including: React components, vanilla JS libs, etc (TODO)


### Not currently supported

TODO: link to issues for capabilities like `useRef`, Web APIs, etc

- `useRef` (refs not exposed to outer application)
- `useContext`
- `<canvas>`
- Direct DOM manipulation
- to allow BWE components to be composed of VM components
- to sandbox the vm inside the security envelope of the BWE

## Getting Started

There are two flows for testing BOS Web Engine, by using the web sandbox or with your local code editor and `bos-loader`

### Web Sandbox

Our recommended testing environment is the web sandbox which can be found here (:exclamation: TODO link)

(:exclamation: TODO updated screenshot of sandbox)

![image](https://hackmd.io/_uploads/Bk8ghBnFp.png)

### Local Editor

:exclamation: TODO give instructions for users who strongly want to use local
editor setup or sync with GitHub. List disadvantages over sandbox

## Documentation

:exclamation: TODO direct to sandbox sidebar for docs