npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@brodeous/weather-cli

v1.1.3

Published

CLI tool that grabs weather forcast data for given location.

Downloads

5

Readme

weather-cli

A CLI designed to retrieve weather data at a given location. This CLI uses the node runtime and will need to be installed prior to the installation of this application.

terminal

Quick Set Up

Installation

This CLI can be installed using the npm package manager

$ npm i -g @brodeous/weather-cli

** Make sure the -g option is passed if you would like the CLI to be accessed from anywhere in the terminal.

Configuration

Next you need to edit the config and add your api keys for the application to retrieve it's data.

First, lets create a config file.

$ getwet config --init

[CONFIG] initialized
    \___ location: <home dir>/.config/getwet/getwet.conf

If you run the following command, you can see there are no api keys saved.

$ getwet config --print

[CONFIG] print

Geolocation > 
Weather API > 

** For full functionality, you will need both keys. If you do not want the ability to use your current location, we will only need the weather_api key.

You will need to go to these two websites and create an account

Once the accounts are made, you need to grab the keys

IP Geolocation

geolocation

Weather API

weatherapi

To then add these keys to the CLI, you will want to run the following command in add them to the appropriate variable.

$ getwet config --edit

[CONFIG] updated

Or if you like to work with the files themselves, you can manually change the variables at $HOME/.config/getwet/getwet.conf

If you run the list command again, you should now see the keys you just set.

$ getwet config --print

[CONFIG] print

Geolocation > <geo key>
Weather API > <weather key>

Usage

The CLI comes with a few options to retrieve the weather information for specific places.

$ getwet --help
Usage: getwet [options] args

A CLI that retrieves current weather data for a specific location.
    > No option will return data based on current public ip.

Options:
  -V, --version              output the version number
  -c, --city <city>          specific city
  -z, --zipcode <zipcode>    specific zipcode
  -l, --lat_long <lat,long>  specific latitude and longitude
  -u, --uninstall            uninstall getwet
  -h, --help                 display help for command

Commands:
  config [options]           configure .conf file


Example:
    --city
        $ getwet -c Dallas
        $ getwet -c 'San Diego'
        $ getwet -c San_Diego
    --zipcode
        $ getwet -z 77007
    --lat_long
        $ getwet -l 39.76893679731222,-86.1639944813316
    --set-key
        $ getwet -s geolocation=<api key>
        $ getwet -s weatherapi=<api key>