深海游弋的鱼 – 默默的点滴

鸿蒙应用开发：提升性能的利器——防抖与节流

为了应对频繁的事件调用所带来的性能瓶颈，我们需要引入防抖（debounce）和节流（throttle）这两个利器。

防抖：抑制不必要的高频事件

防抖是一种技术，它可以在一定时间内抑制不必要的高频事件。在鸿蒙应用开发中，防抖可以用来优化事件处理，例如按钮点击事件。

防抖的工作原理是：当一个事件被频繁调用时，防抖函数会将事件放入一个计时器中。在这个计时器中，事件将在一个指定的等待时间后执行。如果在等待时间内又收到了该事件的调用，那么计时器将被重新设置，等待时间将从头开始计算。

节流：限制事件调用的频率

节流是一种技术，它可以限制事件调用的频率。在鸿蒙应用开发中，节流可以用来优化输入框中的输入事件处理。

节流的工作原理是：当一个事件被频繁调用时，节流函数会将事件放入一个令牌桶中。在这个令牌桶中，事件将按照一个固定的速度执行。如果令牌桶已满，那么事件将被丢弃。

防抖与节流的比较

防抖和节流都是用来处理高频事件的利器，但是它们的工作方式不同。

防抖： 在一定时间内只执行一次事件。
节流： 以固定的速度执行事件，丢弃多余的事件。

在鸿蒙应用开发中的应用

防抖和节流可以在鸿蒙应用开发中得到以下应用：

事件处理： 防抖可以用来优化按钮点击事件等高频事件的处理，避免不必要的高频调用。
输入框输入： 节流可以用来限制输入框中输入事件的频率，避免不必要的多余请求。
网络请求： 防抖和节流可以用来优化网络请求，避免不必要的多余请求。
滚动事件： 节流可以用来限制滚动事件的频率，避免不必要的高频调用。

示例代码

/** 
 * 防抖函数
 *
 * 用法：
 *
 * Text() {
 *  Span($r("app.string.text"))
 * }
 * .onClick(debounce(() => {
 *  // do click
 * }))
 *
 * @param fn { Function } 需要进行防抖处理的函数
 * @param debounceMs { number } 防抖限制的时间，单位（毫秒）
 */
export function debounce(fn: Function, debounceMs: number = 100) {
  let timer: number = 0;
  let cancelTimer = false;
  return () => {
    if (cancelTimer) {
      clearTimeout(timer);
      cancelTimer = false;
    }
    timer = setTimeout(() => {
      timer = 0;
      cancelTimer = false;
      fn();
    }, debounceMs);
    cancelTimer = true;
  };
}

/**
 * 节流函数
 *
 * 注意：要求第一次事件发生的时候立即执行，然后再进行节流操作
 * 
 * 如果先节流后执行会导致用户感觉到明显的响应延迟，造成响应卡顿的假象
 *
 * 用法：
 *
 * Text() {
 *  Span($r("app.string.text"))
 * }
 * .onClick(throttle(() => {
 *  // do click
 * }))
 *
 * @param fn { Function } 需要进行节流处理的函数
 * @param throttleMs { number } 节流限制的时间，单位（毫秒）
 */
export function throttle(fn: Function, throttleMs: number = 200) {
  let drop = false;
  return () => {
    if (!drop) {
      drop = true;
      setTimeout(() => {
        drop = false;
      }, throttleMs);
      fn();
    }
  };
}

