☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 7.0.0-beta.41 of @babel/cli was just published.

This version is covered by your current version range and after updating it in your project the build failed.

@babel/cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

After config consumer key and login success.
shows Invalid signature. Expected basestring is GET&http%3A%2F%2Fapi.fanfou.com
When running nofan
On Ubuntu 18.04 Desktop 64bit, using npm 3.5.2.

Version 7.0.0-beta.51 of @babel/plugin-transform-async-to-generator was just published.

This version is covered by your current version range and after updating it in your project the build failed.

@babel/plugin-transform-async-to-generator is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

Hi! @LitoMore. nofan is really good work. Thanks for the job you have done.

Currently, nofan need an id to reply status
nofan reply|re <id> [text] # Reply status
However, I didn't find any way to show the most recent status id.

If there is an easy way to reply to the recent status on the timeline, it would be more fun to use nofan.

Best regards.

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 7.0.0-beta.43 of @babel/plugin-proposal-object-rest-spread was just published.

This version is covered by your current version range and after updating it in your project the build failed.

@babel/plugin-proposal-object-rest-spread is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 1.3.0 of boxen was just published.

This version is covered by your current version range and after updating it in your project the build failed.

boxen is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Version 4.0.1 of inquirer was just published.

This version is covered by your current version range and after updating it in your project the build failed.

inquirer is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Would get a notification

Update available 0.11.0 → 0.11.1
Run npm i nofan to update

after several hours when rerun nofan
Following is the message after update

$ npm i nofan
/home/marshall
└─┬ [email protected] 
  ├─┬ [email protected]
  │ ├── @pm2/[email protected] 
  │ └─┬ @pm2/[email protected]
  │   └─┬ [email protected]
  │     └── [email protected] 
  └─┬ [email protected]
    └── @types/[email protected] 

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: [email protected]
npm WARN enoent ENOENT: no such file or directory, open '/home/marshall/package.json'
npm WARN marshall No description
npm WARN marshall No repository field.
npm WARN marshall No README data
npm WARN marshall No license field.

It's Ubuntu 18.04 Desktop here

nofan a -> b

The post shows:

a -

It seems like characters after the '>' missing...

Maybe I can use the quotation marks like:

 nofan 'a -> b'

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 7.0.0-beta.43 of @babel/preset-env was just published.

This version is covered by your current version range and after updating it in your project the build failed.

@babel/preset-env is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Thanks for developing such a wonderful project.

If some plain user wants to install nofan on a server without administration. Is there any way to do that? I have tried it, but some error happens:

npm ERR! Linux 3.10.0-862.14.4.el7.x86_64
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "i" "-g" "nofan"
npm ERR! node v6.16.0
npm ERR! npm  v3.10.10
npm ERR! path /usr/lib/node_modules
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access

npm ERR! Error: EACCES: permission denied, access '/usr/lib/node_modules'
npm ERR!     at Error (native)
npm ERR!  { Error: EACCES: permission denied, access '/usr/lib/node_modules'
npm ERR!     at Error (native)
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'access',
npm ERR!   path: '/usr/lib/node_modules' }
npm ERR! 
npm ERR! Please try running this command again as root/Administrator.

npm ERR! Please include the following file with any support request:
npm ERR!     /mnt/data-1/$USERNAME$/RUN/npm-debug.log

When I try using npm -i nofan, a different error happens:

npm WARN enoent ENOENT: no such file or directory, open '/mnt/data-1/$USERNAME$/RUN/package.json'
npm WARN RUN No description
npm WARN RUN No repository field.
npm WARN RUN No README data
npm WARN RUN No license field.

Thanks.

Version 7.0.0-beta.51 of @babel/cli was just published.

This version is covered by your current version range and after updating it in your project the build failed.

@babel/cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 7.0.0-beta.43 of @babel/core was just published.

This version is covered by your current version range and after updating it in your project the build failed.

@babel/core is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 7.0.0-beta.53 of @babel/preset-env was just published.

This version is covered by your current version range and after updating it in your project the build failed.

@babel/preset-env is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 7.0.0-beta.51 of @babel/plugin-proposal-object-rest-spread was just published.

This version is covered by your current version range and after updating it in your project the build failed.

@babel/plugin-proposal-object-rest-spread is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 7.0.0-beta.51 of @babel/preset-env was just published.

This version is covered by your current version range and after updating it in your project the build failed.

@babel/preset-env is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 7.0.0-beta.51 of @babel/core was just published.

This version is covered by your current version range and after updating it in your project the build failed.

@babel/core is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency update-notifier was updated from 2.5.0 to 2.6.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

update-notifier is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 7.0.0-beta.43 of @babel/plugin-transform-async-to-generator was just published.

This version is covered by your current version range and after updating it in your project the build failed.

@babel/plugin-transform-async-to-generator is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 7.0.0-beta.37 of @babel/plugin-transform-async-to-generator was just published.

This version is covered by your current version range and after updating it in your project the build failed.

@babel/plugin-transform-async-to-generator is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 7.0.0-beta.43 of @babel/cli was just published.

This version is covered by your current version range and after updating it in your project the build failed.

@babel/cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