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

bma

v0.0.7

Published

branch manage abstract

Downloads

8

Readme

BMA (Branch Management Abstract)

This is used to manage your git branches automatically and follow some specs.

Branch Specs

Env Branches

env branches are used to deploy, which are not editable. You can only merge to these branches, solve conflict and push.

  • online: master
  • qa: qa
  • dev: dev
  • stage: stage
  • beta: beta

what's more, you can modify the branch name for envs through

setConfig('branch', {dev: 'develop'})

for example.

develop Branches prefix

  • feature
  • bugfix
  • hotfix
  • custom

each develop branch is prefixed with sepcified flag. your can config the branch-prefix through

setConfig('branchPrefix', {feature: 'feature/TASK-'})

Branch Manage

newBranch

  <boolean> newBranch(type, id, config)

  desc: create a new develop branch for specified type
  params:
    type: branch type to create
    id: branch id or desc to specify the task
    config:
      silence: set true to disconsole step info

mergeMasterToBranch

  <boolean> mergeMasterToBranch(branchName, config)

  desc: merge master to specified branch
  params:
    branchName: targetBranchName
    config:
      silence: set true to disconsole step info

mergeToMainBrach

  <boolean> mergeToMainBrach(branchName, mainBranch, config)

  desc: merge specified branch to a main branch
  params:
    branchName: target Branch Name
    mainBranch: main branch type, configured in conf
    config:
      mergeMaster: merge Master to branch before merge action
      forceEnvBranch: specify mainBranchName
      silence: set true to disconsole step info