Skip to content

Commit b02ef4c

Browse files
doc: update technical priorities
Signed-off-by: Jacob Smith <3012099+JakobJingleheimer@users.noreply.github.com> PR-URL: #64505 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Ulises Gascón <ulisesgascongonzalez@gmail.com> Reviewed-By: Aviv Keller <me@aviv.sh>
1 parent 9274903 commit b02ef4c

1 file changed

Lines changed: 2 additions & 13 deletions

File tree

doc/contributing/technical-priorities.md

Lines changed: 2 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,8 @@ and the TSC on a 6-month basis.
1717
Version from the [mini-summit](https://github.com/nodejs/next-10/issues/1)
1818
on October 1st 2022.
1919

20+
Last reviewed: July 2026
21+
2022
## Modern HTTP
2123

2224
_Present in: 2021_
@@ -29,19 +31,6 @@ implementation that is easier to support and makes it easier to integrate
2931
the new HTTP versions (HTTP3, QUIC) and to support efficient
3032
implementations of different versions concurrently.
3133

32-
## Suitable types for end-users
33-
34-
_Present in: 2021_
35-
36-
Using typings with JavaScript can allow a richer experience when using Visual
37-
Studio Code (or any other IDEs) environments, more complete documentation
38-
of APIs and the ability to identify and resolve errors earlier in the
39-
development process. These benefits are important to a large number of Node.js
40-
developers (maybe 50%). Further typing support may be important
41-
to enterprises that are considering expanding their preferred platforms to
42-
include Node.js. It is, therefore, important that the Node.js project work
43-
to ensure there are good typings available for the public Node.js APIs.
44-
4534
## Documentation
4635

4736
_Present in: 2021_

0 commit comments

Comments
 (0)