/**

* 防抖函数

* 用法：

* Text() {

* Span($r("app.string.text"))

* }

* .onClick(debounce(() => {

* // do click

* }))

* @param fn { Function } 需要进行防抖处理的函数

* @param debounceMs { number } 防抖限制的时间，单位（毫秒）

export function debounce(fn: Function, debounceMs: number = 100) {

let timer: number = 0;

let cancelTimer = false;

return () => {

if (cancelTimer) {

clearTimeout(timer);

cancelTimer = false;

}

timer = setTimeout(() => {

timer = 0;

cancelTimer = false;

fn();

}, debounceMs);

cancelTimer = true;

};

}

/**

* 节流函数

* 注意：要求第一次事件发生的时候立即执行，然后再进行节流操作

* 如果先节流后执行会导致用户感觉到明显的响应延迟，造成响应卡顿的假象

* 用法：

* Text() {

* Span($r("app.string.text"))

* }

* .onClick(throttle(() => {

* // do click

* }))

* @param fn { Function } 需要进行节流处理的函数

* @param throttleMs { number } 节流限制的时间，单位（毫秒）

export function throttle(fn: Function, throttleMs: number = 200) {

let drop = false;

return () => {

if (!drop) {

drop = true;

setTimeout(() => {

drop = false;

}, throttleMs);

fn();

}

};

}

总结

防抖和节流是鸿蒙应用开发中提升性能的利器。通过合理使用防抖和节流，可以有效优化事件处理、输入框输入、网络请求和滚动事件，从而提升应用的整体性能和用户体验。

参考链接

Compare Arrays in JavaScript

HarmonyOS NEXT 系统推荐使用 Lodash 库，更符合开发直觉。

ohpm install lodash

1	ohpm install lodash

Arrays are objects in JavaScript, so the triple equals operator === only returns true if the arrays are the same reference.

const a = [1, 2, 3];
const b = [1, 2, 3];

a === a; // true
a === b; // false

const a = [1, 2, 3];

const b = [1, 2, 3];

a === a; // true

a === b; // false

How do you compare whether two arrays are equal? Equality is a tricky subject: the JavaScript spec defines 4 different ways of checking if two values are "equal", and that doesn't take into account deep equality between objects.

In cases like this, it helps to be as explicit as possible about what you mean by "equal." In software engineering, asking a question in the right way often makes the answer obvious.

With that in mind, here's 3 definitions of equality for arrays and how to check them.

Same Length, Each Value Equal

One approach for comparing a and b is checking if each value of a is strictly equal to the corresponding value of b. This works well if all the elements of the arrays are primitives as opposed to objects.

const a = [1, 2, 3];
const b = [4, 5, 6];
const c = [1, 2, 3];

function arrayEquals(a, b) {
  return Array.isArray(a) &&
    Array.isArray(b) &&
    a.length === b.length &&
    a.every((val, index) => val === b[index]);
}

arrayEquals(a, b); // false
arrayEquals(a, c); // true

const a = [1, 2, 3];

const b = [4, 5, 6];

const c = [1, 2, 3];

function arrayEquals(a, b) {

return Array.isArray(a) &&

Array.isArray(b) &&

a.length === b.length &&

a.every((val, index) => val === b[index]);

}

arrayEquals(a, b); // false

arrayEquals(a, c); // true

Deep Equality With POJOs

The previous arrayEquals() function works great for primitive values, but falls short if you want to compare objects by value.

const a = [{ answer: 42 }, { powerLevel: 9001 }];
const b = [{ answer: 42 }, { powerLevel: 9001 }];

// false, because { answer: 42 } !== { answer: 42 }, different references
arrayEquals(a, b);

const a = [{ answer: 42 }, { powerLevel: 9001 }];

const b = [{ answer: 42 }, { powerLevel: 9001 }];

// false, because { answer: 42 } !== { answer: 42 }, different references

arrayEquals(a, b);

One neat way to take into account object values is comparing arrays by their JSON.stringify() output.

const a = [{ answer: 42 }, { powerLevel: 9001 }];
const b = [{ answer: 42 }, { powerLevel: 9001 }];
const c = [{ answer: 42 }, { password: 'taco' }];

JSON.stringify(a) === JSON.stringify(b); // true
JSON.stringify(a) === JSON.stringify(c); // false

const a = [{ answer: 42 }, { powerLevel: 9001 }];

const b = [{ answer: 42 }, { powerLevel: 9001 }];

const c = [{ answer: 42 }, { password: 'taco' }];

JSON.stringify(a) === JSON.stringify(b); // true

JSON.stringify(a) === JSON.stringify(c); // false

This approach is handy because it requires minimal code and no outside libraries. However, comparing JSON.stringify() output has an unfortunate edge case that may be a problem depending on your use case. Since undefined isn't a valid JSON value, the below arrays have the same JSON.stringify() output, because JSON.stringify() converts undefined to null.

const a = [undefined];
const b = [null];

1 2	const a = [undefined]; const b = [null];

Using Lodash's `isEqual()`

In addition to the null vs undefined quirk, comparing JSON.stringify() output also doesn't take into account object types. As far as JSON.stringify() is concerned, an object with a toJSON() function that returns 42 is the same as the number 42.

const a = [{ toJSON: () => 42 }];
const b = [42];

JSON.stringify(a); // '[42]'
JSON.stringify(b); // '[42]'

const a = [{ toJSON: () => 42 }];

const b = [42];

JSON.stringify(a); // '[42]'

JSON.stringify(b); // '[42]'

Similarly, a custom object is the same as a POJO:

class MyClass {
  constructor(obj) {
    Object.assign(this, obj);
  }
}

const a = [new MyClass({ answer: 42 })];
const b = [{ answer: 42 }];

JSON.stringify(a) === JSON.stringify(b); // true

class MyClass {

constructor(obj) {

Object.assign(this, obj);

}

const a = [new MyClass({ answer: 42 })];

const b = [{ answer: 42 }];

JSON.stringify(a) === JSON.stringify(b); // true

Lodash's isEqual() function, on the other hand, takes all this into account.

const _ = require('lodash');

class MyClass {
  constructor(obj) {
    Object.assign(this, obj);
  }
}

const a = [new MyClass({ answer: 42 })];
const b = [{ answer: 42 }];

_.isEqual(a, b); // false

const _ = require('lodash');

class MyClass {

constructor(obj) {

Object.assign(this, obj);

}

const a = [new MyClass({ answer: 42 })];

const b = [{ answer: 42 }];

_.isEqual(a, b); // false

Lodash's isEqual() function is the way to go if you need all the bells and whistles of checking that objects have the same class. The JSON.stringify() approach works well for POJOs, just make sure you take into account null and only use it with trusted data - toJSON() can be a security vulnerability.

参考链接

Compare Arrays in JavaScript

HarmonyOS NEXT鸿蒙手机Charles/Reqable抓包证书配置方面的一些疑惑

【问题1】

鸿蒙手机配置网络代理，只能断开wifi连接，然后再重新连接时才能配置代理？是这样的吗？华为设备网络代理配置需要长按对应的wifi配置弹出，但鸿蒙手机中貌似不管用。

解答

是的。当前确实需要断开WIFI再重新连接时配置代理。

【问题2】

鸿蒙的证书导入有什么推荐的方案吗？使用访问 chls.pro/ssl 的方式不会自动下载？下载证书后，使用「华为管家」，但 Mac 好像没有一个比较稳定的版本？

解答

首先，Mac PC 端 Charles 导出证书，点击 Help -> SSL Proxying -> Save Charles Root Certificate

其次，导入系统根证书至手机，有两个方法。

方法一：启动证书安装器进行指定 pem 证书安装。

1.将 Charles 导出的 pem 文件 hdc file send 到手机存储器内。

2.启动动证书安装

$ hdc shell aa start -a MainAbility -b com.ohos.certmanager

1	$ hdc shell aa start -a MainAbility -b com.ohos.certmanager

3.选择从存储设备安装，选择指定 pem 证书。

方法二：替换 CA 证书，证书路径为沙箱映射路径，系统预设 CA 证书位置：/etc/ssl/certs/cacert.pem，将 Charles 导出的 pem 文件 hdc file send 到此路径下（目前仅支持后缀名为 .pem 的文本格式证书）。

示例命令：

//重新挂载根目录为可写
$ hdc shell mount -o remount,rw /

1 2	//重新挂载根目录为可写 $ hdc shell mount -o remount,rw /

//导入根证书
$ hdc file send ./cacert.pem /etc/ssl/certs/

1 2	//导入根证书 $ hdc file send ./cacert.pem /etc/ssl/certs/

再次，安装 Charles 证书到 PC 系统可信目录。

点击 Help -> SSL Proxying -> Install Charles Root Certificate -> 安装证书 -> 选择证书存储路径为：受信任的根证书颁发机构。

最后，设置代理。

点击 Proxy -> SSL Proxy Settings -> 在 Include 添加 *:* 和 *:443

点击 Proxy -> Proxy Settings -> 勾选 Enable transparent HTTP proxying

注意：截止 2024/03/25 ，华为P60 升级到的鸿蒙 HarmonyOS NEXT，按照上述方式配置之后，依旧是无法通过 Charles / Reqable 进行中间人代理的。目前看到系统并没有使用我们刚刚导入的根证书。导致无法完成中间人抓包。

目前可以部分解决的问题方式是自己启动一个 Tomcat 服务器，然后配置客户端通过 HTTP 的方式进行报文的发送，从而可以看到上行报文内容。

【问题3】

鸿蒙的证书信任如何设置？设置中搜索一些配置关键字然后信任，但问题是，我的鸿蒙测试设备的设置中根本没有搜索……

解答

将 Charles 导出的 pem 文件 hdc file send 到手机存储器内。

可以参考如下命令：

$ hdc file send charles.pem（pc上证书路径） /storage/media/100/local/files/Download/（工程机指定路径）

1	$ hdc file send charles.pem（pc上证书路径） /storage/media/100/local/files/Download/（工程机指定路径）

注意：截止 2024/03/25 ，华为P60 升级到的鸿蒙 HarmonyOS NEXT，只能通过 hdc file send 发送到手机的临时目录 data/local/tmp/ 路径下，而证书凭证应用并不能找到这个目录，导致依旧无法导入证书。

目前可以解决的问题方式是通过U盘作为中介的方式完成文件的传输。

【鸿蒙正式版本 5.0.0 安装根证书】

1. “设置” 页面选择 “隐私和安全”，如下图：

2. “隐私和安全” 页面滑动到最底部，选择 “高级”，如下图：

3. “高级” 页面，选择 “证书与凭据”，如下图：

4. “证书与凭据” 页面，选择 “从存储设备安装”，如下图：

5. “从存储设备安装” 页面，选择 “CA证书”，并在弹出的根证书安装警告对话框中选择 “继续”，如下图：

6. “从存储设备安装” 打开的文件选择器页面，找到下载的根证书，并选中，如下图：

7. 证书导入结果，如下图：

8. 再次点击 “CA证书”，可以查看已经导入的根证书，如下图：

参考链接

基于 Verdaccio 搭建鸿蒙（HarmonyOS Next）开发的轻量级 Node.js 私有仓库

一、背景

最近在进行 HarmonyOS Next 应用开发，官方的 DevEco Studio 4.1 需要时候 Node.js，但是公司开发环境不支持外网访问，需要搭建内网的镜像服务器。下面，我们研究在内网服务器只使用 Apache（HTTPD）/Nginx 提供文件下载服务，不安装 NodeJs 搭建代理服务的方法来建立 NPM 文件下载代理。

执行缓存任务的设备是 MacBook Pro 2023 / macOS Sonoma 14.3 。

二、简介

1. 什么是 Verdaccio

“一个基于 Node.js 的轻量级私有仓库”。
平时使用 npm publish 进行发布时，上传的仓库默认地址是 npm，通过 Verdaccio 工具在本地新建一个仓库地址，再把本地的默认上传仓库地址切换到本地仓库地址即可。当 npm install 时没有找到本地的仓库，则 Verdaccio 默认配置中会从 npm 中央仓库下载。

注：Verdaccio 表示意大利中世纪晚期 fresco 绘画中流行的一种绿色的意思。

2. 优点

私密性高，仅团队共享。
安全性高，能够有效的防治恶意代码攻击。
使用局域网，传输速度快。

3. 官网

三、准备环境

# 我们通过 nvm 管理 node 进行多版本切换 
$ brew install nvm

# 加载并且列出远程的 node 分支,否则执行 `nvm list` `nvm install` 等命令的
# 时候没办法列出或者安装对应的版本

$ nvm ls-remote

# 但是我们使用最新版本的 node 执行安装操作，这样才能干净的进行缓存
# 否则在我们后续安装 verdaccio 的时候，数据是已经缓存过的了
$ nvm install 20.11.0

# 没有特殊情况下，建议把刚刚安装的版本设置为默认版本
$ nvm alias default 20.11.0

# 安装 verdaccio
$ npm install --location=global verdaccio

# 全局安裝 npm 源管理工具（可以快速切换仓库源）

$ npm install --location=global nrm

# 添加一个私有 npm 源，'verdaccio' 为自定义的源地址名称 
$ nrm add verdaccio http://localhost:4873/

# 如果需要还原到默认设置，只需要删除当前用户下的 .nrmrc 文件即可

$ rm -rf .nrmrc

# 我们通过 nvm 管理 node 进行多版本切换

$ brew install nvm

# 加载并且列出远程的 node 分支,否则执行 `nvm list` `nvm install` 等命令的

# 时候没办法列出或者安装对应的版本

$ nvm ls-remote

# 但是我们使用最新版本的 node 执行安装操作，这样才能干净的进行缓存

# 否则在我们后续安装 verdaccio 的时候，数据是已经缓存过的了

$ nvm install 20.11.0

# 没有特殊情况下，建议把刚刚安装的版本设置为默认版本

$ nvm alias default 20.11.0

# 安装 verdaccio

$ npm install --location=global verdaccio

# 全局安裝 npm 源管理工具（可以快速切换仓库源）

$ npm install --location=global nrm

# 添加一个私有 npm 源，'verdaccio' 为自定义的源地址名称

$ nrm add verdaccio http://localhost:4873/

# 如果需要还原到默认设置，只需要删除当前用户下的 .nrmrc 文件即可

$ rm -rf .nrmrc

配置 verdaccio 从华为镜像服务器地址下载，默认配置服务器地址国内访问可能存在问题。另外注意禁用 npm-audit ，安全审计会非常非常慢，而且经常失败。

修改后的完整配置如下：

#
# This is the default configuration file. It allows all users to do anything,
# please read carefully the documentation and best practices to
# improve security.
#
# Look here for more config file examples:
# https://github.com/verdaccio/verdaccio/tree/5.x/conf
#
# Read about the best practices
# https://verdaccio.org/docs/best

# path to a directory with all packages
storage: /Users/xxxx/.local/share/verdaccio/storage
# path to a directory with plugins to include
plugins: ./plugins

# https://verdaccio.org/docs/webui
web:
  title: Verdaccio
  # comment out to disable gravatar support
  # gravatar: false
  # by default packages are ordercer ascendant (asc|desc)
  # sort_packages: asc
  # convert your UI to the dark side
  # darkMode: true
  # html_cache: true
  # by default all features are displayed
  # login: true
  # showInfo: true
  # showSettings: true
  # In combination with darkMode you can force specific theme
  # showThemeSwitch: true
  # showFooter: true
  # showSearch: true
  # showRaw: true
  # showDownloadTarball: true
  #  HTML tags injected after manifest <scripts/>
  # scriptsBodyAfter:
  #    - '<script type="text/javascript" src="https://my.company.com/customJS.min.js"></script>'
  #  HTML tags injected before ends </head>
  #  metaScripts:
  #    - '<script type="text/javascript" src="https://code.jquery.com/jquery-3.5.1.slim.min.js"></script>'
  #    - '<script type="text/javascript" src="https://browser.sentry-cdn.com/5.15.5/bundle.min.js"></script>'
  #    - '<meta name="robots" content="noindex" />'
  #  HTML tags injected first child at <body/>
  #  bodyBefore:
  #    - '<div id="myId">html before webpack scripts</div>'
  #  Public path for template manifest scripts (only manifest)
  #  publicPath: http://somedomain.org/

# https://verdaccio.org/docs/configuration#authentication
auth:
  htpasswd:
    file: ./htpasswd
    # Maximum amount of users allowed to register, defaults to "+inf".
    # You can set this to -1 to disable registration.
    # max_users: 1000
    # Hash algorithm, possible options are: "bcrypt", "md5", "sha1", "crypt".
    # algorithm: bcrypt # by default is crypt, but is recommended use bcrypt for new installations
    # Rounds number for "bcrypt", will be ignored for other algorithms.
    # rounds: 10

# https://verdaccio.org/docs/configuration#uplinks
# a list of other known repositories we can talk to
uplinks:
  # npmjs:
  #   url: https://registry.npmjs.org/
  # 注意依赖顺序，一定要把 ohpm 放在最前面，先去 ohpm 更新，有些依赖，两个镜像上都存在，后面会出现冲突的情况
  ohpm:
    url: https://ohpm.openharmony.cn/ohpm/  
  ohpm2:
    url: https://repo.harmonyos.com/ohpm/
  oh_npm:
    url: https://repo.harmonyos.com/npm/
  npm_mirror:
    url: https://mirrors.huaweicloud.com/repository/npm/

# Learn how to protect your packages
# https://verdaccio.org/docs/protect-your-dependencies/
# https://verdaccio.org/docs/configuration#packages
packages:
  '@*/*':
    # scoped packages
    access: $all
    publish: $authenticated
    unpublish: $authenticated
    proxy: ohpm oh_npm npm_mirror

  '**':
    # allow all users (including non-authenticated users) to read and
    # publish all packages
    #
    # you can specify usernames/groupnames (depending on your auth plugin)
    # and three keywords: "$all", "$anonymous", "$authenticated"
    access: $all

    # allow all known users to publish/publish packages
    # (anyone can register by default, remember?)
    publish: $authenticated
    unpublish: $authenticated

    # if package is not available locally, proxy requests to 'npmjs' registry
    proxy: ohpm oh_npm npm_mirror

