When installing chromatism v3, console log is present in chromatism.umd.js

[Jason Nall]

If you want to see for yourself:

Browse to https://unpkg.com/chromatism@3.0.0/dist/chromatism.umd.js

Perform a search for console.log

There's no console logs present in src on master... is it possible that the umd build was not built for the 3.0.0 release? What else could be causing this?

[Josh Duff]

I'd guess some uncommitted debug code was probably published.

That's one of the reasons I only ever release with these bash commands:

alias patch='pre-version && npm version patch && post-version'
alias feature='pre-version && npm version minor && post-version'
alias breaking='pre-version && npm version major && post-version'
alias pre-version='git diff --exit-code && npm prune && npm install -q && npm test'
alias post-version='(npm run build; exit 0) && git diff --exit-code && git push && git push --tags && npm publish'

it's saved me from bad publishes several times.

[Jason Nall]

@TehShrike Yep, I'm personally a fan of https://github.com/sindresorhus/np

[Josh Duff]

For what it's worth, chromatism2 has no console.logs.