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

eolang

v0.23.0

Published

A collection of command line tools for EOLANG: compiling, parsing, transpiling to other languages, optimizing, and analyzing

Downloads

482

Readme

EOLANG Command Line Took-Kit

EO principles respected here We recommend IntelliJ IDEA

grunt node-current PDD status Hits-of-Code License

First, you install npm and Java SE.

Then, you install eolang package:

npm install -g eolang

Then, you write a simple EO program in hello.eo file in the current directory:

# My first object in EO!
[args] > hello
  QQ.io.stdout > @
    "Hello, world!\n"

Then, you run it:

eoc dataize hello

That's it.

Commands

You can also do many other things with eoc commands (the flow is explained in this blog post):

  • register finds necessary .eo files and registers them in a JSON catalog
  • assemble parses .eo files into .xmir, optimizes them, and pulls foreign EO objects
  • transpile converts .xmir files to the target programming language (Java by default)
  • compile converts target language sources (e.g., .java) to binaries (e.g., .class)
  • link puts all binaries together into a single executable binary
  • dataize dataizes a single object from the executable binary
  • test dataizes all visible unit tests
  • jeo:disassemble converts Java .class files to .xmir (via jeo)
  • jeo:assemble converts .xmir files to Java .class files (via jeo)

There are also commands that help manipulate with XMIR and EO sources (the list is not completed, while some of them are not implemented as of yet):

  • audit inspects all required packages and reports their status
  • foreign inspects all objects found in the program after the assemble step
  • sodg generates .sodg from .xmir, further rederable as XML or Dot
  • phi generates .phi files from .xmir files
  • unphi generates .xmir files from .phi files
  • print generates .eo files from .phi files
  • ~~translate converts Java/C++/Python/etc. program to EO program~~
  • ~~demu removes cage and memory objects~~
  • ~~dejump removes goto objects~~
  • ~~infer suggests object names where it's possible to infer them~~
  • ~~flatten moves inner objects to upper level~~

This command line toolkit simply integrates other tools available in the @objectionary GitHub organization.

How to Contribute

First, run npm install. Then, run grunt. All tests should pass.

If you want to run a single test:

npm test -- test/test_mvnw.js

Make your changes and then make a pull request.