# To improve your security configuration and  avoid dependency confusion
# consider removing the proxy property for private packages
# https://verdaccio.org/docs/best#remove-proxy-to-increase-security-at-private-packages

# https://verdaccio.org/docs/configuration#server
# You can specify HTTP/1.1 server keep alive timeout in seconds for incoming connections.
# A value of 0 makes the http server behave similarly to Node.js versions prior to 8.0.0, which did not have a keep-alive timeout.
# WORKAROUND: Through given configuration you can workaround following issue https://github.com/verdaccio/verdaccio/issues/301. Set to 0 in case 60 is not enough.
server:
  keepAliveTimeout: 60
  # Allow `req.ip` to resolve properly when Verdaccio is behind a proxy or load-balancer
  # See: https://expressjs.com/en/guide/behind-proxies.html
  # trustProxy: '127.0.0.1'

# https://verdaccio.org/docs/configuration#offline-publish
# publish:
#   allow_offline: false

# https://verdaccio.org/docs/configuration#url-prefix
# url_prefix: /verdaccio/
# VERDACCIO_PUBLIC_URL='https://somedomain.org';
# url_prefix: '/my_prefix'
# // url -> https://somedomain.org/my_prefix/
# VERDACCIO_PUBLIC_URL='https://somedomain.org';
# url_prefix: '/'
# // url -> https://somedomain.org/
# VERDACCIO_PUBLIC_URL='https://somedomain.org/first_prefix';
# url_prefix: '/second_prefix'
# // url -> https://somedomain.org/second_prefix/'

# https://verdaccio.org/docs/configuration#security
# security:
#   api:
#     legacy: true
#     jwt:
#       sign:
#         expiresIn: 29d
#       verify:
#         someProp: [value]
#    web:
#      sign:
#        expiresIn: 1h # 1 hour by default
#      verify:
#         someProp: [value]

# https://verdaccio.org/docs/configuration#user-rate-limit
# userRateLimit:
#   windowMs: 50000
#   max: 1000

# https://verdaccio.org/docs/configuration#max-body-size
# max_body_size: 10mb

# https://verdaccio.org/docs/configuration#listen-port
# listen:
# - localhost:4873            # default value
# - http://localhost:4873     # same thing
# - 0.0.0.0:4873              # listen on all addresses (INADDR_ANY)
# - https://example.org:4873  # if you want to use https
# - "[::1]:4873"                # ipv6
# - unix:/tmp/verdaccio.sock    # unix socket

# The HTTPS configuration is useful if you do not consider use a HTTP Proxy
# https://verdaccio.org/docs/configuration#https
# https:
#   key: ./path/verdaccio-key.pem
#   cert: ./path/verdaccio-cert.pem
#   ca: ./path/verdaccio-csr.pem

# https://verdaccio.org/docs/configuration#proxy
# http_proxy: http://something.local/
# https_proxy: https://something.local/

