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

ohsojuicy

v0.0.2

Published

Using OJ with middlewares!

Downloads

12

Readme

OJ with middlewares

oj is a subset of JavaScript (ES5) with Objective-C syntax. This is a layer ontop of the original compiler that allows you to add middlewares.

What is this useful for?

There is an example included: a basic preprocessor. It allows you to include other OJ files within your file. This feels more natural in comparsion to Objective-C/Objective-C++ and allows you to build a foundation and include the parts you need from it.

Example:

#include "Foo.oj"

@implementation Bar : Foo
// Your code
@end

As you can see, you can include another file that holds the implementation for another class. You can extend from it or anything else. It will be included in your source code.

How to use

There is a small command line program (juicy) that allows you to run the OJ compiler underneath the middleware layer, with the preprocessor included. The options are:

| Option | Effect | |--------------|--------------------------------------------------------------------| | -o | Where the output file should go. Default: a.out | | -I | Add a path to the include path. | | -D foo=bar | Define foo to be bar. This works like a traditional #define. |

There are other options that can be used with OJ itself:

  • --warn-unused-ivars: Warn when an instance variable is not used.
  • --warn-unknown-ivars: Warn when an unknown instance variable is attempted to be used.
  • --warn-unknown-selector: Warn when trying to access an unknown selector.
  • --warn-this-in-methods: Warn when this is being used in a method.
  • --source-map-file: Produce a sourcemap file.
  • --source-map-root: Define the root path for the sourcemap.

An example execution would be:

$ juicy app.oj -o app.js

Any file given that does not stick to an option will be treatened as an input file.

How to use in code

var juicy = require("juicy");

// Use the preprocessor
juicy.use("pre-compile", juicy.preprocessor());

// Add your own transformation
juicy.use("pre-compile", function(ctx, next){
    // ...
    next();
});

// Or, after.
juicy.use("post-compile", function(ctx, next){
    // ...
    next();
});

// Run the compiler
juicy.compile({
    files: [...{...}...],
    preprocessor: {
        include_path: [],
        defines: {}
    }
}, function(err, res){
    // this is equivalent to OJ's original callback.
});