1.3 KiB
stage, group, info, title
| stage | group | info | title |
|---|---|---|---|
| none | unassigned | Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/development/development_processes/#development-guidelines-review. | Frontend dependencies |
We use yarn@1 to manage frontend dependencies.
There are a few exceptions in the GitLab repository, stored in vendor/assets/.
What are production and development dependencies?
These dependencies are defined in two groups within package.json, dependencies and devDependencies.
For our purposes, we consider anything that is required to compile our production assets a "production" dependency.
That is, anything required to run the webpack script with NODE_ENV=production.
Tools like eslint, jest, and various plugins and tools used in development are considered devDependencies.
This distinction is used by omnibus to determine which dependencies it requires when building GitLab.
Exceptions are made for some tools that we require in the
compile-production-assets CI job such as webpack-bundle-analyzer to analyze our
production assets post-compile.
Updating dependencies
See the main Dependencies page for general information about dependency updates.