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

todoleet

v1.0.1

Published

Sync LeetCode daily coding challenge to Todoist

Downloads

4

Readme

NOTE This project uses [email protected]. [email protected] was released 1st May 2022, check out the comparison here.

CI Release

Table of Contents

Context

A Cloudflare Worker project that syncs Daily LeetCoding Challenge to your Todoist.

The worker runs every day at 00:01 UTC and syncs the Daily LeetCoding Challenge to your Todoist.

Read more....

Requirements

  • Install Wrangler CLI for Cloudflare Workers deployment
  • Install Miniflare CLI for local development work

Installation

The dependencies are only used for development. So the installation is not required.

npm ci

Usage

For local development, create a .env file with the following:

TODOIST_API_TOKEN="xxxxxxxxxxxxxxxxxxxxxx"

To test out the cron trigger locally, run the following:

# At terminal 1
miniflare

# At terminal 2
curl "http://localhost:8787/.mf/scheduled"

Check if a new task is created on your Todoist.

Deployment

1-Click (Experimental)

Deploy to Cloudflare Workers

Wrangler CLI

  1. Add TODOIST_API_TOKEN using wrangler secret put TODOIST_API_TOKEN. You may find the newly added secret under Cloudflare Worker -> Settings -> Variables. You can get your Todoist API token from https://todoist.com/app/settings/integrations.

  2. This is only required for Wrangler actions. Add CF_API_TOKEN into your GitHub repository secrets. You can create your API token from https://dash.cloudflare.com/profile/api-tokens using the Edit Cloudflare Workers template.

  3. To publish any new changes to your Cloudflare Worker, run wrangler publish

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

  1. Fork this
  2. Create your feature branch (git checkout -b tommy/fooBar)
  3. Commit your changes (git commit -am 'feat: add some fooBar', make sure that your commits are semantic)
  4. Push to the branch (git push origin tommy/fooBar)
  5. Create a new Pull Request

References

  • https://developer.todoist.com/guides/
  • https://developers.cloudflare.com/workers/

FAQ

Is it safe to publish wrangler.toml with account_id and zone_id?

Yes.

How to test cron trigger locally

Currently, there is no way to test scheduled jobs, since we can't fire a scheduled task during development.

Alternatively, we could use Miniflare which supports cron trigger testing.