
Security News
Insecure Agents Podcast: Certified Patches, Supply Chain Security, and AI Agents
Socket CEO Feross Aboukhadijeh joins Insecure Agents to discuss CVE remediation and why supply chain attacks require a different security approach.
balm-core
Advanced tools
balm-core@3(v3) supports fornode@10.13.0+,postcss@7,webpack@4
BalmJS prescribes best practices and tools to help you stay productive.
:rocket: We recommend using Balm CLI to scaffold out a front-end web app.
project
├── .tmp // Scaffolds out a temporary directory for development
├── dist // Scaffolds out the production build
├─┬ src // Source code in here (Create a directory in project)
│ ├── fonts
│ ├── images
│ ├── media
│ ├─┬ scripts
│ │ └── index.js // Required. A entry file for JS.
│ ├─┬ styles
│ │ └── main.css // Required. A entry file for CSS.
│ └── index.html // Required. A entry file for HTML.
├── .dotfile // (e.g. .gitignore, .browserslistrc, etc...)
├── babel.config.js
├── balm.config.js // Required. A configuration file for Balm.
├── package.json // Required.
└── ...
You need to set up your development environment before you can do anything.
Install Node.js® and npm if they are not already on your machine.
Verify that you are running at least node
18.12.0by runningnode -vin a terminal/console window. Older versions maybe produce errors, but newer versions are fine.
You develop apps in the context of an Balm workspace.
To create a new workspace and initial starter app:
# /path/to/YOUR_WORKSPACE
mkdir -p my-project/src/{styles,scripts}
echo "Hello World" > my-project/src/index.html
cd my-project
npm init -y
balmyarn global add balm-core
yarn add -D balm
OR
npm install -g balm-core
npm install -D balm
We currently recommend using Yarn instead of npm.
In your project directory, create a file named balm.config.js in your project root with these contents:
module.exports = {
// Your project config
};
:page_with_curl: Refer to configuration docs to learn more about config balm.
Edit package.json in your project directory:
{
"scripts": {
"dev": "balm",
"prod": "balm -p"
}
}
Run the command in your project directory:
# For development
npm run dev
# For production
npm run prod
To download example and try it, visit balm.js.org.
| Project | Status | Description |
|---|---|---|
| balm-core | :black_joker: BalmJS compiler core (required for balm 3.0+) | |
| balm | :black_joker: BalmJS runtime core | |
| balm-cli | :spades: BalmJS scaffolding tool | |
| balm-gui | N/A | :clubs: GUI for BalmJS |
| balm-ui-lite | :hearts: Material Design Lite + Vue | |
| balm-ui | :diamonds: Next Generation Material UI for Vue.js | |
| balm-scroll | :scroll: Smooth scrolling for Vue.js | |
| balm-ui-pro | More configuration definition, less code implementation for Vue.js | |
| balm-git-flow | The best practices for front-end git flow |
We'd love for you to contribute and make BalmJS even better than it is today! Please make sure to read the Contributing Guide before making a pull request. You can submit any ideas as pull requests or as GitHub issues.
© 2016-present, Elf-mousE
FAQs
BalmJS compiler core
The npm package balm-core receives a total of 8 weekly downloads. As such, balm-core popularity was classified as not popular.
We found that balm-core demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Socket CEO Feross Aboukhadijeh joins Insecure Agents to discuss CVE remediation and why supply chain attacks require a different security approach.

Security News
Tailwind Labs laid off 75% of its engineering team after revenue dropped 80%, as LLMs redirect traffic away from documentation where developers discover paid products.

Security News
The planned feature introduces a review step before releases go live, following the Shai-Hulud attacks and a rocky migration off classic tokens that disrupted maintainer workflows.