# lamdera

> npm install wrapper for Lamdera

Latest version **0.19.1-1.4.0** (published 2025-12-31) · BSD-3-Clause license · 0 weekly downloads

## Install

```sh
npm install lamdera
pnpm add lamdera
yarn add lamdera
bun add lamdera
```

Provides the command `lamdera`.

## Health

**Score 50/100 (C)** — status: stable.

Positive: esm support; no vulnerabilities.

Warnings: low downloads; no types; pre 1.0.

## Facts

| | |
|---|---|
| Version | 0.19.1-1.4.0 |
| Published | 2025-12-31 |
| First published | 2023-06-01 |
| Weekly downloads | 0 |
| License | BSD-3-Clause |
| TypeScript types | none |
| Module format | ESM + CommonJS |
| Dependencies | 0 |
| Unpacked size | 8.3 KB |
| Known vulnerabilities | 0 |
| Install scripts | yes |
| Author | Mario Rogic |
| Maintainers | lamdera |
| Keywords | bin, binary, binaries, lamdera, install, installer |

## Links

- npm: https://www.npmjs.com/package/lamdera
- Repository: https://github.com/lamdera/compiler
- Homepage: https://github.com/lamdera/compiler#readme
- Issues: https://github.com/lamdera/compiler/issues
- npm.io page: https://npm.io/package/lamdera

## Alternatives

- [@mdxeditor/editor](https://npm.io/package/@mdxeditor/editor.md) — 962.4K weekly downloads
- [mmdb-lib](https://npm.io/package/mmdb-lib.md) — 680.9K weekly downloads
- [playcanvas](https://npm.io/package/playcanvas.md) — 36.2K weekly downloads
- [@glw907/cairn-cms](https://npm.io/package/@glw907/cairn-cms.md) — 967 weekly downloads
- [markdown-to-confluence](https://npm.io/package/markdown-to-confluence.md) — 103 weekly downloads

## Recent versions

- 0.19.1-1.4.0 (latest) — 2025-12-31
- 0.19.1-1.3.2 — 2024-11-02
- 0.19.1-1.3.1 — 2024-10-27
- 0.19.1-1.2.1-1 — 2023-10-29
- 0.19.1-1.2.1 — 2023-10-29
- 0.19.1-1.2.0-1 — 2023-09-17
- 0.19.1-1.1.1-3 — 2023-08-27
- 0.19.1-1.1.1-2 — 2023-08-27
- 0.19.1-1.1.1 — 2023-06-01

## README

# Lamdera NPM Installer

[Lamdera](https://lamdera.com) is a delightful platform for full-stack web apps built with [Elm](https://elm-lang.org/).

The Lamdera compiler is a super-set of the Elm compiler and a drop-in replacement: you can use `lamdera` on your existing non-Lamdera Elm projects in the same way you use `elm`.

Beware of [Elm IDE gotchas](https://dashboard.lamdera.app/docs/ides-and-tooling), you'll need to set Lamdera as your Elm compiler.


<br/>

## What is this package for?

### Normal installs ❌

Use the instructions [here](https://dashboard.lamdera.app/docs/download) instead.

Lamdera has no dependency on `npm` to develop locally, so there's no reason to introduce it unless you specifically want to use `npm` for other reasons.

It will also mean you have duplicate copies of the lamdera binary in every single `node_modules`.

### Tooling author ✅

If you're a tooling author, use Lamdera as a dependency and npm as a distribution method, then you _could_ use this package to manage the dependency and installation.

```
npm install --save-dev lamdera@latest
```

It still has the duplication per `node_modules` problem.

### Multiple versions ⚠️

You could also use this package to use different versions of Lamdera in different projects. I.e. `npm install lamdera@latest` in each project and use the binary at `./node_modules/.bin/lamdera` for compilation. However this is generally not recommended. Lamdera users should always use the latest release, as that's what is used when you do a `lamdera deploy`.


### Continuous integration ⚠️

This works, but there are usually faster and more reliable options:

1. You can download `lamdera` directly from [the downloads page](https://dashboard.lamdera.app/docs/download). This is all the `npm` installer does, but with extra HTTP requests to `npmjs.com` servers, making it slower and adding more failure points.
2. Many continuous integration pipelines offer ways to cache files ([i.e. github actions cache](https://github.com/marketplace/actions/cache)) to make builds faster and more reliable.

That said, it will definitely work to use the `npm` installer on CI if you prefer that option.


<br/>

## Install Locally

The following command should download the latest Lamdera binary:

```
npm install lamdera@latest
```

You should be able to run `npx lamdera --version` within your project and see `0.19.1` (the base Elm version), or `--version-full` to see the full Elm + Lamdera release version. Now you can develop with `npx lamdera live`.

---
_Source: https://npm.io/package/lamdera · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._