`npm/npx/npm link` on steroids.
npmy --init
npmy + typescript
or dev npmy ++ typescript
npmy - typescript
npmy up
npmy :publish --draft
, npmy :publish --rc
, npmy :publish --minor
npmy :build
npmy @mail-core/cli init
# Install
npm install -g npmy
# Help
npmy --help
npm
# Install
npmy + @mail-core/cli
# Install as dev
npmy ++ @mail-core/cli
# Uninstall
npmy - @mail-core/cli
npm scripts
# `npm start`
npmy :start
# `npm run build`
npmy :build
npm publish
# Release
# version: x.UP.x
# npm.tag: latest
npmy :publish --minor
# RC
# version: x.x.x-{branch}.UP
# npm.tag: rc
npmy :publish --rc
# Draft (prerelease)
# version: x.x.x-{branch}.UP
# npm.tag: draft
npmy :publish --draft
npx
With support custom registry!!1
# Default regsitry
npmy @mail-core/cli init
# Customize
npmy @mail-core/cli init --registry=https://my.npm.registry.dev
npm outdated
# Soft update deps
npmy up
# Update to latest
npmy up --latest
# Update by filter (starts with):
npmy up @mail-core # ← up deps for "@mail-core/*"
npm link
npm install -g npmy
cd path/to/project
.npmyrc
to .gitignore
touch .npmyrc
.npmyrc
as JSON-file and write {"%TARGET_DEPENDENCY%": "%LOCAL_PATH_TO_PACKAGE_FOLDER%"}
npmy --link .
npmy --link [path] [--include=pattern]
path
— by default current folderadd
— add packages into .npmyrc
(relative or absolute pattern)include
— see glob
version
— print current versionverbose
— process detailing of installation and linkingnpmy --link
— special tool for local packages development, subjecting to other packages being in development.
Usually I solve this task via npm link, or just symlink. These methods don't work, when dependent package has difficult publish cycle (modifies it's source, e.g. using Babel/Rollup/etc) or there are more then one.
Trust me, npmy --link
covers all above mentioned tasks.
# Before: `cd` to your project folder
npmy --link --pkg=tx-i18n --to=~/artifact-project/tx-i18n
npm i
npm test
, code coverage