jackmellis / mono-semantic Goto Github PK

It looks like npmlog is getting overwritten or reset or something, it's definitely not right (and probably is being affected by outside applications).

Best solution is probably to wrap npmlog in another object that basically re-sets the npmlog config each time before logging. That way we should always know the log levels are correct.

• should not create any tags
• should not publish
• should output additional messages
• should output a message at the start of each process

Like githubUrl or githubToken

travis / codeclimate / semantic-release

also add an .npmignore

the publish command should have an --ignore-scripts

the pre command should run the publish scripts

before:

• prepublish
• prepare
• prepublishOnly

after:

• publish
• postpublish

I guess this means we will need lerna installed (should it be a dev dependency).
yarn lerna help - to check that lerna is available
yarn lerna --scope=${pkg.name} run ${script}

handle commits in this format:

feat(package1, package2, package3): changed three packages

The commit analyzer will need to separate these out to check if it matches the current package. The changelog generator will also need to take this into account.

I'm not even sure if the config options are being passed through

the repository could also be a string

You should be able to check pkg.scripts[script]

if something goes wrong during pre it will probably be fine, since nothing is published or committed

if something goes wrong during the publish stage, we could easily find ourselves stuck because half of the packages have been published and half not. Once a package is published, there's not really any way to undo it either

if something goes wrong during post it's not as bad as publish, but it might mean you've got published packages that don't then have git tags

One potential solution would be rather than erroring during the publish phase, we just track which packages published and which didn't, then at the end of the post phase we validate that pre publish and post all succeeded and throw an error for any packages that didn't.