npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

brick-rs

v0.0.13

Published

Descripción de mi aplicación

Downloads

95

Readme

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 Manager | Command | |------------------|------------------------------| | Yarn | yarn add -D brick-rs | | Npm | npm i --save-dev brick-rs | | Pnpm | pnpm 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.