Release v3

[sosukesuzuki]

next branch

• Support ESM plugins (Support ESM plugins #13201)
• Support ESM config files (Support config file in ESM #13130)
• Change trailingComma option default value to all (Change default value of trailingComma to "all" #11479)
• Don't insert spaces in Markdown ( Markdown[next branch]: Do not insert spaces between Chinese/Japanese & latin letters #11597 )
• Remove prettier.doc.builders.concat (Remove prettier.doc.builders.concat #13203)
• Update print function signature to not accept path (need investigate)(Removed since this will break path.map(print))
• Print HTML5 doctype in lowercase? (need discussion Print HTML5 doctype in lowercase #7391)
• Change --loglevel flag to --log-level (Change --loglevel to --log-level #13204)
• Support MDX 2? (MDX 3 #12209) Postponed
• exports field (Restructure package files, add exports #13530)
• Plugins & tools support for v3 (Plugins & tools support for v3 #13616)

---

• prepare
  • Complete milestone items
  • Run on other projects to check for regressions ( v3 prettier-regression-testing#348 )
  • Write release notes (V3 blog post #13436)
    • use node scripts/draft-blog-post.mjs to generate a blog post draft (a file named YYYY-MM-DD-version.md in website/blog) from changelog_unreleased
    • prs-merged-since (readme) may be useful
• publish
  • Run release script
• postpublish
  • Merge release notes
  • Wait for release notes to deploy
  • Clean changelog_unreleased
    • use node scripts/clean-changelog-unreleased.mjs
  • Tweet from @PrettierCode account via TweetDeck
  • Close milestone
  • Send schema PR generated by node scripts/generate-schema.mjs to SchemaStore if we added a new option.
  • Update the release checklist with possible changes]
  • Deprecate @types/prettier since v3.0.0 DefinitelyTyped/DefinitelyTyped#66073

Then monitor Twitter/GitHub for any immediate issues 😄

[kachkaev]

Switching to MDX2 is also breaking and is due. We should probably include #12209 too.

[fisker]

We can include it if someone can work on it. (I don't use MDX, not interested)

[sosukesuzuki]

Switching to MDX2 is also breaking and is due. We should probably include #12209 too.

I had worked on it before and will try again but it was very difficult...

[chrisbobbe]

Please consider PR #7111 ("JS: Break lines before binary operators (fixes #3806)").

#3806 (comment) is a nice status summary for this long-standing issue.

[ExE-Boss]

The following should probably also be included:

• Change useTabs to true by default #7475

[JounQin]

Can we rename --vue-indent-script-and-style to --indent-script-and-style for all SFC files like svelte?

prettier-plugin-svelte has to have a new --svelte-indent-script-and-style option, but they could be unified, actually.

[fisker]

I don't think we are going to make more breaking changes to the plugin system, (except #10156).

I think we are ready to release an alpha version for plugins to adopt.

[xsrvmy]

Other problems: some phrases like U盘 is sometimes typed without space (although fullwidth can be used here), and sometimes dates are typeset without spaces.
And of course prettier should not format in a way that affects output.

[JounQin]

Other problems: some phrases like U盘 is sometimes typed without space (although fullwidth can be used here), and sometimes dates are typeset without spaces. And of course prettier should not format in a way that affects output.

See #11597

[thorn0]

Why not drop Node 14?

[sosukesuzuki]

Node.js 14 is maintenance LTS until April 30, 2023, so we need to support it https://github.com/nodejs/Release#release-schedule

[thorn0]

What if we drop it only for direct-from-github installs?

[fisker]

Sure we can.

[sosukesuzuki]

We can.

[thorn0]

How about completely removing support for Flow comment types? They're a mess and can't be properly supported anyway. See facebook/flow#8355

Related issues: https://github.com/prettier/prettier/issues?q=is%3Aopen+is%3Aissue+label%3A%22area%3Aflow+comment+types%22

An alternative solution that probably isn't really needed: #9564 (comment)

[sosukesuzuki]

How about completely removing support for Flow comment types? They're a mess and can't be properly supported anyway. See facebook/flow#8355

I agree with you.

[HolgerJeromin]

#13016 would be IMO very important to be able to use the cache from release 2.7 (at all).

[martinszeltins]

What about rewriting Prettier in TypeScript for version 3.0? Why is Prettier not written in TypeScript in the first place?

[kachkaev]

@martinszeltins v3 makes a step in this direction by shipping with typings (#14212), thus replacing @types/prettier. Generating those types from source would be even better but that’s currently out of scope. Feel free to help when v3 is released!

[kachkaev]

The latest v3 alpha to date is 3.0.0-alpha.6, which was released on Feb 3 (more than three months ago). I don’t remember if there are any risky changes merged into main after that, but if anyone thinks we should release another alpha, happy to test it a bit this weekend!

[Mister-Hope]

Node.js 14 is maintenance LTS until April 30, 2023, so we need to support it https://github.com/nodejs/Release#release-schedule

So can we relook into dropping Node14 support? I don't think prettier will touch stable before this date?

[fisker]

We discussed Node.js support recently https://github.com/prettier/prettier/wiki/The-policy-to-drop-Node.js-version

I don't understand why anyone except maintainers want support less versions ... Just curious.

[Mister-Hope]

don't understand why anyone except maintainers want support less versions ... Just curious.

As long as there is any performance improvement by dropping node14 (even <1%) then I am positive towards this.

[kachkaev]

It takes time for the community to migrate away from old Node versions, even after their end of life. I’m up for dropping Node 14 in Prettier v4 (not 3), but now, even if release in early May, it would be a bit too early.

[re-thc]

I don't understand why anyone except maintainers want support less versions ... Just curious.

To move the world forward. Otherwise we'd always still be supporting IE too.

[fisker]

Just want to brief here, we are blocked by VSCode support. prettier/prettier-vscode#2947

[ntkoopman]

There is still no conclusion to #3806. I feel this long standing issue should be addressed before v3, even if it's closing it as "won't fix" so we can move on.

[sosukesuzuki]

we'll collect feedback from users via experimental flags after v3 is released. So there is no need to draw any conclusions about it yet.

[AlexAegis]

I know this is last minute but can this be considered for v3? #4081 People working in monorepos are doing some ugly workarounds now, tools like turbo runs prettier from the directory of the package so you have to put a copy or symlink of your .prettierignore file into every package.

[Janther]

Why is the latest release 3.0.0-alpha.6 on Github while on npm is 3.0.0-alpha.12?
There used to be a next branch as well.

[latin-1]

It appears that v3 no longer autoloads plugins. Shouldn't this be mentioned in the release notes?
nevermind

[sosukesuzuki]

released

[karlhorky]

Thanks to everyone involved in Prettier v3!! 🙌 🎉 🚀