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

wasm-brainfuck

v0.1.2

Published

Blazing-fast Brainfuck compiler for WebAssembly

Downloads

4

Readme

Fuck

Do you want to write blazing-fast WebAssembly code in a practially useless esoteric programming language? Do you enjoy overcomplicating everything for bragging rights? Are you a connoisseur of profanity-laden tech? If any of those are true, then wasm-brainfuck is the Brainfuck-to-WebAssembly compiler for you!

Usage

$ npm install fuck
import { Brainfuck } from "wasm-brainfuck";

const program = new Brainfuck(`
		++++++++[>++++[>++>+++>+++>+<<<<-]>+>+>->>+[<]<-]
    >>.>---.+++++++..+++.>>.<-.<.+++.------.--------.
    >>+.>++.
	`);

const result = program.execute("input");
console.log(result.output); // 'Hello World!\n'

Brainfuck

Brainfuck operates on an array of 30,000 8-bit memory cells by default. A data pointer, initially set to 0, keeps track of what cell to operate on.

| Command | Description | | ------- | --------------------------------------------------------------------------------- | | > | Increment the data pointer | | < | Decrement the data pointer | | + | Increment the byte at the data pointer | | - | Decrement the byte at the data pointer | | . | Output the byte at the data pointer as a character | | , | Input a character and store it in the byte at the data pointer | | [ | Jump to instruction after the matching ] if the byte at the data pointer is 0 | | ] | Jump back to the matching [ if the byte at the data pointer is not 0. |

All characters other than ><+-.,[] are considered comments and are ignored.

Customization

wasm-brainfuck uses 30,000 memory cells by default, but this can be customized at compile time. When the data pointer is moved out of range, it wraps back around to the other side of the array.

const program = new Brainfuck("+.>+.", { memorySize: 100_000 });

End-of-file conditions aren't handled consistently in Brainfuck implementations. By default, EOF input is a no-op, leaving the memory cell unchanged. For flexibility, wasm-brainfuck allows EOF behavior to be set at compile time to map EOF to 0 or 255.

import { EofBehavior } from "wasm-brainfuck";
const program = new Brainfuck("+.>+.", { eofBehavior: EofBehavior.SetZero });

Roadmap

  • [x] Brainfuck-to-WebAssembly compiler
  • [ ] Compiler optimizations
  • [ ] Compiler CLI
  • [ ] Syntax highlighter

Publishing to NPM

We recommend using np.