feat: update technical priorities for 2023

Author: sheplu

doc/contributing/technical-priorities.md

@@ -14,6 +14,88 @@ on August 5th 2021.
 They will be updated regularly and will be reviewed by the next-10 team
 and the TSC on a 6-month basis.
 
+
+Version from the [mini-summit](https://github.com/nodejs/next-10/issues/1) on October 1st 2022.
+
+## ESM
+
+The CommonJS module system was one of the key components that led to the success
+of Node.js in its first 10 years. ESM is the standard that has been adopted as
+the equivalent in the broader JavaScript ecosystem and Node.js must continue to
+develop and improve its ESM implementation to stay relevant and ensure
+continued growth for the next 10 years.
+
+## Suitable types for end-users
+
+Using typings with JavaScript can allow a richer experience when using Visual
+Studio Code (or any other IDEs) environments, more complete documentation
+of APIs and the ability to identify and resolve errors earlier in the
+development process. These benefits are important to a large number of Node.js
+developers (maybe 50%).  Further typing support may be important
+to enterprises that are considering expanding their preferred platforms to
+include Node.js. It is, therefore, important that the Node.js project work
+to ensure there are good typings available for the public Node.js APIs.
+
+## Serverless
+
+Serverless is a cloud computing model where the cloud provider manages the underlying infrastructure and automatically allocates resources as needed. Developers only need to focus on writing code for specific functions, which are executed as individual units of work in response to events. Node.js is one of the main technology used by developers in this field therefore it is crucial for us to provide a great solution.
+
+## Small footprint
+
+Small software footprints refer to software that has a minimal impact on system resources such as memory and processing power. This can be achieved through various methods such as optimizing code, reducing the number of dependencies, or using lightweight frameworks. Smaller footprints can lead to faster startup times, reduced memory usage, and improved overall system performance. This is primordial for Node.js to be a lightweigh proposition inside the ecosystem as it is used across a wild variety of projects, from web application to IoT and serverless.
+
+## Observability
+
+The ability to investigate and resolve problems that occur in applications
+running in production is crucial for organizations. Tools that allow
+people to observe the current and past operation of the application are
+needed to support that need. It is therefore important that the Node.js
+project work towards well understood and defined processes for observing
+the behavior of Node.js applications as well as ensuring there are well
+supported tools to implement those processes (logging, metrics and tracing).
+This includes support within the Node.js runtime itself (for example
+generating heap dumps, performance metrics, etc.) as well as support for
+applications on top of the runtime. In addition, it is also important to clearly
+document the use cases, problem determination methods and best
+practices for those tools.
+
+## Modern HTTP
+
+Base HTTP support is a key component of modern cloud-native applications
+and built-in support was part of what made Node.js a success in the first
+10 years. The current implementation is hard to support and a common
+source of vulnerabilities. We must work towards an
+implementation which is easier to support and makes it easier to integrate
+the new HTTP versions (HTTP3, QUIC) and to support efficient
+implementations of different versions concurrently.
+
+## WebAssembly
+
+The use of WebAssembly has been growing over the last few years.
+To ensure Node.js continues to be part of solutions where a
+subset of the solution needs the performance that WebAssembly can
+deliver, Node.js must provide good support for running
+WebAssembly components along with the JavaScript that makes up the rest
+of the solution. This includes implementations of “host” APIs like WASI.
+
+## Documentation
+
+The current documentation is great for experienced developers or people
+who are aware of what they are looking for. On the other hand, for
+beginners this documentation can be quite hard to read and finding the
+desired information is difficult. We must have documentation
+that is suitable for beginners to continue the rapid growth in use.
+This documentation should include more concrete examples and a learning
+path for newcomers.
+
+## Developers-first DX
+
+Developer experience (DX) refers to the overall experience a developer has when working with a software development platform, framework, or tool. It encompasses all aspects of the developer's interactions with the system, from installation and configuration to writing code and debugging. A good DX prioritizes ease of use, efficiency, and productivity, and can lead to faster development times, higher quality code, and greater developer satisfaction. Factors that can impact DX include documentation, community support, testing tools, and integration with other systems.
+
+------
+
+Version from the [mini-summit](https://github.com/nodejs/next-10/issues/76) on August 5th 2021.
+
 ## Modern HTTP
 
 Base HTTP support is a key component of modern cloud-native applications