# https://verdaccio.org/docs/configuration#notifications
# notify:
#   method: POST
#   headers: [{ "Content-Type": "application/json" }]
#   endpoint: https://usagge.hipchat.com/v2/room/3729485/notification?auth_token=mySecretToken
#   content: '{"color":"green","message":"New package published: * {{ name }}*","notify":true,"message_format":"text"}'

middlewares:
  audit:
    enabled: false

# https://verdaccio.org/docs/logger
# log settings
log: { type: stdout, format: pretty, level: http }
#experiments:
#  # support for npm token command
#  token: false
#  # disable writing body size to logs, read more on ticket 1912
#  bytesin_off: false
#  # enable tarball URL redirect for hosting tarball with a different server, the tarball_url_redirect can be a template string
#  tarball_url_redirect: 'https://mycdn.com/verdaccio/${packageName}/${filename}'
#  # the tarball_url_redirect can be a function, takes packageName and filename and returns the url, when working with a js configuration file
#  tarball_url_redirect(packageName, filename) {
#    const signedUrl = // generate a signed url
#    return signedUrl;
#  }

# translate your registry, api i18n not available yet
# i18n:
# list of the available translations https://github.com/verdaccio/verdaccio/blob/master/packages/plugins/ui-theme/src/i18n/ABOUT_TRANSLATIONS.md
#   web: en-US

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

