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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@thiagodiogo/psjava

v0.2.0

Published

Run .psjava files as scripts — plain Java, no ceremony, on top of JShell.

Readme

psjava

npm CI license

Run .psjava files as scripts — plain Java on top of JShell, with zero ceremony.

There's no custom syntax and no transpilation: whatever is in the file is exactly what jshell runs. psjava only adds a small print helper to the session and strips the Windows BOM — nothing else touches your code.

Install

npm install -g @thiagodiogo/psjava

Requires a JDK 11+ with jshell on your PATH. Verify your setup with psjava doctor.

Usage

psjava example.psjava           # run the file
psjava example.psjava --debug   # run, and print the elapsed time at the end
psjava doctor                   # check jshell and the editor syntax highlighting
psjava highlight install        # enable .psjava syntax highlighting in your editors

A .psjava file is just Java:

var name = "world";
print("hello, " + name);

The print helper

psjava defines a print(...) in the session before your code runs (still plain Java — your file stays untouched). It comes with overloads for String, int[], and List:

print("text");                       // text
print(new int[]{1, 2, 3});           // [1, 2, 3]
print(java.util.List.of("a", "b"));  // [a, b]

System.out.println(...) keeps working as usual.

Syntax highlighting

Since a .psjava file is plain Java, psjava highlight install just tells your editor to treat *.psjava as Java — no extension or plugin to maintain:

  • VSCode — adds "*.psjava": "java" to your user settings.json.
  • IntelliJ — maps *.psjava to the Java file type in filetypes.xml.

It detects each editor's config folder automatically (Windows) and asks for the path when it can't find one. Reopen the editor afterwards for the highlighting to kick in. psjava doctor reports, per editor, whether the highlighting is already set up.

How it works

psjava reads your file, prepends the print overloads, and pipes the result straight into jshell -s. The only change made to your source is removing the Windows BOM, which jshell chokes on. That's it — plain Java into JShell.

License

MIT