Perla is a cross-platform single executable binary CLI Tool for a Development Server of Single Page Applications (like vite/webpack but no node required!).

You can install Perla manually by downloading the latest release from the releases page and adding it to your path.

If you prefer a more automated approach, you can use the provided install scripts, they're available on this repository for you to review the contents before running them.

For Linux or macOS, you can run the following command in your terminal:

curl -fsSL https://raw.githubusercontent.com/AngelMunoz/Perla/dev/install.sh | bash

For Windows (or Linux, MacOS if you've installed pwsh), you can use powershell to run the install script:

iwr https://raw.githubusercontent.com/AngelMunoz/Perla/dev/install.ps1 -UseBasicParsing | iex

If you prefer to use the dotnet (global | local) tool, you can install it using the following command:

dotnet tool install --global Perla

Note: From v1.0.0-rc-002 onwards, the dotnet tool requires dotnet 10 preview 7 or above to be installed as we leverage the new multi-rid nuget packaging. This is due the extra weight playwright puts over us by bundling nodejs for each target platform (win, linux, osx, and arch x64 and arm64) on net8 our nuget package goes over 400mb which is over the allowed size on NuGetUploads (they don't have this issue though 😜).

We'll try to address this issue by splitting the testing support in a separate tool in the future if feasible.

The install scripts and manual download from the releases page still work unchanged.

Once you're done with the installation, you can run perla --help to verify that the installation was successful.

Description:
  The Perla Dev Server!

Usage:
  Perla [command] [options] [[--] <additional arguments>...]]

Options:
  -?, -h, --help  Show help and usage information
  --version       Show version information

Commands:
  create, generate, n, new <name>     Creates a new project based on the selected template if it exists
  r, restore                          Restores the project dependencies from the perla.json file
  a, add, i, install <packages>       Adds a package to the project dependencies
  remove, rm <packages>               Removes a package from the project dependencies
  list, ls                            Lists the current dependencies in a table or an npm style json string
  s, serve, start                     Starts the development server and if fable projects are present it also takes care of it.
  b, build                            Builds the SPA application for distribution
  templates <TemplateRepositoryName>  Handles Template Repository operations such as list, add, update, and remove templates []
  describe, ds <properties>           Describes the perla.json file or it's properties as requested

Additional Arguments:
  Arguments passed to the application that is being run.

If you actually use and like nodejs, then you would be better taking a look at the tools that inspired this repository

• jspm - Import map handling, they are the best at manipulating import maps ❤️
• vite
• snowpack

These tools have a bigger community and rely on an even bigger ecosystem plus they support plugins via npm so if you're using node stick with them they are a better choice Perla's unbundled development was inspired by both snowpack and vite, CDN dependencies were inspired by snowpack's remote sources development