# This is the default configuration file. It allows all users to do anything,

# please read carefully the documentation and best practices to

# improve security.

# Look here for more config file examples:

# https://github.com/verdaccio/verdaccio/tree/5.x/conf

# Read about the best practices

# https://verdaccio.org/docs/best

# path to a directory with all packages

storage: /Users/xxxx/.local/share/verdaccio/storage

# path to a directory with plugins to include

plugins: ./plugins

# https://verdaccio.org/docs/webui

web:

title: Verdaccio

# comment out to disable gravatar support

# gravatar: false

# by default packages are ordercer ascendant (asc|desc)

# sort_packages: asc

# convert your UI to the dark side

# darkMode: true

# html_cache: true

# by default all features are displayed

# login: true

# showInfo: true

# showSettings: true

# In combination with darkMode you can force specific theme

# showThemeSwitch: true

# showFooter: true

# showSearch: true

# showRaw: true

# showDownloadTarball: true

# HTML tags injected after manifest <scripts/>

# scriptsBodyAfter:

# - '<script type="text/javascript" src="https://my.company.com/customJS.min.js"></script>'

# HTML tags injected before ends </head>

# metaScripts:

# - '<script type="text/javascript" src="https://code.jquery.com/jquery-3.5.1.slim.min.js"></script>'

# - '<script type="text/javascript" src="https://browser.sentry-cdn.com/5.15.5/bundle.min.js"></script>'

# - '<meta name="robots" content="noindex" />'

# HTML tags injected first child at <body/>

# bodyBefore:

# - '<div id="myId">html before webpack scripts</div>'

# Public path for template manifest scripts (only manifest)

# publicPath: http://somedomain.org/

# https://verdaccio.org/docs/configuration#authentication

auth:

htpasswd:

file: ./htpasswd

# Maximum amount of users allowed to register, defaults to "+inf".

# You can set this to -1 to disable registration.

# max_users: 1000

# Hash algorithm, possible options are: "bcrypt", "md5", "sha1", "crypt".

