riyadhalnur / weather-cli Goto Github PK

View Code? Open in Web Editor NEW

86.0 3.0 7.0 1.02 MB

Check the weather for your city from your terminal

License: MIT License

JavaScript 100.00%

weather weather-cli cli terminal nodejs

weather-cli's Introduction

weather-cli

Check the weather for your city from your terminal

Install

$ npm install -g weather-cli

$ weather --help

  Usage
    $ weather <input>

  Options
    --city, -c City you want to lookup weather for (add state code after city name if city exists in multiple places)
    --country, -C Country you want to lookup weather for
    --scale, -s Weather scale. Defaults to Celcius
    --help Show this help message
    --version Display version info and exit
    config Set the default location and scale

  Examples
    $ weather -c Dhaka -C Bangladesh
    Dhaka, Bangladesh
    Condition: Partly Cloudy
    Temperature: 32°C

    $ weather config -c Dhaka -C Bangladesh -s F
    Default location set to Dhaka, Bangladesh and scale to F

License

Licensed under MIT. See LICENSE for more information.

Issues

Report a bug in issues.

Made with love in Dhaka, Bangladesh by Riyadh Al Nur

weather-cli's People

Contributors

Stargazers

Watchers

Forkers

cloudxtreme abhiramr semtle tynandebold diashenrique curlos

weather-cli's Issues

Air Quality Score

Seems like this can be useful info along with the weather when possible. Append the air quality score to the results when displaying weather info.

how can i change my default city

Option for scale (C or F)

It would be nice to have the option to choose either Celsius or Fahrenheit instead of displaying both.

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
The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

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 🌴

config should also let me set the scale and remember it

I like being able to set my default location.
I prefer to see temperature in Fahrenheit always.

So instead of having to type "weather -s f"
I'd like to type "weather config -c ... -C ... -s f"
and then when I type "weather" I get the display I want.

Thanks for this.

Error: Request failed with status code 400

weather -c Visakhapatnam -C India
raises to error Error: Request failed with status code 400

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

Version 4.17.1 of lodash just got published.

Branch	Build failing 🚨
Dependency	lodash
Current Version	4.17.0
Type	dependency

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

As lodash is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

✅ dependency-ci Dependencies checked Details
❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

[REJECTED] Windows binary

Dear Riyadh,
Could you be so kind to generate .exe for the rest of us who use Windows w/o Node?
I’m told that either Nexe or EnclosureJS might help you to achieve that.

Command line arguments in help and readme are wrong

This is the help text and part of the README.

Usage
  $ weather <input>
Options
  --city, -ct City you want to lookup weather for
  --country, -c Country you want to lookup weather for
  --scale, -s Weather scale. Defaults to Celcius
  --help Show this help message
  --version Display version info and exit
  config Set the default location
Examples
  $ weather -c Dhaka -C Bangladesh
  Dhaka, Bangladesh
  Condition: Partly Cloudy
  Temperature: 32°C
  $ weather config -c Dhaka -C Bangladesh
  Default location set to Dhaka, Bangladesh

Issue

Example and description are inconsistent: -ct -c vs -c -C

Implementation:

https://github.com/riyadhalnur/weather-cli/blob/master/cli.js#L10-L46

Project name error

Javascript error when using weather cli

Not sure if the search is working

It would be nice if the results told me which city it's showing me. For example if I run weather-cli, I get

Condition: Haze
Temperature: 22C/71F

and I'm not sure what city this is. Or if I run weather-cli new, I get:

Condition: Rain/Windy
Temperature: 23C/74F

I'm not sure what city this is. It could be New York, New Mexico, or somewhere else.

Switch APIs

Currently, this app uses Yahoo!'s weather api. The NPM library they publish yql is not secure anymore and I don't have faith in them as a company anymore.

I will work on upgrading this app to use the OpenWeather API through a proxy deployed to now to make sure I don't expose my private API key.

Graceful error handling rather than throwing raw error messages

Done -
Added try/catch block to throw an error message informing user of invalid input params in general.
Fix - #73

To-Do -
Localise error to country/city/temp_notation

Provide ability to select from list of ambiguous results

Right now you can only search by city and country. The name of my city is somewhat generic and there are a lot of results, and mine is not the first in the list. It would be great to have the ability to choose from a list, or at the very least, set the city by coordinates instead of city and country name.