Merge pull request #124 from fortanix/mkrause/250204-upgrade-deps

Upgrade dependencies
fortanix · Feb 4, 2025 · 707533f · 707533f
2 parents 3511fde + 32a86e3
commit 707533f
Show file tree

Hide file tree

Showing 5 changed files with 2,880 additions and 1,105 deletions.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -67,3 +67,14 @@ npm publish --scope=@fortanix --access=public --dry-run # --tag=beta
 Set the --tag as appropriate: beta for beta releases, or remove the --tag if you want to publish a stable release. Remove the --dry-run once you’ve confirmed there are no issues.
 
 **Note: you rarely need to do this manually. Instead, see the "Release workflow" above, which will trigger an npm publish automatically upon creation of a GitHub release.**
+
+
+## FAQ
+
+**Q: I'm getting the following error in GitHub Actions CI after changing the `package.json`, what should I do?**
+
+```
+Error: Cannot find module @rollup/rollup-linux-x64-gnu. 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.
+```
+
+- A: This happens when your local machine uses a different OS (e.g. Mac). One workaround you can find online is to add said dependency to `optionalDependencies`. This fixes that particular problem, but you will just continue to get the same errors for other dependencies. Instead, do as the error message suggests and completely remove `node_modules` and `package-lock.json` and re-install. This should fix the errors.