Coder Social home page Coder Social logo

nofan's People

Contributors

greenkeeper[bot] avatar greenkeeperio-bot avatar litomore avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

nofan's Issues

How to use `reply` and `repost` command

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.

An in-range update of @babel/preset-env is breaking the build 🚨

☝️ 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.

Branch Build failing 🚨
Dependency @babel/preset-env
Current Version 7.0.0-beta.42
Type devDependency

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.

Status Details
  • continuous-integration/appveyor/branch AppVeyor build succeeded Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @babel/preset-env is breaking the build 🚨

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

Branch Build failing 🚨
Dependency @babel/preset-env
Current Version 7.0.0-beta.52
Type devDependency

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.

Status Details
  • continuous-integration/appveyor/branch AppVeyor build succeeded Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @babel/preset-env is breaking the build 🚨

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

Branch Build failing 🚨
Dependency @babel/preset-env
Current Version 7.0.0-beta.50
Type devDependency

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.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
  • continuous-integration/appveyor/branch AppVeyor build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @babel/cli is breaking the build 🚨

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

Branch Build failing 🚨
Dependency @babel/cli
Current Version 7.0.0-beta.50
Type devDependency

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.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
  • continuous-integration/appveyor/branch AppVeyor build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of update-notifier is breaking the build 🚨

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.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build is in progress (Details).
  • continuous-integration/appveyor/branch: AppVeyor build failed (Details).

Commits

The new version differs by 10 commits.

  • 622ee5f 2.6.0
  • ad8ed1b Suggest yarn when installed with yarn (#132)
  • 5f06620 Exit the update check process if it does not respond after 30s (#156)
  • 79e89ad Fix failing test (#155)
  • c8faa84 Add distTag option (#151)
  • 14632e4 Add failing test for #153 (#154)
  • aafd8a0 Require Node.js 8
  • 0d49f51 Add Tidelift mention in the readme
  • 8df01b3 Fix docs position of shouldNotifyInNpmScript (#143)
  • d371834 Docs: isGlobal option does not default to true (#142)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @babel/core is breaking the build 🚨

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

Branch Build failing 🚨
Dependency @babel/core
Current Version 7.0.0-beta.50
Type devDependency

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.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
  • continuous-integration/appveyor/branch AppVeyor build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

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.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of inquirer is breaking the build 🚨

Version 4.0.1 of inquirer was just published.

Branch Build failing 🚨
Dependency inquirer
Current Version 4.0.0
Type dependency

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.

Status Details
  • continuous-integration/appveyor/branch AppVeyor build succeeded Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes v4.0.1
  • Update dependency to fix a LGPL license issue.
Commits

The new version differs by 3 commits.

  • 00f5050 4.0.1
  • 9895054 Bumped version to 4.1.0, bumped external-editor dependency to ^2.1.0 … (#616)
  • 62a72d4 Fix typo (#612)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Install error

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.

An in-range update of @babel/plugin-proposal-object-rest-spread is breaking the build 🚨

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

Branch Build failing 🚨
Dependency @babel/plugin-proposal-object-rest-spread
Current Version 7.0.0-beta.50
Type devDependency

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.

Status Details
  • continuous-integration/appveyor/branch AppVeyor build failed Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @babel/plugin-transform-async-to-generator is breaking the build 🚨

☝️ 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.

Branch Build failing 🚨
Dependency @babel/plugin-transform-async-to-generator
Current Version 7.0.0-beta.42
Type devDependency

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.

Status Details
  • continuous-integration/appveyor/branch AppVeyor build succeeded Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Update fail

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

An in-range update of @babel/core is breaking the build 🚨

☝️ 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.

Branch Build failing 🚨
Dependency @babel/core
Current Version 7.0.0-beta.42
Type devDependency

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.

Status Details
  • continuous-integration/appveyor/branch AppVeyor build succeeded Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @babel/plugin-transform-async-to-generator is breaking the build 🚨

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

Branch Build failing 🚨
Dependency @babel/plugin-transform-async-to-generator
Current Version 7.0.0-beta.36
Type devDependency

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.

Status Details
  • continuous-integration/appveyor/branch AppVeyor build failed Details
  • continuous-integration/travis-ci/push The Travis CI build passed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @babel/plugin-transform-async-to-generator is breaking the build 🚨

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

Branch Build failing 🚨
Dependency @babel/plugin-transform-async-to-generator
Current Version 7.0.0-beta.50
Type devDependency

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.

Status Details
  • continuous-integration/appveyor/branch AppVeyor build failed Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of boxen is breaking the build 🚨

Version 1.3.0 of boxen was just published.

Branch Build failing 🚨
Dependency boxen
Current Version 1.2.2
Type dependency

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.

Status Details
  • continuous-integration/appveyor/branch AppVeyor build succeeded Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 2 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

nofan post

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'

An in-range update of @babel/cli is breaking the build 🚨

☝️ 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.

Branch Build failing 🚨
Dependency @babel/cli
Current Version 7.0.0-beta.40
Type devDependency

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.

Status Details
  • continuous-integration/appveyor/branch AppVeyor build failed Details
  • continuous-integration/travis-ci/push The Travis CI build passed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @babel/plugin-proposal-object-rest-spread is breaking the build 🚨

☝️ 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.

Branch Build failing 🚨
Dependency @babel/plugin-proposal-object-rest-spread
Current Version 7.0.0-beta.42
Type devDependency

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.

Status Details
  • continuous-integration/appveyor/branch AppVeyor build succeeded Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @babel/cli is breaking the build 🚨

☝️ 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.

Branch Build failing 🚨
Dependency @babel/cli
Current Version 7.0.0-beta.42
Type devDependency

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.

Status Details
  • continuous-integration/appveyor/branch AppVeyor build succeeded Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.