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 🙏

© 2026 – Pkg Stats / Ryan Hefner

dartvel_dev

v0.13.16

Published

Dartvel — a batteries-included, AI-native full-stack application platform built around Flutter. This is the npm launcher for the CLI published on pub.dev as dartvel_dev.

Readme

dartvel_dev

The dartvel command for Dartvel, a full-stack application platform built around Flutter: code generation, a dev server with hot reload across the app and its backend, builds for web, mobile, desktop, TV and embedded targets, and deployment.

npm install -g dartvel_dev
dartvel --help

# or without installing
npx dartvel_dev --help

Installing puts two names on your PATH, dartvel and dartvel_dev, for the same program. dartvel_cli is an alias package that installs this one.

What this package does

It is a launcher. The first time it runs, it downloads the self-contained dartvel binary for your platform from the GitHub release with the same version as this package, checks it against the SHA256SUMS published with that release, and keeps it in vendor/ inside the package. Later runs start that binary directly. Arguments, output and the exit code pass through unchanged.

The Dart runtime and the Rust server library are linked into the binary, so nothing has to be installed first. Building an application still needs Flutter, for whichever target you are building. Running the CLI does not.

A release without a SHA256SUMS file still installs, with a message saying the download was not verified. A checksum that does not match is an error, and nothing is kept.

Platforms

| Platform | Release asset | |---|---| | Linux x64 | dartvel-linux-amd64 | | Linux arm64 | dartvel-linux-arm64 | | macOS Intel | dartvel-darwin-amd64 | | macOS Apple silicon | dartvel-darwin-arm64 | | Windows x64 | dartvel-windows-amd64.exe |

Windows on ARM has no build yet; the launcher says so rather than fetching a URL that does not exist. The x64 binary runs there under emulation if you download it yourself. Node 18 or newer.

For 0.11.5, only the Linux binaries are attached until the CI release workflow has run. Until then, on macOS or Windows the first run fails with HTTP 404 and prints the release page. Run the CLI from a project's dependencies with dart run dartvel_cli:dartvel (see the dartvel_cli README).

First steps

dartvel create my_app
cd my_app
dartvel dev

dartvel doctor checks your Dart, Flutter and project setup, and dartvel doctor --target <target> checks one build target's toolchain. The command reference, configuration and troubleshooting are in the dartvel_cli README.

Why not dart pub global activate

An earlier version of this package ran dart pub global activate dartvel_dev and then the activated command. That cannot work: the dartvel_dev package on pub.dev depends on the Flutter SDK, and pub refuses to run a global executable from such a package. It activated, and then every run failed with:

dartvel_dev as globally activated requires the Flutter SDK, which is unsupported for global executables.

Downloading the compiled binary avoids pub altogether.

Why the package is dartvel_dev and the command is dartvel

dartvel on pub.dev was taken on 2026-08-06 by an unrelated package, so the published identifier carries a suffix. The command does not, and neither does anything else you interact with. The same name is used on pub.dev, npm and in the Homebrew tap.

Links