oresoftware / npp

▷ Tool for publishing multiple packages to NPM

NPP / @oresoftware/npp

Publish your dependency trees to NPM with ease. NPP goes hand-in-hand with NLU (npm-link-up)

Caveats / Disclaimer

• Currently only works with Git
• You need Git version > 2.7.0 on your local machine

Quick reference

npp view

npp's Issues

list all git branches without an asterisk

https://stackoverflow.com/questions/51696931/list-all-local-git-branches-without-an-asterisk/51697007#51697007

list all git branches without an asterisk

git for-each-ref --format='%(refname)' refs/heads/*

if package can't be found, we need to throw an error

with this setup:

  "searchRoots": [
    "/home/oleg/WebstormProjects/oresoftware/r2g",
    "/home/oleg/WebstormProjects/sumanjs/suman",
    "/home/oleg/WebstormProjects/sumanjs/suman-types",
    "/home/oleg/WebstormProjects/sumanjs/suman-watch"
  ],
  "packages": {
    "@oresoftware/r2g": true,
    "suman": true,
    "suman-types": true,
    "suman-watch": true
  }

"@oresoftware/r2g" won't be found, because the package name was refactored to just "r2g", so we need to throw an error in that case.

use package.json homepage property

a link like this should appear in the console:
https://github.com/ORESoftware/npp#readme

but it should be sliced to remove the first # char

npm install --save-exact

npm install --save-exact

should save the exact versions, better for libraries.

-d option should delete old branches

The -d option should go through all local branches (not the current branch) and delete them if they are up-to-date with the integration branch

git fetch should only happen once per repo

git fetch origin should only happen once per repo

after creating each release branch, wait for the user to merge on github before continuing

after creating each release branch, wait for the user to merge on github before continuing

get most recent commit of .npp.json file

sha=`git log --all --format=format:%H -n 1 -- .npp.json`
git branch  --contains "$sha" | head -n 1 | tr -d " *"

npp view should not checkout other branches?

npp view should just use the current branch, not checkout integration_temp?

use verdaccio to allow users to do a trial publishing

run through publishing once, then publish to verdaccio

then run it again and skip the version bump

multiple locks keys - using object container for single argument

https://stackoverflow.com/questions/51812488/give-a-string-a-type-besides-string

Have to use the integration branch value .npp.json file instead of using remotes/origin/master

Have to use the integration branch value .npp.json file instead of using remotes/origin/master

change table header color from red to blue

change table header color from red to blue

before publishing, check to see if release branch is merged into master

before crafting releases, we checked to see if branches have all been completely merged into integration

after crafting releases, we depend on the user to merge them into master branches

before we publish we should check to see if each release branch has been merged into master

json schema store

SchemaStore/schemastore#363

npp should work for just one package and one without an .npp.json file

npp should work for just one package and one without an .npp.json file

$ npp publish