Update domprops from FF and Chrome: Is this how?

[kirbysayshi]

Hello!

I noticed that some properties of the TextMetrics API were being mangled (actualBoundingBoxAscent, actualBoundingBoxDescent). They aren't present in domprops.js, so I:

• executed the domprops html in both Firefox and Chrome
• copy/paste merged with existing domprops.js
• sorted using pbpaste | sort -u (note: VSCode does not sort lines correctly...)

Are these roughly the steps to update this list? Is there another way? If so, let me know and I'll update this PR. I'm not very familiar with terser's testing conventions, but I've done what I could to get the tests to pass. Not sure if these changes should be expected or not.

Sidenote: when I tried running the tests (and even the commit hook) locally, I received and ESM error in node 12.16.1. I didn't look too deeply into this, but wanted to mention it as it definitely hindered testing before creating this PR. Error below:

internal/modules/cjs/loader.js:1174
      throw new ERR_REQUIRE_ESM(filename, parentPath, packageJsonPath);
      ^

Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: /Users/drew/GIT/terser/test/compress.js
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1174:13)
    at Module.load (internal/modules/cjs/loader.js:1002:32)
    at Function.Module._load (internal/modules/cjs/loader.js:901:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:74:12)
    at internal/main/run_main_module.js:18:47 {
  code: 'ERR_REQUIRE_ESM'
}

[fabiosantoscode]

Hello there!

Yes, this is exactly how it's done and that script hasn't been run in years.

Development of Terser requires node 14. I guess I'll add this to CONTRIBUTING.md

[fabiosantoscode]

Thank you very much!

[kirbysayshi]

Development of Terser requires node 14. I guess I'll add this to CONTRIBUTING.md

Nice to know! Thanks for accepting!