Blog post, changelog and docs for 1.19

[lydell]

No description provided.

[fisker]

I was thinking about this the other day, maybe we can do this

use dir name changelog

for released changes we can move CHANGELOG.md into it, also we can store changelogs in several pieces files when its became big in future.

for PRs, add subdir pr or pull-request or categorized subdir like @lydell did in this PR , peple can put there changelog in 1234.md or 1234-1235-1236.md , we don't need clean them when we release a new version, we will got the full history.

for unreleased changes , we still use a seperate file unreleased.md only index the file name(link to pr/1234.md) of there PR, (not sure will this cause conflicts, if so we can use subdir
unreleased and move them into pr when release).

TEMPLATE.md should name 0000.md or _TEMPLATE.md so it can be on the top when people open folder

[fisker]

/cc @lydell @lipis @sosukesuzuki ping

[lydell]

@fisker I’m not sure if I get your idea completely, but it sounds a little complicated to me. With my proposal, one can do cat changelog_unreleased/typescript/*.md | pbcopy and paste that under ### TypeScript in the blog post you’re writing. Repeat for every category. Move the highlights to the top. Clean some things up. It’s still a little bit manual, but a lot easier than the current situation. And it shouldn’t cause any merge conflicts. I think we need a little bit of human touch to the changelogs for the to be good.

[lydell]

@thorn0 cspell is failing on “error recovery parsing”:

/home/lydell/forks/prettier/website/blog/2019-11-03-1.19.0.md:196:278 - Unknown word (reco)
CSpell: Files checked: 185, Issues found: 1 in 1 files

Do you know how to fix it?

[thorn0]

@lydell I fixed it in #6816, see https://github.com/prettier/prettier/pull/6816/files#diff-2a298fb798903102dbeeeae48b89b6d6R396

[henrikra]

Everything looks good! I guess this is only one blocking 1.19 release?

[lydell]

So, the plan was to do the release yesterday, but since I failed to get access to the npm package that didn’t happen. Unfortunately I won’t have time to do it today, and not tomorrow either. But I could do it on Friday.

If someone else wants to do the release today or tomorrow, that would be great.

[alexander-akait]

@lydell 😞

@prettier/core Has anyone already made releases, maybe we can help @lydell ?

[ekilah]

I don't suppose anyone knows of a nice way to get this update in the mean time (dying to integrate TS 3.7)?

I ran yarn add https://github.com/prettier/prettier#{master's last commit hash} to try, but there were waaaay more dependencies added to my project than previous versions have had, so I assumed there was something wrong with that approach for prettier.

[henrikra]

Friday is THE day 🥰

[radiosilence]

@ekilah yarn add prettier@prettier/prettier should, or at least adding that in package.json for the version

[j-f1]

I ran yarn add https://github.com/prettier/prettier#{master's last commit hash} to try, but there were waaaay more dependencies added to my project than previous versions have had, so I assumed there was something wrong with that approach for prettier.

That’s the correct way to do it and also expected. When publishing, we bundle all our dependencies into the generated files so they work in Node and the browser. When you install from GitHub like that, you end up having to pull in all the dependencies separately.