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

wlbot

v1.1.12

Published

A CLI for the WeatherLink Live API.

Downloads

114

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

michael.weinermichael.weiner

Keywords

Davis InstrumentsWeatherLink v2 APIWeatherLink APIWeather Link API CLIWeatherLinkWeatherLink CLIweather cli

Readme

WeatherLink Bot (wlbot)

wlbot is a Node.js based CLI that can be used to make some of the most common API calls that are possible with the WeatherLink v2 API.

Table of Contents

Obtaining a WeatherLink API Key

No matter how you install wlbot, it requires that you have a WeatherLink v2 API Key and Secret.

The WeatherLink Developer Portal outlines how to get your API key at https://weatherlink.github.io/v2-api/tutorial:

To retrieve your WeatherLink v2 API Key and API Secret you can go to WeatherLink.com and visit the Account page at https://www.weatherlink.com/account.

Once on the Account page you can click the Generate v2 Key button to create a new WeatherLink v2 API Key and API Secret.

Note: Your API Secret should never be shared with anyone.

Setting Your Environmental Variables

No matter how you install wlbot, it requires several permanent environmental variables to be set. Before running the CLI locally for this first time, you must set the necessary environment variables. The table below specifies the name and value of the environment variables that are required.

| Environment Variable Name | Environment Variable Value | | ----------------------------| --------------------------------- | | WEATHER_LINK_API_KEY | <your_api_key> | | WEATHER_LINK_API_SECRET | <your_api_secret> | | WEATHER_LINK_BASE_API_URL | https://api.weatherlink.com/v2/ |

Note: <your_api_key> and <your_api_secret> should be replaced with the API Key and API Secret that you where given when creating your WeatherLink API as described above.

This article describes how you can set permanent environment variables on macos or Linux.

This article describes how you can set permanent environment variables on Windows Operating Systems.

Installing wlbot via npm

wlbot is listed on the npm repository at https://npmjs.com/package/wlbot.

You can globally install the wlbot CLI by:

  1. Opening a command line prompt on your machine and running npm install -g wlbot.

This process could take a minute or two, depending on your internet connection.

Installing wlbot Manually via the Github Repository

It is easy to get a copy of the wlbot CLI running locally.

Install Dependencies

In order to run wlbot locally, the following will need to be installed on your machine:

Clone Repo

Navigate to the location on your development machine where you want to place this project's directory and clone the repository by running the following command:

git clone https://github.com/mike-weiner/wlbot.git

Install npm Packages

wlbot requires several packages to run on top of Node.js. Those packages can be installed by the following command at the root of the directory for this project running:

npm install

Installing CLI Globally

Once you have all of the environment variables required by the CLI set, we need to globally install the CLI in npm. This will allow you to call wlbot on your command line without being in this project's directory.

To globally install the wlbot package, navigate to the project's root directory on your command line. This should be the directory where this README is found. Then run the following command:

npm i -g .

Note: It is not required that you install wlbot globally in npm. However, if it is not installed globally you will only be able to call the wlbot command when you are in the directory where you have this project located.

Calling the CLI

Congrats! You should now be able to open up a new terminal window and run wlbot. You can run wlbot -h to get help understanding how to use this CLI.

wlbot contains a helpful command to ensure that your environmental variables are set correctly. Run wlbot config to print out the values of the environmental variables that are required by wlbot.

You can run wlbot config -l to list the full values of the environmental variables. Note: Be careful running this command as your WeatherLink API Secret's value will be shown. You don't want to share this with anyone.

Common Commands

There are several commands that you will probably call more frequently than others. Some of the more common commands include:

  • wlbot metadata mine: This command will return an array of station-id numbers for the weather station's that your WeatherLink account has permission to view data for.
  • wlbot weather current <station-id>: This command will return the current weather record for the station whose station id matches <station-id>.

Upgrading wlbot via npm

If you installed wlbot via npm, you can quickly get an updated version via the command line.

To see what version of wlbot you currently have installed:

  1. Open a command line window and run wlbot -V.

To upgrade your installed version of wlbot:

  1. Open a command line window and run npm update -g wlbot.

Downloading the upgrade may take a minute or two based on your internet connection.

Contributing

All contributions are welcome!

First, search open issues to see if a ticket has already been created for the issue or feature request that you have. If a ticket does not already exist, open an issue to discuss what contributions you would like to make.

All contributions should be developed in a feature/ branch off of the development branch as a PR will be required before any changes are merged back into the development branch.

If you are introducing new functionality, please add unit tests (UTs) to ensure the functionality of your contribution and its backwards compatibility. All UTs should be able to run locally. You will need to install the devDependencies to run the UTs.

License

Distributed under the MIT License. See LICENSE.txt for more information.

References

Below are several references that were used to help find inspiration for this project, get a starting point for the CLI, and serve as a resource for the WeatherLink API.