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 🌴
Version 12.2.4 of semantic-release was just published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
semantic-release
|
|
Current Version
|
12.2.3
|
|
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/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 1 commits.
fa2ca8a fix(package): update lodash to version 4.17.4
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 🌴
There have been updates to the babel7 monorepo:
-
- The
devDependency @babel/cli was updated from 7.1.0 to 7.1.1.
🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.
babel7 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).
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 0.55.4 of rollup was just published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
rollup
|
|
Current Version
|
0.55.3
|
|
Type
|
devDependency
|
This version is covered by your current version range and after updating it in your project the build failed.
rollup 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 22 commits.
fa9ec55 0.55.488e0cf4 Merge pull request #1924 from kellyselden/test-dirs9f4956d Merge pull request #1939 from KingHenne/optional-preserve-symlinks0bfe488 Merge pull request #1944 from rollup/external-namespace-deshadowingb4c1002 Merge branch 'master' into external-namespace-deshadowingace48f2 Merge pull request #1947 from rollup/external-reexport-refinements7c88295 Merge branch 'release-0.55.4'cf89454 Update changelog38678de declare preserveSymlinks option as optional03225dd feedback and #1951 case fix7169dab refine reexport test cases0e84d4b external deshadowing fix for #1930fd6c187 Added call to donate after npm install (optional)a08e7ef enabled testing directory structures in chunked mode63a2984 feedback and #1951 case fix
There are 22 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/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 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 🌴
The dependency lodash was updated from 4.17.11 to 4.17.12.
🚨 View failing branch.
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/appveyor/branch: AppVeyor build failed (Details).
- ❌ continuous-integration/travis-ci/push: The Travis CI build failed (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 karma was updated from 3.1.1 to 3.1.2.
🚨 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 failed (Details).
Release Notes for v3.1.2
Bug Fixes
Features
Commits
The new version differs by 11 commits.
7d4d347 chore: release v3.1.25077c18 chore: update contributorsfb05fb1 fix(server): use flatted for json.stringify (#3220)2682bff feat(docs): callout the key debug strategies. (#3219)4e87902 fix(changelog): remove release which does not exist (#3214)30ff73b fix(browser): report errors to console during singleRun=false (#3209)5334d1a fix(file-list): do not preprocess up-to-date files (#3196)dc5f5de fix(deps): upgrade sinon-chai 2.x -> 3.x (#3207)d38f344 fix(package): bump lodash version (#3203)ffb41f9 refactor(browser): log state transitions in debug (#3202)240209f fix(dep): Bump useragent to fix HeadlessChrome version (#3201)
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 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 0.63.3 of rollup was just published.
This version is covered by your current version range and after updating it in your project the build failed.
rollup 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
Commits
The new version differs by 3 commits.
d6c3ea8 0.63.368fdddf Update changelog4465018 Do not fail for binary expressions involving "in" and "instanceof" (#2344)
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 0.64.1 of rollup was just published.
This version is covered by your current version range and after updating it in your project the build failed.
rollup 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).
Commits
The new version differs by 3 commits.
fac4b71 0.64.1f9a967a Update changelog500d72e Do not render initializers of hoisted variables in dead branches (#2384)
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.0.3 of rollup-plugin-babel was just published.
This version is covered by your current version range and after updating it in your project the build failed.
rollup-plugin-babel 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 4 commits.
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 3.0.6 of rollup-plugin-babel was just published.
This version is covered by your current version range and after updating it in your project the build failed.
rollup-plugin-babel 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
Commits
The new version differs by 2 commits.
14226a7 3.0.6f8182c6 Transform built helpers in case people use i.e. some es3 transforms (#227)
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 rollup-plugin-babel was updated from 4.3.2 to 4.3.3.
🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
rollup-plugin-babel 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 5 commits.
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 2.9.1 of jasmine-core was just published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
jasmine-core
|
|
Current Version
|
2.9.0
|
|
Type
|
devDependency
|
This version is covered by your current version range and after updating it in your project the build failed.
jasmine-core 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
2.9.1
Please see the release notes
Commits
The new version differs by 2 commits.
70bce55 Bump version to 2.9.153529bd Clear timeouts when starting to process a milli instead of at the end
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 🌴
There have been updates to the babel7 monorepo:
-
- The
devDependency @babel/cli was updated from 7.2.0 to 7.2.3.
🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.
babel7 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).
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 rollup was updated from 1.1.2 to 1.2.0.
🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
rollup 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 17 commits.
60e8df2 1.2.056ff3e3 Update changelog19a7727 Reimplement variable deconflicting logic (#2689)fe84e00 Update changelogdb42a04 Prevent final resolution and facade creation for inlined dynamic imports (#2677)4d082b0 Respect rendered exports when generating chunk hashes (#2695)14a17af Correctly render function expression inside simplified expression statements. (#2696)0a46310 Add a fix for MaxListenersExceededWarning (#2700)1454b90 Update rollup-pluginutils (#2703)d883243 Update changelogf8faa4b Allow config files to contain non-default exports (#2673)d6a865e Update changelog1ae20fc Improve type of RollupOutput.output (#2679)7f79ab1 Update changelogc702f3a Fix typo in export-globals test (#2693)
There are 17 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 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/appveyor/branch: Waiting for AppVeyor build to complete (Details).
- ❌ continuous-integration/travis-ci/push: The Travis CI 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 🌴
Version 2.1.0 of p-event was just published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
[p-event](https://github.com/sindresorhus/p-event)
|
|
Current Version
|
2.0.0
|
|
Type
|
devDependency
|
This version is covered by your current version range and after updating it in your project the build failed.
p-event 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 2 commits.
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.7 of sinon was just published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
sinon
|
|
Current Version
|
4.4.6
|
|
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 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 🌴
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 🌴
The devDependency jasmine-core was updated from 3.3.0 to 3.4.0.
🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
jasmine-core 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 40 commits.
8fca3b4 Fix links in 3.4 release notese636f5f Bump version to 3.474fd0e0 No fit in the suite618e24b Handle WebSocket events in IE when detecting Errors5c7e25e Allow excluded specs in CI without breaking the output54af109 Merge branch 'wood1986-fix/npm-audit-dependencies-and-fast-glob-only-failed-tests'873a237 Consolidate some dev dependencies and use more maintained versions8ca4463 Make node execution default and override for browsers449eb51 Fix sauce status codes and try travis built-in node supporta5df5a6 Use the correct env var from travis for tunnelsbe58323 bump dependencies for security fixesd389d3c Merge branch 'wood1986-features/no-ruby'994d11d update node CI script to work with SauceLabs828d14f Use node.js for browser-based CIf5663a9 Merge branch 'johnjbarton-duration'
There are 40 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 🌴
🚨 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 it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.
Once you have installed and configured CI on this repository correctly, 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 App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.
Version 0.54.1 of rollup was just published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
rollup
|
|
Current Version
|
0.54.0
|
|
Type
|
devDependency
|
This version is covered by your current version range and after updating it in your project the build failed.
rollup 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 4 commits.
4bd7a0a 0.54.177e3b44 Update changelog74de841 Merge pull request #1871 from KingHenne/more-ts-fixesb413df4 Fix two more ts compiler errors based on emitted d.ts files
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.6.0 of eslint just got published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
eslint
|
|
Current Version
|
4.5.0
|
|
Type
|
devDependency
|
This version is covered by your current version range and after updating it in your project the build failed.
As eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
- ❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
- ❌ continuous-integration/appveyor/branch AppVeyor build failed Details
Release Notes
v4.6.0
- 56dd769 Docs: fix link format in prefer-arrow-callback.md (#9198) (Vse Mozhet Byt)
- 6becf91 Update: add eslint version to error output. (fixes #9037) (#9071) (薛定谔的猫)
- 0e09973 New: function-paren-newline rule (fixes #6074) (#8102) (Teddy Katz)
- 88a64cc Chore: Make parseJsonConfig() a pure function in Linter (#9186) (Teddy Katz)
- 1bbac51 Fix: avoid breaking eslint-plugin-eslint-comments (fixes #9193) (#9196) (Teddy Katz)
- 3e8b70a Fix: off-by-one error in eslint-disable comment checking (#9195) (Teddy Katz)
- 73815f6 Docs: rewrite prefer-arrow-callback documentation (fixes #8950) (#9077) (Charles E. Morgan)
- 0d3a854 Chore: avoid mutating report descriptors in report-translator (#9189) (Teddy Katz)
- 2db356b Update: no-unused-vars Improve message to include the allowed patterns (#9176) (Eli White)
- 8fbaf0a Update: Add configurability to generator-star-spacing (#8985) (Ethan Rutherford)
- 8ed779c Chore: remove currentScopes property from Linter instances (refs #9161) (#9187) (Teddy Katz)
- af4ad60 Fix: Handle error when running init without npm (#9169) (Gabriel Aumala)
- 4b94c6c Chore: make parse() a pure function in Linter (refs #9161) (#9183) (Teddy Katz)
- 1be5634 Chore: don't make Linter a subclass of EventEmitter (refs #9161) (#9177) (Teddy Katz)
- e95af9b Chore: don't include internal test helpers in npm package (#9160) (Teddy Katz)
- 6fb32e1 Chore: avoid using private Linter APIs in astUtils tests (refs #9161) (#9173) (Teddy Katz)
- de6dccd Docs: add documentation for Linter methods (refs #6525) (#9151) (Teddy Katz)
- 2d90030 Chore: remove unused assignment. (#9182) (薛定谔的猫)
- d672aef Chore: refactor reporting logic (refs #9161) (#9168) (Teddy Katz)
- 5ab0434 Fix: indent crash on sparse arrays with "off" option (fixes #9157) (#9166) (Teddy Katz)
- c147b97 Chore: Make SourceCodeFixer accept text instead of a SourceCode instance (#9178) (Teddy Katz)
- f127423 Chore: avoid using private Linter APIs in Linter tests (refs #9161) (#9175) (Teddy Katz)
- 2334335 Chore: avoid using private Linter APIs in SourceCode tests (refs #9161) (#9174) (Teddy Katz)
- 2dc243a Chore: avoid using internal Linter APIs in RuleTester (refs #9161) (#9172) (Teddy Katz)
- d6e436f Fix: no-extra-parens reported some parenthesized IIFEs (fixes #9140) (#9158) (Teddy Katz)
- e6b115c Build: Add an edit link to the rule docs’ metadata (#9049) (Jed Fox)
- fcb7bb4 Chore: avoid unnecessarily complex forEach calls in no-extra-parens (#9159) (Teddy Katz)
- ffa021e Docs: quotes rule - when does \n require backticks (#9135) (avimar)
- 60c5148 Chore: improve coverage in lib/*.js (#9130) (Teddy Katz)
Commits
The new version differs by 31 commits.
8f01a99 4.6.0c0acbf2 Build: changelog update for 4.6.056dd769 Docs: fix link format in prefer-arrow-callback.md (#9198)6becf91 Update: add eslint version to error output. (fixes #9037) (#9071)0e09973 New: function-paren-newline rule (fixes #6074) (#8102)88a64cc Chore: Make parseJsonConfig() a pure function in Linter (#9186)1bbac51 Fix: avoid breaking eslint-plugin-eslint-comments (fixes #9193) (#9196)3e8b70a Fix: off-by-one error in eslint-disable comment checking (#9195)73815f6 Docs: rewrite prefer-arrow-callback documentation (fixes #8950) (#9077)0d3a854 Chore: avoid mutating report descriptors in report-translator (#9189)2db356b Update: no-unused-vars Improve message to include the allowed patterns (#9176)8fbaf0a Update: Add configurability to generator-star-spacing (#8985)8ed779c Chore: remove currentScopes property from Linter instances (refs #9161) (#9187)af4ad60 Fix: Handle error when running init without npm (#9169)4b94c6c Chore: make parse() a pure function in Linter (refs #9161) (#9183)
There are 31 commits in total.
See the full diff
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 🌴
Version 11.2.1 of nyc just got published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
nyc
|
|
Current Version
|
11.2.0
|
|
Type
|
devDependency
|
This version is covered by your current version range and after updating it in your project the build failed.
As nyc is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
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.
87281f9 chore(release): 11.2.13bd1527 fix: create temp directory when --no-clean flag is set #663 (#664)a10d478 fix: apply exclude logic before remapping coverage (#667)
See the full diff
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 🌴
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 15.9.12 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.12
Bug Fixes
- hide sensitive data in relesae notes and
fail/success plugin params (dffe148)
Commits
The new version differs by 1 commits.
dffe148 fix: hide sensitive data in relesae notes and fail/success plugin params
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 15.1.3 of semantic-release was just published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
semantic-release
|
|
Current Version
|
15.1.2
|
|
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/appveyor/branch Waiting for AppVeyor build to complete Details
- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes
v15.1.3
15.1.3 (2018-03-20)
Bug Fixes
- prevent git prompt before permissions verification (30ee231)
- remove
execa timeout (3c46455)
Commits
The new version differs by 3 commits.
30ee231 fix: prevent git prompt before permissions verification3c46455 fix: remove execa timeoutdff0a34 docs: add "Introduction to Semantic Release" article
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