Update compat data (specifically for rhino 1.7.14)

[phulin]

Q	A
Fixed Issues?
Patch: Bug Fix?
Major: Breaking Change?
Minor: New Feature?
Tests Added + Pass?	No
Documentation PR Link
Any Dependency Changes?
License	MIT

This is a first attempt at updating compat data, in this case specifically to support rhino 1.7.14. Per discussion over at mozilla/rhino#1164 with @nicolo-ribaudo, I updated the fixtures as well with make build-compat-data && make bootstrap && OVERWRITE=true yarn jest. Unfortunately, this seems to have triggered a number of unrelated changes to the fixture stdout files and caused one of the fixture tests to fail:

 FAIL  packages/babel-preset-env/test/fixtures.js (12.192 s)
babel-preset-env/shipped proposals > new class features chrome 94
        SyntaxError: /Users/phulin/Documents/Projects/kol/babel/packages/babel-preset-env/test/fixtures/shipped-proposals/new-class-features-chrome-94/input.js: Static class blocks are not enabled. Please add `@babel/plugin-proposal-class-static-block` to your configuration.
        > 1 | class A {
            | ^
          2 |   #foo;
          3 |
          4 |   static {

Curious for any advice you all have as to how to resolve these. I'm sure I'm doing something wrong here.

[nicolo-ribaudo]

Uh, it's because of #14181 / compat-table/compat-table#1784. We'll handle that issue soon-ish, but for now you can edit

babel/packages/babel-compat-data/scripts/data/plugin-features.js

Lines 158 to 164 in b1e79de

	"proposal-class-properties": {
	features: [
	"static class fields",
	"instance class fields, public instance class fields",
	"instance class fields, private instance class fields basic support",
	"instance class fields, computed instance class fields",
	],

to explicitly list the other static fields test (and remove the generic "static class fields"):

"static class fields, public static class fields",
"static class fields, private static class fields",
"static class fields, computed static class fields"

[phulin]

Huh, that doesn't seem to have addressed either the test failure or the extraneous stdout.txt changes. Any other ideas?

[nicolo-ribaudo]

It didn't work because the separator is / (with one space before and one after), not , 😬
"static class fields / public static class fields", etc.

[phulin]

Perfect, thank you. That appears to have worked correctly. I didn't commit the changes to plugin-features.js as I assume those are temporarily required only.

[nicolo-ribaudo]

Oh please commit them, so that the committed script always reflects the committed data.

[babel-bot]

Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/50936/

[phulin]

Done. Thanks for the help.

[nicolo-ribaudo]

I will open another PR changing , to / here. I'd prefer to keep it separate because it might cause changes to our compat data and fixtures not related to rhino.