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

pts-lang

v1.1.0

Published

## Using PTS in a project

Downloads

5

Readme

PTS (Package Template Script) / An implementation of Package Templates in TypeScript

Using PTS in a project

Initialize the project

mkdir <name of project>
cd <name of project>
npm init -Y
npm install pts-lang

Add a start and/or build script to package.json:

{
  "scripts": {
    "start": "pts-lang -i src/index.pts --run",
    "build": "pts-lang -i src/index.pts -o build/index"
  }
}

The start script only runs the program, and doesn't emit any files, while the build script transpiles the src/index.pts file to JavaScript. If you'd rather have TypeScript as output you can use -t:

pts-lang -i src/index.pts -o build/index -t ts

TODOs

  • [x] Instantiating closed templates
  • [x] Renaming classes
    • [x] Rename class declarations
    • [x] Rename class heritage
    • [x] Rename class instantiations
    • [x] Rename member_expressions on static class fields (i.e. A.k)
    • [x] Rename other class references, i.e. as a type (Maybe enough to have another pass on type_identifiers)
  • [x] Renaming fields
    • [x] Rename field declaration (public_field_definition)
    • [x] Rename this.x from same class (local member_expressions)
    • [x] Rename this.x from super class (member_expressions)
    • [x] Rename other references to fields, i.e. member_expressions of variables, a.i
  • [ ] Merging classes
    • [x] Merge bodies of two classes
    • [ ] Checking if it is valid to merge classes (Do they have different heritage?)
    • [ ] Merge heritage
  • [ ] Addto statements
    • [x] Check if the class to be added to exists
    • [x] Merge bodies of the class and addto-statement
    • [ ] Add implementing interfaces and extended classes to the class
    • [ ] Override attributes
  • [ ] Validating templates