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

@projectit/template

v0.5.0

Published

An empty template for a project using <a href="https://www.projectit.org">ProjectIt</a>. The template project provides a shell for the generated editor that enables the user to work with multiple models and model units.

Downloads

2

Readme

ProjectIt-template

An empty template for a project using ProjectIt. The template project provides a shell for the generated editor that enables the user to work with multiple models and model units.

For an explanation of the content of the project see Project Structure.

Getting started

In the following the root of the project will be indicated with '~'.

  • Clone or copy branch master.

  • Next, install all necessary packages by running:

    yarn install
  • Create a folder for your language in ~/src, to hold the definition files for your language. We usually call it defs, but any name will do. (Here the name defs will be used.)

  • Create a language definition file which defines the structure of your language. The extension of this file must be .ast. You can, for instance, copy EntityLanguage.ast from the ProjectIt example to your own defs-folder. Or, you can follow the tutorial on language structure definition.

Note: Only the language structure is required. Defaults will be generated for the editor, scoper, typer, and validator. This is called the first level of customization.

  • Next, adjust the scripts entry in the package.json file. The generate script should include your defs folder as well as the folder where you want the generated code to be stored.

  • Run the generator and see the generated files appearing in the folder where you decided to store the generated code:

    yarn generate
  • Adjust the configuration of the web application by changing the two lines in the file ~/src/webapp/WebappConfiguration.ts.

  • Start the server (note that anything that is saved in the editor will be stored in ~/modelstore):

    yarn model-server
  • Open another (bash) terminal, and start the generated editor from it:

    yern prepare-app
    yarn dev

The last command opens your preferred browser with the generated editor for the language on localhost:5000.

  • Try out the editor

If you are having trouble using the editor, have a look at the key-bindings under the Help menu.

Styling is done though a collection of css variables in style/_freon_theme-light.scss. If you change the theme, run yarn prepare-app to uopdate the running app with the new style.