Edits to the paragraph about Prettier

[DNin01]

Changes

I removed the mention of Prettier for VS Code as I think it always uses the latest version and you also need to change the settings for it to work with our code style, and I don't really want to take up space to explain how to configure it. The parser it uses also cannot format CSS, even though Prettier has an official CSS parser.

I was thinking of also linking to the online Prettier playground as an easy-to-use alternative, but that also appears to only be able to use the latest version. That would be fine except that, like many developers, we hardcode a version, after we learned how automatic updates go the hard way.

I haven't tried Prettier on RunKit yet, but that might be one other option for those who aren't ready to install Node.js just to format code. If anyone knows of any other easy ways to get code formatted with Prettier's algorithms before committing changes that 1. can be configured and 2. can use a specific version, let me know.

Despite all of these removed references, I did add a link to the prettier package on npm, and continue to recommend enabling the Actions feature.

[Hans5958]

Again and again, these issues can be solved if we have package.json. Almost feels like we should have done this.

[DNin01]

Again and again, these issues can be solved if we have package.json. Almost feels like we should have done this.

It would also be a great opportunity to add other developer tools like chrome-types and ESLint, wherever that is.

[Samq64]

The changes look good assuming we're not adding a package.json.