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

g-code-builder

v0.4.1

Published

> Programming interface to build gcode, and make it possible to use > scripting to dynamically generate tool paths.

Downloads

6

Readme

GCode Builder

Programming interface to build gcode, and make it possible to use scripting to dynamically generate tool paths.

Limitations

CNC only.

Ideas

  • Different levels of abstraction when building G-code.
    • G-code level should be available.
    • Geometry helpers should be available (blocks).
      • Circles.
      • Rectangles.
      • Zig zag.
      • Planing.
    • Block editing tasks should be available.
      • Holding tabs.
      • Stepdown.
  • Optimizers in each level.
    • Optimize program by calculating the least amount of traveling.
  • Decorator pattern for decorating a Program, or decorating a Block?
    • Decorating a block with holding tabs?
    • Decorating a Program with a machining step?
      • Cutout.
      • Engraving.
      • Drilling.
      • Planing.
  • Should not be able to add a block to a block, just blocks to a program.
  • Command -> Block -> Program -> Job.
    • Purpose of each?
      • Command - Obvious - Primitive - Lib
      • Block - Group of Commands - Primitive - Lib
      • Program - Collection of blocks - Primitive, extendable - Lib
      • Not part of lib below

      • Job - Extended Program w. parameters/conditional block construction.
  • No need for tool change if the correct tool is already loaded.
    • Virtual machine?
  • Add operator hints and help in jobs.
    • Description of the job.
      • Where is the origin? Orientation etc.
  • Support for adding blocks at specific positions:
    • After another block, using IDs of some sort.
    • First, last.