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

balm

v4.31.0

Published

BalmJS runtime core

Downloads

227

Readme

NPM version License Coverage Percentage

balm@3(v3) supports for [email protected]+, postcss@7, webpack@4

Introduction

BalmJS prescribes best practices and tools to help you stay productive.

  • Naturally: Make web development simple, natural and pleasant.
  • Structure-Based: One configuration file can manage webapp projects with at least 90% use cases.
  • Learn Once, Run Any Webapps: Any front-end technology stack will be developed and built in the same way.

Features

  • Based on gulp + webpack for webapp projects
  • Automagically compile PostCSS/Sass/Less
  • CSS Autoprefixing
  • Automagically generate CSS Image Sprites
  • enable ES2015+ features using Babel
  • Awesome images optimization
  • Built-in preview server with BrowserSync
  • Custom publish assets to remote (Front-end to Back-end) project
  • ZIP/FTP/PWA supported
  • Easily define and extend your own tasks

Structure

: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.
└── ...

Installation

0. Requirements

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.0 by running node -v in 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

1. Installing balm

yarn 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.

2. Configuration

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.

3. Usage

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

Demo

Documentation

To download example and try it, visit balm.js.org.

Ecosystem

| Project | Status | Description | | ---------------------------------------------------------- | -------------------------------------------------------- | ------------------------------------------------------------------ | | balm-core | NPM version | :black_joker: BalmJS compiler core (required for balm 3.0+) | | balm | NPM version | :black_joker: BalmJS runtime core | | balm-cli | NPM version | :spades: BalmJS scaffolding tool | | balm-gui | N/A | :clubs: GUI for BalmJS | | balm-ui-lite | NPM version | :hearts: Material Design Lite + Vue | | balm-ui | NPM version | :diamonds: Next Generation Material UI for Vue.js | | balm-scroll | NPM version | :scroll: Smooth scrolling for Vue.js | | balm-ui-pro | NPM version | More configuration definition, less code implementation for Vue.js | | balm-git-flow | NPM version | The best practices for front-end git flow |

Contributing

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.

License

MIT

© 2016-present, Elf-mousE