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.
Docs
Edit this page to fix an error or add an improvement in a merge request.
Create an issue to suggest an improvement to this page.
Product
Create an issue if there's something you don't like about this feature.
Propose functionality by submitting a feature request.
Feature availability and product trials
View pricing to see all GitLab tiers and features, or to upgrade.
Try GitLab for free with access to all features for 30 days.
Get help
If you didn't find what you were looking for, search the docs.
If you want help with something specific and could use community support, post on the GitLab forum.
For problems setting up or using this feature (depending on your GitLab subscription).
Request support