### Initialize Soundworks Project

Source: https://github.com/collective-soundworks/soundworks/blob/main/tests/integration/test-browser/README.md

Use the soundworks wizard to interactively configure and create new clients, install plugins, and set up environment configuration files.

```bash
npx soundworks
```

--------------------------------

### Manually install @soundworks/core

Source: https://github.com/collective-soundworks/soundworks/blob/main/README.md

This command installs the core soundworks package. It is typically handled automatically by the `@soundworks/create` wizard.

```sh
npm install @soundworks/core
```

--------------------------------

### Start Server with Production Environment Configuration

Source: https://github.com/collective-soundworks/soundworks/blob/main/tests/integration/test-browser/README.md

Set the `ENV` environment variable to `prod` to start the server using the `/config/env/prod.js` configuration file. This allows for environment-specific settings.

```bash
ENV=prod npm run start
```

--------------------------------

### Create New Soundworks Application

Source: https://github.com/collective-soundworks/soundworks/blob/main/misc/assets/DOC.md

Use this command to create a new soundworks application with the guided wizard. Refer to the getting started guide for detailed instructions.

```sh
npx @soundworks/create@latest
```

--------------------------------

### Manual Installation of Soundworks Core

Source: https://github.com/collective-soundworks/soundworks/blob/main/misc/assets/DOC.md

Install the @soundworks/core package manually using npm. This is an alternative to using the creation wizard.

```sh
npm install --save @soundworks/core
```

--------------------------------

### Launch Server Without Rebuilding

Source: https://github.com/collective-soundworks/soundworks/blob/main/tests/integration/test-browser/README.md

The `npm run start` script is a shortcut to launch the server without rebuilding the application. It directly executes the server's entry point.

```bash
npm run start
```

--------------------------------

### Emulate Multiple Node Client Instances

Source: https://github.com/collective-soundworks/soundworks/blob/main/tests/integration/test-browser/README.md

The `EMULATE` environment variable, when used with `npm run watch:process`, allows running multiple node client instances in parallel within the same terminal. For example, `EMULATE=4` launches 4 instances of the client `thing`.

```bash
EMULATE=4 npm run watch:process thing
```

--------------------------------

### Build Application for Production

Source: https://github.com/collective-soundworks/soundworks/blob/main/tests/integration/test-browser/README.md

The `npm run build:prod` script builds the application for production, including minifying files for browser clients.

```bash
npm run build:prod
```

--------------------------------

### Launch Application in Development Mode

Source: https://github.com/collective-soundworks/soundworks/blob/main/tests/integration/test-browser/README.md

The `npm run dev` script launches the application in development mode. It watches for file changes, transpiles and bundles files, and restarts the server as needed.

```bash
npm run dev
```

--------------------------------

### Watch and Restart Node Client

Source: https://github.com/collective-soundworks/soundworks/blob/main/tests/integration/ping-pong/README.md

Launches a specific node client (e.g., 'thing') and restarts it automatically when its source files are updated. Requires 'npm run dev' to be running in another terminal.

```bash
npm run watch thing
```

--------------------------------

### Watch and Restart Node Client

Source: https://github.com/collective-soundworks/soundworks/blob/main/tests/integration/test-browser/README.md

The `npm run watch [name]` script is used for node clients. It launches the specified client and restarts it when its sources are updated. This is typically used alongside `npm run dev`.

```bash
npm run dev
npm run watch thing
```

--------------------------------

### Override Server Port

Source: https://github.com/collective-soundworks/soundworks/blob/main/tests/integration/test-browser/README.md

Use the `PORT` environment variable to override the default port defined in the configuration file. This allows launching the server on a specific port, such as `3000`.

```bash
PORT=3000 npm run start
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.