You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
bcoin@CryptoTED-devel-signature:/var/Coinygram-Sig$ npm install bclient
npm ERR! cb() never called!
npm ERR! This is an error with npm itself. Please report this error at:
npm ERR! <https://github.com/npm/npm/issues>
How can the CLI team reproduce the problem?
# cd /var
# mkdir <APPNAME>-Sig
# chown <USER>:<GROUP> <APPNAME>-Sig/
# chmod 775 <APPNAME>-Sig/
# su <USER>
(<USER>)$ cd <APPNAME>-Sig
(<USER>)$ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sensible defaults.
See \`npm help json` for definitive documentation on these fields
and exactly what they do.
Use \`npm install <pkg>` afterwards to install a package and
save it as a dependency in the package.json file.
Press ^C at any time to quit.
package name: (<APPNAME>-sig)
version: (1.0.0)
description: Verifies the signature of incoming requests
entry point: (index.js) signature.js
test command:
git repository: https://git.<path>/<APPNAME>-Sig.git
keywords:
author: Mike Rightmire
license: (ISC)
About to write to /var/<APPNAME>-Sig/package.json:
{
"name": "<APPNAME>-sig",
"version": "1.0.0",
"description": "Verifies the signature of incoming requests",
"main": "signature.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"repository": {
"type": "git",
"url": "https://git.<path>/<APPNAME>-Sig.git"
},
"author": "Mike Rightmire",
"license": "ISC"
}
Is this OK? (yes) yes
(<USER>)$ npm install express --save
npm notice created a lockfile as package-lock.json. You should commit this file.
+ express@4.16.3
added 50 packages from 47 contributors and audited 119 packages in 4.256s
found 0 vulnerabilities
Windows, OS X/macOS, or Linux?:
Linux CryptoTED-devel-signature 3.16.0-5-amd64 bin requires filename #1 SMP Debian 3.16.51-3+deb8u1 (2018-01-08) x86_64 GNU/Linux
I'm opening this issue because:
What's going wrong?
How can the CLI team reproduce the problem?
# cd /var
# mkdir <APPNAME>-Sig
# chown <USER>:<GROUP> <APPNAME>-Sig/
# chmod 775 <APPNAME>-Sig/
# su <USER>
(<USER>)$ cd <APPNAME>-Sig
(<USER>)$ npm init
(<USER>)$ npm install express --save
(<USER>)$ vi signature.js
(test)
(<USER>)$ node signature.js
(In new window)
(<USER>)$ elinks http://localhost:3000/
supporting information:
npm -v
prints:6.1.0
node -v
prints:v8.11.2
npm config get registry
prints:https://registry.npmjs.org/
Windows, OS X/macOS, or Linux?:
Linux CryptoTED-devel-signature 3.16.0-5-amd64 bin requires filename #1 SMP Debian 3.16.51-3+deb8u1 (2018-01-08) x86_64 GNU/Linux
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
2018-06-01T07_13_53_903Z-debug.log
The text was updated successfully, but these errors were encountered: