11cb0ef41Sopenharmony_ci<!DOCTYPE html><html><head>
21cb0ef41Sopenharmony_ci<meta charset="utf-8">
31cb0ef41Sopenharmony_ci<title>workspaces</title>
41cb0ef41Sopenharmony_ci<style>
51cb0ef41Sopenharmony_cibody {
61cb0ef41Sopenharmony_ci    background-color: #ffffff;
71cb0ef41Sopenharmony_ci    color: #24292e;
81cb0ef41Sopenharmony_ci
91cb0ef41Sopenharmony_ci    margin: 0;
101cb0ef41Sopenharmony_ci
111cb0ef41Sopenharmony_ci    line-height: 1.5;
121cb0ef41Sopenharmony_ci
131cb0ef41Sopenharmony_ci    font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji";
141cb0ef41Sopenharmony_ci}
151cb0ef41Sopenharmony_ci#rainbar {
161cb0ef41Sopenharmony_ci    height: 10px;
171cb0ef41Sopenharmony_ci    background-image: linear-gradient(139deg, #fb8817, #ff4b01, #c12127, #e02aff);
181cb0ef41Sopenharmony_ci}
191cb0ef41Sopenharmony_ci
201cb0ef41Sopenharmony_cia {
211cb0ef41Sopenharmony_ci    text-decoration: none;
221cb0ef41Sopenharmony_ci    color: #0366d6;
231cb0ef41Sopenharmony_ci}
241cb0ef41Sopenharmony_cia:hover {
251cb0ef41Sopenharmony_ci    text-decoration: underline;
261cb0ef41Sopenharmony_ci}
271cb0ef41Sopenharmony_ci
281cb0ef41Sopenharmony_cipre {
291cb0ef41Sopenharmony_ci    margin: 1em 0px;
301cb0ef41Sopenharmony_ci    padding: 1em;
311cb0ef41Sopenharmony_ci    border: solid 1px #e1e4e8;
321cb0ef41Sopenharmony_ci    border-radius: 6px;
331cb0ef41Sopenharmony_ci
341cb0ef41Sopenharmony_ci    display: block;
351cb0ef41Sopenharmony_ci    overflow: auto;
361cb0ef41Sopenharmony_ci
371cb0ef41Sopenharmony_ci    white-space: pre;
381cb0ef41Sopenharmony_ci
391cb0ef41Sopenharmony_ci    background-color: #f6f8fa;
401cb0ef41Sopenharmony_ci    color: #393a34;
411cb0ef41Sopenharmony_ci}
421cb0ef41Sopenharmony_cicode {
431cb0ef41Sopenharmony_ci    font-family: SFMono-Regular, Consolas, "Liberation Mono", Menlo, Courier, monospace;
441cb0ef41Sopenharmony_ci    font-size: 85%;
451cb0ef41Sopenharmony_ci    padding: 0.2em 0.4em;
461cb0ef41Sopenharmony_ci    background-color: #f6f8fa;
471cb0ef41Sopenharmony_ci    color: #393a34;
481cb0ef41Sopenharmony_ci}
491cb0ef41Sopenharmony_cipre > code {
501cb0ef41Sopenharmony_ci    padding: 0;
511cb0ef41Sopenharmony_ci    background-color: inherit;
521cb0ef41Sopenharmony_ci    color: inherit;
531cb0ef41Sopenharmony_ci}
541cb0ef41Sopenharmony_cih1, h2, h3 {
551cb0ef41Sopenharmony_ci    font-weight: 600;
561cb0ef41Sopenharmony_ci}
571cb0ef41Sopenharmony_ci
581cb0ef41Sopenharmony_ci#logobar {
591cb0ef41Sopenharmony_ci    background-color: #333333;
601cb0ef41Sopenharmony_ci    margin: 0 auto;
611cb0ef41Sopenharmony_ci    padding: 1em 4em;
621cb0ef41Sopenharmony_ci}
631cb0ef41Sopenharmony_ci#logobar .logo {
641cb0ef41Sopenharmony_ci    float: left;
651cb0ef41Sopenharmony_ci}
661cb0ef41Sopenharmony_ci#logobar .title {
671cb0ef41Sopenharmony_ci    font-weight: 600;
681cb0ef41Sopenharmony_ci    color: #dddddd;
691cb0ef41Sopenharmony_ci    float: left;
701cb0ef41Sopenharmony_ci    margin: 5px 0 0 1em;
711cb0ef41Sopenharmony_ci}
721cb0ef41Sopenharmony_ci#logobar:after {
731cb0ef41Sopenharmony_ci    content: "";
741cb0ef41Sopenharmony_ci    display: block;
751cb0ef41Sopenharmony_ci    clear: both;
761cb0ef41Sopenharmony_ci}
771cb0ef41Sopenharmony_ci
781cb0ef41Sopenharmony_ci#content {
791cb0ef41Sopenharmony_ci    margin: 0 auto;
801cb0ef41Sopenharmony_ci    padding: 0 4em;
811cb0ef41Sopenharmony_ci}
821cb0ef41Sopenharmony_ci
831cb0ef41Sopenharmony_ci#table_of_contents > h2 {
841cb0ef41Sopenharmony_ci    font-size: 1.17em;
851cb0ef41Sopenharmony_ci}
861cb0ef41Sopenharmony_ci#table_of_contents ul:first-child {
871cb0ef41Sopenharmony_ci    border: solid 1px #e1e4e8;
881cb0ef41Sopenharmony_ci    border-radius: 6px;
891cb0ef41Sopenharmony_ci    padding: 1em;
901cb0ef41Sopenharmony_ci    background-color: #f6f8fa;
911cb0ef41Sopenharmony_ci    color: #393a34;
921cb0ef41Sopenharmony_ci}
931cb0ef41Sopenharmony_ci#table_of_contents ul {
941cb0ef41Sopenharmony_ci    list-style-type: none;
951cb0ef41Sopenharmony_ci    padding-left: 1.5em;
961cb0ef41Sopenharmony_ci}
971cb0ef41Sopenharmony_ci#table_of_contents li {
981cb0ef41Sopenharmony_ci    font-size: 0.9em;
991cb0ef41Sopenharmony_ci}
1001cb0ef41Sopenharmony_ci#table_of_contents li a {
1011cb0ef41Sopenharmony_ci    color: #000000;
1021cb0ef41Sopenharmony_ci}
1031cb0ef41Sopenharmony_ci
1041cb0ef41Sopenharmony_ciheader.title {
1051cb0ef41Sopenharmony_ci    border-bottom: solid 1px #e1e4e8;
1061cb0ef41Sopenharmony_ci}
1071cb0ef41Sopenharmony_ciheader.title > h1 {
1081cb0ef41Sopenharmony_ci    margin-bottom: 0.25em;
1091cb0ef41Sopenharmony_ci}
1101cb0ef41Sopenharmony_ciheader.title > .description {
1111cb0ef41Sopenharmony_ci    display: block;
1121cb0ef41Sopenharmony_ci    margin-bottom: 0.5em;
1131cb0ef41Sopenharmony_ci    line-height: 1;
1141cb0ef41Sopenharmony_ci}
1151cb0ef41Sopenharmony_ci
1161cb0ef41Sopenharmony_cifooter#edit {
1171cb0ef41Sopenharmony_ci    border-top: solid 1px #e1e4e8;
1181cb0ef41Sopenharmony_ci    margin: 3em 0 4em 0;
1191cb0ef41Sopenharmony_ci    padding-top: 2em;
1201cb0ef41Sopenharmony_ci}
1211cb0ef41Sopenharmony_ci</style>
1221cb0ef41Sopenharmony_ci</head>
1231cb0ef41Sopenharmony_ci<body>
1241cb0ef41Sopenharmony_ci<div id="banner">
1251cb0ef41Sopenharmony_ci<div id="rainbar"></div>
1261cb0ef41Sopenharmony_ci<div id="logobar">
1271cb0ef41Sopenharmony_ci<svg class="logo" role="img" height="32" width="32" viewBox="0 0 700 700">
1281cb0ef41Sopenharmony_ci<polygon fill="#cb0000" points="0,700 700,700 700,0 0,0"></polygon>
1291cb0ef41Sopenharmony_ci<polygon fill="#ffffff" points="150,550 350,550 350,250 450,250 450,550 550,550 550,150 150,150"></polygon>
1301cb0ef41Sopenharmony_ci</svg>
1311cb0ef41Sopenharmony_ci<div class="title">
1321cb0ef41Sopenharmony_cinpm command-line interface
1331cb0ef41Sopenharmony_ci</div>
1341cb0ef41Sopenharmony_ci</div>
1351cb0ef41Sopenharmony_ci</div>
1361cb0ef41Sopenharmony_ci
1371cb0ef41Sopenharmony_ci<section id="content">
1381cb0ef41Sopenharmony_ci<header class="title">
1391cb0ef41Sopenharmony_ci<h1 id="workspaces">workspaces</h1>
1401cb0ef41Sopenharmony_ci<span class="description">Working with workspaces</span>
1411cb0ef41Sopenharmony_ci</header>
1421cb0ef41Sopenharmony_ci
1431cb0ef41Sopenharmony_ci<section id="table_of_contents">
1441cb0ef41Sopenharmony_ci<h2 id="table-of-contents">Table of contents</h2>
1451cb0ef41Sopenharmony_ci<div id="_table_of_contents"><ul><li><a href="#description">Description</a></li><li><a href="#defining-workspaces">Defining workspaces</a></li><li><a href="#getting-started-with-workspaces">Getting started with workspaces</a></li><li><a href="#adding-dependencies-to-a-workspace">Adding dependencies to a workspace</a></li><li><a href="#using-workspaces">Using workspaces</a></li><li><a href="#running-commands-in-the-context-of-workspaces">Running commands in the context of workspaces</a></li><li><a href="#ignoring-missing-scripts">Ignoring missing scripts</a></li><li><a href="#see-also">See also</a></li></ul></div>
1461cb0ef41Sopenharmony_ci</section>
1471cb0ef41Sopenharmony_ci
1481cb0ef41Sopenharmony_ci<div id="_content"><h3 id="description">Description</h3>
1491cb0ef41Sopenharmony_ci<p><strong>Workspaces</strong> is a generic term that refers to the set of features in the
1501cb0ef41Sopenharmony_cinpm cli that provides support for managing multiple packages from your local
1511cb0ef41Sopenharmony_cifile system from within a singular top-level, root package.</p>
1521cb0ef41Sopenharmony_ci<p>This set of features makes up for a much more streamlined workflow handling
1531cb0ef41Sopenharmony_cilinked packages from the local file system. It automates the linking process
1541cb0ef41Sopenharmony_cias part of <code>npm install</code> and removes the need to manually use <code>npm link</code> in
1551cb0ef41Sopenharmony_ciorder to add references to packages that should be symlinked into the current
1561cb0ef41Sopenharmony_ci<code>node_modules</code> folder.</p>
1571cb0ef41Sopenharmony_ci<p>We also refer to these packages being auto-symlinked during <code>npm install</code> as a
1581cb0ef41Sopenharmony_cisingle <strong>workspace</strong>, meaning it's a nested package within the current local
1591cb0ef41Sopenharmony_cifile system that is explicitly defined in the <a href="../configuring-npm/package-json#workspaces.html"><code>package.json</code></a>
1601cb0ef41Sopenharmony_ci<code>workspaces</code> configuration.</p>
1611cb0ef41Sopenharmony_ci<h3 id="defining-workspaces">Defining workspaces</h3>
1621cb0ef41Sopenharmony_ci<p>Workspaces are usually defined via the <code>workspaces</code> property of the
1631cb0ef41Sopenharmony_ci<a href="../configuring-npm/package-json#workspaces.html"><code>package.json</code></a> file, e.g:</p>
1641cb0ef41Sopenharmony_ci<pre><code class="language-json">{
1651cb0ef41Sopenharmony_ci  "name": "my-workspaces-powered-project",
1661cb0ef41Sopenharmony_ci  "workspaces": [
1671cb0ef41Sopenharmony_ci    "packages/a"
1681cb0ef41Sopenharmony_ci  ]
1691cb0ef41Sopenharmony_ci}
1701cb0ef41Sopenharmony_ci</code></pre>
1711cb0ef41Sopenharmony_ci<p>Given the above <code>package.json</code> example living at a current working
1721cb0ef41Sopenharmony_cidirectory <code>.</code> that contains a folder named <code>packages/a</code> that itself contains
1731cb0ef41Sopenharmony_cia <code>package.json</code> inside it, defining a Node.js package, e.g:</p>
1741cb0ef41Sopenharmony_ci<pre><code>.
1751cb0ef41Sopenharmony_ci+-- package.json
1761cb0ef41Sopenharmony_ci`-- packages
1771cb0ef41Sopenharmony_ci   +-- a
1781cb0ef41Sopenharmony_ci   |   `-- package.json
1791cb0ef41Sopenharmony_ci</code></pre>
1801cb0ef41Sopenharmony_ci<p>The expected result once running <code>npm install</code> in this current working
1811cb0ef41Sopenharmony_cidirectory <code>.</code> is that the folder <code>packages/a</code> will get symlinked to the
1821cb0ef41Sopenharmony_ci<code>node_modules</code> folder of the current working dir.</p>
1831cb0ef41Sopenharmony_ci<p>Below is a post <code>npm install</code> example, given that same previous example
1841cb0ef41Sopenharmony_cistructure of files and folders:</p>
1851cb0ef41Sopenharmony_ci<pre><code>.
1861cb0ef41Sopenharmony_ci+-- node_modules
1871cb0ef41Sopenharmony_ci|  `-- a -&gt; ../packages/a
1881cb0ef41Sopenharmony_ci+-- package-lock.json
1891cb0ef41Sopenharmony_ci+-- package.json
1901cb0ef41Sopenharmony_ci`-- packages
1911cb0ef41Sopenharmony_ci   +-- a
1921cb0ef41Sopenharmony_ci   |   `-- package.json
1931cb0ef41Sopenharmony_ci</code></pre>
1941cb0ef41Sopenharmony_ci<h3 id="getting-started-with-workspaces">Getting started with workspaces</h3>
1951cb0ef41Sopenharmony_ci<p>You may automate the required steps to define a new workspace using
1961cb0ef41Sopenharmony_ci<a href="../commands/npm-init.html">npm init</a>. For example in a project that already has a
1971cb0ef41Sopenharmony_ci<code>package.json</code> defined you can run:</p>
1981cb0ef41Sopenharmony_ci<pre><code>npm init -w ./packages/a
1991cb0ef41Sopenharmony_ci</code></pre>
2001cb0ef41Sopenharmony_ci<p>This command will create the missing folders and a new <code>package.json</code>
2011cb0ef41Sopenharmony_cifile (if needed) while also making sure to properly configure the
2021cb0ef41Sopenharmony_ci<code>"workspaces"</code> property of your root project <code>package.json</code>.</p>
2031cb0ef41Sopenharmony_ci<h3 id="adding-dependencies-to-a-workspace">Adding dependencies to a workspace</h3>
2041cb0ef41Sopenharmony_ci<p>It's possible to directly add/remove/update dependencies of your workspaces
2051cb0ef41Sopenharmony_ciusing the <a href="../using-npm/config#workspace.html"><code>workspace</code> config</a>.</p>
2061cb0ef41Sopenharmony_ci<p>For example, assuming the following structure:</p>
2071cb0ef41Sopenharmony_ci<pre><code>.
2081cb0ef41Sopenharmony_ci+-- package.json
2091cb0ef41Sopenharmony_ci`-- packages
2101cb0ef41Sopenharmony_ci   +-- a
2111cb0ef41Sopenharmony_ci   |   `-- package.json
2121cb0ef41Sopenharmony_ci   `-- b
2131cb0ef41Sopenharmony_ci       `-- package.json
2141cb0ef41Sopenharmony_ci</code></pre>
2151cb0ef41Sopenharmony_ci<p>If you want to add a dependency named <code>abbrev</code> from the registry as a
2161cb0ef41Sopenharmony_cidependency of your workspace <strong>a</strong>, you may use the workspace config to tell
2171cb0ef41Sopenharmony_cithe npm installer that package should be added as a dependency of the provided
2181cb0ef41Sopenharmony_ciworkspace:</p>
2191cb0ef41Sopenharmony_ci<pre><code>npm install abbrev -w a
2201cb0ef41Sopenharmony_ci</code></pre>
2211cb0ef41Sopenharmony_ci<p>Note: other installing commands such as <code>uninstall</code>, <code>ci</code>, etc will also
2221cb0ef41Sopenharmony_cirespect the provided <code>workspace</code> configuration.</p>
2231cb0ef41Sopenharmony_ci<h3 id="using-workspaces">Using workspaces</h3>
2241cb0ef41Sopenharmony_ci<p>Given the <a href="https://nodejs.org/dist/latest-v14.x/docs/api/modules.html#modules_all_together">specifics of how Node.js handles module resolution</a> it's possible to consume any defined workspace
2251cb0ef41Sopenharmony_ciby its declared <code>package.json</code> <code>name</code>. Continuing from the example defined
2261cb0ef41Sopenharmony_ciabove, let's also create a Node.js script that will require the workspace <code>a</code>
2271cb0ef41Sopenharmony_ciexample module, e.g:</p>
2281cb0ef41Sopenharmony_ci<pre><code>// ./packages/a/index.js
2291cb0ef41Sopenharmony_cimodule.exports = 'a'
2301cb0ef41Sopenharmony_ci
2311cb0ef41Sopenharmony_ci// ./lib/index.js
2321cb0ef41Sopenharmony_ciconst moduleA = require('a')
2331cb0ef41Sopenharmony_ciconsole.log(moduleA) // -&gt; a
2341cb0ef41Sopenharmony_ci</code></pre>
2351cb0ef41Sopenharmony_ci<p>When running it with:</p>
2361cb0ef41Sopenharmony_ci<p><code>node lib/index.js</code></p>
2371cb0ef41Sopenharmony_ci<p>This demonstrates how the nature of <code>node_modules</code> resolution allows for
2381cb0ef41Sopenharmony_ci<strong>workspaces</strong> to enable a portable workflow for requiring each <strong>workspace</strong>
2391cb0ef41Sopenharmony_ciin such a way that is also easy to <a href="../commands/npm-publish.html">publish</a> these
2401cb0ef41Sopenharmony_cinested workspaces to be consumed elsewhere.</p>
2411cb0ef41Sopenharmony_ci<h3 id="running-commands-in-the-context-of-workspaces">Running commands in the context of workspaces</h3>
2421cb0ef41Sopenharmony_ci<p>You can use the <code>workspace</code> configuration option to run commands in the context
2431cb0ef41Sopenharmony_ciof a configured workspace.
2441cb0ef41Sopenharmony_ciAdditionally, if your current directory is in a workspace, the <code>workspace</code>
2451cb0ef41Sopenharmony_ciconfiguration is implicitly set, and <code>prefix</code> is set to the root workspace.</p>
2461cb0ef41Sopenharmony_ci<p>Following is a quick example on how to use the <code>npm run</code> command in the context
2471cb0ef41Sopenharmony_ciof nested workspaces. For a project containing multiple workspaces, e.g:</p>
2481cb0ef41Sopenharmony_ci<pre><code>.
2491cb0ef41Sopenharmony_ci+-- package.json
2501cb0ef41Sopenharmony_ci`-- packages
2511cb0ef41Sopenharmony_ci   +-- a
2521cb0ef41Sopenharmony_ci   |   `-- package.json
2531cb0ef41Sopenharmony_ci   `-- b
2541cb0ef41Sopenharmony_ci       `-- package.json
2551cb0ef41Sopenharmony_ci</code></pre>
2561cb0ef41Sopenharmony_ci<p>By running a command using the <code>workspace</code> option, it's possible to run the
2571cb0ef41Sopenharmony_cigiven command in the context of that specific workspace. e.g:</p>
2581cb0ef41Sopenharmony_ci<pre><code>npm run test --workspace=a
2591cb0ef41Sopenharmony_ci</code></pre>
2601cb0ef41Sopenharmony_ci<p>You could also run the command within the workspace.</p>
2611cb0ef41Sopenharmony_ci<pre><code>cd packages/a &amp;&amp; npm run test
2621cb0ef41Sopenharmony_ci</code></pre>
2631cb0ef41Sopenharmony_ci<p>Either will run the <code>test</code> script defined within the
2641cb0ef41Sopenharmony_ci<code>./packages/a/package.json</code> file.</p>
2651cb0ef41Sopenharmony_ci<p>Please note that you can also specify this argument multiple times in the
2661cb0ef41Sopenharmony_cicommand-line in order to target multiple workspaces, e.g:</p>
2671cb0ef41Sopenharmony_ci<pre><code>npm run test --workspace=a --workspace=b
2681cb0ef41Sopenharmony_ci</code></pre>
2691cb0ef41Sopenharmony_ci<p>Or run the command for each workspace within the 'packages' folder:</p>
2701cb0ef41Sopenharmony_ci<pre><code>npm run test --workspace=packages
2711cb0ef41Sopenharmony_ci</code></pre>
2721cb0ef41Sopenharmony_ci<p>It's also possible to use the <code>workspaces</code> (plural) configuration option to
2731cb0ef41Sopenharmony_cienable the same behavior but running that command in the context of <strong>all</strong>
2741cb0ef41Sopenharmony_ciconfigured workspaces. e.g:</p>
2751cb0ef41Sopenharmony_ci<pre><code>npm run test --workspaces
2761cb0ef41Sopenharmony_ci</code></pre>
2771cb0ef41Sopenharmony_ci<p>Will run the <code>test</code> script in both <code>./packages/a</code> and <code>./packages/b</code>.</p>
2781cb0ef41Sopenharmony_ci<p>Commands will be run in each workspace in the order they appear in your <code>package.json</code></p>
2791cb0ef41Sopenharmony_ci<pre><code>{
2801cb0ef41Sopenharmony_ci  "workspaces": [ "packages/a", "packages/b" ]
2811cb0ef41Sopenharmony_ci}
2821cb0ef41Sopenharmony_ci</code></pre>
2831cb0ef41Sopenharmony_ci<p>Order of run is different with:</p>
2841cb0ef41Sopenharmony_ci<pre><code>{
2851cb0ef41Sopenharmony_ci  "workspaces": [ "packages/b", "packages/a" ]
2861cb0ef41Sopenharmony_ci}
2871cb0ef41Sopenharmony_ci</code></pre>
2881cb0ef41Sopenharmony_ci<h3 id="ignoring-missing-scripts">Ignoring missing scripts</h3>
2891cb0ef41Sopenharmony_ci<p>It is not required for all of the workspaces to implement scripts run with the <code>npm run</code> command.</p>
2901cb0ef41Sopenharmony_ci<p>By running the command with the <code>--if-present</code> flag, npm will ignore workspaces missing target script.</p>
2911cb0ef41Sopenharmony_ci<pre><code>npm run test --workspaces --if-present
2921cb0ef41Sopenharmony_ci</code></pre>
2931cb0ef41Sopenharmony_ci<h3 id="see-also">See also</h3>
2941cb0ef41Sopenharmony_ci<ul>
2951cb0ef41Sopenharmony_ci<li><a href="../commands/npm-install.html">npm install</a></li>
2961cb0ef41Sopenharmony_ci<li><a href="../commands/npm-publish.html">npm publish</a></li>
2971cb0ef41Sopenharmony_ci<li><a href="../commands/npm-run-script.html">npm run-script</a></li>
2981cb0ef41Sopenharmony_ci<li><a href="../using-npm/config.html">config</a></li>
2991cb0ef41Sopenharmony_ci</ul></div>
3001cb0ef41Sopenharmony_ci
3011cb0ef41Sopenharmony_ci<footer id="edit">
3021cb0ef41Sopenharmony_ci<a href="https://github.com/npm/cli/edit/latest/docs/content/using-npm/workspaces.md">
3031cb0ef41Sopenharmony_ci<svg role="img" viewBox="0 0 16 16" width="16" height="16" fill="currentcolor" style="vertical-align: text-bottom; margin-right: 0.3em;">
3041cb0ef41Sopenharmony_ci<path fill-rule="evenodd" d="M11.013 1.427a1.75 1.75 0 012.474 0l1.086 1.086a1.75 1.75 0 010 2.474l-8.61 8.61c-.21.21-.47.364-.756.445l-3.251.93a.75.75 0 01-.927-.928l.929-3.25a1.75 1.75 0 01.445-.758l8.61-8.61zm1.414 1.06a.25.25 0 00-.354 0L10.811 3.75l1.439 1.44 1.263-1.263a.25.25 0 000-.354l-1.086-1.086zM11.189 6.25L9.75 4.81l-6.286 6.287a.25.25 0 00-.064.108l-.558 1.953 1.953-.558a.249.249 0 00.108-.064l6.286-6.286z"></path>
3051cb0ef41Sopenharmony_ci</svg>
3061cb0ef41Sopenharmony_ciEdit this page on GitHub
3071cb0ef41Sopenharmony_ci</a>
3081cb0ef41Sopenharmony_ci</footer>
3091cb0ef41Sopenharmony_ci</section>
3101cb0ef41Sopenharmony_ci
3111cb0ef41Sopenharmony_ci
3121cb0ef41Sopenharmony_ci
3131cb0ef41Sopenharmony_ci</body></html>