Team Ai
Datasetpublic

codekingpro/portable-devtools

sourceHugging Faceupdated 5mo agoView on Hugging Face
1likes14kdownloads
npm-update.html549 linesDownload Raw Back to commands
1<!DOCTYPE html><html><head>
2<meta charset="utf-8">
3<title>npm-update</title>
4<style>
5body {
6    background-color: #ffffff;
7    color: #24292e;
8
9    margin: 0;
10
11    line-height: 1.5;
12
13    font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji";
14}
15#rainbar {
16    height: 10px;
17    background-image: linear-gradient(139deg, #fb8817, #ff4b01, #c12127, #e02aff);
18}
19
20a {
21    text-decoration: none;
22    color: #0366d6;
23}
24a:hover {
25    text-decoration: underline;
26}
27
28pre {
29    margin: 1em 0px;
30    padding: 1em;
31    border: solid 1px #e1e4e8;
32    border-radius: 6px;
33
34    display: block;
35    overflow: auto;
36
37    white-space: pre;
38
39    background-color: #f6f8fa;
40    color: #393a34;
41}
42code {
43    font-family: SFMono-Regular, Consolas, "Liberation Mono", Menlo, Courier, monospace;
44    font-size: 85%;
45    padding: 0.2em 0.4em;
46    background-color: #f6f8fa;
47    color: #393a34;
48}
49pre > code {
50    padding: 0;
51    background-color: inherit;
52    color: inherit;
53}
54h1, h2, h3 {
55    font-weight: 600;
56}
57
58#logobar {
59    background-color: #333333;
60    margin: 0 auto;
61    padding: 1em 4em;
62}
63#logobar .logo {
64    float: left;
65}
66#logobar .title {
67    font-weight: 600;
68    color: #dddddd;
69    float: left;
70    margin: 5px 0 0 1em;
71}
72#logobar:after {
73    content: "";
74    display: block;
75    clear: both;
76}
77
78#content {
79    margin: 0 auto;
80    padding: 0 4em;
81}
82
83#table_of_contents > h2 {
84    font-size: 1.17em;
85}
86#table_of_contents ul:first-child {
87    border: solid 1px #e1e4e8;
88    border-radius: 6px;
89    padding: 1em;
90    background-color: #f6f8fa;
91    color: #393a34;
92}
93#table_of_contents ul {
94    list-style-type: none;
95    padding-left: 1.5em;
96}
97#table_of_contents li {
98    font-size: 0.9em;
99}
100#table_of_contents li a {
101    color: #000000;
102}
103
104header.title {
105    border-bottom: solid 1px #e1e4e8;
106}
107header.title > h1 {
108    margin-bottom: 0.25em;
109}
110header.title > .description {
111    display: block;
112    margin-bottom: 0.5em;
113    line-height: 1;
114}
115
116header.title .version {
117    font-size: 0.8em;
118    color: #666666;
119}
120
121footer#edit {
122    border-top: solid 1px #e1e4e8;
123    margin: 3em 0 4em 0;
124    padding-top: 2em;
125}
126
127table {
128    width: 100%;
129    margin: 1em 0;
130    border-radius: 6px;
131    border: 1px solid #e1e4e8;
132    overflow: hidden;
133    border-collapse: separate;
134    border-spacing: 0;
135}
136
137table thead {
138    background-color: #f6f8fa;
139}
140
141table tbody {
142    background-color: #ffffff;
143}
144
145table th,
146table td {
147    padding: 0.75em;
148    text-align: left;
149    border-right: 1px solid #e1e4e8;
150    border-bottom: 1px solid #e1e4e8;
151}
152
153table th:last-child,
154table td:last-child {
155    border-right: none;
156}
157
158table tbody tr:last-child td {
159    border-bottom: none;
160}
161
162table th {
163    font-weight: 600;
164    background-color: #f6f8fa;
165}
166
167table code {
168    white-space: nowrap;
169}
170
171</style>
172</head>
173<body>
174<div id="banner">
175<div id="rainbar"></div>
176<div id="logobar">
177<svg class="logo" role="img" height="32" width="32" viewBox="0 0 700 700">
178<polygon fill="#cb0000" points="0,700 700,700 700,0 0,0"></polygon>
179<polygon fill="#ffffff" points="150,550 350,550 350,250 450,250 450,550 550,550 550,150 150,150"></polygon>
180</svg>
181<div class="title">
182npm command-line interface
183</div>
184</div>
185</div>
186
187<section id="content">
188<header class="title">
189<h1 id="----npm-update----11121">
190    <span>npm-update</span>
191    <span class="version">@11.12.1</span>
192</h1>
193<span class="description">Update packages</span>
194</header>
195
196<section id="table_of_contents">
197<h2 id="table-of-contents">Table of contents</h2>
198<div id="_table_of_contents"><ul><li><a href="#synopsis">Synopsis</a></li><li><a href="#description">Description</a></li><li><a href="#example">Example</a></li><ul><li><a href="#caret-dependencies">Caret Dependencies</a></li><li><a href="#tilde-dependencies">Tilde Dependencies</a></li><li><a href="#caret-dependencies-below-100">Caret Dependencies below 1.0.0</a></li><li><a href="#subdependencies">Subdependencies</a></li><li><a href="#updating-globally-installed-packages">Updating Globally-Installed Packages</a></li></ul><li><a href="#configuration">Configuration</a></li><ul><li><a href="#save"><code>save</code></a></li><li><a href="#global"><code>global</code></a></li><li><a href="#install-strategy"><code>install-strategy</code></a></li><li><a href="#legacy-bundling"><code>legacy-bundling</code></a></li><li><a href="#global-style"><code>global-style</code></a></li><li><a href="#omit"><code>omit</code></a></li><li><a href="#include"><code>include</code></a></li><li><a href="#strict-peer-deps"><code>strict-peer-deps</code></a></li><li><a href="#package-lock"><code>package-lock</code></a></li><li><a href="#foreground-scripts"><code>foreground-scripts</code></a></li><li><a href="#ignore-scripts"><code>ignore-scripts</code></a></li><li><a href="#audit"><code>audit</code></a></li><li><a href="#before"><code>before</code></a></li><li><a href="#min-release-age"><code>min-release-age</code></a></li><li><a href="#bin-links"><code>bin-links</code></a></li><li><a href="#fund"><code>fund</code></a></li><li><a href="#dry-run"><code>dry-run</code></a></li><li><a href="#workspace"><code>workspace</code></a></li><li><a href="#workspaces"><code>workspaces</code></a></li><li><a href="#include-workspace-root"><code>include-workspace-root</code></a></li><li><a href="#install-links"><code>install-links</code></a></li></ul><li><a href="#see-also">See Also</a></li></ul></div>
199</section>
200
201<div id="_content"><h3 id="synopsis">Synopsis</h3>
202<pre><code class="language-bash">npm update [&lt;pkg&gt;...]
203
204aliases: up, upgrade, udpate
205</code></pre>
206<h3 id="description">Description</h3>
207<p>This command will update all the packages listed to the latest version (specified by the <a href="../using-npm/config#tag.html"><code>tag</code> config</a>), respecting the semver constraints of both your package and its dependencies (if they also require the same package).</p>
208<p>It will also install missing packages.</p>
209<p>If the <code>-g</code> flag is specified, this command will update globally installed packages.</p>
210<p>If no package name is specified, all packages in the specified location (global or local) will be updated.</p>
211<p>Note that by default <code>npm update</code> will not update the semver values of direct dependencies in your project <code>package.json</code>.
212If you want to also update values in <code>package.json</code> you can run: <code>npm update --save</code> (or add the <code>save=true</code> option to a <a href="../configuring-npm/npmrc.html">configuration file</a> to make that the default behavior).</p>
213<h3 id="example">Example</h3>
214<p>For the examples below, assume that the current package is <code>app</code> and it depends on dependencies, <code>dep1</code> (<code>dep2</code>, .. etc.).
215The published versions of <code>dep1</code> are:</p>
216<pre><code class="language-json">{
217  "dist-tags": { "latest": "1.2.2" },
218  "versions": [
219    "1.2.2",
220    "1.2.1",
221    "1.2.0",
222    "1.1.2",
223    "1.1.1",
224    "1.0.0",
225    "0.4.1",
226    "0.4.0",
227    "0.2.0"
228  ]
229}
230</code></pre>
231<h4 id="caret-dependencies">Caret Dependencies</h4>
232<p>If <code>app</code>'s <code>package.json</code> contains:</p>
233<pre><code class="language-json">"dependencies": {
234  "dep1": "^1.1.1"
235}
236</code></pre>
237<p>Then <code>npm update</code> will install <code>dep1@1.2.2</code>, because <code>1.2.2</code> is <code>latest</code> and
238<code>1.2.2</code> satisfies <code>^1.1.1</code>.</p>
239<h4 id="tilde-dependencies">Tilde Dependencies</h4>
240<p>However, if <code>app</code>'s <code>package.json</code> contains:</p>
241<pre><code class="language-json">"dependencies": {
242  "dep1": "~1.1.1"
243}
244</code></pre>
245<p>In this case, running <code>npm update</code> will install <code>dep1@1.1.2</code>.
246Even though the <code>latest</code> tag points to <code>1.2.2</code>, this version does not satisfy <code>~1.1.1</code>, which is equivalent to <code>&gt;=1.1.1 &lt;1.2.0</code>.
247So the highest-sorting version that satisfies
248<code>~1.1.1</code> is used, which is <code>1.1.2</code>.</p>
249<h4 id="caret-dependencies-below-100">Caret Dependencies below 1.0.0</h4>
250<p>Suppose <code>app</code> has a caret dependency on a version below <code>1.0.0</code>, for example:</p>
251<pre><code class="language-json">"dependencies": {
252  "dep1": "^0.2.0"
253}
254</code></pre>
255<p><code>npm update</code> will install <code>dep1@0.2.0</code>.</p>
256<p>If the dependence were on <code>^0.4.0</code>:</p>
257<pre><code class="language-json">"dependencies": {
258  "dep1": "^0.4.0"
259}
260</code></pre>
261<p>Then <code>npm update</code> will install <code>dep1@0.4.1</code>, because that is the highest-sorting version that satisfies <code>^0.4.0</code> (<code>&gt;= 0.4.0 &lt;0.5.0</code>)</p>
262<h4 id="subdependencies">Subdependencies</h4>
263<p>Suppose your app now also has a dependency on <code>dep2</code></p>
264<pre><code class="language-json">{
265  "name": "my-app",
266  "dependencies": {
267      "dep1": "^1.0.0",
268      "dep2": "1.0.0"
269  }
270}
271</code></pre>
272<p>and <code>dep2</code> itself depends on this limited range of <code>dep1</code></p>
273<pre><code class="language-json">{
274"name": "dep2",
275  "dependencies": {
276    "dep1": "~1.1.1"
277  }
278}
279</code></pre>
280<p>Then <code>npm update</code> will install <code>dep1@1.1.2</code> because that is the highest version that <code>dep2</code> allows.
281npm will prioritize having a single version of <code>dep1</code> in your tree rather than two when that single version can satisfy the semver requirements of multiple dependencies in your tree.
282In this case if you really did need your package to use a newer version you would need to use <code>npm install</code>.</p>
283<h4 id="updating-globally-installed-packages">Updating Globally-Installed Packages</h4>
284<p><code>npm update -g</code> will apply the <code>update</code> action to each globally installed package that is <code>outdated</code> -- that is, has a version that is different from <code>wanted</code>.</p>
285<p>Note: Globally installed packages are treated as if they are installed with a caret semver range specified.
286So if you require to update to <code>latest</code> you may need to run <code>npm install -g [&lt;pkg&gt;...]</code></p>
287<p>NOTE: If a package has been upgraded to a version newer than <code>latest</code>, it will be <em>downgraded</em>.</p>
288<h3 id="configuration">Configuration</h3>
289<h4 id="save"><code>save</code></h4>
290<ul>
291<li>Default: <code>true</code> unless when using <code>npm update</code> where it defaults to <code>false</code></li>
292<li>Type: Boolean</li>
293</ul>
294<p>Save installed packages to a <code>package.json</code> file as dependencies.</p>
295<p>When used with the <code>npm rm</code> command, removes the dependency from
296<code>package.json</code>.</p>
297<p>Will also prevent writing to <code>package-lock.json</code> if set to <code>false</code>.</p>
298<h4 id="global"><code>global</code></h4>
299<ul>
300<li>Default: false</li>
301<li>Type: Boolean</li>
302</ul>
303<p>Operates in "global" mode, so that packages are installed into the <code>prefix</code>
304folder instead of the current working directory. See
305<a href="../configuring-npm/folders.html">folders</a> for more on the differences in behavior.</p>
306<ul>
307<li>packages are installed into the <code>{prefix}/lib/node_modules</code> folder, instead
308of the current working directory.</li>
309<li>bin files are linked to <code>{prefix}/bin</code></li>
310<li>man pages are linked to <code>{prefix}/share/man</code></li>
311</ul>
312<h4 id="install-strategy"><code>install-strategy</code></h4>
313<ul>
314<li>Default: "hoisted"</li>
315<li>Type: "hoisted", "nested", "shallow", or "linked"</li>
316</ul>
317<p>Sets the strategy for installing packages in node_modules. hoisted
318(default): Install non-duplicated in top-level, and duplicated as necessary
319within directory structure. nested: (formerly --legacy-bundling) install in
320place, no hoisting. shallow (formerly --global-style) only install direct
321deps at top-level. linked: (experimental) install in node_modules/.store,
322link in place, unhoisted.</p>
323<h4 id="legacy-bundling"><code>legacy-bundling</code></h4>
324<ul>
325<li>Default: false</li>
326<li>Type: Boolean</li>
327<li>DEPRECATED: This option has been deprecated in favor of
328<code>--install-strategy=nested</code></li>
329</ul>
330<p>Instead of hoisting package installs in <code>node_modules</code>, install packages in
331the same manner that they are depended on. This may cause very deep
332directory structures and duplicate package installs as there is no
333de-duplicating. Sets <code>--install-strategy=nested</code>.</p>
334<h4 id="global-style"><code>global-style</code></h4>
335<ul>
336<li>Default: false</li>
337<li>Type: Boolean</li>
338<li>DEPRECATED: This option has been deprecated in favor of
339<code>--install-strategy=shallow</code></li>
340</ul>
341<p>Only install direct dependencies in the top level <code>node_modules</code>, but hoist
342on deeper dependencies. Sets <code>--install-strategy=shallow</code>.</p>
343<h4 id="omit"><code>omit</code></h4>
344<ul>
345<li>Default: 'dev' if the <code>NODE_ENV</code> environment variable is set to
346'production'; otherwise, empty.</li>
347<li>Type: "dev", "optional", or "peer" (can be set multiple times)</li>
348</ul>
349<p>Dependency types to omit from the installation tree on disk.</p>
350<p>Note that these dependencies <em>are</em> still resolved and added to the
351<code>package-lock.json</code> or <code>npm-shrinkwrap.json</code> file. They are just not
352physically installed on disk.</p>
353<p>If a package type appears in both the <code>--include</code> and <code>--omit</code> lists, then
354it will be included.</p>
355<p>If the resulting omit list includes <code>'dev'</code>, then the <code>NODE_ENV</code> environment
356variable will be set to <code>'production'</code> for all lifecycle scripts.</p>
357<h4 id="include"><code>include</code></h4>
358<ul>
359<li>Default:</li>
360<li>Type: "prod", "dev", "optional", or "peer" (can be set multiple times)</li>
361</ul>
362<p>Option that allows for defining which types of dependencies to install.</p>
363<p>This is the inverse of <code>--omit=&lt;type&gt;</code>.</p>
364<p>Dependency types specified in <code>--include</code> will not be omitted, regardless of
365the order in which omit/include are specified on the command-line.</p>
366<h4 id="strict-peer-deps"><code>strict-peer-deps</code></h4>
367<ul>
368<li>Default: false</li>
369<li>Type: Boolean</li>
370</ul>
371<p>If set to <code>true</code>, and <code>--legacy-peer-deps</code> is not set, then <em>any</em>
372conflicting <code>peerDependencies</code> will be treated as an install failure, even
373if npm could reasonably guess the appropriate resolution based on non-peer
374dependency relationships.</p>
375<p>By default, conflicting <code>peerDependencies</code> deep in the dependency graph will
376be resolved using the nearest non-peer dependency specification, even if
377doing so will result in some packages receiving a peer dependency outside
378the range set in their package's <code>peerDependencies</code> object.</p>
379<p>When such an override is performed, a warning is printed, explaining the
380conflict and the packages involved. If <code>--strict-peer-deps</code> is set, then
381this warning is treated as a failure.</p>
382<h4 id="package-lock"><code>package-lock</code></h4>
383<ul>
384<li>Default: true</li>
385<li>Type: Boolean</li>
386</ul>
387<p>If set to false, then ignore <code>package-lock.json</code> files when installing. This
388will also prevent <em>writing</em> <code>package-lock.json</code> if <code>save</code> is true.</p>
389<h4 id="foreground-scripts"><code>foreground-scripts</code></h4>
390<ul>
391<li>Default: <code>false</code> unless when using <code>npm pack</code> or <code>npm publish</code> where it
392defaults to <code>true</code></li>
393<li>Type: Boolean</li>
394</ul>
395<p>Run all build scripts (ie, <code>preinstall</code>, <code>install</code>, and <code>postinstall</code>)
396scripts for installed packages in the foreground process, sharing standard
397input, output, and error with the main npm process.</p>
398<p>Note that this will generally make installs run slower, and be much noisier,
399but can be useful for debugging.</p>
400<h4 id="ignore-scripts"><code>ignore-scripts</code></h4>
401<ul>
402<li>Default: false</li>
403<li>Type: Boolean</li>
404</ul>
405<p>If true, npm does not run scripts specified in package.json files.</p>
406<p>Note that commands explicitly intended to run a particular script, such as
407<code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run</code> will still
408run their intended script if <code>ignore-scripts</code> is set, but they will <em>not</em>
409run any pre- or post-scripts.</p>
410<h4 id="audit"><code>audit</code></h4>
411<ul>
412<li>Default: true</li>
413<li>Type: Boolean</li>
414</ul>
415<p>When "true" submit audit reports alongside the current npm command to the
416default registry and all registries configured for scopes. See the
417documentation for <a href="../commands/npm-audit.html"><code>npm audit</code></a> for details on what is
418submitted.</p>
419<h4 id="before"><code>before</code></h4>
420<ul>
421<li>Default: null</li>
422<li>Type: null or Date</li>
423</ul>
424<p>If passed to <code>npm install</code>, will rebuild the npm tree such that only
425versions that were available <strong>on or before</strong> the given date are installed.
426If there are no versions available for the current set of dependencies, the
427command will error.</p>
428<p>If the requested version is a <code>dist-tag</code> and the given tag does not pass the
429<code>--before</code> filter, the most recent version less than or equal to that tag
430will be used. For example, <code>foo@latest</code> might install <code>foo@1.2</code> even though
431<code>latest</code> is <code>2.0</code>.</p>
432<p>This config cannot be used with: <code>min-release-age</code></p>
433<h4 id="min-release-age"><code>min-release-age</code></h4>
434<ul>
435<li>Default: null</li>
436<li>Type: null or Number</li>
437</ul>
438<p>If set, npm will build the npm tree such that only versions that were
439available more than the given number of days ago will be installed. If there
440are no versions available for the current set of dependencies, the command
441will error.</p>
442<p>This flag is a complement to <code>before</code>, which accepts an exact date instead
443of a relative number of days.</p>
444<p>This config cannot be used with: <code>before</code></p>
445<p>This value is not exported to the environment for child processes.</p>
446<h4 id="bin-links"><code>bin-links</code></h4>
447<ul>
448<li>Default: true</li>
449<li>Type: Boolean</li>
450</ul>
451<p>Tells npm to create symlinks (or <code>.cmd</code> shims on Windows) for package
452executables.</p>
453<p>Set to false to have it not do this. This can be used to work around the
454fact that some file systems don't support symlinks, even on ostensibly Unix
455systems.</p>
456<h4 id="fund"><code>fund</code></h4>
457<ul>
458<li>Default: true</li>
459<li>Type: Boolean</li>
460</ul>
461<p>When "true" displays the message at the end of each <code>npm install</code>
462acknowledging the number of dependencies looking for funding. See <a href="../commands/npm-fund.html"><code>npm fund</code></a> for details.</p>
463<h4 id="dry-run"><code>dry-run</code></h4>
464<ul>
465<li>Default: false</li>
466<li>Type: Boolean</li>
467</ul>
468<p>Indicates that you don't want npm to make any changes and that it should
469only report what it would have done. This can be passed into any of the
470commands that modify your local installation, eg, <code>install</code>, <code>update</code>,
471<code>dedupe</code>, <code>uninstall</code>, as well as <code>pack</code> and <code>publish</code>.</p>
472<p>Note: This is NOT honored by other network related commands, eg <code>dist-tags</code>,
473<code>owner</code>, etc.</p>
474<h4 id="workspace"><code>workspace</code></h4>
475<ul>
476<li>Default:</li>
477<li>Type: String (can be set multiple times)</li>
478</ul>
479<p>Enable running a command in the context of the configured workspaces of the
480current project while filtering by running only the workspaces defined by
481this configuration option.</p>
482<p>Valid values for the <code>workspace</code> config are either:</p>
483<ul>
484<li>Workspace names</li>
485<li>Path to a workspace directory</li>
486<li>Path to a parent workspace directory (will result in selecting all
487workspaces within that folder)</li>
488</ul>
489<p>When set for the <code>npm init</code> command, this may be set to the folder of a
490workspace which does not yet exist, to create the folder and set it up as a
491brand new workspace within the project.</p>
492<p>This value is not exported to the environment for child processes.</p>
493<h4 id="workspaces"><code>workspaces</code></h4>
494<ul>
495<li>Default: null</li>
496<li>Type: null or Boolean</li>
497</ul>
498<p>Set to true to run the command in the context of <strong>all</strong> configured
499workspaces.</p>
500<p>Explicitly setting this to false will cause commands like <code>install</code> to
501ignore workspaces altogether. When not set explicitly:</p>
502<ul>
503<li>Commands that operate on the <code>node_modules</code> tree (install, update, etc.)
504will link workspaces into the <code>node_modules</code> folder. - Commands that do
505other things (test, exec, publish, etc.) will operate on the root project,
506<em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li>
507</ul>
508<p>This value is not exported to the environment for child processes.</p>
509<h4 id="include-workspace-root"><code>include-workspace-root</code></h4>
510<ul>
511<li>Default: false</li>
512<li>Type: Boolean</li>
513</ul>
514<p>Include the workspace root when workspaces are enabled for a command.</p>
515<p>When false, specifying individual workspaces via the <code>workspace</code> config, or
516all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on
517the specified workspaces, and not on the root project.</p>
518<p>This value is not exported to the environment for child processes.</p>
519<h4 id="install-links"><code>install-links</code></h4>
520<ul>
521<li>Default: false</li>
522<li>Type: Boolean</li>
523</ul>
524<p>When set file: protocol dependencies will be packed and installed as regular
525dependencies instead of creating a symlink. This option has no effect on
526workspaces.</p>
527<h3 id="see-also">See Also</h3>
528<ul>
529<li><a href="../commands/npm-install.html">npm install</a></li>
530<li><a href="../commands/npm-outdated.html">npm outdated</a></li>
531<li><a href="../commands/npm-shrinkwrap.html">npm shrinkwrap</a></li>
532<li><a href="../using-npm/registry.html">npm registry</a></li>
533<li><a href="../configuring-npm/folders.html">npm folders</a></li>
534<li><a href="../commands/npm-ls.html">npm ls</a></li>
535</ul></div>
536
537<footer id="edit">
538<a href="https://github.com/npm/cli/edit/latest/docs/lib/content/commands/npm-update.md">
539<svg role="img" viewBox="0 0 16 16" width="16" height="16" fill="currentcolor" style="vertical-align: text-bottom; margin-right: 0.3em;">
540<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>
541</svg>
542Edit this page on GitHub
543</a>
544</footer>
545</section>
546
547
548
549</body></html>
codekingpro/portable-devtools · Team Ai