open-index/open-npm huggingface dataset:
npm package: @projectit/example
Description: An example project showing how to build a projectional editor with ProjectIt.
Latest version: 0.5.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# ProjectIt-example
An example project showing how to build a projectional editor with ProjectIt.

This example works with version 0.5.0 of ProjectIt.

You should also read the documentation at https://www.projectit.org/020_Getting_Started/010_Installation.

For an explanation of the content of the project see
<a href="https://www.projectit.org//020_Getting_Started/020_Project_Structure" target="_blank">
Project Structure</a>.

## 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:

    ```bash
    yarn install
    ```

*   Run the generator and see the generated files appearing in the folder ~/src/picode:
    ```bash
    yarn generate
    ```


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

    ```bash
    yarn model-server
    ```

* Open another (bash) terminal, and start the generated editor from it:

     ```bash
     yarn prepare-app   # Needed generate the runtime css files.
     yarn dev
     ```
     
* Open the app in the browser on `localhost:5000`

The last command opens your preferred browser with the generated editor for the language
on [localhost:5000](http://localhost:5000/).

Under the `View` menu you can deselect the `myTables` option to get a view as text without tables.

Styling is done though a collection of css variables in `src/webapp/style/_freon_theme-light.scss`.
If you change the theme, run `yarn prepare-app` to uopdate the running app with the new style.
npm package: @projectit/template
Description: 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.
Latest version: 0.5.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# ProjectIt-template

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.

For an explanation of the content of the project see
<a href="https://www.projectit.org/020_Getting_Started/020_Project_Structure" target="_blank">
Project Structure</a>.

## 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:
    ```bash
    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 <a href="https://www.projectit.org/030_Developing_a_Language/010_Default_Level" target="_blank">language structure definition</a>.

> 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:

```bash
    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`):
    ```bash
    yarn model-server
    ```

*	Open another (bash) terminal, and start the generated editor from it:
     ```bash
     yern prepare-app
     yarn dev
     ```

The last command opens your preferred browser with the generated editor for the language
on [localhost:5000](http://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.
npm package: @projectjam/morse-translate
Description: a morse code encoder & decoder
Author: Project Jam
Latest version: 0.5.0

[![npm](https://nodei.co/npm/@projectjam/morse-translate.png?downloads=true&downloadrank=true&stars=true)](https://nodei.co/npm/@projectjam/morse-translate/)

> [!note]
> we are using morsecode.world's list of morse code symbols. find more [here](https://morsecode.world/international/morse.html)

# @projectjam/morse-translate

a morse code translator that is blazing fast and efficient

## features

- blazing fast and efficient
- easy to use
- supports custom symbols
- supports abbreviations
- supports typescript, commonjs and esm

## installation

```bash
npm install @projectjam/morse-translate
```

## usage

### for typescript/esm

```typescript
import { translate } from '@projectjam/morse-translate';

console.log(translate('hello world')); // to encode
console.log(translate('.... . .-.. .-.. ---')); // to decode
```

### for javascript/cjs

```javascript
const { translate } = require('@projectjam/morse-translate');

console.log(translate('hello world')); // to encode
console.log(translate('.... . .-.. .-.. ---')); // to decode
```

## contributing

pull requests are welcome! for major changes, please open an issue first or [email us](mailto:contact@project-jam.is-a.dev). make sure tests are updated to cover new options.