I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Release Notes
1.6.0: Config File, JSX
I want to give a special shout out to @azz who has been maintaining the repository and implementing a bunch of the changes in this release as I had less time to devote to prettier due to vacation and switching team :)
Highlights
Configuration
Implement cosmiconfig for workspace configuration (#2434) by @azz
Since the very first release of prettier, people have asked for a .prettierrc file. We've been trying to have as few options as possible and tried to avoid being one more .dotfile that you have to have when starting a new project.
But, the truth is, we need to have some way to configure prettier that can be kept in sync with all the integrations. By not having one, we pushed the problem to them and saw a bunch of incompatible ways of handling the problem. So now, it's handled by prettier itself.
// .prettierrc
{
"trailingComma": "es5",
"singleQuote": true
}For more information on configuration file support, see the README.
Along with telling what configuration to use, you can write a file .prettierignore to tell which files not to convert.
# .prettierignore
dist/
package.json
JSX
Improve JSX Formatting (#2398) by @suchipi
The last big friction point from people trying to adopt prettier was around how JSX was being printed. We went through all the issues that were raised and made a bunch of changes:
- Arrow Function Expressions returning JSX will now add parens when the JSX breaks
// Before
const Component = props =>
<div>
Hello {props.name}!
</div>;
// After
const Component = props => (
<div>
Hello {props.name}!
</div>
);
- Conditional expressions within (or containing) JSX are formatted in a different way using parenthesis
// Before
<div>
{props.isVisible
? <BaseForm
url="/auth/google"
method="GET"
/>
: <Placeholder />}
</div>;
// After
<div>
{props.isVisible ? (
<BaseForm
url="/auth/google"
method="GET"
/>
) : (
<Placeholder />
)}
</div>
- JSX in logical expressions (|| or &&) is always wrapped in parens when the JSX breaks
// Before
<div>
{props.isVisible &&
<BaseForm
url="/auth/google"
method="GET"
/>}
</div>;
// After
<div>
{props.isVisible && (
<BaseForm
url="/auth/google"
method="GET"
/>
)}
</div>
Hopefully this is going to be more in line with how the majority of the community is writing JSX and we can have prettier be used in more place ;)
Inline single expressions in JSX (#2442) by @karl
With JSX, we started by respecting a lot of line breaks that were in the original source. This had the advantage of doing fewer changes to your codebase but chipped away the value of a consistent pretty printer as the same semantic code could be written in two ways.
During each new release we've tightened this and made decisions around how to always print a piece of code. The latest of those is what happens if there's a single child in a JSX object, we're now always going to inline it.
// Before
return (
<div>
{this.props.test}
</div>
);
return <div>{this.props.test}</div>;
// After
return <div>{this.props.test}</div>;
return <div>{this.props.test}</div>;
Ensure there is a line break after leading JSX white space (#2348) by @karl
Leading JSX empty spaces are now on their own line. It looked weird to have them before a tag as it "indented" it differently compared to the rest.
// Before
<span className="d1">
{' '}<a
href="https://github.schibsted.io/finn/troika"
className="link"
/>
</span>
// After
<span className="d1">
{' '}
<a
href="https://github.schibsted.io/finn/troika"
className="link"
/>
</span>
Other Changes
JSON
Use babylon.parseExpression for JSON (#2476) by @josephfrazier
We used to use a strict JSON parser that would throw if there was a comment or a trailing comma. This was inconvenient as many JSON files in practice are parsed using JavaScript or json5 that are not as strict. Now, we have relaxed this and are using the JavaScript parser to parse and print JSON. This means that comments will be maintained if there were some.
Note that this is purely additive, if your original file was JSON compliant, it will keep printing a valid JSON.
// Before
Syntax error
// After
{ / some comment / "a": 1 }
JavaScript
Add more supervisory parens (#2423) by @azz
Parenthesis are a hot topic because they are not part of the AST, so prettier ignores all the ones you are putting and re-creating them from scratch. We went through all the things that people reported and came up with a few edge cases that were very confusing when comparisons were chained and % was mixed with * or /.
One thing that we are not changing is the fact that we remove extra parenthesis around combinations of basic arithmetic operators: +-*/.
// Before
x !== y === z;
x * y % z;
// After
(x !== y) === z;
(x * y) % z;
Implement prettier-ignore inside JSX (#2487) by @azz
It's useful to be able to ignore pieces of JSX, it's now possible to add a comment inside of a JSX expression to ignore the formatting of the next element.
// Before
<Component>
{/*prettier-ignore*/}
<span ugly format="" />
</Component>
// Before
<Component>
{/prettier-ignore/}
<span ugly format='' />
</Component>
Do not swallow prettier-ignore comments (#2664)
In order to support some edge cases, in the internals, we have the ability to avoid printing comments in a generic way and print them in the call site instead. It turns out that when we used prettier-ignore, we didn't print the comments at all! This is now fixed.
// Before
push(
<td> :)
</td>,
);
// After
push(
// prettier-ignore
<td> :)
</td>,
);
Fix indentation of a do-while condition (#2359) by @jsnajdr
It took 6 months for someone to report that do-while were broken when the while condition is multi-line, it confirms my hunch that this construct is not widely used in practice.
// Before
do {} while (
someVeryLongFunc(
someVeryLongArgA,
someVeryLongArgB,
someVeryLongArgC
)
);
// After
do {} while (
someVeryLongFunc(
someVeryLongArgA,
someVeryLongArgB,
someVeryLongArgC
)
);
Break sequence expressions (#2388) by @bakkot
Another underused feature of JavaScript is sequence expressions. We used to do a bad job at printing them when they would go multi-line, this has been corrected :)
// Before
(a = b ? c : "lllllllllllllllllllllll"), (a = b
? c
: "lllllllllllllllllllllll"), (a = b ? c : "lllllllllllllllllllllll"), (a = b
? c
: "lllllllllllllllllllllll"), (a = b ? c : "lllllllllllllllllllllll");
// After
(a = b ? c : 'lllllllllllllllllllllll'),
(a = b ? c : 'lllllllllllllllllllllll'),
(a = b ? c : 'lllllllllllllllllllllll'),
(a = b ? c : 'lllllllllllllllllllllll'),
(a = b ? c : 'lllllllllllllllllllllll')
Trim trailing whitespace from comments (#2494) by @azz
We took the stance with prettier to remove all the trailing whitespaces. We used to not touch comments because it's user generated, but that doesn't mean that they should have whitespace :)
// Before
// There is some space here ->______________
// After
// There is some space here ->
Fix interleaved comments in class decorators (#2660, #2661)
Our handling for comments inside of the class declaration was very naive, we would just move all the comments to the top. We now are more precise and respect the comments that are interleaved inside of decorators and around extends.
// Before
// A
// B
// C
@Foo()
@Bar()
class Bar {}
// After
// A
@Foo()
// B
@Bar()
// C
class Bar {}
Improve bind expression formatting (#2493) by @azz
Bind expressions are being discussed at TC39 and we figured we could print it with prettier. We used to be very naive about it and just chain it. Now, we use the same logic as we have for method chaining with the . operator for it. We also fixed some edge cases where it would output invalid code.
// Before
observable::filter(data => data.someTest)::throttle(() =>
interval(10)::take(1)::takeUntil(observable::filter(data => someOtherTest))
)::map(someFunction);
// After
observable
::filter(data => data.someTest)
::throttle(() =>
interval(10)::take(1)::takeUntil(observable::filter(data => someOtherTest))
)
::map(someFunction);
Add support for printing optional catch binding (#2570) by @existentialism
It's being discussed at TC39 to be able to make the argument of a catch(e) optional. Let's make sure we can support it in prettier if people use it.
// Before
Syntax error
// After
try {} catch {}
Add support for printing optional chaining syntax (#2572) by @azz
Another new proposal being discussed at TC39 is an optional chaining syntax. This is currently a stage 1 proposal, so the syntax may change at any time.
obj?.prop // optional static property access
obj?.[expr] // optional dynamic property access
func?.(...args) // optional function or method call
Handle Closure Compiler type cast syntax correctly (#2484) by @yangsu
Comments are tricky to get right, but especially when they have meaning based on where they are positioned. We're now special casing the way we deal with comments used as type cast for Closure Compiler such that they keep having the same semantics.
// Before
let assignment /** @type {string} */ = getValue();
// After
let assignment = /** @type {string} */ (getValue());
Inline first computed property lookup in member chain (#2670) by @azz
It looks kind of odd to have a computed property lookup on the next line, so we added a special case to inline it.
// Before
data
[key]('foo')
.then(() => console.log('bar'))
.catch(() => console.log('baz'));
// After
data[key]('foo')
.then(() => console.log('bar'))
.catch(() => console.log('baz'));
Flow
The flow team introduced two very exciting features under a new syntax. We now support them in prettier. I've personally been waiting for opaque types for a veerrryyyy long time!
// Before
Syntax error
// After
opaque type ID = string;
export type * from "module";
Strip away unnecessary quotes in keys in type objects and interfaces (#2643)
We've been doing this on JavaScript objects since the early days of prettier but forgot to apply the same thing to Flow and TypeScript types.
// Before
type A = {
"string": "A";
}
// After
type A = {
string: "A";
}
Print TypeParameter even when unary function type (#2406) by @danwang
Oopsy, we were dropping the generic in this very specific case.
// Before
type myFunction = A => B;
// After
type myFunction = <T>(A) => B;
Keep parens around FunctionTypeAnnotation inside ArrayTypeAnnotation (#2561) by @azz
Parenthesis... someday we'll get all of them fixed :)
// Before
const actionArray: () => void[] = [];
// After
const actionArray: (() => void)[] = [];
TypeScript
Support TypeScript 2.5 RC (#2672) by @azz
TypeScript 2.5 RC was recently announced, allowing you to use the upcoming "optional catch binding" syntax in TypeScript, too. 🎉
Don't add namespace keyword to global declaration (#2329) by @azz
// Before
namespace global {
export namespace JSX { }
}
// After
global {
export namespace JSX {}
}
Fix <this.Component /> (#2472) by @backus
Thanks to the untyped and permissive nature of JavaScript, we've been able to concat undefined to a string and get some interesting code as a result. Now fixed for this case :)
// Before
<undefined.Author />
// After
<this.Author />
Allow type assertions to hug (#2439) by @azz
We want to make sure that all the special cases that we added for JavaScript and Flow also work for TypeScript constructs. In this case, objects should also hug if they are wrapped in a as operator.
// Before
const state = JSON.stringify(
{
next: window.location.href,
nonce,
} as State
);
// After
const state = JSON.stringify({
next: window.location.href,
nonce,
} as State);
Remove parens for type assertions in binary expressions (#2419) by @azz
Most of the time we add parenthesis for correctness but in this case, we added them for nothing, so we can just get rid of them and have a cleaner code :)
// Before
(<x>a) || {};
// After
<x>a || {};
Print parens around type assertion as LHS in assignment (#2525) by @azz
Yet another case of missing parenthesis. Thankfully we're getting very few of them nowadays and they are for extremely rare edge cases.
// Before
foo.bar as Baz = [bar];
// After
(foo.bar as Baz) = [bar];
Print declare for TSInterfaceDeclaration (#2574) by @existentialism
The declare keyword doesn't do anything for interface so we never put it there. However, it felt weird if you were in a declaration file and seeing everything have declare before it except for interfaces. So now we reprint declare if it was there in the first place.
// Before
interface Dictionary<T> {
[index: string]: T
}
// After
declare interface Dictionary<T> {
[index: string]: T
}
CSS
Normalize quotes in CSS (#2624) by @lydell
In order to get a first version of CSS to ship, we kept string quotes as is. We are now respecting the singleQuote option of prettier. The difficulty here was to make sure that we output correct code for all the crazy escapes, unicode characters, emoji, special rules like charset which only work with double quotes...
// Before
div {
content: "abc";
}
// After
div {
content: 'abc';
}
Normalize numbers in CSS (#2627) by @lydell
Another place where we can reuse the logic we've done for JavaScript to improve CSS printing.
// Before
border: 1px solid rgba(0., 0.0, .0, .3);
// After
border: 1px solid rgba(0, 0, 0, 0.3);
Quote unquoted CSS attribute values in selectors (#2644) by @lydell
I can never quite remember the rules behind quotes around attributes so we're now always putting quotes there.
// Before
a[id=test] {}
// After
a[id="test"] {}
Add support for css keyword (#2337) by @zanza00
// Before
const header = css`.top-bar {background: black;margin: 0;position: fixed;}`
// After
const header = css</span></span> <span class="pl-s"> .top-bar {</span> <span class="pl-s"> background: black;</span> <span class="pl-s"> margin: 0;</span> <span class="pl-s"> position: fixed;</span> <span class="pl-s"> }</span> <span class="pl-s"><span class="pl-pds">;
Support styled-components with existing component (#2552, #2619) by @azz
styled-components has a lot of different variants for tagging template literals as CSS. It's not ideal that we've got to encode all those ways inside of prettier but since we started, might as well do it for real.
styled(ExistingComponent)`
css: property;
`;
styled.button.attr({})</span></span> <span class="pl-s"> border: rebeccapurple;</span> <span class="pl-s"><span class="pl-pds">;
Trim whitespace in descendant combinator (#2411) by @azz
The CSS parsers we use do not give us a 100% semantic tree: in many occasions they bail and just give us what is being entered. It's up to us to make sure we clean this up while maintaining correctness. In this case, we just printed spaces between selectors as is but we know it's correct to always replace it by a single space.
// Before
.hello
.<span class="pl-smi">how</span><span class="pl-k">-</span>you<span class="pl-k">-</span>doin {
height: 42;
}
// After
.hello .how-you-doin {
height: 42;
}
Strip BOM before parsing (#2373) by @azz
I still have nightmares from dealing with BOM in a previous life. Thankfully, in 2017 it's no longer a big issue as most tooling is now aware of it. Thanks @azz for fixing an edge cases related to CSS parsing.
// Before
[BOM]/* Block comment *
html {
content: "#{1}";
}// After
[BOM]/* Block comment */
html {
content: "#{1}";
}GraphQL
Add support for range-formatting GraphQL (#2319) by @josephfrazier
If you tried to use the range formatting feature in a GraphQL file, it would throw an exception, now it properly worked again and only reformats the piece you selected.
Add .gql file extension to be parsed as GraphQL (#2357) by @rrdelaney
At Facebook, we use .graphql extension but it looks like it's common to have .gql as well, doesn't cost a lot to support it in the heuristic that figures out what parser to use.
CLI
Support multiple patterns with ignore pattern (#2356) by @evilebottnawi
It was already possible to have multiple glob patterns but they would be additive, with this change, you can add a glob pattern to ignore some files. It should be very handy to ignore folders that are deeply nested.
prettier --write '{**/*,*}.{js,jsx,json}' '!vendor/**'Make --list-different to work with --stdin (#2393) by @josephfrazier
This is a handy way of knowing if prettier would print a piece of code in a different way. We already had all the concepts in place, we just needed to wire them up correctly.
$ echo 'call ( ) ;' | prettier --list-different
(stdin)
$ echo $?
1
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
|
Branch
|
Build failing 🚨
|
|
Dependency
|
@metahub/karma-jasmine-jquery
|
|
Current Version
|
1.1.1
|
|
Type
|
devDependency
|
This version is covered by your current version range and after updating it in your project the build failed.
@metahub/karma-jasmine-jquery is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ✅ continuous-integration/travis-ci/push The Travis CI build passed Details
- ❌ continuous-integration/appveyor/branch AppVeyor build cancelled Details
Release Notes
v1.1.2
1.1.2 (2018-01-04)
📚 Documentation
⚙️ Continuous Integrations
♻️ Chores
- eslint: Use
eslint-config-pretty (aa7088c)
- package: update @commitlint/config-angular to version 5.1.1 (bbd93c1)
- package: update ava to version 0.24.0 (337f137)
- package: update dependencies (232d933)
- package: update eslint-config-pretty to version 2.1.1 (59ad9a5)
- package: update karma-babel-preprocessor to version 7.0.0 (5ae707e)
- package: update rollup to version 0.49.1 (093b5ef), closes #11
- package: update rollup to version 0.50.0 (c2d6499)
- package: update rollup to version 0.52.0 (f0583c0)
- package: update rollup to version 0.53.0 (697053b)
- put babel conf in package.json (6ef090c)
- remove commitizen (8a8d90d)
- remove commitlint (d0e7213)
- remove commitlint (56cd132)
- Remove git hooks (b7c8479)
- update karma to the latest version (2a4931a)
- update semantic-release (7d4ea9b)
- use Codecov to check for coverage (8798425)
- use XO instead of custom eslint (940336c)
💎 Styles
Commits
The new version differs by 25 commits.
2a4931a chore: update karma to the latest versionefadcfd docs(readme): update repo URL59bc419 docs(readme): Update badges6ef090c chore: put babel conf in package.json940336c chore: use XO instead of custom eslint8798425 chore: use Codecov to check for coverage7d4ea9b chore: update semantic-release8a8d90d chore: remove commitizen56cd132 chore: remove commitlintd0e7213 chore: remove commitlintb7c8479 chore: Remove git hooks697053b chore(package): update rollup to version 0.53.0bbd93c1 chore(package): update @commitlint/config-angular to version 5.1.1f0583c0 chore(package): update rollup to version 0.52.0337f137 chore(package): update ava to version 0.24.0
There are 25 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Version 15.7.0 of semantic-release was just published.
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
- ✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
Release Notes
v15.7.0
15.7.0 (2018-07-10)
Bug Fixes
- do not set
path to plugin config defined as a Function or an Array (f93eeb7)
Features
- allow to define multiple
generateNotes plugins (5989989)
Commits
The new version differs by 12 commits.
24ce560 refactor: build plugin pipeline parameters at initializationeb26254 refactor: use Object.entries rather than Object.keys50061bb refactor: remove unnecessary object destructuring5989989 feat: allow to define multiple generateNotes plugins576eb60 refactor: simplify plugin validationf7f4aab refactor: use the lastInput arg to compute the prepare pipeline next input12de628 refactor: fix incorrect comments in lib/plugins/pipeline.jsd303286 docs: fix default value for analyzeCommits plugined9c456 refactor: always return an Array of results/errors from a plugin pipelinecac4882 docs: clarify verifyRelease plugin description09348f1 style: disable max-params warning for lib/plugins/normalize.jsf93eeb7 fix: do not set path to plugin config defined as a Function or an Array
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Version 15.9.7 of semantic-release was just published.
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
- ✅ continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).
Release Notes
v15.9.7
15.9.7 (2018-08-10)
Reverts
- "fix: do not convert ssh
repositoryUrl to https" (93377eb)
Commits
The new version differs by 1 commits.
93377eb revert: "fix: do not convert ssh repositoryUrl to https"
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The devDependency karma was updated from 3.0.0 to 3.1.0.
🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
karma is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/appveyor/branch: Waiting for AppVeyor build to complete (Details).
- ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
Release Notes for v3.1.0
Bug Fixes
Features
- config: Add config option for browser socket timeout (#3102) (11e3a9d), closes #2927
- config: add support for ES modules (e811adb)
- frameworks: report start() errors back to server. (#3126) (8257375)
- server: .dom files include HTML tags in page. (#3178) (4651524)
- server: Add public API to force a file refresh (dab8a82)
- server: Add stop method (#3153) (6d96d8e), closes #3149
- server: Add support for encoded source files (#3123) (68b37d3)
Commits
The new version differs by 43 commits.
0a2d2e9 chore: release v3.1.02385690 chore: update contributorsf94284d refactor(lib): use assert library instead of throwing error directly8542f27 refactor(lib): coffe script support (#3188)1458267 refactor(lib): small update in lib/emitter_wrapperc311ac0 refactor(server): use ES6 string interpolation wherever possible7634e71 fix(browser): emit 'browsers_change' in collection (#3183)e811adb feat(config): add support for ES modules0f8b2b1 fix(config): remove phantomjs in favor of chrome headless (#3175)f28a454 refactor(server): Clearer error messages on fatal errors4651524 feat(server): .dom files include HTML tags in page. (#3178)5cc4089 refactor(server): refactoring of stopper (#3174)8efb28d refactor(server): refactoring of lib/browser (#3171)dab8a82 feat(server): Add public API to force a file refresh871a1c9 refactor(server): refactoring of watcher (#3173)
There are 43 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The devDependency codecov was updated from 3.1.0 to 3.2.0.
🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
codecov is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
- ❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).
Commits
The new version differs by 3 commits.
e427d90 feat(services): add azure pipelines (#114)023d204 Use small HTTP dependency (#110)500f308 Update Readme
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Version 4.1.6 of sinon was just published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
sinon
|
|
Current Version
|
4.1.5
|
|
Type
|
devDependency
|
This version is covered by your current version range and after updating it in your project the build failed.
sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
- ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
Commits
The new version differs by 10 commits.
68c37ed Update docs/changelog.md and set new release id in docs/_config.ymlcd8ae51 Add release documentation for v4.1.629e80be 4.1.6a5c59a5 Update History.md and AUTHORS for new release0ae60b6 Merge pull request #1653 from mroderick/upgrade-dependenciesdcd4191 Upgrade browserify to latesta316f02 Upgrade markdownlint-cli to latest78ebdb3 Upgrade lint-staged to latestfcf967b Upgrade dependency supports-color7c3cb4f Enable StaleBot with default configuration (#1649)
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Version 15.9.14 of semantic-release was just published.
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
- ✅ continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).
Release Notes
v15.9.14
Bug Fixes
- pass custom
env and cwd to env-ci (540d4fa)
Commits
The new version differs by 1 commits.
540d4fa fix: pass custom env and cwd to env-ci
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Version 15.9.2 of semantic-release was just published.
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
- ✅ continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).
Release Notes
v15.9.2
15.9.2 (2018-07-30)
Bug Fixes
- also hide sensitive info when loggin from
cli.js (43d0646)
Commits
The new version differs by 1 commits.
43d0646 fix: also hide sensitive info when loggin from cli.js
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Version 1.10.0 of prettier was just published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
prettier
|
|
Current Version
|
1.9.2
|
|
Type
|
devDependency
|
This version is covered by your current version range and after updating it in your project the build failed.
prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes
1.10: One Year of Prettier 🎂
🔗 Release Notes
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The dependency chokidar was updated from 2.0.4 to 2.1.0.
🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
chokidar is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
- ❌ continuous-integration/appveyor/branch: Waiting for AppVeyor build to complete (Details).
- ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Commits
The new version differs by 32 commits.
There are 32 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Version 12.4.0 of semantic-release was just published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
semantic-release
|
|
Current Version
|
12.3.0
|
|
Type
|
devDependency
|
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
- ✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
Commits
The new version differs by 1 commits.
fb0caa0 feat: hide sensitive info in stdout/sdtin
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
🚨 You need to enable Continuous Integration on all branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.
Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.
If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.
We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.
The devDependency sinon was updated from 7.2.3 to 7.2.4.
🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/appveyor/branch: Waiting for AppVeyor build to complete (Details).
- ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Commits
The new version differs by 13 commits.
06fc27d Update docs/changelog.md and set new release id in docs/_config.yml54da371 Add release documentation for v7.2.4e5de1fe 7.2.4d158672 Update CHANGELOG.md and AUTHORS for new release1431c78 minor package updates37c955d Merge pull request #1979 from fatso83/update-npm-depsfc2a32a Merge pull request #1975 from ehmicky/master85f2fcd Update eslint-plugin-mocha707e068 Fix high prio audit warnings8282bc0 Update nise to use @sinonjs/text-encodingc1d9625 Make all properties non-enumerable in spies, stubs, mocks and fakes894951c Merge pull request #1973 from mgred/default-sandbox-example876aebb docs(sandbox): add example for default sandbox
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Version 4.17.5 of lodash was just published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
lodash
|
|
Current Version
|
4.17.4
|
|
Type
|
dependency
|
This version is covered by your current version range and after updating it in your project the build failed.
lodash is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
- ✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The devDependency semantic-release was updated from 15.13.11 to 15.13.12.
🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
- ❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).
Release Notes for v15.13.12
Bug Fixes
- package: update resolve-from to version 5.0.0 (6f3c21a)
Commits
The new version differs by 1 commits.
6f3c21a fix(package): update resolve-from to version 5.0.0
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The devDependency proxyquire was updated from 2.1.0 to 2.1.1.
🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
proxyquire is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push: The Travis CI build is in progress (Details).
- ❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).
Commits
The new version differs by 6 commits.
5b88b07 2.1.13905975 Update dependencies (#243)3ca62af funding: adding github funding spec12606d1 README.md: Fix typo (#241)3da0603 Add file path reference to readme (#237)cb725be readme: fix simple-get example
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
conventional-changelog-metahub
|
|
Current Version
|
1.2.2
|
|
Type
|
devDependency
|
This version is covered by your current version range and after updating it in your project the build failed.
conventional-changelog-metahub is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes
v1.2.3
1.2.3 (2018-03-22)
🐛 Bug Fixes
- package: update conventional-changelog-angular to version 3.0.0 (6c8b619)
⚙️ Continuous Integrations
♻️ Chores
- package: update ava to version 0.25.0 (af73e67)
- package: update execa to version 0.10.0 (4d0bf66)
- package: update proxyquire to version 2.0.0 (b2e69fd)
- package: update semantic-release to version 15.0.0 (7100a28)
- package: update xo to version 0.20.0 (c2b45ef)
💎 Styles
Commits
The new version differs by 9 commits ahead by 9, behind by 1.
6c8b619 fix(package): update conventional-changelog-angular to version 3.0.04d0bf66 chore(package): update execa to version 0.10.07100a28 chore(package): update semantic-release to version 15.0.0b2e69fd chore(package): update proxyquire to version 2.0.059a02fc style: lintf7d2db1 ci(lint): simplify XO configc2b45ef chore(package): update xo to version 0.20.0af73e67 chore(package): update ava to version 0.25.01d8324f fix: do not use Babel
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Version 15.6.0 of semantic-release was just published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
[semantic-release](https://github.com/semantic-release/semantic-release)
|
|
Current Version
|
15.5.5
|
|
Type
|
devDependency
|
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
- ✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
Release Notes
v15.6.0
15.6.0 (2018-06-19)
Features
- allow to disable the publish plugin hook (4454d57)
Commits
The new version differs by 1 commits.
4454d57 feat: allow to disable the publish plugin hook
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
|
Branch
|
Build failing 🚨
|
|
Dependency
|
eslint-plugin-prettier
|
|
Current Version
|
2.4.0
|
|
Type
|
devDependency
|
This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
- ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
Commits
The new version differs by 3 commits.
eba622e Build: update package.json and changelog for v2.5.00b6ab55 Fix: pass filepath to prettier (#76)804ead7 Update: Add URL to rule documentation to the metadata (#75)
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Version 5.0.9 of sinon was just published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
sinon
|
|
Current Version
|
5.0.8
|
|
Type
|
devDependency
|
This version is covered by your current version range and after updating it in your project the build failed.
sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
- ✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
Commits
The new version differs by 5 commits.
86b930c Update docs/changelog.md and set new release id in docs/_config.yml033aa60 Add release documentation for v5.0.93321085 5.0.99f321d5 Update History.md and AUTHORS for new releasee862196 Upgrade @std/esm to esm.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Version 4.4.5 of sinon was just published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
sinon
|
|
Current Version
|
4.4.4
|
|
Type
|
devDependency
|
This version is covered by your current version range and after updating it in your project the build failed.
sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 5 commits.
2fa34f6 Update docs/changelog.md and set new release id in docs/_config.ymld048ad1 Add release documentation for v4.4.541f0b83 4.4.5d088fae Update History.md and AUTHORS for new release4751ee9 Add postinstall banner pointing to Open Collective
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Recommend Projects
-
-
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
An Open Source Machine Learning Framework for Everyone
-
The Web framework for perfectionists with deadlines.
-
A PHP framework for web artisans
-
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
Some thing interesting about web. New door for the world.
-
A server is a program made to process requests and deliver data to clients.
-
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Some thing interesting about visualization, use data art
-
Some thing interesting about game, make everyone happy.
-
Recommend Org
-
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Open source projects and samples from Microsoft.
-
Google ❤️ Open Source for everyone.
-
Alibaba Open Source for everyone
-
Data-Driven Documents codes.
-
China tencent open source team.
-
![greenkeeper[bot] avatar](https://avatars.githubusercontent.com/in/505?v=4 "greenkeeper[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent