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

oscript-interpreter

v0.3.0

Published

A interpreter of the OScript language using the abstract syntax tree (AST).

Downloads

6

Readme

OScript AST Interpreter

NPM version

A interpreter of the OScript language using the abstract syntax tree (AST). The AST can be produced by the oscript-parser.

This project is still a work in progress. It includes neither VM nor database. It can be used to test code in scripts that depends only on global functions like Echo or objects like Str.

Synopsis

import { parseText } from 'oscript-parser'
import { interpret } from 'oscript-interpreter'

const source = 'Echo("Test")'
interpret(parseText(source, { sourceType: 'script' })) // prints "Test"

Installation

Use your favourite package manager to install this package locally in your Node.js project:

npm i oscript-interpreter
pnpm i oscript-interpreter
yarn add  oscript-interpreter

Interface

interpret(ast, options) interprets the ast and performs operations described by the nodes of the AST. The option globals can be an object with variables and functions which will be inserted to the global scope. Keys of the object are supposed to be identifiers and values are supposed to be variable values or functions. The option warnings can be a boolean flag to enable treating problems, which the interpreter can recover from as errors and fail the ecxecution.

import { parseText } from 'oscript-parser'
import { interpret } from 'oscript-interpreter'

const source = 'Echo("Test")'
interpret(parseText(source, { sourceType: 'script' })) // prints "Test"

Tools

osexec(1)

The osexec executable can be used from the shell by installing oscript-interpreter globally using npm:

$ npm i -g oscript-interpreter
$ osparse -h

Usage: osparse [option...] [file]

Options:
  --[no]-context          show near source as error context. defaults to true
  --[no]-colors           enable colors in the terminal. default is auto
  -D|--define <name>      define a named value for preprocessor
  -S|--source <type>      source type is object, script (default) or dump
  -O|--old-version        expect an old version of OScript. defaults to false
  -w|--warnings           consider warnings as failures too
  -s|--silent             suppress error output
  -v|--verbose            print error stacktrace
  -p|--performance        print parsing timing
  -V|--version            print version number
  -h|--help               print usage instructions

If no file name is provided, standard input will be read. If no source type
is provided, it will be inferred from the file extension: ".os" -> object,
".e|lxe" -> script, ".osx" -> dump. The source type object will enable the
new OScript language and source type dump the old one by default.

Examples:
  echo 'echo("foo")' | osexec -S script
  osexec -w foo.e

Example usage:

$ echo "echo("foo")" | osexec -S script

foo

License

Copyright (c) 2021-2022 Ferdinand Prantl

Licensed under the MIT license.