0.0.13 β€’ Published 7 months ago

brick-rs v0.0.13

Weekly downloads
-
License
MIT
Repository
-
Last release
7 months ago

What is Brick?

​Brick is under active development. The purpose of this binary is to run jobs on modified routes to avoid heavy loads and waiting times. Currently, it only works with Cypress e2e and Jest. watch the GitHub repository to keep tabs on future releases.

Untitled-2023-09-19-1214(1)(1)

Add to a New Project

Install

Package ManagerCommand
Yarnyarn add -D brick-rs
Npmnpm i --save-dev brick-rs
Pnpmpnpm add -D brick-rs

Config

For pnpm and npm Projects

Add the following script to your package.json file:

{
		"scripts": {
			...
			"brick": "brickrs"
		}
}

For yarn Projects

If the binary doesn't execute properly with Yarn projects, configure it manually in your package.json

{
		"scripts": {
			...
			"brick": "./node_modules/brick-rs/target/debug/brick"
		}
}

Create a brick.config.json file with the following content:

{
		"pm": "pnpm",
		"root": "components",
		"jobs": ["jest", "cypress"]
}

pm Project package manager

root The entry point where the program looks for changes.

πŸ“ cypress
	πŸ“ e2e
            πŸ“ home
            πŸ“ about
πŸ“ src
  πŸ“ components **(root)**
    πŸ“ home
	πŸ“„ index.ts **x** **(modified)**
      πŸ“ __tests__
	πŸ“„ index.test.ts
	πŸ“ about

jobs The jobs to execute on the specified directories with changes.

In this case, the jobs will run on the home folder (components/home/*). If you have Cypress, it will look for the folder with the same name: cypress/e2e/home. It's crucial that they have matching names.

Note: Ensure Cypress is properly configured, and the server is running, especially for e2e tests.

Finally

To run the brick script after configuring your project, use the following command if you are using pnpm as your package manager:

pnpm run brick

image

Contributing

After completing the development, you can test it locally on our front end by following these steps:

  1. Build the project and copy the binary to the test environment:

cargo build && ./copy_target.sh

This will copy the binary to our front-end testing environment /test-brick.

  1. Inside our testing environment /test-brick, run the following command to execute the binary. This allows us to avoid working with the entire package and only focus on running the binary, which is crucial. pnpm run brick-build

This script enables us to execute the binary efficiently, simplifying the testing process.

0.0.13

7 months ago

0.0.12

7 months ago

0.0.11

7 months ago

0.0.36-test

7 months ago

0.0.35-test

7 months ago

0.0.34-test

7 months ago

0.0.33-test

7 months ago

0.0.32-test

7 months ago

0.0.31-test

7 months ago

0.0.30-test

7 months ago

0.0.29-test

7 months ago

0.0.28-test

7 months ago

0.0.27-test

7 months ago

0.0.26-test

7 months ago

0.0.25-test

7 months ago

0.0.24-test

7 months ago

0.0.23-test

7 months ago

0.0.22-test

7 months ago

0.0.21-test

7 months ago

0.0.20-test

7 months ago

0.0.19-test

7 months ago

0.0.18-test

7 months ago

0.0.17-test

7 months ago

0.0.16-test

7 months ago

0.0.15-test

7 months ago

0.0.14-test

7 months ago

0.0.13-test

7 months ago

0.0.12-test

7 months ago

0.0.11-test

7 months ago

0.0.10-test

7 months ago

0.0.9-test

7 months ago

0.0.8-test

7 months ago

0.0.7-test

7 months ago

0.0.6-test

7 months ago

0.0.5-test

7 months ago

0.0.4-test

7 months ago

0.0.3-test

7 months ago

0.0.2-test

7 months ago

0.0.1-test

7 months ago

0.0.1

7 months ago

1.0.0

7 months ago