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

moks

v1.3.2

Published

An experimental interperted programming language

Downloads

11

Readme

moks

An interpreted language that I am writing @recursecenter.

Sample program in moks:

let fib n = {
  (n < 2)? {
    1
  } : {
    fib (n-1) + fib (n-2)
  }
}

print (fib 10) // should be 89
print (fib 20) // should be 10946

print (map (\x { x + 1; }) [1 2 3 4]) // should be [2 3 4 5]

Either semicolons OR newlines terminate lines. Do not use both or my parser will throw a cryptic error.

Play with it

Note: moks needs iojs currently since it uses features from v8 that node doesn't have yet

npm i -g moks

This should install the moks interpreter globally.

You can then run moks <path to .mok file> or moks -e "<expressions in valid moks syntax>".

For e.g.,:

moks ./fib.mok
moks -e "let add x y = {  x + y; }; print (add 2 3);"

Future plans

Things/features I plan to experiment with in the future:

  • ~~FFI to Javascript~~
  • ~~support arrays & maps~~
  • ~~module system~~
  • ~~lamda support~~
  • ~~add nil~~
  • repl
  • error handling
  • marking side effects syntactically
  • runtime optimizations
  • stack based runtime (currently uses the underlying js runtime stack)
  • macros
  • simple type system
  • pausable and rewindable code editing

Also, if you use emacs, here's a simple emacs major mode for moks.