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

virtual_machine_builder

v1.0.5

Published

A language for building virtual machines!

Downloads

10

Readme

npm version

virtual_machine_builder

A small *language to build virtual machines.

Contact me for help, because I will respond. Discord: amukh1#9613

Prerequisites

This project requires NodeJS (version 8 or later) and NPM. Node and NPM are really easy to install. To make sure you have them available on your machine, try running the following command.

$ npm -v && node -v
6.4.1
v8.16.0

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Installation

BEFORE YOU INSTALL: please read the prerequisites

To install and set up the library, run:

$ npm install virtual_machine_builder

Or if you prefer using Yarn:

$ yarn add --dev virtual_machine_builder

Usage

virtual_machine_builder has one file extension: .vm to define a new intruction, write it in the file as follows:

instruction:
add, <-- name
0001, <-- opcode
3, <-- number of operands
instruc-end;

instruction:
sub,
0010,
3,
instruc-end;

End your instruction with instruc-end; You can have as many instructions as you want in one file.

To add functionality to your intructions, you must make functions for each instruction (MAKE SURE THE FUNCTION NAMES MATCH THE INSTRUCTION), and pass them each into an object. Then when you call the object into the prep() method (see later), include this object.

function add(operands, vm){
    vm.registers[operands[3]] = vm.registers[operands[1]] + vm.registers[operands[2]]
    // console.log(operands); // [opcode, 1, 2, 3]
    // vm.registers
    // vm.stack
    // vm.ram
}

// Customize the intruction however you want in the javascript file.

module.exports = add;

Example program:

instruction:
add,
0001,
3,
instruc-end;

instruction:
sub,
0010,
3,
instruc-end;

instruction:
ld_immd,
0011,
2,
instruc-end;

instruction:
output,
0100,
1,
instruc-end;

See "example" folder for the Javascript implementations.

Actually using your new VM:

In another Javascript file (outside the instructions folder), import the library

var VM = require('virtual_machine_builder');
var fs = require('fs'); // file system 

Then, create a new virtual machine and run it:

var vm_schematic = fs.readFileSync('./file.vm', 'utf8');
var vm = new VM(schematic, true); // takes in the contents of the .vm file, and a boolean for "console" mode or not.
vm.prep({
    add: add,
    sub: sub,
    ld_immd: ld_immd,
    output: output
}); // prepares the virtual machine for execution and parses vm file

vm.run(`binary_code\n`); // runs the virtual machine with many lines of binary code separated by newlines
vm.runln(`0001 1 2 3`); // adds 1 and 2, and stores the result in register 3 (4th register including 0)
// vm.runln(`binary_code`); // runs the virtual machine with one line of binary code

Passing false into the second argument of the initial VM declaration will make it so the vm doesnt log all the instructions while prepping.

Contributing

You can contribute to the project by making a pull request on GitHub.

Credits

Amukh1.

Built With

Authors

See also the list of contributors who participated in this project.

License

MIT License © Amukh1 2022