Release Notes
1.9.0: JSX Fragments, EditorConfig and Arrow Parens
This release adds an option for arrow function parens in arguments, support for the new JSX fragment syntax (<>), support for .editorconfig files, and nice additions to our GraphQL and Markdown support.
Highlights
JavaScript
Option to add parens in arrow function arguments (#3324) by @rattrayalex and @suchipi
When printing arrow functions, Prettier omitted parens around the arguments if they weren’t strictly necessary, like so:
// no parens
foo => {};
// parens
(foo: Number) => {};
// parens
({ foo }) => {}
// parens
(foo = 5) => {}
This lead to the most commented thread in our issue tracker. Prettier now has the --arrow-parens option (arrowParens in the config) that can assume two values today:
"avoid" - (default) preserve the behavior that omits parens when possible"always" - always includes parens
Prettier will now recognize and format JSX with the new fragment syntax, like the code below:
function MyComponent() {
return (
<>
<Children1 />
<Children2 />
<Children3 />
</>
);
}Fix slow formatting long texts in JSX (#3268, #3273) by @duailibe
We received feedback that formatting a JSX file with a really long text (~1000 lines) was really slow and noticed there was two performance bottlenecks in our fill primitive, which prints text until it reaches the print width and then insert a line break.
Markdown
Add an option to preserve text line breaks (#3340) by @ikatyang
After the release of our Markdown support, we received feedback that breaking text to respect the print width could affect some renderers that could be sensitive to line breaks. In 1.8.2 we released a new option proseWrap: false that would print a paragraph in a single line, and users would rely on the "soft wrapping" feature of editors.
In 1.9 we are releasing a new option proseWrap: "preserve" which will respect the original line breaks of text, and lets the users decide where the text should break.
[WARNING] proseWrap with boolean value is deprecated, use "always", "never" or "preserve" instead.
[BREAKING CHANGE] proseWrap option now defaults to "preserve" as some renderers are linebreak-sensitive.
GraphQL
Support top-level interpolations (#3370) by @lydell
When GraphQL support was released, Prettier did not support interpolation so it would skip formatting if any interpolations were present, because interpolations make formatting very difficult. While that works well for the most part, users of the Apollo Client were missing out on Prettier’s GraphQL support sometimes, because Apollo Client uses interpolation to share fragments between queries. The good news is that only top-level interpolations are allowed, and that was way easier to add support for in Prettier.
In 1.9 we format GraphQL queries with top-level interpolation:
gql`
query User {
user(id: "Bob") {
...UserDetails
}
}
${UserDetailsFragment}
`(Prettier will continue to skip formatting if the interpolation is inside a query or mutation or so.)
Preserve intentional new lines in GraphQL (#3252) by @duailibe
Prettier will now respect intentional line breaks inside GraphQL queries (but limit to 1), where before it would remove them.
CSS
Don't lowercase element names and attribute names in selectors (#3317) by @lydell
CSS is mostly case insensitive, so Prettier has been lowercasing stuff for a while to keep things consistent. Turns out we overlooked a detail in the CSS spec. Element and attribute names in selectors depend on the markup language: In HTML they are case insensitive, but in SVG (XML) they are not. Previously Prettier would incorrectly lowercase element and attribute names, but now we don’t anymore.
Configuration
It's taken a while, but Prettier will finally respect your .editorconfig file. This includes:
indent_styleindent_size/tab_widthmax_line_length
The prettier CLI respects .editorconfig by default, but you can opt out with --no-editorconfig.
However, the API doesn't respect .editorconfig by default, in order to avoid potential editor integration issues (see here for details). To opt in, add editorconfig: true to the prettier.resolveConfig options.
Other changes
JavaScript
Don't break simple elements in JSX (#3250) by @duailibe
Prettier won't break an element with no attributes anymore, keeping elements like <br /> as an unit.
Don't break identifiers inside template literals expressions (#3299) by @duailibe
In the previous release we tried a new strategy of breaking template literals with expressions inside to respect the print width. We've received feedback that for some cases it was actually preferred that it would exceed print width than breaking in multiple lines.
From now on, template literals expressions that contain a single identifier won't break anymore:
const foo = `Hello ${username}. Today is ${month} ${day}. You have ${newMessages} new messages`.Fix formatting of comment inside arrow function (#3334) by @jackyho112
Fixes an edge case where Prettier was moving comments around breaking tools like Webpack:
const API = {
loader: () => import('./test' /* webpackChunkName: "test" */),
};
// would get formatted to
const API = {
loader: (/ webpackChunkName: "test" /) => import("./test")
};
Fix printing of comments around decorators and class properties (#3382) by @azz
There was a case where comments between a decorator and a class property were moved to an invalid position.
// Before
class Something {
@decorator
static // comment
property = 1;
}
// After
class Something {
@decorator
// comment
static property = 1;
}
Flow
Do not break on empty type parameters (#3281) by @vjeux
It won't break empty type parameters (foo: Type<>) anymore.
Add support for flow mixins when using babylon (#3391) by @bakkot
We were accidentally dropping flow mixins, this has been fixed, but only for the babylon parser.
// Before
class Foo extends Bar {}
// After
class Foo extends Bar mixins Baz {}
TypeScript
Don't print a trailing comma after object rest spread (#3313) by @duailibe
This was inconsistent with JavaScript and Flow, Prettier won't print a trailing comma in the following cases, when using the TypeScript parser:
const {
bar,
baz,
...rest
} = foo;Print parens around type assertions for decorators (#3329) by @azz
We were omitting parens around type assertions inside decorators:
@(bind as ClassDecorator)
class Decorated {}Markdown
Don't break inlineCode (#3230) by @ikatyang
Prettier won't break text inside inlineCode meaning it will only break of after it.
No extra whitespace between non-CJK and CJK-punctuation and vice-versa (#3244, #3249) by @ikatyang
Fixes cases where Prettier would insert extra whitespace like in the following examples:
扩展运算符（spread ）是三个点（`...`）。
This is an english paragraph with a CJK quote " 中文 ".
Escape all emphasis-like text (#3246) by @ikatyang
Fixes the case where \_\_text\_\_ would be formatted as __text__.
Handle punctuation variants (#3254) by @ikatyang
Prettier now considers not only ASCII punctuation characters but Unicode as well.
Support TOML front matter (#3290) by @ikatyang
We already supported YAML in the front matter of Markdown files and we added the TOML format as well, since some static site generators support it.
+++
date: '2017-10-10T22:49:47.369Z'
title: 'My Post Title'
categories: ['foo', 'bar']
+++
This is the markdown body of my post.
Only indent the first non-list node in checkbox list item (#3297) by @ikatyang
Fixes a bug where it would indent lines after a list when it shouldn't:
* parent list item
<span class="pl-v">*</span> child list item
* [x] parent task list item
<span class="pl-v">*</span> [x] child task list item</pre></div>
would become:
* parent list item
* child list item
* [x] parent task list item
<span class="pl-v">*</span> [x] child task list item</pre></div>
Preserve non-breaking whitespaces (#3327) by @ikatyang
Non-breaking whitespaces are useful to keep words separated by spaces together in the same line (i.e. number and units or multi-word product names). Prettier was wrongfully converting them to regular whitespaces.
Do not break before special prefix (#3347) by @ikatyang
Fixes a bug where Prettier could break text if it went over the print width right before a number followed by . which would be parsed as a numbered list:
She grew up in an isolated village in the 19th century and met her father aged
29. Oh no, why are we in a numbered list now?
Omit semicolon in simple JSX expressions (#3330) by @sapegin
Prettier will omit the semicolon (before and after) inside code samples if it's a simple JSX expression:
No semi:
jsx</span><span class="pl-s1"></span> <span class="pl-s1"><div>Example</div></span> <span class="pl-s1"></span><span class="pl-c1">
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 🌴
Tasks to complete:
We currently have the sku eslint config here which enables us to expose the settings to an IDE (such as Atom).
Version 4.0.1 of inquirer was just published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
inquirer
|
|
Current Version
|
4.0.0
|
|
Type
|
dependency
|
This version is covered by your current version range and after updating it in your project the build failed.
inquirer 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 could not complete due to an error Details
Release Notes
v4.0.1
- Update dependency to fix a LGPL license issue.
Commits
The new version differs by 3 commits.
00f5050 4.0.19895054 Bumped version to 4.1.0, bumped external-editor dependency to ^2.1.0 … (#616)62a72d4 Fix typo (#612)
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 🌴
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
Repository problems
These problems occurred while renovating this repository. View logs.
- WARN: Using npm packages for Renovate presets is now deprecated. Please migrate to repository-based presets instead.
Open
These updates have all been created already. Click a checkbox below to force a retry/rebase of any.
Detected dependencies
github-actions
.github/workflows/release.yml
.github/workflows/snapshot.yml
seek-oss/changesets-snapshot v0
.github/workflows/validate.yml
npm
docs/package.json
fixtures/assertion-removal/package.json
fixtures/braid-design-system/package.json
braid-design-system ^32.0.0
fixtures/configure/package.json
fixtures/custom-src-paths/package.json
fixtures/jest-test/package.json
fixtures/library-build/package.json
fixtures/library-file/package.json
fixtures/lint-format/package.json
fixtures/multiple-routes/package.json
fixtures/public-path/package.json
fixtures/react-css-modules/package.json
fixtures/sku-test/package.json
fixtures/sku-webpack-plugin/package.json
braid-design-system ^32.0.0
fixtures/sku-with-https/package.json
fixtures/source-maps/package.json
fixtures/ssr-hello-world/package.json
fixtures/storybook-config/package.json
braid-design-system ^32.0.0
fixtures/styling/package.json
fixtures/translations/package.json
fixtures/typescript-css-modules/package.json
package.json
eslint-config-seek ^12.0.1renovate-config-seek ^0.4.0typescript *
packages/sku/package.json
browserslist-config-seek ^2.1.0eslint-config-seek ^12.0.1typescript ~5.3.0braid-design-system ^32.0.0
test-utils/package.json
nvm
.nvmrc
Version 16.2.0 of react-dom was just published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
react-dom
|
|
Current Version
|
16.1.1
|
|
Type
|
devDependency
|
This version is covered by your current version range and after updating it in your project the build failed.
react-dom 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
Release Notes
v16.2.0
React
- Add
Fragment as named export to React. (@clemmy in #10783)
- Support experimental Call/Return types in
React.Children utilities. (@MatteoVH in #11422)
React DOM
- Fix radio buttons not getting checked when using multiple lists of radios. (@landvibe in #11227)
- Fix radio buttons not receiving the
onChange event in some cases. (@jquense in #11028)
React Test Renderer
- Fix
setState() callback firing too early when called from componentWillMount. (@accordeiro in #11507)
React Reconciler
- Expose
react-reconciler/reflection with utilities useful to custom renderers. (@rivenhk in #11683)
Internal Changes
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 🌴
Summary
Static files (eg main.js, styles.css) generated into the specified dist folder should be served by the supplied express server without further configuration. This is a setting for development, not production builds.
Motivation
Without this, unless the appropriate express.static call is passed into middleware, requests for static files will fall into the render function fallback. In a typical case this would cause the app to return a rendered 404 html page instead of the js or css requested.
Detailed design
In config/server/server.js, after the express app is instantiated but before the render function fallback, we should include a line much like the following:
app.use(express.static(path.join(__dirname, './')));
How We Teach This
This should cause local server rendering to work as expected, and should not require teaching.
Drawbacks
This is not limited to sku-generated static files, if the server finds any others in its root it'll happily serve them too. That's still probably behaving as expected.
Alternatives
You can just pass this in manually as middleware, that just seems like an odd thing to require.
Unresolved questions
Is it worth creating a static folder for this purpose?
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]")
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "renovate[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent