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

golfc

v0.2.1

Published

CLI for managing code.golf solutions

Downloads

5

Readme

Golfc

CLI for managing code golf solutions at https://code.golf.

⚠️ Warning: This CLI is not currently stable, so future releases may cause breaking changes.

⚠️ Warning: There is currently no API for code.golf. Future changes to the site may break this CLI.

Installation

npm install golfc --location=global

To uninstall, use

npm uninstall golfc --location=global

Usage

Preparing a golfc workspace

Simply create a blank directory for everything to go into; ~/code-golf-sols would work well.

Saving the code.golf token

Of course, to fetch your solutions, the script needs your token.

In Chromium-based browsers, the token can be retrieved from __Host-session in about://settings/cookies/detail?site=code.golf or from Application/Storage/Cookies in the browser developer tools (Ctrl+Shift+I).

The easiest way to provide the token is by an environment variable like export CODE_GOLF_TOKEN=yourtoke-n123-goes-here-0123456789abcd.

You could also put the token in a .env file like so:

CODE_GOLF_TOKEN=yourtoke-n123-goes-here-0123456789abcd

Here is where I would typically say "gitignore your .env file," but you're not going to be publishing this directory anywhere public because it includes your (private) solutions.

You will have to replace the token when it expires in a couple months.

Development

A relatively modern nodejs install is required.

git clone https://github.com/jared-hughes/golfc.git
cd golfc
npm install
npm run build
# recommended: this will add the golfc script to your $PATH
npm install . --location=global

Fetch

Run golfc fetch to fetch all solutions and insert them into folders.

This command will overwrite files, so be careful. You might want to use a (local) repository and commit changes.

Submit

Run golfc submit -h fibonacci -l python -i somedir/fibonacci.py to submit your solution at somedir/fibonacci.py as python code to the Fibonacci hole.

This command might only overwrite files in the output/ directory.