# algorithm: bcrypt # by default is crypt, but is recommended use bcrypt for new installations

# Rounds number for "bcrypt", will be ignored for other algorithms.

# rounds: 10

# https://verdaccio.org/docs/configuration#uplinks

# a list of other known repositories we can talk to

uplinks:

# npmjs:

# url: https://registry.npmjs.org/

# 注意依赖顺序，一定要把 ohpm 放在最前面，先去 ohpm 更新，有些依赖，两个镜像上都存在，后面会出现冲突的情况

ohpm:

url: https://ohpm.openharmony.cn/ohpm/

ohpm2:

url: https://repo.harmonyos.com/ohpm/

oh_npm:

url: https://repo.harmonyos.com/npm/

npm_mirror:

url: https://mirrors.huaweicloud.com/repository/npm/

# Learn how to protect your packages

# https://verdaccio.org/docs/protect-your-dependencies/

# https://verdaccio.org/docs/configuration#packages

packages:

'@*/*':

# scoped packages

access: $all

publish: $authenticated

unpublish: $authenticated

proxy: ohpm oh_npm npm_mirror

'**':

# allow all users (including non-authenticated users) to read and

# publish all packages

# you can specify usernames/groupnames (depending on your auth plugin)

# and three keywords: "$all", "$anonymous", "$authenticated"

access: $all

# allow all known users to publish/publish packages

# (anyone can register by default, remember?)

publish: $authenticated

unpublish: $authenticated

# if package is not available locally, proxy requests to 'npmjs' registry

proxy: ohpm oh_npm npm_mirror

# To improve your security configuration and avoid dependency confusion

# consider removing the proxy property for private packages

# https://verdaccio.org/docs/best#remove-proxy-to-increase-security-at-private-packages

# https://verdaccio.org/docs/configuration#server

# You can specify HTTP/1.1 server keep alive timeout in seconds for incoming connections.

# A value of 0 makes the http server behave similarly to Node.js versions prior to 8.0.0, which did not have a keep-alive timeout.

# WORKAROUND: Through given configuration you can workaround following issue https://github.com/verdaccio/verdaccio/issues/301. Set to 0 in case 60 is not enough.

server:

keepAliveTimeout: 60

# Allow `req.ip` to resolve properly when Verdaccio is behind a proxy or load-balancer

# See: https://expressjs.com/en/guide/behind-proxies.html

# trustProxy: '127.0.0.1'

# https://verdaccio.org/docs/configuration#offline-publish

# publish:

# allow_offline: false

# https://verdaccio.org/docs/configuration#url-prefix

# url_prefix: /verdaccio/

# VERDACCIO_PUBLIC_URL='https://somedomain.org';

# url_prefix: '/my_prefix'

# // url -> https://somedomain.org/my_prefix/

# VERDACCIO_PUBLIC_URL='https://somedomain.org';

# url_prefix: '/'

# // url -> https://somedomain.org/

# VERDACCIO_PUBLIC_URL='https://somedomain.org/first_prefix';

# url_prefix: '/second_prefix'

# // url -> https://somedomain.org/second_prefix/'

# https://verdaccio.org/docs/configuration#security

# security:

# api:

# legacy: true

# jwt:

# sign:

# expiresIn: 29d

# verify:

# someProp: [value]

# web:

# sign:

# expiresIn: 1h # 1 hour by default

# verify:

# someProp: [value]

# https://verdaccio.org/docs/configuration#user-rate-limit

# userRateLimit:

# windowMs: 50000

# max: 1000

# https://verdaccio.org/docs/configuration#max-body-size

# max_body_size: 10mb

# https://verdaccio.org/docs/configuration#listen-port

# listen:

# - localhost:4873 # default value

# - http://localhost:4873 # same thing

# - 0.0.0.0:4873 # listen on all addresses (INADDR_ANY)

# - https://example.org:4873 # if you want to use https

# - "[::1]:4873" # ipv6

# - unix:/tmp/verdaccio.sock # unix socket

# The HTTPS configuration is useful if you do not consider use a HTTP Proxy

# https://verdaccio.org/docs/configuration#https

# https:

# key: ./path/verdaccio-key.pem

# cert: ./path/verdaccio-cert.pem

# ca: ./path/verdaccio-csr.pem

# https://verdaccio.org/docs/configuration#proxy

# http_proxy: http://something.local/

# https_proxy: https://something.local/

# https://verdaccio.org/docs/configuration#notifications

# notify:

# method: POST

# headers: [{ "Content-Type": "application/json" }]

# endpoint: https://usagge.hipchat.com/v2/room/3729485/notification?auth_token=mySecretToken

# content: '{"color":"green","message":"New package published: * {{ name }}*","notify":true,"message_format":"text"}'

