ws added EventListenerOptions and removed optional flag on callback

[wilwade]

Fixing types around addEventListener for the ws package:

• Added options (from merged PR: Add support for the EventTarget once option websockets/ws#1754)
• Made callback/listener non-optional, because it isn't optional From documentation: https://github.com/websockets/ws/blob/da42ea17451f11eed54adb54d3beeedbb1c2aa70/doc/ws.md#websocketaddeventlistenertype-listener-options

Please fill in this template.

• Use a meaningful title for the pull request. Include the name of the package modified.
• Test the change in your own code. (Compile and run.)
• Add or edit tests to reflect the change. (Run with npm test.)
• Follow the advice from the readme.
• Avoid common mistakes.
• Run npm run lint package-name (or tsc if no tslint.json is present).

Select one of these and delete the others:

If changing an existing definition:

• Provide a URL to documentation or source code which provides context for the suggested changes: https://github.com/websockets/ws/blob/da42ea17451f11eed54adb54d3beeedbb1c2aa70/doc/ws.md#websocketaddeventlistenertype-listener-options
• If this PR brings the type definitions up to date with a new version of the JS library, update the version number in the header.
• Include tests for your changes
• If you are making substantial changes, consider adding a tslint.json containing { "extends": "dtslint/dt.json" }. If for reason the any rule need to be disabled, disable it for that line using // tslint:disable-next-line [ruleName] and not for whole package so that the need for disabling can be reviewed.

[typescript-bot]

@wilwade Thank you for submitting this PR! I see this is your first time submitting to DefinitelyTyped 👋 — I'm the local bot who will help you through the process of getting things through.

This is a live comment which I will keep updated.

1 package in this PR

• ws on npm, on unpkg

Code Reviews

Because you edited one package and updated the tests (👏), I can help you merge this PR once someone else signs off on it.

Status

• ✅ No merge conflicts
• ✅ Continuous integration tests have passed
• ✅ Most recent commit is approved by type definition owners or DT maintainers

All of the items on the list are green. To merge, you need to post a comment including the string "Ready to merge" to bring in your changes.

---

Diagnostic Information: What the bot saw about this PR

{
  "type": "info",
  "now": "-",
  "pr_number": 46794,
  "author": "wilwade",
  "owners": [
    "loyd",
    "elithrar",
    "mlamp",
    "TitaneBoy",
    "orblazer",
    "reduckted",
    "teidesu",
    "wojtkowiak"
  ],
  "dangerLevel": "ScopedAndTested",
  "headCommitAbbrOid": "ecea87a",
  "headCommitOid": "ecea87a8ae3f48365b5b6fe575f8e80e2c661b06",
  "mergeIsRequested": true,
  "stalenessInDays": 0,
  "lastPushDate": "2020-08-14T20:50:20.000Z",
  "lastCommentDate": "2020-09-28T22:46:40.000Z",
  "maintainerBlessed": true,
  "reviewLink": "https://github.com/DefinitelyTyped/DefinitelyTyped/pull/46794/files",
  "hasMergeConflict": false,
  "authorIsOwner": false,
  "isFirstContribution": true,
  "popularityLevel": "Critical",
  "newPackages": [],
  "packages": [
    "ws"
  ],
  "files": [
    {
      "path": "types/ws/index.d.ts",
      "kind": "definition",
      "package": "ws"
    },
    {
      "path": "types/ws/ws-tests.ts",
      "kind": "test",
      "package": "ws"
    }
  ],
  "hasDismissedReview": false,
  "ciResult": "pass",
  "lastReviewDate": "2020-09-28T18:30:52.000Z",
  "reviewersWithStaleReviews": [],
  "approvalFlags": 4,
  "isChangesRequested": false
}

[typescript-bot]

🔔 @loyd @elithrar @mlamp @TitaneBoy @orblazer @reduckted @teidesu @wojtkowiak — please review this PR in the next few days. Be sure to explicitly select Approve or Request Changes in the GitHub UI so I know what's going on.

[danger-public]

Inspecting the JavaScript source for this package found some properties that are not in the .d.ts files.
The check for missing properties isn't always right, so take this list as advice, not a requirement.

ws (unpkg)

was missing the following properties:

1. once
2. EventEmitter
3. Receiver
4. Sender

Generated by 🚫 dangerJS against ecea87a

[typescript-bot]

👋 Hi there! I’ve run some quick measurements against master and your PR. These metrics should help the humans reviewing this PR gauge whether it might negatively affect compile times or editor responsiveness for users who install these typings.

Let’s review the numbers, shall we?

Comparison details 📊

	master	#46794	diff
Batch compilation
Memory usage (MiB)	65.4	67.8	+3.6%
Type count	9215	9220	0%
Assignability cache size	1727	1727	0%
Language service
Samples taken	282	292	+4%
Identifiers in tests	282	292	+4%
getCompletionsAtPosition
Mean duration (ms)	360.2	354.2	-1.7%
Mean CV	8.8%	8.8%
Worst duration (ms)	492.8	442.2	-10.3%
Worst identifier	http	event
getQuickInfoAtPosition
Mean duration (ms)	360.9	353.2	-2.1%
Mean CV	9.0%	9.1%	+1.3%
Worst duration (ms)	437.1	446.9	+2.2%
Worst identifier	createServer	once

It looks like nothing changed too much. I won’t post performance data again unless it gets worse.

[amcasey]

Personally, I might also add a test demonstrating that not passing a callback is an error.

[typescript-bot]

@wilwade Everything looks good here. Great job! I am ready to merge this PR on your behalf.

If you'd like that to happen, please post a comment saying:

Ready to merge

and I'll merge this PR almost instantly. Thanks for helping out! ❤️

(@loyd, @elithrar, @mlamp, @TitaneBoy, @orblazer, @reduckted, @teidesu, @wojtkowiak: you can do this too.)

[wilwade]

Ready to merge

[typescript-bot]

I just published @types/ws@7.2.7 to npm.