-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BREAKING: Remove built-in copy of standard
#17
Conversation
5f1a654
to
ac7e149
Compare
`standard` is no longer bundled with snazzy. You must install `standard` manually alongside `snazzy`. Run `npm install standard --save-dev` to get a copy of `standard`, then run `standard | snazzy` where you previously used to ran `snazzy`. Though this takes more steps, it's better because it allows the user to control the exact version of `standard` that gets used. And for users who were piping into `snazzy` all along, this means a quicker install, since an extra copy of `standard` will not get installed.
bin/cmd.js
Outdated
} | ||
}) | ||
|
||
process.stdout.on('error', function () {}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this line intentional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought that I introduced that line to prevent a bug in Node.js, but I can't find the commit where I introduced it. This line was been in the codebase since the initial commit.
I'll remove it and see if anything breaks! 😅
@feross just one comment, otherwise looks good. Also might want to bump node versions in |
What if
And then var outputFormatter
try {
outputFormatter = require(moduleNameFromConfig)
} catch (e) {
outputFormatter = normalDefaultOutput
} |
Thanks for the review, @ungoldman! @jsumners I'm hesitant to add config options to |
7.0.0 |
standard
is no longer bundled with snazzy. You must installstandard
manually alongsidesnazzy
.Run
npm install standard --save-dev
to get a copy ofstandard
, then runstandard | snazzy
where you previously used to ransnazzy
.Though this takes more steps, it's better because it allows the user to control the exact version of
standard
that gets used. And for users who were piping intosnazzy
all along, this means a quicker install, since an extra copy ofstandard
will not get installed.