|
Isomorphic JavaScript utilities optimized for performance and DX. |
|
Exposes APIs for testing and building scalable NodeJS applications. |
|
Re-packages binaries to partition builds for AWS build-size limits. |
|
Optimizes Puppeteer for fast execution on Serverless platforms. |
|
A real-time globally distributed API for Magic: The Gathering. |
|
A Discord Bot for Magic: The Gathering cards, deck building, and strategy. |
1. Installing NodeJS
NodeJS (aka Node) is a cross-platform JavaScript environment built on top of the V8 engine that powers Google Chrome. It is used for testing and running packages and applications developed in this project. NodeJS also comes packaged with the NPM package manager, which is recommended for installing global dependencies.
You can download a NodeJS installer from the official downloads page, or through a package manager.
Verify or check your installed NodeJS version by running the below command:
node --versionNote
If a project requires a specific version of NodeJS determined by the V8 version, use:
$ node
> process.versions.v8
'9.4.146.19-node.13'2. Installing Yarn
This project uses the Yarn package manager to manage project dependencies and scripts. Yarn version 3.5.0+ is supported, though it's recommended to install Yarn through Corepack as detailed below.
Note
If you're using Yarn <2.0, you can upgrade by running yarn set version berry.
The recommended way to install or upgrade Yarn is through a NodeJS binary called Corepack. Corepack installs a proxy for Yarn or PNPM binaries that transparently intercepts Yarn or PNPM commands, installs them (if not already installed), and runs the command. This vastly simplifies installation and versioning of package managers across NodeJS projects without the fuss of OS-specific quirks.
To install Yarn through Corepack, run the below command(s) depending on your NodeJS version:
# For NodeJS v16.9.0+ and v14.19.0+
$ corepack enable
# For NodeJS <16.10
$ npm uninstall -g yarn pnpm
$ npm install -g corepackWhen completed, verify yarn installs successfully:
$ yarn --version
3.5.0To install project dependencies, run yarn or yarn install. For a comprehensive list of Yarn commands, consult the Yarn docs.
This project uses a monorepo approach to manage dependencies and projects. Monorepos allow for a simplified developer experience, providing better discoverability and atomicity.
With the Yarn workspaces feature, multiple packages and applications can easily coexist and cross-reference each other across different workspaces (aka packages/ or services/). This aids in the efficiency of testability and sharability of configurations, packages and applications without duplicating dependencies or code.
You can list all available workspaces by running:
$ yarn workspaces listTo run a script from a specific workspace, run:
$ yarn workspace <workspace> run <script>
# or
$ yarn workspace <workspace> <script>![NOTE] You can also use
yarn run <script>oryarn run <script>to run a script from your current working directory. This is the recommended way of running scripts if you're working on a specific project.
Additionally, to run scripts by name from all workspaces, use:
$ yarn workspaces foreach <script>In addition to sharing dependencies with yarn workspaces, projects can also share scripts from the config/ workspace withing adding any dependencies to the project's project.json file. This allows for a single source of truth for running scripts across the monorepo.
Shared configs also typically contain base configurations and executables for extending and bootstrapping new projects, establishing sensible defaults or extending the base functionality of tooling. This is useful if nuances in a base configuration can't be separated into individual configuration files, where it'd instead make more sense to control or vendor features programmatically.
Below is a breakdown of all shared configs in this monorepo:
| Config | Docs | Scripts | Command |
|---|---|---|---|
|
•
CLI
• Config |
• watch• force• clean• prepack |
$ yarn tsc <...args?>
$ yarn g:config tsc -d <workspace> <...args?> |
|
•
CLI
• Config |
• watch• clean |
$ yarn jest <...args?>
$ yarn g:config jest -d <workspace> <...args?> |
Learn more about running shared scripts with the Yarn Global Runner.
Run workspace scripts anyhow and from anywhere with the yarn global runner.
This allows you to run pre-defined scripts like yarn jest clean. You can run your own commands independently or combine them with pre-defined scripts, e.g. with yarn tsc watch --target ES5 or yarn tsc -w --target ES5.
In yarn configured projects, just run:
# > videre-project/packages/@videre-nodejs/:
$ yarn jest <...args?>
# or
$ yarn tsc <...args?>Or in any other project directory, run with g:workspace or g:config:
# > videre-project/.../:
$ yarn g:workspace @videre/js jest <...args?>
# or
$ yarn g:config jest -d @videre/nodejs <...args?>More examples
For workspace scripts, run commands with
g:workspace:# > videre-project/.../: $ yarn g:workspace <workspace> <...flags?> <script> <...args?> # e.g. $ yarn g:workspace @videre/js -v jest --watch -- file.test.ts $ yarn g:workspace config-jest -d @videre/js -v watch -- file.test.tsFor config scripts, run commands with
g:config:# > videre-project/.../: $ yarn g:config <workspace> <...flags> <script> <...args?> # e.g. $ yarn g:config jest -d @videre/js -v watch -- file.test.ts
Optional flags include:
(-d|--default)Passes a default argument to a script. You can pass multiple arguments with-d foo bar --.(-q|--quiet)Disables yarn runner output (perserves script output).(-v|--verbose)Enables verbose yarn runner script tracing.
Note
The default argument for g:config scripts must be the current working directory or the name/location of a workspace. This is done to allow for scripts to efficiently read and execute in the expected workspace location.
Contributions of any size to this project are always welcome!
Refer to CONTRIBUTING.md for instructions (and tips) on making contributions to this project.