style: Enable ESLint and Prettier for all files

[nschonni]

This is a little big, so I can try and break it down a bit, if the end result is desired:

• Remove ESLint rules that overlap with Prettier/EditorConfig
• Remove Prettier rules overlapping with EditorConfig
• Replace Prettier-eslint with plugin/config versions
• Set Environment to ES2022 and remove globals that are not required
• Remove babel parser, since covered by ES2022
• Ignore WASM folders because of top level awaits
• Rename script commands to match mdn/content

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[NiedziolkaMichal]

I can see few problems with this commit:

• Unfortunately it's going to change height of multiple examples. For example Array.reduceRight will be converted from smaller to medium. Basic solution is to make separate PR in content repository, in which we revisit specified heights of all interactive examples modified in this PR. Alternative solution is to wait for #839 & #7679 to be deployed, which will make it no longer necessary to update content repo.

• Comments in examples of bitwise operators are no longer aligned. For example take a look at &=. Currently it's very easy to see how individual bits are affected, which makes those operators easier to be understood.

• Forced line breaks in arrays will make some examples huge. For example take a look at extends or NumberFormat.

• I feel code style would be better without line wrapping like in examples TypedArray.at or Symbol.split, but that's just my opinion.

• I feel unnecessary double parenthesis in examples like exponentiation assignment might be confusing to the user.

Except for that I can see clear benefits of this PR. Most of the examples would look better with those changes applied.

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[schalkneethling]

Hey @nschonni, thoughts on the comments here #2288 (comment)

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[schalkneethling]

Hey @nschonni and @NiedziolkaMichal,

First, thank you for the work you have done here, Nick. There were a couple of items brought up by Michal here #2288 (comment)

Please review them when you have a moment. Also, there are a couple of conflicts at the moment, mainly in package.json. Thanks so much.

[nschonni]

The config does have overrides for particular files

interactive-examples/.eslintrc

Line 71 in 2315bc6

"overrides": [

If you've got suggestions for those, then I can add them, but I didn't see anything actionable for me from the comments above

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[schalkneethling]

Hey @nschonni and @NiedziolkaMichal,

We had a chat about this one. The work here is great and something we want but, the following topic raised by Michal is a blocker at the moment.

Unfortunately it's going to change height of multiple examples.

We have brought this to the attention of engineering and will follow up on this in the new year. We are also discussing whether this can be something the community can assist with if we have low-bandwidth internally.

We hope this makes sense and is acceptable to you all. Thanks again for the work done.

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[schalkneethling]

@NiedziolkaMichal, @bsmth, anyone opposed to us landing this one?

[bsmth]

I think the changes are good, but it might be best if these two PRs land first so we don't introduce display issues:

• Adds height-data.json bob#839
• feat(macros/EmbedInteractiveExample): use height from height-data.json yari#7679

[schalkneethling]

I think the changes are good, but it might be best if these two PRs land first so we don't introduce display issues:

• Adds height-data.json bob#839
• feat(macros/EmbedInteractiveExample): use height from height-data.json yari#7679

I have assigned reviewers for these pull requests.