0.9.0 • Published 2 years ago
cam-baker v0.9.0
Installation
npm install cam-baker
# or yarn
yarn add cam-bakerHow to use
Call CLI commands directly using npx <command> pattern:
npx baker dev
# or
npx baker build
# or
npx baker stopOr 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.jsConfiguration
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
./publicand./distartifacts - 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
0.8.4
2 years ago
0.9.0
2 years ago
0.8.3
2 years ago
0.8.2
2 years ago
0.8.1
2 years ago
0.8.0
2 years ago
0.7.1
2 years ago
0.7.0
2 years ago
0.6.0
3 years ago
0.5.0
3 years ago
0.4.1
3 years ago
0.4.2
3 years ago
0.4.0
3 years ago
0.3.1
3 years ago
0.3.0
3 years ago
0.2.0
3 years ago
0.1.1
3 years ago
0.1.0
3 years ago
0.0.1
3 years ago