eslint-snowball-config |
prettier-config |
renovate-config |
semantic-release-config |
---|---|---|---|
Quality on main branch |
Security on main branch |
Release on main branch |
---|---|---|
The open-source mono-repository for packages developed, maintained and used by Snowball.
Before anything, start by cloning the repository:
git clone git@github.com:snowball-tech/glacier.git
If you haven't setup any SSH key to your GitHub account, you will need to do so. Check out the documentation on how to connect with SSH. Alternatively, you can also use HTTPS to clone the repository (but this is not recommended):
git clone https://github.com/snowball-tech/glacier.git
Note that you can also use the GitHub CLI to clone the repository:
gh repo clone snowball-tech/glacier
When cloned, go into the repository directory:
cd glacier
Before setting up this repository and start using it/contributing to it, you'll need to make sure you have some tools installed on your machine.
Click here to see the details
Click for more information
If you are on MacOS, you will need some extra things to make the steps below easier.
- Homebrew
First of all, you will need HomeBrew:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
You can always check the official documentation if you have any question or issue
- Shell
You are probably using Zsh as your default shell.
Some steps below are updating the .zshrc
file in your home directory.
So we have to make sure this file exists:
touch ~/.zshrc
If you are using Bash as your default shell, run:
touch ~/.bash_profile
These commands may give you an error if the files already existed. You can ignore it.
To be able to work with this repository, you will have to have a working version of NodeJS.
You can simply install the latest version of the 18.x.x or LTS 20.x.x build.
To do so, it's recommended to use a Node Version Manager like NVM or N
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.3/install.sh | bash
Note that you may check on the official installation documentation if a newer version is available.
You can always check the official documentation if you have any question or issue
Then restart your terminal (on MacOS you have to completely quit the Terminal application before restarting it).
Then you can make NVM automatically select the appropriate NodeJS version for the repository:
nvm use
curl -L https://bit.ly/n-install | bash
Then restart your terminal (on MacOS you have to completely quit the Terminal application before restarting it).
Alternatively, on MacOS you can also run:
brew install nAnd then restart your terminal by completely quitting the Terminal application and restarting it.
You can always check the official installation documentation and the official documentation if you have any question or issue
Then you can make N automatically select the appropriate NodeJS version for the repository:
n auto
This mono-repository is base on Yarn Workspaces. So you'll have to have Yarn on its 4.x.x version.
When having NodeJS installed, simply run:
corepack enable
corepack prepare yarn@stable --activate
You can always check the official installation documentation if you have any question or issue
Then make sure you have the latest 4.x.x version installed:
yarn --version
This should output a 4.x.x version (e.g. "4.5.3").
There is an automated setup process that will handle all the steps for you (dependencies, configuration, ...):
yarn setup
You are now ready to start working on Glacier.
It's recommended to regularly update the dependencies and the environment on your local copy of the repository:
yarn setup
This repository is a mono-repository. This means that it contains multiple packages and applications all together in a single Git repository.
Each of these packages and applications contains their own documentation in
their own README.md
file.
See the dedicated
TOOLING.md
documentation for more information about the mono-repository management with Yarn workspaces.
This repository is organized around two major directories:
glacier
|-- packages
|-- ...
Packages are located in the packages directory.
This directory contains packages made to be published in a public NPM repository (https://www.npmjs.com) and used in other packages and/or apps.
There are currently 5 packages available in Glacier:
-
eslint-snowball-config: a composable ESLint v9 configuration to enable config, plugin and rules according to your needs;
-
prettier-config: the base Prettier configuration and ignored files. This configuration disables semicolon, enforce usage of single quotes and add all trailing commas.
It also offers the organize attributes and Shell script plugins out of the box; -
renovate-config: a base opinionated Renovate configuration with support for NPM, Golang, secrets and many more;
-
semantic-release-config: a mono-repository oriented configuration for Semantic Release that allows to publish multiple packages.
It also provide the commit rules for generating changelog and create releases.
See the dedicated CONVENTIONS.md
and
TOOLING.md
documentations.
See the dedicated CONVENTIONS.md
and
TOOLING.md
documentations.
Always remember to add dependency if you really need it to avoid cluttering the packages and degrading the performance both in the developers and users side.
It is your duty as a member of the Snowball's engineering team to help mainting the dependencies up to date. This means that you are expected and should help reviewing, testing and merging dependencies updates PRs on a regular basis.
The best way to do so is to regularly check the Renovate dashboard and the list of Pull Requests, for example every morning at the beginning of your day.
Also, see the dedicated TOOLING.md
documentation for more
information.
See the dedicated TOOLING.md
documentation.
See the dedicated TOOLING.md
documentation.
See the dedicated CONTRIBUTING.md
documentation.
See the dedicated CONVENTIONS.md
documentation.
If you have any questions or feedback, feel free to reach out to us using this repository issues or discussions.
You can also use the internal #engineering Slack channel if you are a member of the Snowball tech team.
You can also check
the dedicated TROUBLESHOOTING.md
documentation
for frequently asked question and troubleshooting.