如何修复使用 ZEIT Now、Next.js 和 Gun.js 时"OSSL_WEBCRYPTO_OR_TEXT_ENCODING_NOT_INSTALLED is not defined"部署错误


由于

Gun.js 引用错误,我无法通过 ZEIT Now 部署 Next.js 应用程序,OSSL_WEBCRYPTO_OR_TEXT_ENCODING_NOT_INSTALLED is not defined 。在本地计算机上以开发模式运行时没有错误。

在部署日志中的错误之前是消息"默认情况下可能不包含node-webcrypto-ossl 和文本编码,请将其添加到您的 package.json!这样做并没有修复错误,也没有按照 https://github.com/amark/gun#additional-cryptography-libraries 添加@trust/webcrypto(我正在使用 SEA 进行用户身份验证((编辑:从依赖项中删除@trust/webcrypto(。

来自现在部署日志的堆栈跟踪:

Compiled with warnings.
./node_modules/gun/gun.js
Critical dependency: the request of a dependency is an expression
./node_modules/gun/sea.js
Critical dependency: the request of a dependency is an expression
./node_modules/gun/gun.js
Critical dependency: the request of a dependency is an expression
./node_modules/gun/sea.js
Critical dependency: the request of a dependency is an expression
Hello wonderful person! :) Thanks for using GUN, feel free to ask for help on https://gitter.im/amark/gun and ask StackOverflow questions tagged with 'gun'!
node-webcrypto-ossl and text-encoding may not be included by default, please add it to your package.json!
> Build error occurred
ReferenceError: OSSL_WEBCRYPTO_OR_TEXT_ENCODING_NOT_INSTALLED is not defined
    at /tmp/173ebd33/.next/serverless/pages/index.js:13474:7
    at /tmp/173ebd33/.next/serverless/pages/index.js:13301:7
    at /tmp/173ebd33/.next/serverless/pages/index.js:13478:5
    at Object.<anonymous> (/tmp/173ebd33/.next/serverless/pages/index.js:14596:2)
    at Object.md/m (/tmp/173ebd33/.next/serverless/pages/index.js:14597:30)
    at __webpack_require__ (/tmp/173ebd33/.next/serverless/pages/index.js:23:31)
    at Object.1TCz (/tmp/173ebd33/.next/serverless/pages/index.js:865:11)
    at __webpack_require__ (/tmp/173ebd33/.next/serverless/pages/index.js:23:31)
    at Module.VVmT (/tmp/173ebd33/.next/serverless/pages/index.js:11281:12)
    at __webpack_require__ (/tmp/173ebd33/.next/serverless/pages/index.js:23:31)
    at /tmp/173ebd33/.next/serverless/pages/index.js:91:18
    at Object.<anonymous> (/tmp/173ebd33/.next/serverless/pages/index.js:94:10)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
npm
 ERR! code ELIFECYCLE
npm
 ERR! errno 1
npm
 ERR! maptivist@1.0.0 now-build: `next build`
npm ERR!
 Exit status 1
npm ERR!
npm ERR! Failed at the maptivist@1.0.0 now-build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

package.json依赖项:

{
  "dependencies": {
    "directory-named-webpack-plugin": "^4.0.1",
    "gun": "^0.2019.726",
    "mapbox-gl": "^1.2.1",
    "next": "^9.0.3",
    "next-offline": "^4.0.3",
    "node-webcrypto-ossl": "^1.0.48",
    "react": "^16.9.0",
    "react-dom": "^16.9.0",
    "styled-components": "^4.3.2",
    "text-encoding": "^0.7.0"
  }
}

node-webcrypto-ossl package-lock.json中与内容有关的内容:

...
"gun": {
  "version": "0.2019.726",
  "resolved": "https://registry.npmjs.org/gun/-/gun-0.2019.726.tgz",
  "integrity": "sha512-LVSxhGwaemZbrirSk6fp2KXORLUyjs6bnssjSjl/OhwbfLv7fvMhNfaOZuorzYsehxqMKJvxyNdFq/mZNXpjHQ==",
  "requires": {
    "emailjs": "^2.2.0",
    "node-webcrypto-ossl": "^1.0.47",
    "text-encoding": "^0.7.0",  
    "ws": "~>7.1.0"
  }
},
...
"node-webcrypto-ossl": {
  "version": "1.0.48",
  "resolved": "https://registry.npmjs.org/node-webcrypto-ossl/-/node-webcrypto-ossl-1.0.48.tgz",
  "integrity": "sha512-MWUkQ/5wrs7lpAr+fhsLMfjdxKGd3dQFVqWbNMkyYyCMRW8E7ScailqtCZYDLTnJtU6B+91rXxCJNyZvbYaSOg==",
  "requires": {
    "mkdirp": "^0.5.1",
    "nan": "^2.13.2",
    "tslib": "^1.9.3",
    "webcrypto-core": "^0.1.26"
  }
},
...

node-webcrypto-osslnode_modules中可见。

请帮忙! :-(

@randy-morantes你的package.json看起来是正确的。

你能尝试分享:

  • 错误的堆栈跟踪。
  • 调用导致此问题的 gun 的服务器代码。

我是 peculiar\webcrypto 和 node-webcrypto-ossl 包的作者。根据枪源:

https://github.com/amark/gun/blob/e0d85f02b567a43d39cda0fe71522b84ff52a08b/sea/shim.js#L25

看起来他们还没有切换到奇特\网络加密。尝试将node-webcrypto-ossl添加到您的 package.json 中。

最新版本

的Next.js("next": "9.0.4""next-offline": "4.0.5"(修复了这个问题!

我昨晚遇到了这个问题,终于使用一些猴子补丁和黑客成功修复了它。诀窍是将从webpack和反应环境中取出,然后使用window.gun访问它。此外,当它不在 webpack 中时,枪似乎跑得更快。

这就是我在Gatsbyjs项目中的做法:

阅读此文档:https://www.gatsbyjs.org/docs/custom-html/

  1. 将 ./cache/default-html.js 复制到 ./src/html.js
  2. 现在在 html.js 中启动枪和海。你可以在这里从github或jsdelivr加载外部js文件。
  3. 然后在你的gatsby act组件中,只需调用window.gun和window.user,就可以享受黑客攻击:

    如果(窗口(枪...

  4. 现在运行 gatsby 构建,您可以看到它是构建的,没有错误。

最新更新