DappConnect Chat SDK to easily add a decentralized, censorship-resistant chat feature to your dApp, powered by Waku v2 and Status Communities.

Go to file

markoburcul 40f015563a jenkinsfile: filter stages based on path Ideally we would want to trigger Jenkins build based on the path where change occurred. Unfortunately this is not supported by Jenkins. As a workaround we are conditionally executing steps if the change occured in the apps/connector/ path. Prior to this we need to fetch the changelog diff between current branch and target branch to understand if there was a change present in the target dir and if we need to run all stages. The population of changelog is needed just the first time the PR is opened and in the subsequent steps we don't need this. Referenced issue: https://github.com/status-im/status-web/issues/590 Signed-off-by: markoburcul <marko@status.im>		2024-10-11 15:53:58 +02:00
.changeset	Release (#610 )	2024-10-11 14:19:49 +02:00
.github/workflows	2.0 (#523 )	2024-09-25 17:17:58 +02:00
.husky	Add pre-commit git hooks (#229 )	2022-02-24 23:27:22 +01:00
.vscode	2.0 (#523 )	2024-09-25 17:17:58 +02:00
apps/connector	jenkinsfile: filter stages based on path	2024-10-11 15:53:58 +02:00
packages	Release (#610 )	2024-10-11 14:19:49 +02:00
patches	handle larger messages (#531 )	2024-03-15 11:04:03 +09:00
.editorconfig	Add editorconfig	2022-02-25 14:56:28 +01:00
.eslintignore	2.0 (#523 )	2024-09-25 17:17:58 +02:00
.gitignore	2.0 (#523 )	2024-09-25 17:17:58 +02:00
.prettierrc	2.0 (#523 )	2024-09-25 17:17:58 +02:00
LICENSE.md	2.0 (#523 )	2024-09-25 17:17:58 +02:00
README.md	add `apps/connector` (#589 )	2024-10-03 12:06:54 +02:00
package.json	2.0 (#523 )	2024-09-25 17:17:58 +02:00
tsconfig.base.json	2.0 (#523 )	2024-09-25 17:17:58 +02:00
turbo.json	2.0 (#523 )	2024-09-25 17:17:58 +02:00
vercel.json	Set up website deployment (#391 )	2023-05-12 15:06:04 +02:00
yarn.lock	add `<Switch />` and `<DropdownMenu.SwitchItem />` (#582 )	2024-09-27 16:51:28 +02:00

README.md

`status-web`

This monorepo contains packages for building web applications in the Status ecosystem. These packages can be used separately or combined to create consistent and beautiful user interfaces.

Packages

Name	`npm`	Description
`@status-im/components`		Component library built with Radix UI, React Aria, Tailwind CSS.
`@status-im/js`		Libary for Waku protocol integration and blockchain interactions.
`@status-im/icons`		Auto-generated icon library based on our design system.
`@status-im/colors`		Auto-generated color palette based on our design system.
`@status-im/eslint-config`		Shared ESLint configuration for consistent code style across projects.

Apps

Name	Description
`./apps/connector`	Status Desktop Wallet extended to decentralised applications in your browser.

Prerequisites

Required:

Node.js v18.x
Yarn v1.22.x

Recommended:

Visual Studio Code
- install extensions listed in .vscode/extensions.json for optimal development experience

Stack

Turborepo: Manages our monorepo and speeds up builds
TypeScript: Adds type safety to our code
React: Our main library for building UIs
Radix UI / React Aria: Provides accessible UI primitives
Tailwind CSS: Used for styling
Vite: Our build tool and dev server
Storybook: For developing and showcasing components
ESLint: Keeps our code consistent and catches potential issues
Prettier: Formats our code
Changesets: Manages versioning and changelogs

Getting Started

Clone the repository:

git clone https://github.com/status-im/status-web.git
cd status-web

Install dependencies:
```
yarn install
```
Build all packages:
```
yarn build
```
Run tests:
```
yarn test
```
Start development mode:
```
yarn dev
```

Storybook

To view and interact with the components, you can run Storybook:

yarn storybook

This will start the Storybook server, allowing you to browse and test components in isolation.