The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
rollup	Ready	Preview	Comment	Aug 26, 2025 5:40am

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.79%. Comparing base (59c16b9) to head (41cdb44).
⚠️ Report is 4 commits behind head on master.

@@           Coverage Diff           @@
##           master    #6081   +/-   ##
=======================================
  Coverage   98.79%   98.79%           
=======================================
  Files         271      271           
  Lines       10620    10620           
  Branches     2838     2838           
=======================================
  Hits        10492    10492           
  Misses         88       88           
  Partials       40       40           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Got it, I'll wait and re-check the PR.

I have updated this PR after #6078 was merged. You can continue to review this PR now. @lukastaegert

This PR has been released as part of rollup@4.50.0. You can test it via npm install rollup.

It works. @lukastaegert

@hqzing

/storage/Users/currentUser/codes/test/node_modules/rollup/dist/native.js:83
                throw new Error(
                      ^

Error: Cannot find module @rollup/rollup-openharmony-arm64. npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try `npm i` again after removing both package-lock.json and node_modules directory.
    at requireWithFriendlyError (/storage/Users/currentUser/codes/test/node_modules/rollup/dist/native.js:83:9)
    at Object.<anonymous> (/storage/Users/currentUser/codes/test/node_modules/rollup/dist/native.js:92:76)
    at Module._compile (node:internal/modules/cjs/loader:1546:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1691:10)
    at Module.load (node:internal/modules/cjs/loader:1317:32)
    ... 2 lines matching cause stack trace ...
    at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
    at cjsLoader (node:internal/modules/esm/translators:329:5)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:260:7) {
  [cause]: Error: Error loading shared library /storage/Users/currentUser/codes/test/node_modules/@rollup/rollup-openharmony-arm64/rollup.openharmony-arm64.node: Permission denied
      at Module._extensions..node (node:internal/modules/cjs/loader:1717:18)
      at Module.load (node:internal/modules/cjs/loader:1317:32)
      at Module._load (node:internal/modules/cjs/loader:1127:12)
      at TracingChannel.traceSync (node:diagnostics_channel:315:14)
      at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
      at Module.require (node:internal/modules/cjs/loader:1339:12)
      at require (node:internal/modules/helpers:126:16)
      at requireWithFriendlyError (/storage/Users/currentUser/codes/test/node_modules/rollup/dist/native.js:65:10)
      at Object.<anonymous> (/storage/Users/currentUser/codes/test/node_modules/rollup/dist/native.js:92:76)
      at Module._compile (node:internal/modules/cjs/loader:1546:14) {
    code: 'ERR_DLOPEN_FAILED'
  }
}

Thank you for your contribution. I have encountered an issue during use: in native. js, try executing const localName=`./rollup. ${packageBase}. node `; But in the HarmonyOS system, this cannot work. Considering system limitations, how should this place be handled appropriately?

@yuanbaobaoo

HarmonyOS is a special commercial distribution of OpenHarmony. Compared with the community edition of OpenHarmony, this distribution imposes many additional security restrictions. For example, when loading a dynamic library on HarmonyOS, the library must carry a valid code signature.

Your issue is most likely caused by rollup.openharmony-arm64.node lacking such a signature, so the system refuses to load it.

At the moment, however, I have no plan to add a dedicated signature for HarmonyOS. Vendors have not yet provided a mature toolchain or a complete signing workflow; I prefer to wait until they improve both the toolchain and the security mechanisms before tackling signature-related work.

In the meantime, you can try using the npm package ohos-signpost to work around the problem.

If you have further questions, feel free to email me directly.

@yuanbaobaoo

HarmonyOS is a special commercial distribution of OpenHarmony. Compared with the community edition of OpenHarmony, this distribution imposes many additional security restrictions. For example, when loading a dynamic library on HarmonyOS, the library must carry a valid code signature.

Your issue is most likely caused by rollup.openharmony-arm64.node lacking such a signature, so the system refuses to load it.

At the moment, however, I have no plan to add a dedicated signature for HarmonyOS. Vendors have not yet provided a mature toolchain or a complete signing workflow; I prefer to wait until they improve both the toolchain and the security mechanisms before tackling signature-related work.

In the meantime, you can try using the npm package ohos-signpost to work around the problem.

If you have further questions, feel free to email me directly.

ok，i will try the solution you provided first, thank you