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

jedi-runtime

v0.1.21

Published

Runtime suite for Jediscript.

Downloads

7

Readme

High Performance Virtual Machine for JediScript.

Current maintainer: Evan Sebastian

Introduction

This project comprises Parser, Compiler, and a Virtual Machine for JediScript. It makes no assumption of the underlying platform, meaning that except for one source file for configuration, the library should be portable.

This project = One platform specific "lib/jfdi.js" file + other files under lib

General Usage

Simply include the concatenated javascript file generated every build in the HTML. Requirejs is already included and need not be imported separately.

var source = "1 + 2;";
var Parser = require('lib/parser/parser');
var compile = require('lib/compiler/compiler');
var Runtime = require('lib/vm/runtime');

var ast = Parser.parse(source);
var instructions = compile(ast).instructions;
var result = new Runtime().execute_instruction(instructions);

Project Structure

lib       - Source folder, everything inside here will be concatenated together with
        jfdi.js as platform dependent entry point
test      - Test folder
coverage  - Test coverage report
doc       - Documentation of instruction semantics.

Prerequisites.

This project is completely client side with each file defined as a Require.js module. However, we will be using many convenient tools (linters, test runners) from the Node.js stack.

  1. Mercurial.

  2. Node.js (~0.10).Installation instruction can be found in Node.js website

  3. Grunt-cli (~0.4.5). Grunt is used to run the tasks (linting, concatenating, testing) Once you install Node, you should be able to use the npm command. You can then run:

     npm install -g grunt-cli
  4. Google Chrome (~39). The unit tests will be run in Google Chrome.

Getting Started

  1. Clone this repository.
  2. Run npm install to install the dependencies.
  3. Run grunt to build the javascript file according to Gruntfile.js
  4. Run grunt test to execute a new Chrome window running all the test cases.

Code Coverage

Code coverage for every file under lib is generated automatically each invocation of grunt test and can be seen in the file coverage/<Chrome version>/index.html

Try to make at least 95% of the code covered.

How to Debug tests using Karma

Instead of running grunt test, you can run ./node_modules/karma/bin/start to start a Karma instance in your default browser. You can then proceed to run/debug the test cases by clicking the button "DEBUG" in the Karma interface.

Please contact the maintainer if you have any questions or to file a bug report.