<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Monorepo on Janik von Rotz</title>
    <link>https://janikvonrotz.ch/tags/monorepo/</link>
    <description>Recent content in Monorepo on Janik von Rotz</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 13 Dec 2019 18:17:28 +0100</lastBuildDate>
    <atom:link href="https://janikvonrotz.ch/tags/monorepo/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Build multiple Docker image from Yarn workspace packages</title>
      <link>https://janikvonrotz.ch/2019/12/13/build-multiple-docker-images-from-yarn-workspace-packages/</link>
      <pubDate>Fri, 13 Dec 2019 18:17:28 +0100</pubDate>
      <guid>https://janikvonrotz.ch/2019/12/13/build-multiple-docker-images-from-yarn-workspace-packages/</guid>
      <description>&lt;p&gt;If you decide to manage your node application repository as a monorepo you sure heard about &lt;a href=&#34;https://yarnpkg.com/lang/en/docs/workspaces/&#34;&gt;Yarn workspaces&lt;/a&gt;. Yarn has an out-of-the-box support for managing multiple packages in a single codebase. Using yarn workspaces package dependencies can be centralized and packages can reference each other. Tasks can be executed for all packages at once. It solves various build related problems for a monorepo.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