middlewares:

audit:

enabled: false

# https://verdaccio.org/docs/logger

# log settings

log: { type: stdout, format: pretty, level: http }

#experiments:

# # support for npm token command

# token: false

# # disable writing body size to logs, read more on ticket 1912

# bytesin_off: false

# # enable tarball URL redirect for hosting tarball with a different server, the tarball_url_redirect can be a template string

# tarball_url_redirect: 'https://mycdn.com/verdaccio/${packageName}/${filename}'

# # the tarball_url_redirect can be a function, takes packageName and filename and returns the url, when working with a js configuration file

# tarball_url_redirect(packageName, filename) {

# const signedUrl = // generate a signed url

# return signedUrl;

# }

# translate your registry, api i18n not available yet

# i18n:

# list of the available translations https://github.com/verdaccio/verdaccio/blob/master/packages/plugins/ui-theme/src/i18n/ABOUT_TRANSLATIONS.md

# web: en-US

启动一个独立的Shell 运行 verdaccio

$ nvm use 20.11.0

$ verdaccio                                
 info --- config file  - /Users/xxxx/.config/verdaccio/config.yaml
 info --- the "crypt" algorithm is deprecated consider switch to "bcrypt" in the configuration file. Read the documentation for additional details
 info --- using htpasswd file: /Users/xxxx/.config/verdaccio/htpasswd
 info --- plugin successfully loaded: verdaccio-htpasswd
 info --- plugin successfully loaded: verdaccio-audit
 warn --- http address - http://localhost:4873/ - verdaccio/5.29.0

$ nvm use 20.11.0

$ verdaccio

info --- config file - /Users/xxxx/.config/verdaccio/config.yaml

info --- the "crypt" algorithm is deprecated consider switch to "bcrypt" in the configuration file. Read the documentation for additional details

info --- using htpasswd file: /Users/xxxx/.config/verdaccio/htpasswd

info --- plugin successfully loaded: verdaccio-htpasswd

info --- plugin successfully loaded: verdaccio-audit

warn --- http address - http://localhost:4873/ - verdaccio/5.29.0

清理缓存，并且要求通过 verdaccio 代理下载：

$ nvm use 20.11.0

# 'verdaccio' 为添加源时定义的源地址名称
$ nrm use verdaccio

# 列出缓存目录路径
$ npm config ls -l | grep cache

# 清理缓存
$ npm cache clean --force

$ nvm use 20.11.0

# 'verdaccio' 为添加源时定义的源地址名称

$ nrm use verdaccio

# 列出缓存目录路径

$ npm config ls -l | grep cache

# 清理缓存

$ npm cache clean --force

当前(2024/02/01)申请并通过了华为开发计划的才可以下载到 HarmonyOS NEXT 开发需要的 HUAWEI DevEco Studio 4.x 版本(API 11)，HUAWEI DevEco Studio 5.x (API 11、API 12) HarmonyOS Developer管理中心套件货架目前只有这个版本的包含离线鸿蒙开发依赖 ohpm-repo，官方文档以及报错信息还是稀烂，基本找不到有用信息，需要自己研究。

注意：目前测试发现 DevEco Studio 4.1.3.500 版本无法真机调试 C++ 代码。 DevEco Studio 4.1.3.501 版本可以正常调试。

截止 2024/04/01 最新Release版本是 DevEco Studio 4.1.3.700，最新测试版本 DevEco Studio 5.0.3.100(SP1)，可惜编译不通过，报错如下：

ERR_PNPM_NO_MATCHING_VERSION  No matching version found for @ohos/hvigor-ohos-plugin@4.2.0

1	ERR_PNPM_NO_MATCHING_VERSION No matching version found for @ohos/hvigor-ohos-plugin@4.2.0

DevEco Studio 4.1.3.501 使用的官方SDK下载地址：

下载完成后，解压缩到 SDK 目录下的 HarmonyOS-NEXT-DP1 目录即可，如下图：

继续阅读基于 Verdaccio 搭建鸿蒙（HarmonyOS Next）开发的轻量级 Node.js 私有仓库

2024 年 11 月
一	二	三	四	五	六	日
				1	2	3
4	5	6	7	8	9	10
11	12	13	14	15	16	17
18	19	20	21	22	23	24
25	26	27	28	29	30

在鸿蒙应用开发中的应用

总结

参考链接

Same Length, Each Value Equal

Deep Equality With POJOs

Using Lodash's isEqual()

参考链接

【问题1】

解答

【问题2】

解答

【问题3】

解答

【鸿蒙正式版本 5.0.0 安装根证书】

参考链接

一、背景

二、简介

1. 什么是 Verdaccio

2. 优点

3. 官网

三、准备环境

Using Lodash's `isEqual()`