How many times have you needed to quickly generate UUID, for example, for test purposes? Probably each time you opened a web page with online generator, copy and paste into your code. Then, when you need another one, you had to open this page or refresh, copy and paste it, probably loosing focus on what you've been doing so far.
The main goal of this project is to provide quick way to generate new UUIDs. The initial stage, the Google Chrome Extension, seems to be the easiest way to invoke the generator without need to switch a work context.
More features coming soon!
Feel free to install the extension from Google Chrome WebStore:
You can choose whether you'd like to develop the extension locally or with docker.
Requirements:
- Node.js 14+
Install npm dependencies and run following scripts to develop the project:
# Install dependencies
npm install
# Run the app locally
npm start
npm run-script build
Unit tests
npm test
The project uses Cypress to run browser e2e tests.
You can run them locally manually having the app started with npm start
with:
npx cypress open
Or just run all the test with:
npx cypress run
For more details on how to use the Cypress, please refer to their docs.
First you need to install dependencies:
docker-compose run node npm install
This project provides a very simple Google Analytics page views and events tracing. Following events are registered:
Event (category/action) | Labels | Description |
---|---|---|
UI/MODE_SELECT |
|
Switching between generation screens |
UI/REFRESH | ~ | New single UUID generation |
UI/COPY | ~ | Copying single UUID using copy the button |
UI/REFRESH_MULTI | SIZE=x | Multi UUID generation with specified size |
UI/COPY_MULTI | SIZE=x | Copying multiple UUID using copy the button |
UI/OPTION_SELECT | E.g.
|
Selecting an option in multi generation screen |
LINK/CLICK | ~ | Clicking the external link in the footer |
You can configure your tracking key by putting it into .env.local
file (see .env
for the example and how to use environment variables in React Apps)
Please read CONTRIBUTING.md for details on the code of conduct, and the process for submitting pull requests.