A 'npm/yarn publish' wrapper with my preferred defaults.

## Publish Package (using yarn): 1. `yarn login` 2. `yarn build` 3. `yarn publish`

testing publishing a fork of fullcalendar using yarn publish

``` yarn build yarn publish --new-version 0.0.25 ```

```shell yarn release # npm login yarn publish ```

yarn publish test

- yarn install - yarn build - yarn publish

yarn publish

A better `yarn publish`

- yarn install - yarn build - yarn publish (in case you want to publish the project to a private registry.)

## Publishing Compile es module via rollup `yarn compile` Then publish via `yarn publish` This will ask you to update the version

1. Bump common-gateway-react version and add -betaX 1. Publish this version to npm - `yarn publish --tag beta` 1. Set this as the version in the RC 1. PR and have it tested 1. When all good, remove -betaX and release a formal version 1. Set this as the

Generic CLI tool to automate versioning and package publishing-related tasks.

yarn build # publish yarn publish

``` npm publish --access public yarn publish --access public ```

Work with npm/yarn packages locally like a boss.

Organise your package versioning and publishing to make both contributors and maintainers happy

Various JavaScript/TypeScript utilities of wide relevance to the MetaMask codebase

- yarn install - yarn build - yarn publish (in case you want to publish the project to a private registry.)

Algorithm for finding the root of a yarn workspace, extracted from yarnpkg.com