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 🙏

© 2026 – Pkg Stats / Ryan Hefner

n8n-nodes-4geeks

v0.2.3

Published

4Geeks lets you manage a coding school.

Readme

n8n community node integration for 4Geeks

Make sure you have the n8n cli installed: $ npm install -g @n8n/node-cli

n8n is a fair-code licensed workflow automation platform. This is the installation guide for new community nodes documentation.

This is what you normally do next:

# Install dependencies
npm install  # or you can use yarn

# Compile the files to update the dev instance
npm run build

# Run the dev n8n instance
npm run dev

Adding new triggers

To add a new trigger, create a TypeScript file in nodes/BreathecodeTrigger/triggers/ that exports a BreathecodeEventDefinition object.

Each trigger must define an event name (the one we create in our API), label, description and if you want filters, add properties and a filter function that returns true when the webhook should be processed. Optionally, include a transform function to modify the payload before it's sent to the workflow. Finally, import and add your trigger to the array in triggers/index.ts.

Seeing your changes in our n8n instance

They must be pulled from the Digital Ocean instance's droplet launch console.

# Pull the changes
cd n8n-docker-caddy/n8n-nodes-4geeks
git pull origin main

# Rebuild the docker image
cd ..
docker compose build n8n
docker compose down
docker compose up -d