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 🙏

© 2024 – Pkg Stats / Ryan Hefner

cam-baker

v0.9.0

Published

Non official Camunda CLI for building Tasklist embedded forms

Downloads

25

Readme

NPM License Netlify Status

Installation

npm install cam-baker

# or yarn

yarn add cam-baker

How to use

Call CLI commands directly using npx <command> pattern:

npx baker dev
# or
npx baker build
# or
npx baker stop

Or create your own NPM Scripts on package.json to initilize and build the project

{
  "scripts": {
    "dev": "baker",
    "build": "baker build",
    "stop": "baker stop"
  }
}

Avaliable Commands

|Command |Example |Description| |-----------|------------|-----------| |<default>|baker -c config/my-config.js|initialize CLI watchers and services| |dev |baker dev |same as above baker default command| |build |baker build |build entry files into standalone html files for Camunda Tasklist| |stop |baker stop |stops Camunda Run server| |help |baker help |show CLI commands and options|

Custom Config Path and Filename: -c or --config Used to indicate custom filename and path to the config file, needed when you don't want to use the default camunda.config.js.

npx baker --config config/my-custom-config-file.js

Configuration

See the Configuration Guide

Configuration File Example

camunda.config.js

import { defineConfig } from 'cam-baker'

export default defineConfig({
  // using `defineConfig` enables support for editor intellisense
})

Next Steps

  • Validate the idea throwing the repo for Camunda and dev community
  • Add more detailed usage instructions, specially on how to handle deploys with ./public and ./dist artifacts
  • Add more detailed usage instructions when running Camunda from a Spring Project (no need for ./public)
  • Add a minimal test coverage
  • Evaluate usage of Vite with custom plugins/configuration instead low level implementations