Dev Launchers (https://devlaunchers.org)
This is the monorepo for all DevLaunchers internal products, we use React.js/Next.js and many other wonderful libraries.
Dev Launchers is a nonprofit tech company working to democratize access to technology and tech related skills. At our core, we build projects and run programs that are designed to prepare the world for a rapidly changing future. We've built an inclusive, software focused incubator giving people from diverse backgrounds the skills and resources necessary to succeed in careers touched by technology, and have an open community focused on advancing technology, one another, and ourselves. This repository holds the beginnings of the online platform we're creating in order to first impart the general skills required for members to begin their own projects, and then support their exploration as they tackle building something they're excited about. It also functions as our organization's website!
Visit https://devlaunchers.org/join to join one of our teams!
-
Clone the repo
-
Install dependencies:
yarn install -
Run the tailwindcss compiler:
yarn workspace @devlaunchers/tailwind dev -
Run the app's development server:
yarn workspace @devlaunchers/app dev
We are using semantic versioning to tag release. Follow https://github.com/semantic-release/semantic-release#commit-message-format to format the commit messages.
We've created a command to guide you create conventional commit message all you need to do is run yarn commit
The release cadence is every 4 weeks. We will create a PR to merge the master branch into the release branch.
Some convenience scripts can be run in any folder of this repo and will call their counterparts defined in packages and apps.
| Name | Description |
|---|---|
yarn g:changeset |
Add a changeset to declare a new version |
yarn nuke:node_modules |
Remove node_modules folder in sub-folders |
yarn commit |
Format your commit message to follow our convention (Run git add -p first) |
yarn g:typecheck |
Run typechecks in all workspaces |
yarn g:lint |
Display linter issues in all workspaces |
yarn g:lint --fix |
Attempt to run linter auto-fix in all workspaces |
yarn g:build |
Run build in all workspaces |
yarn g:clean |
Clean builds in all workspaces |
yarn g:check-dist |
Ensure build dist files passes es2017 (run g:build first). [WIP] |
yarn g:check-size |
Ensure browser dist files are within size limit (run g:build first). [WIP] |
yarn clean:global-cache |
Clean tooling caches (eslint, jest...) |
yarn deps:check --dep dev |
Will print what packages can be upgraded globally (see also .ncurc.yml) |
yarn deps:update --dep dev |
Apply possible updates (run yarn install && yarn dedupe after) |
yarn check:install |
Verify if there's no peer-deps missing in packages |
yarn dedupe |
Built-in yarn deduplication of the lock file |
Why using
:to prefix scripts names ? It's convenient in yarn 3+, we can call those scripts from any folder in the monorepo.g:is a shortcut forglobal:. See the complete list in root package.json.
The global commands yarn deps:check and yarn deps:update will help to maintain the same versions across the entire monorepo.
They are based on the excellent npm-check-updates
(see options, i.e: yarn check:deps -t minor).
After running
yarn deps:update, ayarn installis required. To prevent having duplicates in the yarn.lock, you can runyarn dedupe --checkandyarn dedupeto apply deduplication. The duplicate check is enforced in the example github actions.
Available at: https://staging.devlaunchers.org This runs the main development branch (
master) and is automatically redeployed when that branch is updated
The Dev Launchers platform is licensed under GNU General Public License v3.