- {% if page.title contains 'middleware' %}
- {% capture readme %}{% include mw-list.md %}{% endcapture %}
- {% else %}
- {% capture readme %}{% include util-list.md %}{% endcapture %}
- {% endif %}
- {{ readme | markdownify }}
+
+
+
+
diff --git a/_layouts/page.html b/_layouts/page.html
index a760250451..0a93f56c84 100644
--- a/_layouts/page.html
+++ b/_layouts/page.html
@@ -1,8 +1,4 @@
-
{% if page.lang %}
@@ -14,23 +10,30 @@
{% endif %}
-
+ {% if page.lang != 'en' %}
+
-
- {% include api/en/3x/res.md %}
+
diff --git a/de/4x/api.md b/de/4x/api.md
old mode 100755
new mode 100644
index b29bca87c9..4db5c42322
--- a/de/4x/api.md
+++ b/de/4x/api.md
@@ -1,26 +1,25 @@
---
-layout: 4x-api
+layout: api
+version: 4x
title: Express 4.x - API-Referenz
+description: Access the API reference for Express.js 4.x, detailing all modules, methods, and properties for building web applications with this version.
menu: api
-lang: de
+redirect_from: " "
---
+
{% include i18n-notice.html %}
-
- {% endif %}
-
-{{ content }}
-
+ {% endif %}
+
+ {% if page.layout == 'middleware' %}
+
+ {{ content }}
+
+ {% else %}
+
+
+ {{ content }}
+ {% include github-edit-btn.html %}
+
+
+ {% endif %}
- {% include footer/footer-{{ page.lang }}.html %}
+ {% include footer.html %}
diff --git a/_layouts/post.html b/_layouts/post.html
new file mode 100644
index 0000000000..4f79504c5b
--- /dev/null
+++ b/_layouts/post.html
@@ -0,0 +1,36 @@
+
+
+ {% include head.html %}
+
+
+ {% include header.html %}
+
+
+
+
+
+ {% if page.title %}
+
+
+
+ {% include footer.html %}
+
+
+
+
diff --git a/_posts/2024-07-16-welcome-post.md b/_posts/2024-07-16-welcome-post.md
new file mode 100644
index 0000000000..52fc60a25a
--- /dev/null
+++ b/_posts/2024-07-16-welcome-post.md
@@ -0,0 +1,27 @@
+---
+title: Welcome to The Express Blog!
+description: Introducing the new Express blog — a primary platform for announcements, updates, and communication from the Express technical committee.
+tags: site-admin
+authors:
+ - name: Rand McKinney
+ github: crandmck
+ - name: Chris Del
+ github: chrisdel101
+---
+
+Welcome to the new Express blog! The blog is meant to be a primary means of communication for the Express technical committee (TC). While we currently have other channels such as X, LinkedIn, and of course GitHub, there's no authoritative "soapbox" for announcements and general communication.
+
+Initially, the Express blog will be a venue:
+- For periodic announcements of new releases, pre-releases, plans, and ongoing work on the project.
+- For the Express TC to discuss issues of particular importance to the Express community.
+- To highlight security issues or other urgent information.
+
+Eventually, we hope the blog will evolve into a more general communication hub for the entire Express community; for example to share examples, tips, and experiences with the Express ecosystem and other information that's not simply technical documentation or GitHub discussion.
+
+Initially, posts will be written by TC members (potentially collaborating others), mainly because we don't have bandwidth to review general posts from the broader community. Eventually, we would love to open up the blog for broader contributions, but for now the focus is on trying to release Express 5.0, and the reality of an open-source project is that everyone has finite time to contribute.
+
+Express TC member [Ulises Gascón](https://github.com/UlisesGascon) suggested a number of interesting topics for blog posts in [expressjs.com issue 1500](https://github.com/expressjs/expressjs.com/issues/1500), but there are undoubtedly many others.
+
+If you have an idea for a post, feel free to pitch the idea! You can add a comment to [expressjs.com issue 1500](https://github.com/expressjs/expressjs.com/issues/1500) or open a new issue, and then after appropriate discussion, open a PR. We've also written up simple [instructions to create a blog post](/en/blog/write-post.html).
+
+Happy blogging!
diff --git a/_posts/2024-09-29-security-releases.md b/_posts/2024-09-29-security-releases.md
new file mode 100644
index 0000000000..658fe345f5
--- /dev/null
+++ b/_posts/2024-09-29-security-releases.md
@@ -0,0 +1,137 @@
+---
+title: September 2024 Security Releases
+description: Security releases for Express, body-parser, send, serve-static, and path-to-regexp have been published. We recommend that all users upgrade as soon as possible.
+tags: security vulnerabilities
+authors:
+ - name: Ulises Gascón
+ github: UlisesGascon
+---
+
+Recently, the Express team has been made aware of a number of security vulnerabilities in the Express project. We have released a number of patches to address these vulnerabilities.
+
+{% include admonitions/warning.html
+content="We strongly recommend that you upgrade these modules to the recommended (or latest) version as soon as possible."
+%}
+
+The following vulnerabilities have been addressed:
+
+- [High severity vulnerability CVE-2024-45590 in body-parser middleware](#high-severity-vulnerability-cve-2024-45590-in-body-parser-middleware)
+- [High severity vulnerability CVE-2024-47178 in basic-auth-connect middleware](#high-severity-vulnerability-cve-2024-47178-in-basic-auth-connect-middleware)
+- [Moderate severity vulnerability CVE-2024-43796 in Express core](#moderate-severity-vulnerability-cve-2024-43796-in-express-core)
+- [Moderate severity vulnerability CVE-2024-43799 in send utility module](#moderate-severity-vulnerability-cve-2024-43799-in-send-utility-module)
+- [Moderate severity vulnerability CVE-2024-43800 in serve-static middleware](#moderate-severity-vulnerability-cve-2024-43800-in-serve-static-middleware)
+- [Moderate severity vulnerability CVE-2024-45296 in path-to-regexp utility module](#moderate-severity-vulnerability-cve-2024-45296-in-path-to-regexp-utility-module)
+
+## High severity vulnerability CVE-2024-45590 in body-parser middleware
+
+**[body-parser](https://www.npmjs.com/package/body-parser) version `<1.20.3` is vulnerable to denial of service when URL-encoding is enabled**
+
+A malicious actor using a specially-crafted payload could flood the server with a large number of requests, resulting in denial of service.
+
+**Affected versions**: `<1.20.3`
+
+**Patched versions**: `>=1.20.3`
+
+This vulnerability was discovered during the [OSTIF audit to Express](https://github.com/expressjs/security-wg/issues/6) and was mitigated by [the Express security triage team](https://github.com/expressjs/security-wg?tab=readme-ov-file#security-triage-team).
+
+For more details, see [GHSA-qwcr-r2fm-qrc7](https://github.com/expressjs/body-parser/security/advisories/GHSA-qwcr-r2fm-qrc7).
+
+## High severity vulnerability CVE-2024-47178 in basic-auth-connect middleware
+
+**[basic-auth-connect](https://www.npmjs.com/package/basic-auth-connect) uses a timing-unsafe equality comparison**
+
+basic-auth-connect `<1.1.0` uses a timing-unsafe equality comparison that can leak timing information
+
+**Affected versions**
+- `<1.1.0`
+
+**Patched versions**
+- `>=1.1.0`
+
+This vulnerability was discovered during the [OSTIF audit to Express](https://github.com/expressjs/security-wg/issues/6) and was mitigated by [the Express Securty triage team](https://github.com/expressjs/security-wg?tab=readme-ov-file#security-triage-team).
+
+More details area available in [GHSA-7p89-p6hx-q4fw](https://github.com/expressjs/basic-auth-connect/security/advisories/GHSA-7p89-p6hx-q4fw)
+
+
+
+## Moderate severity vulnerability CVE-2024-43796 in Express core
+
+The core **[express](https://www.npmjs.com/package/express) package is vulnerable to cross-site scripting (XSS) attack via `response.redirect()`**.
+
+In Express version <4.20.0, passing untrusted user input—even after sanitizing it—to `response.redirect()` may execute untrusted code.
+
+**Affected versions**:
+- `<4.20.0`
+- `>=5.0.0-alpha.1`, `<5.0.0`
+
+**Patched versions**:
+- `>=4.20.0`
+- `>=5.0.0`
+
+This vulnerability was discovered during the [OSTIF audit of Express](https://github.com/expressjs/security-wg/issues/6) and was mitigated by [the Express security triage team](https://github.com/expressjs/security-wg?tab=readme-ov-file#security-triage-team).
+
+For more details, see [GHSA-qw6h-vgh9-j6wx](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx).
+
+
+## Moderate severity vulnerability CVE-2024-43799 in send utility module
+
+The **[send](https://www.npmjs.com/package/send) utility module is vulnerable to template injection that can lead to vulnerability to cross-site scripting (XSS) attack**.
+
+Passing untrusted user input—even after sanitizing it—to `SendStream.redirect()` can execute untrusted code.
+
+**Affected versions**: `< 0.19.0`
+
+**Patched versions**: `>=0.19.0`
+
+This vulnerability was discovered during the [OSTIF audit of Express](https://github.com/expressjs/security-wg/issues/6) and was mitigated by [the Express security triage team](https://github.com/expressjs/security-wg?tab=readme-ov-file#security-triage-team).
+
+For more details, see [GHSA-m6fv-jmcg-4jfg](https://github.com/pillarjs/send/security/advisories/GHSA-m6fv-jmcg-4jfg).
+
+
+## Moderate severity vulnerability CVE-2024-43800 in serve-static middleware
+
+The **[serve-static](https://www.npmjs.com/package/serve-static) middleware module is vulnerable to template injection that can lead to vulnerability to cross-site scripting (XSS) attack**.
+
+Passing untrusted user input—even after sanitizing it—to `redirect()` can execute untrusted code.
+
+**Affected versions**:
+- `< 1.16.0`
+- `>=2.0.0`, `<2.1.0`
+
+**Patched versions**:
+- `>=1.16.0`
+- `>=2.1.0`
+
+This vulnerability was discovered during the [OSTIF audit of Express](https://github.com/expressjs/security-wg/issues/6) and was mitigated by [the Express security triage team](https://github.com/expressjs/security-wg?tab=readme-ov-file#security-triage-team).
+
+For more details, see [GHSA-cm22-4g7w-348p](https://github.com/expressjs/serve-static/security/advisories/GHSA-cm22-4g7w-348p)
+
+
+## Moderate severity vulnerability CVE-2024-45296 in path-to-regexp utility module
+
+The **[path-to-regexp](https://www.npmjs.com/package/path-to-regexp) utility module is vulnerable to regular expression denial of service (ReDoS) attack**.
+
+A bad regular expression is generated any time you have two parameters within a single segment, separated by something that is not a period (`.`). For example, `/:a-:b`.
+
+Using `/:a-:b` will produce the regular expression `/^\/([^\/]+?)-([^\/]+?)\/?$/`. This can be exploited by a path such as `/a${'-a'.repeat(8_000)}/a`. [OWASP](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS) has a good example of why this occurs, but in essence, the `/a` at the end ensures this route would never match, but due to naive backtracking it will still attempt every combination of the `:a-:b` on the repeated 8,000 `-a`.
+
+Because JavaScript is single-threaded and regex matching runs on the main thread, poor performance will block the event loop and can lead to a DoS. In local benchmarks, exploiting the unsafe regex will result in performance that is over 1000x worse than the safe regex. In a more realistic environment, using Express v4 and ten concurrent connections results in an average latency of ~600ms vs 1ms.
+
+**Affected versions**:
+- `>=4.0.0`, `<8.0.0`
+- `>=0.2.0`, `<1.9.0`
+- `<0.1.10`
+- `>=2.0.0`, `<3.3.0`
+- `>=4.0.0`, `<6.3.0`
+
+**Patched versions**:
+- `>=8.0.0`
+- `>=1.9.0`
+- `>=0.1.10`
+- `>=3.3.0`
+- `>=6.3.0`
+
+Thanks to [Blake Embrey](https://github.com/blakeembrey) who reported and created the security patch.
+
+For more details, see [GHSA-9wv6-86v2-598j](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j)
+
diff --git a/_posts/2024-10-01-HeroDevs-partnership-announcement.md b/_posts/2024-10-01-HeroDevs-partnership-announcement.md
new file mode 100644
index 0000000000..9ae9dac7a1
--- /dev/null
+++ b/_posts/2024-10-01-HeroDevs-partnership-announcement.md
@@ -0,0 +1,26 @@
+---
+title: Express Never Ending Support Launched by HeroDevs and Express.js
+description: The Express.js team is pleased to announce a partnership with HeroDevs to launch Express Never-Ending Support (NES), providing long-term support for applications built with legacy Express. This collaboration ensures that developers relying on older versions of the framework will continue to receive critical security and compatibility updates, allowing them to maintain and scale their applications securely, even after the framework's official end-of-life.
+tags: partnerships announcements
+authors:
+ - name: Express Technical Committee
+ github: expressjs
+---
+
+The Express.js team is pleased to announce a partnership with HeroDevs to launch [Express Never-Ending Support (NES)](https://www.herodevs.com/support/express-nes), providing long-term support for applications built with legacy Express. This collaboration ensures that developers relying on older versions of the framework will continue to receive critical security and compatibility updates, allowing them to maintain and scale their applications securely, even after the framework's official end-of-life.
+
+Express.js is known for its minimalistic design and flexibility, offering developers a powerful yet lightweight framework for building web and mobile applications. Its extensive set of HTTP utility methods and middleware have made creating APIs both efficient and scalable—qualities that have made it a go-to choice for Node.js developers over the years.
+
+However, Express.js v3.x reached its end-of-life in July 2015, leaving many businesses and developers in need of support to keep their applications secure and compliant.
+
+> "We’re grateful to see HeroDevs stepping in to provide extended long-term support for Express
+>
+> Express NES ensures that the many businesses and developers who rely on Express can continue using it safely and securely, even years after its original end-of-life. This kind of ongoing commitment to the open-source ecosystem is crucial, and we’re excited to see the benefits it brings to the developer community.” — said a spokesperson for the Express Technical Committee.
+
+Express NES is designed as a drop-in replacement for legacy versions of Express.js, offering security patches, compatibility updates and compliance fixes. This solution ensures that developers can remain on legacy Express.js without becoming vulnerable to security risks and compliance issues.
+
+> “We’re thrilled to introduce Express NES as part of our continued mission to support the sustainability of key open-source tools
+>
+> Our partnership with OpenJS has enabled us to meet the needs of developers still relying on older versions of critical frameworks. Express NES ensures that they can continue building and maintaining their applications without the risk of security vulnerabilities or loss of compliance.” — Joe Eames, VP of Partnership at HeroDevs.
+
+For more information on Express NES and how to get started, visit [HeroDevs’ website](https://www.herodevs.com/support/express-nes).
\ No newline at end of file
diff --git a/_posts/2024-10-15-v5-release.md b/_posts/2024-10-15-v5-release.md
new file mode 100644
index 0000000000..3e33233d7a
--- /dev/null
+++ b/_posts/2024-10-15-v5-release.md
@@ -0,0 +1,131 @@
+---
+title: "Introducing Express v5: A New Era for the Node.js Framework"
+tags: releases
+authors:
+ - name: Wes Todd
+ github: wesleytodd
+ - name: Express Technical Committee
+ github: expressjs
+description: Announcing the release of Express version 5
+---
+
+Ten years ago (July 2014) the [Express v5 release pull request](https://github.com/expressjs/express/pull/2237) was opened, and now at long last it's been merged and published!
+
+We want to recognize the work of all our contributors, especially [Doug Wilson](https://github.com/dougwilson), who spent the last ten years ensuring Express was the most stable project around. Without his contributions and those of many others, this release could not have happened.
+
+Eight months ago we went public with a plan to move [Express forward](https://github.com/expressjs/discussions/issues/160). This plan included re-committing to the governance outlined years ago and adding more contributors to help kickstart progress. Many people may not realize that robust project governance is critical to the health of a large open-source project. We want to thank the [OpenJS Foundation Cross Project
+Council](https://github.com/openjs-foundation/cross-project-council/) and its members for helping us put together this plan.
+
+## So what about v5?
+
+This release is designed to be boring!
+That may sound odd, but we've intentionally kept it simple to unblock the ecosystem and enable more impactful changes in future releases. This is also about signaling to the Node.js ecosystem that Express is moving again.
+The focus of this release is on dropping old Node.js version support, addressing security concerns, and simplifying maintenance.
+
+Before going into the changes in this release, let's address why it was released v5 on the `next` dist-tag. As part of reviving the project, we started a [Security working group](https://github.com/expressjs/security-wg) and [security triage team](https://github.com/expressjs/security-wg?tab=readme-ov-file#security-triage-team) to address the growing needs around open source supply chain security. We undertook a security audit (more details to come on that) and uncovered some problems that needed to be addressed. Thus, in addition to the "normal" work done in public issues, we also did a lot of security work in private forks.
+This security work required orchestration when releasing, to ensure the code and CVE reports went out together. You can find a summary of the most recent vulnerabilities patched in [our security release notes](https://expressjs.com/2024/09/29/security-releases.html).
+
+While we weren't able to simultaneously release v5, this blog post, the changelog, and documentation, we felt it was most important to have a secure and stable release.
+
+As soon as possible, we'll provide more details on our long-term support (LTS) plans, including when the release will move from `next` to `latest`. For now, if you are uncomfortable being on the bleeding edge (even if it is a rather dull edge) then you should wait to upgrade until the release is tagged `latest`. That said, we look forward to working with you to address any bugs you encounter as you upgrade.
+
+## Breaking changes
+
+The v5 release has the minimum possible number of breaking changes, listed here in order of impact to applications.
+
+- [Ending support for old Node.js versions](#ending-support-for-old-nodejs-versions)
+- [Changes to path matching and regular expressions](#changes-to-path-matching-and-regular-expressions)
+- [Promise support](#promise-support)
+- [Body parser changes](#body-parser-changes)
+- [Removing deprecated method signatures](#removing-deprecated-method-signatures)
+
+There are also a number of subtle changes: for details, see [Migrating to Express 5]({{site.url}}/{{page.lang}}/guide/migrating-5).
+
+### Ending support for old Node.js versions
+
+Goodbye Node.js 0.10, hello Node 18 and up!
+
+This release drops support for Node.js versions before v18. This is an important change because supporting old Node.js versions has been holding back many critical performance and maintainability changes. This change also enables more stable and maintainable continuous integration (CI), adopting new language and runtime features, and dropping dependencies that are no longer required.
+
+We recognize that this might cause difficulty for some enterprises with older or "parked" applications, and because of this we are working on a [partnership with HeroDevs](https://expressjs.com/2024/10/01/HeroDevs-partnership-announcement.html) to offer "never-ending support" that will include critical security patches even after v4 enters end-of-life (more on these plans soon). That said, we strongly suggest that you update to modern Node.js versions as soon as possible.
+
+### Changes to path matching and regular expressions
+
+The v5 releases updates to `path-to-regexp@8.x` from `path-to-regexp@0.x`, which incorporates many years of changes. If you were using any of the 5.0.0-beta releases, a last-minute update which greatly changed the path semantics to [remove the possibility of any ReDoS attacks](https://blakeembrey.com/posts/2024-09-web-redos/). For more detailed changes, [see the `path-to-regexp` readme](https://github.com/pillarjs/path-to-regexp?tab=readme-ov-file#express--4x).
+
+#### No more regex
+
+This release no longer supports "sub-expression" regular expressions, for example `/:foo(\\d+)`.
+This is a commonly-used pattern, but we removed it for security reasons. Unfortunately, it's easy to write a regular expression that has exponential time behavior when parsing input: The dreaded regular expression denial of service (ReDoS) attack. It's very difficult to prevent this, but as a library that converts strings to regular expressions, we are on the hook for such security aspects.
+
+*How to migrate:* The best approach to prevent ReDoS attacks is to use a robust input validation library. [There are many on `npm`](https://www.npmjs.com/search?q=validate%20express) depending on your needs. TC member Wes Todd maintains [a middleware-based "code first" OpenAPI library](https://www.npmjs.com/package/@wesleytodd/openapi) for this kind of thing.
+
+#### Splats, optional, and captures oh my
+
+This release includes simplified patterns for common route patterns. With the removal of regular expression semantics comes other small but impactful changes to how you write your routes.
+
+1. `:name?` becomes `{:name}`. Usage of `{}` for optional parts of your route means you can now do things like `/base{/:optional}/:required` and what parts are actually optional is much more explicit.
+2. `*` becomes `*name`.
+3. New reserved characters: `(`, `)`, `[`, `]`, `?`, `+`, & `!`. These have been reserved to leave room for future improvements and to prevent mistakes when migrating where those characters mean specific things in previous versions.
+
+#### Name everything
+
+This release no longer supports ordered numerical parameters.
+
+In Express v4, you could get numerical parameters using regex capture groups (for example, `/user(s?)` => `req.params[0] === 's'`). Now all parameters must be named. Along with requiring a name, Express now supports all valid JavaScript identifiers or quoted (for example, `/:"this"`).
+
+### Promise support
+
+This one may be a bit contentious, but we "promise" we're moving in the right direction. We added support for returned *rejected* promises from errors raised in middleware. This *does not include* calling `next` from returned *resolved* promises. There are a lot of edge cases in old Express apps that have expectations of `Promise` behavior, and before we can run we need to walk. For most folks, this means you can now write middleware like the following:
+
+```javascript
+app.use(async (req, res, next) => {
+ req.locals.user = await getUser(req);
+ next();
+});
+```
+
+Notice that this example uses `async/await` and the `getUser` call may throw an error (if, for example, the user doesn't exist, the user database is down, and so on), but we still call `next` if it is successful. We don't need to catch the error in line anymore if we want to rely on error-handling middleware instead because the router will now catch the rejected promise and treat that as calling `next(err)`.
+
+NOTE: Best practice is to handle errors as close to the site as possible. So while this is now handled in the router, it's best to catch the error in the middleware and handle it without relying on separate error-handling middleware.
+
+### Body parser changes
+
+There are a number of `body-parser` changes:
+
+- Add option to customize the urlencoded body depth with a default value of 32 as mitigation for [CVE-2024-45590](https://nvd.nist.gov/vuln/detail/CVE-2024-45590) ([technical details](https://github.com/expressjs/body-parser/commit/b2695c4450f06ba3b0ccf48d872a229bb41c9bce))
+- Remove deprecated `bodyParser()` combination middleware
+- `req.body` is no longer always initialized to `{}`
+- `urlencoded` parser now defaults `extended` to false
+- Added support for Brotli lossless data compression
+
+### Removing deprecated method signatures
+
+Express v5 removes a number of deprecated method signatures, many of which were carried over from v3. Below are the changes you need to make:
+
+- `res.redirect('back')` and `res.location('back')`: The magic string `'back'` is no longer supported. Use `req.get('Referrer') || '/'` explicitly instead.
+- `res.send(status, body)` and `res.send(body, status)` signatures: Use `res.status(status).send(body)`.
+- `res.send(status)` signature: Use `res.sendStatus(status)` for simple status responses, or `res.status(status).send()` for sending a status code with an optional body.
+- `res.redirect(url, status)` signature: Use `res.redirect(status, url)`.
+- `res.json(status, obj)` and `res.json(obj, status)` signatures: Use `res.status(status).json(obj)`.
+- `res.jsonp(status, obj)` and `res.jsonp(obj, status)` signatures: Use `res.status(status).jsonp(obj)`.
+- `app.param(fn)`: This method has been deprecated. Instead, access parameters directly via `req.params`, or use `req.body` or `req.query` as needed.
+- `app.del('/', () => {})` method: Use `app.delete('/', () => {})` instead.
+- `req.acceptsCharset`: Use `req.acceptsCharsets` (plural).
+- `req.acceptsEncoding`: Use `req.acceptsEncodings` (plural).
+- `req.acceptsLanguage`: Use `req.acceptsLanguages` (plural).
+- `res.sendfile` method: Use `res.sendFile` instead.
+
+As a framework, we aim to ensure that the API is as consistent as possible. We've removed these deprecated signatures to make the API more predictable and easier to use. By streamlining each method to use a single, consistent signature, we simplify the developer experience and reduce confusion.
+
+## Migration and security guidance
+
+For developers looking to migrate from v4 to v5, there's a [detailed migration guide]({{site.url}}/{{page.lang}}/guide/migrating-5) to help you navigate through the changes and ensure a smooth upgrade process.
+
+Additionally, we’ve been working hard on a comprehensive [Threat Model](https://github.com/expressjs/security-wg/blob/main/docs/ThreatModel.md) that helps illustrate our philosophy of a "Fast, unopinionated, minimalist web framework for Node.js." It provides critical insights into areas like user input validation and security practices that are essential for safe and secure usage of Express in your applications.
+
+## Our work is just starting
+
+We see the v5 release as a milestone toward an Express ecosystem that's a stable and reliable tool for companies, governments, educators, and hobby projects. It is our commitment as the new stewards of the Express project to move the ecosystem forward with this goal in mind. If you want to support this work, which we do on a volunteer basis, please consider supporting the project and its maintainers via [our sponsorship opportunities](https://opencollective.com/express).
+
+We have an [extensive working backlog](https://github.com/expressjs/discussions/issues/266) of tasks, PRs, and issues for Express and dependencies. Naturally, we expect developers will continue to report issues to add to this backlog and open PRs moving forward, and we'll continue to collaborate with the community to triage and resolve them. We look forward to continuing to improve Express and making it useful for its users across the world.
diff --git a/_posts/2024-10-22-security-audit-milestone-achievement.md b/_posts/2024-10-22-security-audit-milestone-achievement.md
new file mode 100644
index 0000000000..bf8bee0fca
--- /dev/null
+++ b/_posts/2024-10-22-security-audit-milestone-achievement.md
@@ -0,0 +1,57 @@
+---
+title: "Express.js Security Audit: A Milestone Achievement"
+tags: security audit releases
+authors:
+ - name: Express Technical Committee
+ github: expressjs
+description: Celebrating the successful completion of the Express.js security audit conducted by Ada Logics and facilitated by OSTIF.
+---
+
+
+We are thrilled to announce the successful completion of a comprehensive security audit for Express.js, conducted by [Ada Logics](https://adalogics.com/) and facilitated by [OSTIF](https://ostif.org/). This extensive review of our framework and its core components marks a significant milestone in our commitment to ensuring the security and reliability of Express.js for our community.
+
+## A Collaborative Effort
+
+This audit was made possible through the collaboration between [the Express Security Working Group](https://github.com/expressjs/security-wg), Ada Logics, OSTIF, and the [OpenJS Foundation](https://openjsf.org/). Our focus was on thoroughly evaluating the Express.js codebase, including its dependencies and core libraries. The primary goal was to identify any potential security vulnerabilities and to strengthen the overall security posture of the framework.
+
+### Key Highlights of the Audit
+
+- **Audit Duration**: Conducted in April and May 2024.
+- **Scope**: Core Express.js codebase and critical dependencies, such as `body-parser`, `basic-auth-connect`, `serve-static`, and more.
+- **Findings**: A total of 5 security vulnerabilities were identified, all of which have been addressed and patched.
+- **Severity**: Issues ranged from moderate to high severity, impacting components like `res.redirect` and `serve-static`.
+
+## A Closer Look at the Findings
+
+The audit identified several vulnerabilities, including potential Cross-Site Scripting (XSS) risks and a Denial of Service (DoS) vulnerability in the `body-parser` middleware. Here are the key CVEs reported:
+
+- **CVE-2024-43796**: XSS in `res.redirect`—fixed in versions >= 4.20.0 and >= 5.0.0.
+- **CVE-2024-45590**: DoS in `body-parser`—patched in version >= 1.20.3.
+- **CVE-2024-47178**: Timing vulnerability in `basic-auth-connect`—patched in version >= 1.1.0.
+- **CVE-2024-43799**: XSS in the `send` utility module—patched in version >= 0.19.0.
+- **CVE-2024-43800**: XSS in `serve-static`—fixed in versions >= 1.16.0 and >= 2.1.0.
+
+Each of these vulnerabilities was promptly addressed by our dedicated [security triage team](https://github.com/expressjs/security-wg?tab=readme-ov-file#security-triage-team), ensuring that users remain protected against known threats.
+
+For full details on the audit results, you can access the [official audit report here](https://ostif.org/wp-content/uploads/2024/10/expressjs-2024-security-audit-report.pdf).
+
+## A Commitment to Transparency and Security
+
+At Express, security is a top priority, and we believe in the importance of transparency when it comes to vulnerabilities and their resolution. This audit not only highlights our proactive approach but also reinforces our ongoing commitment to building a secure web framework for all.
+
+We strongly recommend all users update to the latest versions of the affected packages to benefit from the recent security fixes. For more information on the patches and how to upgrade, please refer to our [September 2024 Security Release announcement](https://expressjs.com/2024/09/29/security-releases.html).
+
+## A Word of Thanks
+
+This audit would not have been possible without the efforts and expertise of many individuals and organizations. We want to extend our gratitude to:
+
+- The team at Ada Logics for their diligent review and insights.
+- OSTIF for their coordination and support throughout the audit process.
+- The OpenJS Foundation for sponsoring this important initiative.
+- Our Express.js community, who continue to support and trust us with their projects.
+- [Jordan Harband](https://github.com/ljharb) for his amazing support while we needed changes in [qs](https://www.npmjs.com/package/qs).
+
+
+Together, we’ve made Express.js stronger, more resilient, and ready for the challenges ahead. We look forward to continuing to serve our community with a focus on excellence and security.
+
+Thank you for being a part of this journey with us!
diff --git a/_posts/2025-01-09-rewind-2024-triumphs-and-2025-vision.md b/_posts/2025-01-09-rewind-2024-triumphs-and-2025-vision.md
new file mode 100644
index 0000000000..cc2a734b02
--- /dev/null
+++ b/_posts/2025-01-09-rewind-2024-triumphs-and-2025-vision.md
@@ -0,0 +1,83 @@
+---
+title: "A New Chapter for Express.js: Triumphs of 2024 and an ambitious 2025"
+tags: news rewind 2024
+authors:
+ - name: Express Technical Committee
+ github: expressjs
+description: Explore the transformative journey of Express.js in 2024, marked by governance improvements, the long-awaited release of Express 5.0, and heightened security measures. Look into the ambitious plans for 2025, including performance optimizations, scoped packages, and a bold roadmap for sustained growth in the Node.js ecosystem.
+---
+
+
+As we step into the new year, it’s almost impossible to ignore the unmistakable energy coursing through the Express.js community. The past twelve months have proven both foundational and forward-looking: an era of governance overhauls, technical triumphs, and security enhancements that not only shaped 2024 but also laid the groundwork for what promises to be a transformative 2025.
+In this long-form recap and forecast, we’ll journey through the story of Express.js with its evolution, its hurdles, and the new heights it’s poised to reach.
+
+---
+
+## A Transformative 2024
+
+Few could have predicted just how pivotal 2024 would be for the Express.js project. From the revitalization of its governance structures to the unveiling of long-awaited features, it was a year that solidified the framework’s role as a mainstay in the Node.js ecosystem.
+
+### Governance and Community Milestones
+
+Central to the project’s growth was the [Express Forward Plan](https://github.com/expressjs/discussions/issues/160), devised to ensure strategic alignment and long-term sustainability. This year also saw the introduction of a new generation of Technical Committee (TC) members, each bringing fresh insights and energy to the community. Those members include [Blake Embrey](https://github.com/blakeembrey), [Chris de Almeida](https://github.com/ctcpip), [Jean Burellier](https://github.com/sheplu), [Jon Church](https://github.com/jonchurch), [Linus Unnebäck](https://github.com/LinusU), [Rand McKinney](https://github.com/crandmck), [Ulises Gascón](https://github.com/ulisesgascon), and [Wes Todd](https://github.com/wesleytodd). By defining a clear path and transparent processes, the community was able to collaborate on ambitious updates more cohesively than ever before. A revitalized release process further streamlined how new versions are planned and executed, eliminating much of the guesswork and inconsistent timing that had previously challenged contributors.
+
+In parallel, the [Security Working Group](https://github.com/expressjs/discussions/issues/165) took shape. Express.js, widely recognized for its importance to the broader Node.js landscape, formally introduced a [security triage team](https://github.com/expressjs/security-wg#security-triage-team) dedicated to proactively identifying and resolving vulnerabilities. This forward-thinking approach was bolstered by the adoption of a [Threat Model for Express.js](https://github.com/expressjs/express/pull/5526), underscoring the project’s commitment to robust, future-proof security.
+
+As if these achievements weren’t enough, Express.js proudly reached [Impact Project status](https://github.com/openjs-foundation/cross-project-council/pull/1404) under the OpenJS Foundation. This acknowledgment affirmed the significance of the framework to the JavaScript ecosystem and showcased the community’s tireless efforts in ensuring its enduring relevance.
+
+### Technical Advancements and the Release of Express 5.0
+
+Naturally, 2024 will forever be remembered as the year when Express.js finally introduced its much-anticipated [Express 5.0](https://expressjs.com/2024/10/15/v5-release.html). After more than a decade of community discussions and behind-the-scenes experimentation, this release brought modern features and a future-oriented architecture to the framework, acting as a catalyst for the next chapter of Express.js development.
+
+But the story did not end there. Even before the release of Express 5.0 was fully established, the community had already begun charting the course for [Express 6.0](https://github.com/expressjs/discussions/issues/267), reflecting an unwavering commitment to innovation. Guiding critical decisions throughout 2024 were new [decision framework](https://github.com/expressjs/discussions/issues/285), which helped the Technical Committee tackle pressing matters such as [engine usage](https://github.com/expressjs/discussions/issues/286) and [dependency management](https://github.com/expressjs/discussions/issues/279). Collectively, these measures fostered transparency and agility, ensuring that Express.js continues to evolve in response to the community’s most urgent needs.
+
+### Maintenance, Tooling, and Collaboration
+
+Express.js also deepened its relationship with the Node.js community by re-integrating into the [Node.js CITGM project](https://github.com/expressjs/express/issues/5489). This move ensured broader ecosystem compatibility and provided developers with further validation that they can rely on Express.js as a dependable cornerstone of their Node.js applications.
+
+### A Heightened Security Posture
+
+Above all, 2024 will stand out for Express.js’s vigorous approach to security. In partnership with the [OpenJS Foundation](https://openjsf.org/) and [OSTIF](https://ostif.org/), the project undertook a comprehensive [security audit](https://expressjs.com/2024/10/22/security-audit-milestone-achievement.html) that yielded critical insights and propelled immediate improvements. The sense of proactive vigilance extended to the adoption of the [OSSF Scorecard](https://github.com/expressjs/discussions/issues/162), implemented at an organizational level to keep track of security metrics and maintain focus on ongoing enhancements.
+
+Throughout the year, maintainers rapidly responded to disclosed vulnerabilities such as [CVE-2024-43796](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-45590](https://github.com/expressjs/body-parser/security/advisories/GHSA-qwcr-r2fm-qrc7), and [CVE-2024-47178](https://github.com/expressjs/basic-auth-connect/security/advisories/GHSA-7p89-p6hx-q4fw). Each instance underscored the community’s readiness to defend the framework’s integrity and safeguard its user base. In a further demonstration of long-term commitment, Express.js teamed up with [HeroDevs](https://www.herodevs.com/) to establish [Never-Ending Support (NES)](https://openjsf.org/blog/at-the-openjs-foundation-were-excited-to-announce-), offering an extended maintenance plan that reaffirms Express.js as a reliable foundation for developers now and in the years to come.
+
+
+---
+
+## A Bold Vision for 2025
+
+While 2024 laid a sturdy bedrock, the Express.js Technical Committee is not resting on its laurels. The newly revealed roadmap for 2025—bolstered by the [Sovereign Tech Fund (STF)](https://www.sovereign.tech/)—embodies a spirit of forward momentum. It promises notable strides in security, performance, and general developer experience, with each initiative building on the insights gained over the past year.
+
+### Automating npm Releases
+
+At the forefront of this plan is the automation of npm releases, an endeavor designed to free maintainers from manual steps and human error. By streamlining the publishing process, the project can achieve faster turnaround times for patches and new features, preserving the stability that developers have come to expect from Express.js. It’s an internal shift with massive external benefits: smoother upgrades, more frequent releases, and a deeper reservoir of confidence for users.
+
+### Introducing Scoped Packages
+
+Express.js will also explore a transition toward scoped packages. By clearly delineating which modules fall under the Express.js umbrella, the maintainers hope to reduce confusion and foster an environment more conducive to organized expansion. As new packages and features are proposed, scoping will make it simpler to track official tools and ensure that community contributions meet consistent quality standards.
+
+### Strengthening Security Reporting and Procedures
+
+Since security remains one of the project’s primary pillars, 2025 will see a significant push to refine how vulnerabilities are reported and managed. Building upon the success of the Security Working Group, the new process will introduce transparent guidelines for reporting potential issues and a consistent triage routine for mitigating them. Additional training for both the Security Triage group and the Technical Committee will further cultivate a shared culture of readiness. Moreover, Express.js is poised to integrate [OSSF Scorecard](https://github.com/expressjs/discussions/issues/162) even more deeply into daily operations, ensuring that both maintainers and users have real-time insights into the project’s health.
+
+### Performance Monitoring and Deep-Level Optimizations
+
+Performance is another focal point. By systematically monitoring the framework’s speed and responsiveness—along with that of its dependencies—the Express.js team aims to pinpoint bottlenecks more rapidly. Over time, insights from these monitoring efforts will drive deeper optimizations in the core Express.js code and its core libraries. These improvements, expected to come to fruition by mid-2026, promise a faster, more scalable framework that can handle the heaviest production workloads with ease.
+
+### Phasing Out Legacy Techniques and Enhancing Documentation
+
+A future of agility and resilience depends on eliminating outdated techniques that invite complexity and fragility. As a result, Express.js will begin phasing out monkey-patching and passthrough APIs that rely too heavily on Node.js internals. This modernization strategy not only reduces technical debt but also ensures that Express.js remains aligned with Node.js updates going forward.
+
+In tandem, the project will make a concerted effort to bolster its security documentation. Through updated guides and best practices, maintainers hope to demystify crucial topics like secure session handling, input validation, and access control. The goal is to arm developers—from novices to seasoned engineers—with the knowledge they need to protect their applications against an ever-evolving threat landscape.
+
+---
+
+## The Road Ahead
+
+As Express.js steps into 2025, it does so with a powerful sense of purpose. The achievements of the past year—culminating in the official release of Express 5.0 and wide-reaching governance enhancements—serve as a sturdy foundation for what’s to come. Yet, the framework’s leadership knows there is always more to build, more to secure, and more to imagine.
+
+Through automated releases, scopes for packages, rigorous security protocols, performance monitoring, and an ongoing effort to modernize core APIs, Express.js is evolving in real-time. And it isn’t just about technology; it’s about forging a collaborative environment where contributors can rely on transparent processes, robust training, and a supportive governance structure.
+
+Whether you’re a seasoned maintainer, an occasional contributor, or a newcomer to this thriving ecosystem, your voice matters. Join the [Express.js GitHub Discussions](https://github.com/expressjs/discussions), attend open meetings, and stay tuned for updates on [Express.js blog](https://expressjs.com/) as we finalize timetables for these initiatives. Each advancement, no matter how technical, flows from a common aspiration: to sustain Express.js as a fast, safe, and influential framework for millions of developers worldwide.
+Together, we’ll keep the spirit of 2024 alive—pushing boundaries, refining practices, and laying the path to a future where Express.js remains at the heart of modern web development.
+
diff --git a/_posts/2025-03-31-v5-1-latest-release.md b/_posts/2025-03-31-v5-1-latest-release.md
new file mode 100644
index 0000000000..9a1ee879dc
--- /dev/null
+++ b/_posts/2025-03-31-v5-1-latest-release.md
@@ -0,0 +1,170 @@
+---
+title: "Express@5.1.0: Now the Default on npm with LTS Timeline"
+tags: news release
+authors:
+ - name: Express Technical Committee
+ github: expressjs
+description: Express 5.1.0 is now the default on npm, and we're introducing an official LTS schedule for the v4 and v5 release lines.
+---
+
+Express v5.0.0 was released on September 9th last year, but we didn't make it the `latest` release on npm. Many asked us
+why and when it would be, and frankly we were not ready at the time to take that jump. If you have not followed the news
+from the project this past year, we have been [hard at work reviving the project](https://expressjs.com/2025/01/09/rewind-2024-triumphs-and-2025-vision.html)
+and when we pushed the initial v5 release there were many loose ends still hanging. So first lets quickly go over some
+of those loose ends.
+
+### Documentation updates
+
+We had not updated the docs, provided migration guides, or even fully reviewed some of the stagnated v4/5 docs in a long
+time. Since then we have had tons of great contributors help get things into better shape. As with any volunteer based
+Open Source project, we love contributions to help us improve so as you upgrade please continue to open PRs to fix
+anything we missed.
+
+You can find our [v5 docs](https://expressjs.com/en/5x/api.html) and our [migration guide](https://expressjs.com/en/guide/migrating-5.html) on the website.
+
+### Migration Support
+
+We know that migrating between versions can be challenging, especially when it involves significant changes in a widely used framework like Express. That's why we have worked on a solution to simplify part of the process and reduce the impact on developers.
+
+Thanks to the incredible efforts of [Sebastian](https://github.com/bjohansebas) and [Filip](https://github.com/kjugi), we have developed a new [codemod package](https://www.npmjs.com/package/@expressjs/codemod) specifically designed to facilitate the transition from Express v4 to v5, as well as future major versions. This package automates many of the necessary code changes, minimizing manual effort and making the upgrade as smooth and efficient as possible.
+
+However, we understand that not all changes can be automated. Some breaking changes, such as the [new Path Route Matching syntax](https://expressjs.com/en/guide/migrating-5.html#path-syntax), require manual modifications by developers. You can read more about all of the breaking changes which came with v5 in our [original release announcement](https://expressjs.com/2024/10/15/v5-release.html).
+
+For more details on the migration process and how to use the codemod package, check the [repository’s README](https://github.com/expressjs/codemod#readme) and the [migration guide](https://expressjs.com/en/guide/migrating-5.html).
+
+### Ecosystem compatibility
+
+The Express ecosystem is one of its strongest assets. It goes back to the early days of Node.js and is the backbone
+that keeps express popular. When it goes [10 years without a major release](https://expressjs.com/2024/10/15/v5-release.html)
+everything from middleware to documentation needed updates. We wanted to make sure folks had
+some time to get all of that updated before we had everyone moving over. Particularly we care about our very large
+beginner user base who may not know the blog post they are reading is not compatible with what they get from
+`npm i express`.
+
+We recognize that some friction is inevitable during major upgrades, but thanks to work from ecosystem partners
+like [Kamil](https://github.com/kamilmysliwiec) from NestJS [working to update `express` before we went `latest`](https://github.com/expressjs/express/issues/5944#issuecomment-2523074127)
+we will hopefully be ahead of the curve. And as I said above, we always welcome help to make this transition easier for
+those who follow after you, PRs are the best support you can give.
+
+### Long Term Support
+
+We had been discussing how to support v4 now that v5 was out, but we had not defined a clear guideline or expectation,
+and we had (still don't have) end user docs on our plans here. While we still have progress to make here, we have a
+[proposed LTS strategy ](https://github.com/expressjs/discussions/pull/352) which will be the basis for our forthcoming
+docs. Input is very welcome on this so we can make sure it is clearly communicated and acceptable to the community.
+
+Additionally since then [we have announced a partnership with HeroDevs](https://expressjs.com/2024/10/01/HeroDevs-partnership-announcement.html) to help companies who are less capable of
+updating. More information on how this will work when v4 EOL will come when we get closer to that time.
+
+---
+
+## Support Phases and Going latest
+
+What does it mean to "go latest"? If you are unfamiliar with how npm `dist-tags` work, the `latest` tag is what users
+will get when they run `npm install express`. This is important because it means it is the "default installed version"
+and will trigger the transition of nearly 17 million weekly downloads from our current latest v4.21.2 to v5. As we start
+this transition we want users, companies, and other organizations to know exactly what it means for support. To help
+with this we have developed an LTS strategy which defines our 3 support phases and set's target dates for when v4 will
+enter EOL.
+
+Express major versions will go through three supported phases:
+
+ - `CURRENT`: A new major version is designated as `CURRENT` upon release. It is available but not the `latest` version
+ on npm for a minimum of 3 months.
+ - `ACTIVE`: After the minimum 3 month period and the TC agrees it is stable and secure, the `ACTIVE` version is
+ tagged `latest` on npm for a minimum of 12 months.
+ - `MAINTENANCE`: When a new major version becomes `ACTIVE`, the previous major version enters `MAINTENANCE` for 12 months.
+
+### CURRENT
+
+- New majors will go through a short period of hardening to ensure stability, security, and ecosystem libraries/resources
+ compatibility.
+- We will strive to ensure no breaking changes are included, but reserve the right to make security or high priority
+ fixes of breaking nature within this period.
+- `CURRENT` lines will receive all types of active work including: bug fixes, security patches, new features, and
+ deprecation notices.
+- Users are recommended to use `CURRENT` lines and to upgrade as quickly as their risk profile allows
+
+### ACTIVE
+
+- `ACTIVE` lines will receive all types of active work including: bug fixes, security patches, new features, and
+ deprecation notices.
+- For users, `ACTIVE` lines are considered the most stable and well supported version at any given time.
+
+### MAINTENANCE
+
+- `MAINTENANCE` lines will only receive security patches or high priority bug fixes.
+- Users are highly encouraged to upgrade to a `CURRENT` or `ACTIVE` release.
+
+### Proposed Schedule
+
+For the existing release lines, we will set the following phase dates:
+
+{{page.title}}
+ {% endif %} + {% if page.sub_title %} +{{page.sub_title}}
+ {% endif %} +
+ {% include blog/authors.html authors=page.authors %}
+
+ {{ content }}
+ {% include github-edit-btn.html %}
+ {{page.date| date: "%d %b %Y" }}
+
+
+| Major | CURRENT | ACTIVE | MAINTENANCE | EOL |
+| ----- | ------- | ------ | ----------- | --- |
+| 4.x | | | 2025-04-01 | *no sooner than 2026-10-01 |
+| 5.x | 2024-09-11 | 2025-03-31 | **no sooner than 2026-04-01 | **no sooner than 2027-04-01 |
+| 6.x | ***no sooner than 2026-01-01 | | | |
+
+
+
+As you can see, this means that v5.1.0 being tagged `latest` indicates that we moved from `CURRENT` to `ACTIVE` which
+starts the clock on EOL for v4 by moving it to `MAINTENANCE`. We recognize that v4 is a special case having been the
+only major version for most of the history of Node.js itself. Because of this, we want to remain flexible and also
+provide a bit longer support. We want to do what is best for the ecosystem, so consider these goals not commitments.
+
+\*: v4 is a special case, and we may extend MAINTENENCE support
+\*\*: v5 MAINTENENCE and EOL dates are determined by when v6 is released, these dates reflect the earliest dates if we
+were to ship v6 on 2025-10-01
+\*\*\* : v6 work has not officially started yet, this is simply the earliest date we can ship based on our proposed policy
+
+---
+
+## Finally, what changed in v5.1.0
+
+This release primarily focused on tech debt from supporting so many old Node.js versions and other things that stagnated but were not landed before v5.0.0 went out.
+
+### Express 5.1.0 Main Changes
+
+* Add support for `Uint8Array` in `res.send()`
+* Transitioned all remaining dependencies to use `^` ranges instead of locked versions
+* Add package.json funding field to highlight our OpenCollective
+* Added support for ETag option in `res.sendFile()`
+* Added support for adding multiple links with the same rel with `res.links()`
+* Performance: Use loop for acceptParams
+* See [Changelog v5.1.0](https://github.com/expressjs/express/releases/tag/v5.1.0)
+
+### Dependencies updated
+
+We also invested time to prepare several releases in the packages that Express depend on. Most of this packages are used by other libraries and framework as individual libraries.
+
+* [body-parser@2.2.0](https://github.com/expressjs/body-parser/releases/tag/v2.2.0)
+ * Remove legacy node.js support checks for Brotli & `AsyncLocalStorage`
+ * Remove `unpipe` & `destroy`
+* [router@2.2.0](https://github.com/pillarjs/router/releases/tag/v2.2.0)
+ * Restore `debug`. Now with the `router` scope instead of `express`.
+ * Remove legacy node.js support checks for `setImmediate`
+ * Deprecate non-native promise support
+ * Remove `after`, `safe-buffer`, `array-flatten`, `setprotoypeof`, `methods`, `utils-merge`
+* [finalhandler@2.1.0](https://github.com/pillarjs/finalhandler/releases/tag/v2.1.0)
+ * Remove legacy node.js support checks for `headersSent`, `setImmediate`, & http2 support
+ * Remove `unpipe`
+* [serve-static@2.2.0](https://github.com/expressjs/serve-static/releases/tag/v2.2.0)
+
+---
+
+## Thanks and What's Next
+
+Thanks so much to everyone involved in Express over the past year, the work all our contributors have put in is
+incredible, and we couldn't do it without them. If you are not able to become a contributor yourself, please consider
+asking your companies to support the project financially on [OpenCollective](https://opencollective.com/express).
+
+As we look ahead, we’re excited to keep building momentum. If you haven’t read it yet, our [Rewind 2024 + 2025 Vision blog post](https://expressjs.com/2025/01/09/rewind-2024-triumphs-and-2025-vision.html) lays out where we’ve been and where we're headed. This includes performances scoped packages, better automation, security hardening, and more.
+
+One major initiative is our new [Performance Working Group](https://github.com/expressjs/discussions/pull/306), focused on identifying and fixing long-standing bottlenecks in Express. We're grateful to be kicking this off with support from the [Sovereign Tech Fund (STF)](https://openjsf.org/sovereign-tech-fund/), who are helping us invest in long-term sustainability and performance of core infrastructure. Additionally, we will be working to [improve our Typescript DX](https://github.com/expressjs/discussions/issues/192) and taking next steps to [improve the website](https://github.com/expressjs/expressjs.com/issues/1787).
+
+And yes, v6 discussions are already starting to heat up. Keep an eye out for updates, and as always, see you in the issues!
+
+Big thanks to [@wesleytodd](https://github.com/wesleytodd), [@blakeembrey](https://github.com/blakeembrey), [@bjohansebas](https://github.com/bjohansebas), [@UlisesGascon](https://github.com/UlisesGascon), [@Phillip9587](https://github.com/Phillip9587), [@carpasse](https://github.com/carpasse), [@jonchurch](https://github.com/jonchurch), [@ctcpip](https://github.com/ctcpip), [@inigomarquinez](https://github.com/inigomarquinez), [@carlosstenzel](https://github.com/carlosstenzel), [@crandmck](https://github.com/crandmck), [@chrisdel101](https://github.com/chrisdel101), [@dpopp07](https://github.com/dpopp07), [@Ayoub-Mabrouk](https://github.com/Ayoub-Mabrouk), [@jonkoops](https://github.com/jonkoops), [@IamLizu](https://github.com/IamLizu), [@marco-ippolito](https://github.com/marco-ippolito), [@ipreencekmr](https://github.com/ipreencekmr), [@ShubhamOulkar](https://github.com/ShubhamOulkar), [@raksbisht](https://github.com/raksbisht), [@jeffreybaird](https://github.com/jeffreybaird), [@dougwilson](https://github.com/dougwilson), [@mertcanaltin](https://github.com/mertcanaltin), [@GeorgeShvab](https://github.com/GeorgeShvab), [@RobinTail](https://github.com/RobinTail), [@EvanHahn](https://github.com/EvanHahn), [@rhodgkins](https://github.com/rhodgkins), [@cengizcmataraci](https://github.com/cengizcmataraci), [@Shantanugupta43](https://github.com/Shantanugupta43), [@italojs](https://github.com/italojs), [@ljharb](https://github.com/ljharb), [@MaoShizhong](https://github.com/MaoShizhong), [@aroyan](https://github.com/aroyan), [@Binilkks](https://github.com/Binilkks), [@danielgindi](https://github.com/danielgindi), [@papandreou](https://github.com/papandreou), [@jsoref](https://github.com/jsoref), [@bigbigDreamer](https://github.com/bigbigDreamer), [@broofa](https://github.com/broofa), [@CommanderRoot](https://github.com/CommanderRoot), [@andvea](https://github.com/andvea), [@juanarbol](https://github.com/juanarbol), [@agungjati](https://github.com/agungjati), [@alexandercerutti](https://github.com/alexandercerutti), [@pr4j3sh](https://github.com/pr4j3sh), [@hamirmahal](https://github.com/hamirmahal), [@slagiewka](https://github.com/slagiewka), [@Abdel-Monaam-Aouini](https://github.com/Abdel-Monaam-Aouini), [@sazk07](https://github.com/sazk07), [@bhavya3024](https://github.com/bhavya3024), [@joshbuker](https://github.com/joshbuker), [@almic](https://github.com/almic), [@FDrag0n](https://github.com/FDrag0n), [@Dmitry-Kondar](https://github.com/Dmitry-Kondar), [@attrid](https://github.com/attrid), [@kristof-low](https://github.com/kristof-low), [@gireeshpunathil](https://github.com/gireeshpunathil), [@UzairJ99](https://github.com/UzairJ99), [@choi2021](https://github.com/choi2021), [@hayden36](https://github.com/hayden36), [@joharkhan99](https://github.com/joharkhan99), [@peterh-capella](https://github.com/peterh-capella), [@johnburnett](https://github.com/johnburnett), [@nicolasgandrade](https://github.com/nicolasgandrade), [@axhuwastaken](https://github.com/axhuwastaken), [@abhijeetpandit7](https://github.com/abhijeetpandit7), [@peterdanwan](https://github.com/peterdanwan), [@rehmansheikh222](https://github.com/rehmansheikh222), [@corydalis10](https://github.com/corydalis10), [@mgsantos177](https://github.com/mgsantos177), [@wilyJ80](https://github.com/wilyJ80), [@LuiGeeDev](https://github.com/LuiGeeDev), [@juliogarciape](https://github.com/juliogarciape), [@aelmardhi](https://github.com/aelmardhi), [@Ahmed1monm](https://github.com/Ahmed1monm), [@erensarac](https://github.com/erensarac), [@tomasz13nocon](https://github.com/tomasz13nocon), [@tianbuyung](https://github.com/tianbuyung), [@GreyTearsDev](https://github.com/GreyTearsDev), [@aastha-cse](https://github.com/aastha-cse), [@krzysdz](https://github.com/krzysdz), [@Miguelrom](https://github.com/Miguelrom), [@bnoordhuis](https://github.com/bnoordhuis), [@MehfoozurRehman](https://github.com/MehfoozurRehman), [@EasonLin0716](https://github.com/EasonLin0716), [@grjan7](https://github.com/grjan7), [@mishrasur7](https://github.com/mishrasur7), [@gregfenton](https://github.com/gregfenton), [@zareefhasan](https://github.com/zareefhasan), [@Tejas150](https://github.com/Tejas150), [@jpricardo](https://github.com/jpricardo), [@nikeee](https://github.com/nikeee), [@dotnetCarpenter](https://github.com/dotnetCarpenter), [@engpetermwangi](https://github.com/engpetermwangi), [@msimerson](https://github.com/msimerson), [@fetsorn](https://github.com/fetsorn), [@manoharreddyporeddy](https://github.com/manoharreddyporeddy), [@lancatlin](https://github.com/lancatlin), [@mifi](https://github.com/mifi), [@meowingwhitey](https://github.com/meowingwhitey), [@sheplu](https://github.com/sheplu), [@krsriq](https://github.com/krsriq), [@ravibisht](https://github.com/ravibisht), [@wojtekmaj](https://github.com/wojtekmaj), [@aqeelat](https://github.com/aqeelat), [@melikhov-dev](https://github.com/melikhov-dev), [@alexstrat](https://github.com/alexstrat), [@isnifer](https://github.com/isnifer), [@TorstenDittmann](https://github.com/TorstenDittmann), [@Uzlopak](https://github.com/Uzlopak), [@gurgunday](https://github.com/gurgunday), [@kurtextrem](https://github.com/kurtextrem), [@hdtmccallie](https://github.com/hdtmccallie), [@proudparrot2](https://github.com/proudparrot2), [@bewinsnw](https://github.com/bewinsnw), [@jonboulle](https://github.com/jonboulle), [@alexander-akait](https://github.com/alexander-akait), [@alxndrsn](https://github.com/alxndrsn), [@DimitriPapadopoulos](https://github.com/DimitriPapadopoulos), [@greggman](https://github.com/greggman), [@jkbach](https://github.com/jkbach), [@julien-c](https://github.com/julien-c), [@risu729](https://github.com/risu729), [@JohnSimumatik](https://github.com/JohnSimumatik), [@dhouck](https://github.com/dhouck), [@pedro-php](https://github.com/pedro-php), [@aminerol](https://github.com/aminerol), [@robertsky](https://github.com/robertsky), [@ipetrouchtchak-fi](https://github.com/ipetrouchtchak-fi), [@tinhochu](https://github.com/tinhochu), [@Lord-Kamina](https://github.com/Lord-Kamina), [@joshkel](https://github.com/joshkel), [@raiandexter0607](https://github.com/raiandexter0607), [@NateEag](https://github.com/NateEag), [@rmhaiderali](https://github.com/rmhaiderali), [@ljeda](https://github.com/ljeda)
diff --git a/_posts/2025-05-16-express-cleanup-legacy-packages.md b/_posts/2025-05-16-express-cleanup-legacy-packages.md
new file mode 100644
index 0000000000..eee24e3bb1
--- /dev/null
+++ b/_posts/2025-05-16-express-cleanup-legacy-packages.md
@@ -0,0 +1,48 @@
+---
+title: "Spring Cleaning in Express.js: Deprecations and the Path Ahead"
+tags: news
+authors:
+ - name: Express Technical Committee
+ github: expressjs
+description: As part of a broader effort to modernize and streamline Express.js, we’ve deprecated several outdated packages including csurf, connect-multiparty, and path-match. Learn why we made these changes and what it means for the future of the framework.
+---
+
+As Express.js continues to power web applications across the world, it's important that we maintain a clean, reliable, and modern codebase. In that spirit, we've done a bit of spring cleaning.
+
+Over the past few weeks, we've evaluated legacy packages within the Express.js ecosystem — some of which have become outdated, unmaintained, or misaligned with modern best practices. As a result, we’ve officially deprecated several of them.
+
+## 🚨 Packages Deprecated
+
+Here are the key packages we’ve deprecated:
+
+- [`csurf`](https://www.npmjs.com/package/csurf): A CSRF middleware that’s long been difficult to maintain and is better handled today through frameworks or custom implementations that align with your architecture.
+- [`connect-multiparty`](https://www.npmjs.com/package/connect-multiparty): A multipart form-data parser that relies on deprecated libraries and hasn’t aged well.
+- [`path-match`](https://www.npmjs.com/package/path-match): A route-matching utility that has been superseded by more modern and maintained alternatives.
+
+Each of these packages was originally created to solve real problems—but time has moved on, and the ecosystem has evolved.
+
+## 🤔 Why This Matters
+
+Maintaining deprecated or inactive dependencies introduces technical debt and security risk. By formally deprecating these packages, we:
+
+- Encourage developers to adopt better-maintained and more secure solutions.
+- Reduce confusion around which tools are actively supported by Express.
+- Focus our efforts on modernizing the core and surrounding ecosystem.
+
+## 🗂️ What You Should Do
+
+If your application depends on any of these packages, now is a great time to look for alternatives. For instance:
+
+- Consider finding a modern CSRF protection strategy on [npm](https://www.npmjs.com/search?q=csurf) that aligns with your specific needs.
+- Use up-to-date multipart parsers like [`multer`](https://www.npmjs.com/package/multer).
+- Replace path-match logic with standard [`path-to-regexp`](https://www.npmjs.com/package/path-to-regexp).
+
+## 📘 What's Next
+
+We're not stopping here. This cleanup is part of a broader effort to streamline Express.js, prepare for the future, and clarify what is and isn’t officially supported.
+
+👉 A full discussion of these changes can be found [expressjs/discussions#134](https://github.com/expressjs/discussions/issues/134).
+
+📢 Stay tuned—we'll continue to post updates and insights as we modernize the Express ecosystem.
+
+💚Thanks to the community for your continued trust and support.
diff --git a/_posts/2025-05-19-security-releases.md b/_posts/2025-05-19-security-releases.md
new file mode 100644
index 0000000000..bfab761a5b
--- /dev/null
+++ b/_posts/2025-05-19-security-releases.md
@@ -0,0 +1,51 @@
+---
+title: May 2025 Security Releases
+description: Security release for Multer has been published. We recommend that all users upgrade as soon as possible.
+tags: security vulnerabilities
+authors:
+ - name: Ulises Gascón
+ github: UlisesGascon
+---
+
+The Express team has released a new major version of [Multer](https://www.npmjs.com/package/multer) addressing two high-severity security vulnerabilities. This update improves the reliability and security of handling file uploads in Express applications.
+
+{% include admonitions/warning.html
+content="We strongly recommend that you upgrade to Multer v2.0.0 or later as soon as possible."
+%}
+
+The following vulnerabilities have been addressed:
+
+- [High severity vulnerability CVE-2025-47935 in Multer middleware](#high-severity-vulnerability-cve-2025-47935-in-multer-middleware)
+- [High severity vulnerability CVE-2025-47944 in Multer middleware](#high-severity-vulnerability-cve-2025-47944-in-multer-middleware)
+
+## High severity vulnerability CVE-2025-47935 in Multer middleware
+
+**[Multer](https://www.npmjs.com/package/multer) versions `<2.0.0` are vulnerable to denial of service due to a memory leak caused by improper stream handling.**
+
+When the HTTP request stream emits an error, the internal `busboy` stream is not closed, violating Node.js stream safety guidance.
+
+This leads to unclosed streams accumulating over time, consuming memory and file descriptors. Under sustained or repeated failure conditions, this can result in denial of service, requiring manual server restarts to recover. All users of Multer handling file uploads are potentially impacted.
+
+**Affected versions**: `<2.0.0`
+**Patched version**: `>=2.0.0`
+
+For more details, see [GHSA-44fp-w29j-9vj5](https://github.com/expressjs/multer/security/advisories/GHSA-44fp-w29j-9vj5).
+
+## High severity vulnerability CVE-2025-47944 in Multer middleware
+
+**[Multer](https://www.npmjs.com/package/multer) versions `>=1.4.4-lts.1` and `<2.0.0` are vulnerable to a denial of service via a malformed multipart request.**
+
+A specially crafted request can cause an unhandled exception inside Multer, resulting in a crash of the server process.
+
+**Affected versions**: `>=1.4.4-lts.1` and `<2.0.0`
+**Patched version**: `>=2.0.0`
+
+For more details, see [GHSA-4pg4-qvpc-4q3h](https://github.com/expressjs/multer/security/advisories/GHSA-4pg4-qvpc-4q3h).
+
+---
+
+**Multer v2.0.0** also introduces a breaking change:
+
+- The minimum supported Node.js version is now **10.16.0**.
+
+We recommend upgrading to the latest version of Multer immediately to secure your applications.
diff --git a/_posts/2025-06-05-vulnerability-reporting-process-overhaul.md b/_posts/2025-06-05-vulnerability-reporting-process-overhaul.md
new file mode 100644
index 0000000000..28f654a598
--- /dev/null
+++ b/_posts/2025-06-05-vulnerability-reporting-process-overhaul.md
@@ -0,0 +1,86 @@
+---
+title: How Express.js Rebuilt Its Vulnerability Reporting Process
+description: Express.js has overhauled its vulnerability reporting workflow with a unified process, consolidated documentation, and GitHub Security Advisories enabled across all repositories.
+tags: security vulnerabilities process governance
+authors:
+ - name: Ulises Gascón
+ github: UlisesGascon
+---
+
+
+The Express.js project has completed a major milestone in its ongoing commitment to security: the implementation of a formal, centralized vulnerability reporting and response process.
+
+Until recently, security reports were typically handled over email — an approach that worked in the early days but no longer scaled with the growing complexity and user base of Express. This informal system introduced potential delays, inconsistent handling, and increased the risk of issues being missed or misunderstood.
+
+Thanks to support from the [Sovereign Tech Fund](https://sovereign.tech), the Express.js Security Working Group has now completed a ground-up overhaul of how we manage vulnerability reports.
+
+
+## 🛠️ Key Improvements
+
+### Formalized Vulnerability Reporting Workflow
+
+A comprehensive runbook and process flow have been created to guide maintainers through each step of triaging, confirming, and addressing reported security issues.
+- [View the documentation](https://github.com/expressjs/security-wg/blob/main/docs/handle_security_reports.md)
+- [Security Report Handling Flowchart](https://github.com/expressjs/security-wg/blob/main/docs/handle_security_reports.md#security-report-handling-flowchart)
+
+### Unified Security Policy Across Repositories
+
+All Express.js repositories now share a single, unified `SECURITY.md` policy to ensure consistency and remove confusion for reporters and maintainers alike.
+
+- [View the unified Security Policy](https://github.com/expressjs/.github/blob/master/SECURITY.md)
+
+### GitHub Security Advisories Enabled
+
+Security Advisories are now enabled across all Express.js repositories, allowing for secure, private vulnerability reporting through GitHub’s built-in system.
+
+- [How to report a security bug using GitHub Security Advisory](https://github.com/expressjs/.github/blob/master/SECURITY.md#reporting-security-bugs-via-github-security-advisory-preferred)
+
+### Clear Maintainer Responsibilities
+
+Expectations around ownership and response timelines have been clarified and published to reduce ambiguity and improve responsiveness.
+
+> A [Security triage team member](https://github.com/expressjs/security-wg#security-triage-team) or [the repo captain](https://github.com/expressjs/express/blob/master/Contributing.md#active-projects-and-captains) will acknowledge your report as soon as possible.
+>
+> After the initial reply to your report, the security team will
+endeavor to keep you informed of the progress towards a fix and full
+announcement, and may ask for additional information or guidance.
+>
+> _[Security Policy](https://github.com/expressjs/.github/blob/master/SECURITY.md)_
+
+
+## 🛡️ Express is Now Covered Under the OpenJS Foundation CNA
+
+As of June 2025, the [OpenJS Foundation](https://openjsf.org/) is officially a [CVE Numbering Authority (CNA)](https://openjsf.org/blog/openjs-foundation-cna), empowered to assign CVE identifiers for security vulnerabilities across its hosted projects—including Express.
+
+What this means for the community:
+
+- Security vulnerabilities in Express can now receive official CVE IDs through OpenJS, improving transparency and coordination.
+- The foundation provides support and tooling to streamline the vulnerability disclosure process, particularly for maintainers and security researchers.
+- For critical issues, the CNA helps ensure that disclosures follow best practices and are recorded in global vulnerability databases.
+
+
+Please refer to [Express’s Security Policy](https://github.com/expressjs/express/security/policy) for the correct disclosure process. If needed, escalation routes through the OpenJS CNA are now available.
+
+This advancement is part of a broader effort to strengthen the security of JavaScript’s open-source ecosystem—especially for widely used, community-driven projects like Express.
+
+Learn more:
+- [OpenJS Foundation is now a CNA – Official Blog Post](https://openjsf.org/blog/openjs-foundation-cna)
+- [Socket.dev Coverage: OpenJS Foundation Becomes a CNA](https://socket.dev/blog/openjs-foundation-is-now-a-cna)
+
+## 👀 Coming Soon: Bug Bounty Program in the Works
+
+To further enhance the security of our ecosystem and encourage responsible vulnerability disclosure, the Express.js team has begun exploring participation in a community-focused bug bounty initiative—powered by the [Sovereign Tech Resilience program](https://www.sovereign.tech/programs/bug-resilience).
+
+This collaboration aims to:
+
+- Reward contributors for discovering and responsibly reporting security issues
+- Improve our ability to address vulnerabilities quickly and transparently
+- Strengthen long-term resilience for users and maintainers alike
+
+Join the conversation and share your thoughts in [expressjs/discussions#345 – Bug Bounty Proposal](https://github.com/expressjs/discussions/issues/345)
+
+## Why This Matters
+
+Security is a shared responsibility — and one that must evolve as the project grows. With these updates, Express.js has laid the foundation for a more reliable, scalable, and transparent vulnerability response system.
+
+We’re grateful to the [OpenJS Foundation](https://openjsf.org/) and the [Sovereign Tech Fund](https://www.sovereign.tech/) for their support and are excited to share this progress with the broader community.
diff --git a/_posts/2025-07-18-security-releases.md b/_posts/2025-07-18-security-releases.md
new file mode 100644
index 0000000000..e6e4d86033
--- /dev/null
+++ b/_posts/2025-07-18-security-releases.md
@@ -0,0 +1,29 @@
+---
+title: June 2025 Security Releases
+description: Security update for Multer released. All users are encouraged to upgrade.
+tags: security vulnerabilities
+authors:
+ - name: Ulises Gascón
+ github: UlisesGascon
+---
+
+The Express team has released a new patch version of [Multer](https://www.npmjs.com/package/multer), addressing a high-severity vulnerability that could lead to a Denial of Service (DoS) attack.
+
+{% include admonitions/warning.html
+content="We strongly recommend that all users upgrade to Multer v2.0.1 or later immediately."
+%}
+
+This release addresses the following vulnerability:
+
+### High severity vulnerability CVE-2025-48997 in Multer middleware
+
+**[Multer](https://www.npmjs.com/package/multer) versions `>=1.4.4-lts.1` and `<2.0.1` are vulnerable to a Denial of Service (DoS) attack.**
+
+An attacker can trigger this vulnerability by sending an upload request with an empty string as the field name. This malformed request causes an unhandled exception, leading to a crash of the server process.
+
+**Affected versions**: `>=1.4.4-lts.1` and `<2.0.1`
+**Patched version**: `2.0.1`
+
+For more details, see [GHSA-g5hg-p3ph-g8qg](https://github.com/expressjs/multer/security/advisories/GHSA-g5hg-p3ph-g8qg).
+
+
diff --git a/_posts/2025-07-31-security-releases.md b/_posts/2025-07-31-security-releases.md
new file mode 100644
index 0000000000..6582649097
--- /dev/null
+++ b/_posts/2025-07-31-security-releases.md
@@ -0,0 +1,46 @@
+---
+title: July 2025 Security Releases
+description: Security releases for Multer and On-headers has been published. We recommend that all users upgrade as soon as possible.
+tags: security vulnerabilities
+authors:
+ - name: Ulises Gascón
+ github: UlisesGascon
+---
+
+The Express team has released a new patch version of [Multer](https://www.npmjs.com/package/multer) addressing a high-severity security vulnerability, and a new minor version of [on-headers](https://www.npmjs.com/package/on-headers) addressing a low-severity security vulnerability.
+
+
+{% include admonitions/warning.html
+content="We recommend upgrading to the latest version of Multer and On-headers immediately to secure your applications."
+%}
+
+The following vulnerabilities have been addressed:
+
+- [High severity vulnerability CVE-2025-7338 in Multer middleware](#high-severity-vulnerability-cve-2025-7338-in-multer-middleware)
+- [Low severity vulnerability CVE-2025-7339 in On-header middleware](#low-severity-vulnerability-cve-2025-7339-in-on-header-middleware)
+
+## High severity vulnerability CVE-2025-7338 in Multer middleware
+
+**[Multer](https://www.npmjs.com/package/multer) versions `>=1.4.4-lts.1` and `<2.0.2` are vulnerable to denial of service via unhandled exception from malformed request.**
+
+This request causes an unhandled exception, leading to a crash of the process.
+
+**Affected versions**: `>=1.4.4-lts.1, <2.0.2`
+**Patched version**: `2.0.2`
+
+For more details, see [GHSA-fjgf-rc76-4x9p](https://github.com/expressjs/multer/security/advisories/GHSA-fjgf-rc76-4x9p).
+
+## Low severity vulnerability CVE-2025-7339 in On-header middleware
+
+**[On-headers](https://www.npmjs.com/package/on-headers) versions `<1.1.0` is vulnerable to http response header manipulation**
+
+A bug in on-headers versions `<1.1.0` may result in response headers being inadvertently modified when an array is passed to `response.writeHead()`
+
+**Affected versions**: `<1.1.0`
+**Patched version**: `1.1.0`
+
+For more details, see [GHSA-76c9-3jph-rj3q](https://github.com/jshttp/on-headers/security/advisories/GHSA-76c9-3jph-rj3q).
+
+---
+
+We recommend upgrading to the latest version of Multer and On-headers immediately to secure your applications.
diff --git a/crowdin.yml b/crowdin.yml
new file mode 100644
index 0000000000..9d7061f080
--- /dev/null
+++ b/crowdin.yml
@@ -0,0 +1,13 @@
+files:
+ - source: /en/**/*.*
+ ignore:
+ - /en/blog/**/*.*
+ translation: /%two_letters_code%/**/%original_file_name%
+ - source: /_data/en/**/*.*
+ translation: /_data/%two_letters_code%/**/%original_file_name%
+ - source: /index.md
+ translation: /%two_letters_code%/index.md
+preserve_hierarchy: true
+project_id_env: CROWDIN_PROJECT_ID
+base_url: 'https://express.api.crowdin.com'
+api_token_env: CROWDIN_PERSONAL_TOKEN
diff --git a/css/de.css b/css/de.css
deleted file mode 100644
index fd7af0c21a..0000000000
--- a/css/de.css
+++ /dev/null
@@ -1,18 +0,0 @@
-/*
- Copyright (c) 2016 StrongLoop, IBM, and Express Contributors
- License: MIT
-*/
-/* For image callouts in writing-middleware.md */
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 135px;}
-
-#callout5 {top: 150px;}
-
-#callout6 {top: 160px;}
-
diff --git a/css/dropit.css b/css/dropit.css
deleted file mode 100644
index 2cde3fc6a4..0000000000
--- a/css/dropit.css
+++ /dev/null
@@ -1,34 +0,0 @@
-/*
- * Dropit v1.1.0
- * http://dev7studios.com/dropit
- *
- * Copyright 2012, Dev7studios
- * Free to use and abuse under the MIT license.
- * http://www.opensource.org/licenses/mit-license.php
- */
-
-/* These styles assume you are using ul and li */
-.dropit {
- list-style: none;
- padding: 0;
- margin: 0;
-}
-
-.dropit .dropit-trigger {
- position: relative;
- margin-bottom: 6px;
-}
-
-.dropit .dropit-submenu {
- position: absolute;
- top: 100%;
- left: 0; /* dropdown left or right */
- z-index: 1000;
- display: none;
- min-width: 215px;
- list-style: none;
- padding: 0;
- margin: 0;
-}
-
-.dropit .dropit-open .dropit-submenu { display: block; }
diff --git a/css/en.css b/css/en.css
deleted file mode 100644
index 1b920cecdf..0000000000
--- a/css/en.css
+++ /dev/null
@@ -1,17 +0,0 @@
-/*
- Copyright (c) 2016 StrongLoop, IBM, and Express Contributors
- License: MIT
-*/
-/* For image callouts in writing-middleware.md */
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 145px;}
-
-#callout5 {top: 170px;}
-
-#callout6 {top: 195px;}
diff --git a/css/es.css b/css/es.css
deleted file mode 100644
index dfc300a126..0000000000
--- a/css/es.css
+++ /dev/null
@@ -1,17 +0,0 @@
-/*
- Copyright (c) 2016 StrongLoop, IBM, and Express Contributors
- License: MIT
-*/
-/* For image callouts in writing-middleware.md */
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 140px;}
-
-#callout5 {top: 150px;}
-
-#callout6 {top: 160px;}
diff --git a/css/font-awesome.min.css b/css/font-awesome.min.css
deleted file mode 100644
index ec53d4d6d5..0000000000
--- a/css/font-awesome.min.css
+++ /dev/null
@@ -1,4 +0,0 @@
-/*!
- * Font Awesome 4.2.0 by @davegandy - http://fontawesome.io - @fontawesome
- * License - http://fontawesome.io/license (Font: SIL OFL 1.1, CSS: MIT License)
- */@font-face{font-family:'FontAwesome';src:url('../fonts/fontawesome-webfont.eot?v=4.2.0');src:url('../fonts/fontawesome-webfont.eot?#iefix&v=4.2.0') format('embedded-opentype'),url('../fonts/fontawesome-webfont.woff?v=4.2.0') format('woff'),url('../fonts/fontawesome-webfont.ttf?v=4.2.0') format('truetype'),url('../fonts/fontawesome-webfont.svg?v=4.2.0#fontawesomeregular') format('svg');font-weight:normal;font-style:normal}.fa{display:inline-block;font:normal normal normal 14px/1 FontAwesome;font-size:inherit;text-rendering:auto;-webkit-font-smoothing:antialiased;-moz-osx-font-smoothing:grayscale}.fa-lg{font-size:1.33333333em;line-height:.75em;vertical-align:-15%}.fa-2x{font-size:2em}.fa-3x{font-size:3em}.fa-4x{font-size:4em}.fa-5x{font-size:5em}.fa-fw{width:1.28571429em;text-align:center}.fa-ul{padding-left:0;margin-left:2.14285714em;list-style-type:none}.fa-ul>li{position:relative}.fa-li{position:absolute;left:-2.14285714em;width:2.14285714em;top:.14285714em;text-align:center}.fa-li.fa-lg{left:-1.85714286em}.fa-border{padding:.2em .25em .15em;border:solid .08em #eee;border-radius:.1em}.pull-right{float:right}.pull-left{float:left}.fa.pull-left{margin-right:.3em}.fa.pull-right{margin-left:.3em}.fa-spin{-webkit-animation:fa-spin 2s infinite linear;animation:fa-spin 2s infinite linear}@-webkit-keyframes fa-spin{0%{-webkit-transform:rotate(0deg);transform:rotate(0deg)}100%{-webkit-transform:rotate(359deg);transform:rotate(359deg)}}@keyframes fa-spin{0%{-webkit-transform:rotate(0deg);transform:rotate(0deg)}100%{-webkit-transform:rotate(359deg);transform:rotate(359deg)}}.fa-rotate-90{filter:progid:DXImageTransform.Microsoft.BasicImage(rotation=1);-webkit-transform:rotate(90deg);-ms-transform:rotate(90deg);transform:rotate(90deg)}.fa-rotate-180{filter:progid:DXImageTransform.Microsoft.BasicImage(rotation=2);-webkit-transform:rotate(180deg);-ms-transform:rotate(180deg);transform:rotate(180deg)}.fa-rotate-270{filter:progid:DXImageTransform.Microsoft.BasicImage(rotation=3);-webkit-transform:rotate(270deg);-ms-transform:rotate(270deg);transform:rotate(270deg)}.fa-flip-horizontal{filter:progid:DXImageTransform.Microsoft.BasicImage(rotation=0, mirror=1);-webkit-transform:scale(-1, 1);-ms-transform:scale(-1, 1);transform:scale(-1, 1)}.fa-flip-vertical{filter:progid:DXImageTransform.Microsoft.BasicImage(rotation=2, mirror=1);-webkit-transform:scale(1, -1);-ms-transform:scale(1, -1);transform:scale(1, -1)}:root .fa-rotate-90,:root .fa-rotate-180,:root .fa-rotate-270,:root .fa-flip-horizontal,:root .fa-flip-vertical{filter:none}.fa-stack{position:relative;display:inline-block;width:2em;height:2em;line-height:2em;vertical-align:middle}.fa-stack-1x,.fa-stack-2x{position:absolute;left:0;width:100%;text-align:center}.fa-stack-1x{line-height:inherit}.fa-stack-2x{font-size:2em}.fa-inverse{color:#fff}.fa-glass:before{content:"\f000"}.fa-music:before{content:"\f001"}.fa-search:before{content:"\f002"}.fa-envelope-o:before{content:"\f003"}.fa-heart:before{content:"\f004"}.fa-star:before{content:"\f005"}.fa-star-o:before{content:"\f006"}.fa-user:before{content:"\f007"}.fa-film:before{content:"\f008"}.fa-th-large:before{content:"\f009"}.fa-th:before{content:"\f00a"}.fa-th-list:before{content:"\f00b"}.fa-check:before{content:"\f00c"}.fa-remove:before,.fa-close:before,.fa-times:before{content:"\f00d"}.fa-search-plus:before{content:"\f00e"}.fa-search-minus:before{content:"\f010"}.fa-power-off:before{content:"\f011"}.fa-signal:before{content:"\f012"}.fa-gear:before,.fa-cog:before{content:"\f013"}.fa-trash-o:before{content:"\f014"}.fa-home:before{content:"\f015"}.fa-file-o:before{content:"\f016"}.fa-clock-o:before{content:"\f017"}.fa-road:before{content:"\f018"}.fa-download:before{content:"\f019"}.fa-arrow-circle-o-down:before{content:"\f01a"}.fa-arrow-circle-o-up:before{content:"\f01b"}.fa-inbox:before{content:"\f01c"}.fa-play-circle-o:before{content:"\f01d"}.fa-rotate-right:before,.fa-repeat:before{content:"\f01e"}.fa-refresh:before{content:"\f021"}.fa-list-alt:before{content:"\f022"}.fa-lock:before{content:"\f023"}.fa-flag:before{content:"\f024"}.fa-headphones:before{content:"\f025"}.fa-volume-off:before{content:"\f026"}.fa-volume-down:before{content:"\f027"}.fa-volume-up:before{content:"\f028"}.fa-qrcode:before{content:"\f029"}.fa-barcode:before{content:"\f02a"}.fa-tag:before{content:"\f02b"}.fa-tags:before{content:"\f02c"}.fa-book:before{content:"\f02d"}.fa-bookmark:before{content:"\f02e"}.fa-print:before{content:"\f02f"}.fa-camera:before{content:"\f030"}.fa-font:before{content:"\f031"}.fa-bold:before{content:"\f032"}.fa-italic:before{content:"\f033"}.fa-text-height:before{content:"\f034"}.fa-text-width:before{content:"\f035"}.fa-align-left:before{content:"\f036"}.fa-align-center:before{content:"\f037"}.fa-align-right:before{content:"\f038"}.fa-align-justify:before{content:"\f039"}.fa-list:before{content:"\f03a"}.fa-dedent:before,.fa-outdent:before{content:"\f03b"}.fa-indent:before{content:"\f03c"}.fa-video-camera:before{content:"\f03d"}.fa-photo:before,.fa-image:before,.fa-picture-o:before{content:"\f03e"}.fa-pencil:before{content:"\f040"}.fa-map-marker:before{content:"\f041"}.fa-adjust:before{content:"\f042"}.fa-tint:before{content:"\f043"}.fa-edit:before,.fa-pencil-square-o:before{content:"\f044"}.fa-share-square-o:before{content:"\f045"}.fa-check-square-o:before{content:"\f046"}.fa-arrows:before{content:"\f047"}.fa-step-backward:before{content:"\f048"}.fa-fast-backward:before{content:"\f049"}.fa-backward:before{content:"\f04a"}.fa-play:before{content:"\f04b"}.fa-pause:before{content:"\f04c"}.fa-stop:before{content:"\f04d"}.fa-forward:before{content:"\f04e"}.fa-fast-forward:before{content:"\f050"}.fa-step-forward:before{content:"\f051"}.fa-eject:before{content:"\f052"}.fa-chevron-left:before{content:"\f053"}.fa-chevron-right:before{content:"\f054"}.fa-plus-circle:before{content:"\f055"}.fa-minus-circle:before{content:"\f056"}.fa-times-circle:before{content:"\f057"}.fa-check-circle:before{content:"\f058"}.fa-question-circle:before{content:"\f059"}.fa-info-circle:before{content:"\f05a"}.fa-crosshairs:before{content:"\f05b"}.fa-times-circle-o:before{content:"\f05c"}.fa-check-circle-o:before{content:"\f05d"}.fa-ban:before{content:"\f05e"}.fa-arrow-left:before{content:"\f060"}.fa-arrow-right:before{content:"\f061"}.fa-arrow-up:before{content:"\f062"}.fa-arrow-down:before{content:"\f063"}.fa-mail-forward:before,.fa-share:before{content:"\f064"}.fa-expand:before{content:"\f065"}.fa-compress:before{content:"\f066"}.fa-plus:before{content:"\f067"}.fa-minus:before{content:"\f068"}.fa-asterisk:before{content:"\f069"}.fa-exclamation-circle:before{content:"\f06a"}.fa-gift:before{content:"\f06b"}.fa-leaf:before{content:"\f06c"}.fa-fire:before{content:"\f06d"}.fa-eye:before{content:"\f06e"}.fa-eye-slash:before{content:"\f070"}.fa-warning:before,.fa-exclamation-triangle:before{content:"\f071"}.fa-plane:before{content:"\f072"}.fa-calendar:before{content:"\f073"}.fa-random:before{content:"\f074"}.fa-comment:before{content:"\f075"}.fa-magnet:before{content:"\f076"}.fa-chevron-up:before{content:"\f077"}.fa-chevron-down:before{content:"\f078"}.fa-retweet:before{content:"\f079"}.fa-shopping-cart:before{content:"\f07a"}.fa-folder:before{content:"\f07b"}.fa-folder-open:before{content:"\f07c"}.fa-arrows-v:before{content:"\f07d"}.fa-arrows-h:before{content:"\f07e"}.fa-bar-chart-o:before,.fa-bar-chart:before{content:"\f080"}.fa-twitter-square:before{content:"\f081"}.fa-facebook-square:before{content:"\f082"}.fa-camera-retro:before{content:"\f083"}.fa-key:before{content:"\f084"}.fa-gears:before,.fa-cogs:before{content:"\f085"}.fa-comments:before{content:"\f086"}.fa-thumbs-o-up:before{content:"\f087"}.fa-thumbs-o-down:before{content:"\f088"}.fa-star-half:before{content:"\f089"}.fa-heart-o:before{content:"\f08a"}.fa-sign-out:before{content:"\f08b"}.fa-linkedin-square:before{content:"\f08c"}.fa-thumb-tack:before{content:"\f08d"}.fa-external-link:before{content:"\f08e"}.fa-sign-in:before{content:"\f090"}.fa-trophy:before{content:"\f091"}.fa-github-square:before{content:"\f092"}.fa-upload:before{content:"\f093"}.fa-lemon-o:before{content:"\f094"}.fa-phone:before{content:"\f095"}.fa-square-o:before{content:"\f096"}.fa-bookmark-o:before{content:"\f097"}.fa-phone-square:before{content:"\f098"}.fa-twitter:before{content:"\f099"}.fa-facebook:before{content:"\f09a"}.fa-github:before{content:"\f09b"}.fa-unlock:before{content:"\f09c"}.fa-credit-card:before{content:"\f09d"}.fa-rss:before{content:"\f09e"}.fa-hdd-o:before{content:"\f0a0"}.fa-bullhorn:before{content:"\f0a1"}.fa-bell:before{content:"\f0f3"}.fa-certificate:before{content:"\f0a3"}.fa-hand-o-right:before{content:"\f0a4"}.fa-hand-o-left:before{content:"\f0a5"}.fa-hand-o-up:before{content:"\f0a6"}.fa-hand-o-down:before{content:"\f0a7"}.fa-arrow-circle-left:before{content:"\f0a8"}.fa-arrow-circle-right:before{content:"\f0a9"}.fa-arrow-circle-up:before{content:"\f0aa"}.fa-arrow-circle-down:before{content:"\f0ab"}.fa-globe:before{content:"\f0ac"}.fa-wrench:before{content:"\f0ad"}.fa-tasks:before{content:"\f0ae"}.fa-filter:before{content:"\f0b0"}.fa-briefcase:before{content:"\f0b1"}.fa-arrows-alt:before{content:"\f0b2"}.fa-group:before,.fa-users:before{content:"\f0c0"}.fa-chain:before,.fa-link:before{content:"\f0c1"}.fa-cloud:before{content:"\f0c2"}.fa-flask:before{content:"\f0c3"}.fa-cut:before,.fa-scissors:before{content:"\f0c4"}.fa-copy:before,.fa-files-o:before{content:"\f0c5"}.fa-paperclip:before{content:"\f0c6"}.fa-save:before,.fa-floppy-o:before{content:"\f0c7"}.fa-square:before{content:"\f0c8"}.fa-navicon:before,.fa-reorder:before,.fa-bars:before{content:"\f0c9"}.fa-list-ul:before{content:"\f0ca"}.fa-list-ol:before{content:"\f0cb"}.fa-strikethrough:before{content:"\f0cc"}.fa-underline:before{content:"\f0cd"}.fa-table:before{content:"\f0ce"}.fa-magic:before{content:"\f0d0"}.fa-truck:before{content:"\f0d1"}.fa-pinterest:before{content:"\f0d2"}.fa-pinterest-square:before{content:"\f0d3"}.fa-google-plus-square:before{content:"\f0d4"}.fa-google-plus:before{content:"\f0d5"}.fa-money:before{content:"\f0d6"}.fa-caret-down:before{content:"\f0d7"}.fa-caret-up:before{content:"\f0d8"}.fa-caret-left:before{content:"\f0d9"}.fa-caret-right:before{content:"\f0da"}.fa-columns:before{content:"\f0db"}.fa-unsorted:before,.fa-sort:before{content:"\f0dc"}.fa-sort-down:before,.fa-sort-desc:before{content:"\f0dd"}.fa-sort-up:before,.fa-sort-asc:before{content:"\f0de"}.fa-envelope:before{content:"\f0e0"}.fa-linkedin:before{content:"\f0e1"}.fa-rotate-left:before,.fa-undo:before{content:"\f0e2"}.fa-legal:before,.fa-gavel:before{content:"\f0e3"}.fa-dashboard:before,.fa-tachometer:before{content:"\f0e4"}.fa-comment-o:before{content:"\f0e5"}.fa-comments-o:before{content:"\f0e6"}.fa-flash:before,.fa-bolt:before{content:"\f0e7"}.fa-sitemap:before{content:"\f0e8"}.fa-umbrella:before{content:"\f0e9"}.fa-paste:before,.fa-clipboard:before{content:"\f0ea"}.fa-lightbulb-o:before{content:"\f0eb"}.fa-exchange:before{content:"\f0ec"}.fa-cloud-download:before{content:"\f0ed"}.fa-cloud-upload:before{content:"\f0ee"}.fa-user-md:before{content:"\f0f0"}.fa-stethoscope:before{content:"\f0f1"}.fa-suitcase:before{content:"\f0f2"}.fa-bell-o:before{content:"\f0a2"}.fa-coffee:before{content:"\f0f4"}.fa-cutlery:before{content:"\f0f5"}.fa-file-text-o:before{content:"\f0f6"}.fa-building-o:before{content:"\f0f7"}.fa-hospital-o:before{content:"\f0f8"}.fa-ambulance:before{content:"\f0f9"}.fa-medkit:before{content:"\f0fa"}.fa-fighter-jet:before{content:"\f0fb"}.fa-beer:before{content:"\f0fc"}.fa-h-square:before{content:"\f0fd"}.fa-plus-square:before{content:"\f0fe"}.fa-angle-double-left:before{content:"\f100"}.fa-angle-double-right:before{content:"\f101"}.fa-angle-double-up:before{content:"\f102"}.fa-angle-double-down:before{content:"\f103"}.fa-angle-left:before{content:"\f104"}.fa-angle-right:before{content:"\f105"}.fa-angle-up:before{content:"\f106"}.fa-angle-down:before{content:"\f107"}.fa-desktop:before{content:"\f108"}.fa-laptop:before{content:"\f109"}.fa-tablet:before{content:"\f10a"}.fa-mobile-phone:before,.fa-mobile:before{content:"\f10b"}.fa-circle-o:before{content:"\f10c"}.fa-quote-left:before{content:"\f10d"}.fa-quote-right:before{content:"\f10e"}.fa-spinner:before{content:"\f110"}.fa-circle:before{content:"\f111"}.fa-mail-reply:before,.fa-reply:before{content:"\f112"}.fa-github-alt:before{content:"\f113"}.fa-folder-o:before{content:"\f114"}.fa-folder-open-o:before{content:"\f115"}.fa-smile-o:before{content:"\f118"}.fa-frown-o:before{content:"\f119"}.fa-meh-o:before{content:"\f11a"}.fa-gamepad:before{content:"\f11b"}.fa-keyboard-o:before{content:"\f11c"}.fa-flag-o:before{content:"\f11d"}.fa-flag-checkered:before{content:"\f11e"}.fa-terminal:before{content:"\f120"}.fa-code:before{content:"\f121"}.fa-mail-reply-all:before,.fa-reply-all:before{content:"\f122"}.fa-star-half-empty:before,.fa-star-half-full:before,.fa-star-half-o:before{content:"\f123"}.fa-location-arrow:before{content:"\f124"}.fa-crop:before{content:"\f125"}.fa-code-fork:before{content:"\f126"}.fa-unlink:before,.fa-chain-broken:before{content:"\f127"}.fa-question:before{content:"\f128"}.fa-info:before{content:"\f129"}.fa-exclamation:before{content:"\f12a"}.fa-superscript:before{content:"\f12b"}.fa-subscript:before{content:"\f12c"}.fa-eraser:before{content:"\f12d"}.fa-puzzle-piece:before{content:"\f12e"}.fa-microphone:before{content:"\f130"}.fa-microphone-slash:before{content:"\f131"}.fa-shield:before{content:"\f132"}.fa-calendar-o:before{content:"\f133"}.fa-fire-extinguisher:before{content:"\f134"}.fa-rocket:before{content:"\f135"}.fa-maxcdn:before{content:"\f136"}.fa-chevron-circle-left:before{content:"\f137"}.fa-chevron-circle-right:before{content:"\f138"}.fa-chevron-circle-up:before{content:"\f139"}.fa-chevron-circle-down:before{content:"\f13a"}.fa-html5:before{content:"\f13b"}.fa-css3:before{content:"\f13c"}.fa-anchor:before{content:"\f13d"}.fa-unlock-alt:before{content:"\f13e"}.fa-bullseye:before{content:"\f140"}.fa-ellipsis-h:before{content:"\f141"}.fa-ellipsis-v:before{content:"\f142"}.fa-rss-square:before{content:"\f143"}.fa-play-circle:before{content:"\f144"}.fa-ticket:before{content:"\f145"}.fa-minus-square:before{content:"\f146"}.fa-minus-square-o:before{content:"\f147"}.fa-level-up:before{content:"\f148"}.fa-level-down:before{content:"\f149"}.fa-check-square:before{content:"\f14a"}.fa-pencil-square:before{content:"\f14b"}.fa-external-link-square:before{content:"\f14c"}.fa-share-square:before{content:"\f14d"}.fa-compass:before{content:"\f14e"}.fa-toggle-down:before,.fa-caret-square-o-down:before{content:"\f150"}.fa-toggle-up:before,.fa-caret-square-o-up:before{content:"\f151"}.fa-toggle-right:before,.fa-caret-square-o-right:before{content:"\f152"}.fa-euro:before,.fa-eur:before{content:"\f153"}.fa-gbp:before{content:"\f154"}.fa-dollar:before,.fa-usd:before{content:"\f155"}.fa-rupee:before,.fa-inr:before{content:"\f156"}.fa-cny:before,.fa-rmb:before,.fa-yen:before,.fa-jpy:before{content:"\f157"}.fa-ruble:before,.fa-rouble:before,.fa-rub:before{content:"\f158"}.fa-won:before,.fa-krw:before{content:"\f159"}.fa-bitcoin:before,.fa-btc:before{content:"\f15a"}.fa-file:before{content:"\f15b"}.fa-file-text:before{content:"\f15c"}.fa-sort-alpha-asc:before{content:"\f15d"}.fa-sort-alpha-desc:before{content:"\f15e"}.fa-sort-amount-asc:before{content:"\f160"}.fa-sort-amount-desc:before{content:"\f161"}.fa-sort-numeric-asc:before{content:"\f162"}.fa-sort-numeric-desc:before{content:"\f163"}.fa-thumbs-up:before{content:"\f164"}.fa-thumbs-down:before{content:"\f165"}.fa-youtube-square:before{content:"\f166"}.fa-youtube:before{content:"\f167"}.fa-xing:before{content:"\f168"}.fa-xing-square:before{content:"\f169"}.fa-youtube-play:before{content:"\f16a"}.fa-dropbox:before{content:"\f16b"}.fa-stack-overflow:before{content:"\f16c"}.fa-instagram:before{content:"\f16d"}.fa-flickr:before{content:"\f16e"}.fa-adn:before{content:"\f170"}.fa-bitbucket:before{content:"\f171"}.fa-bitbucket-square:before{content:"\f172"}.fa-tumblr:before{content:"\f173"}.fa-tumblr-square:before{content:"\f174"}.fa-long-arrow-down:before{content:"\f175"}.fa-long-arrow-up:before{content:"\f176"}.fa-long-arrow-left:before{content:"\f177"}.fa-long-arrow-right:before{content:"\f178"}.fa-apple:before{content:"\f179"}.fa-windows:before{content:"\f17a"}.fa-android:before{content:"\f17b"}.fa-linux:before{content:"\f17c"}.fa-dribbble:before{content:"\f17d"}.fa-skype:before{content:"\f17e"}.fa-foursquare:before{content:"\f180"}.fa-trello:before{content:"\f181"}.fa-female:before{content:"\f182"}.fa-male:before{content:"\f183"}.fa-gittip:before{content:"\f184"}.fa-sun-o:before{content:"\f185"}.fa-moon-o:before{content:"\f186"}.fa-archive:before{content:"\f187"}.fa-bug:before{content:"\f188"}.fa-vk:before{content:"\f189"}.fa-weibo:before{content:"\f18a"}.fa-renren:before{content:"\f18b"}.fa-pagelines:before{content:"\f18c"}.fa-stack-exchange:before{content:"\f18d"}.fa-arrow-circle-o-right:before{content:"\f18e"}.fa-arrow-circle-o-left:before{content:"\f190"}.fa-toggle-left:before,.fa-caret-square-o-left:before{content:"\f191"}.fa-dot-circle-o:before{content:"\f192"}.fa-wheelchair:before{content:"\f193"}.fa-vimeo-square:before{content:"\f194"}.fa-turkish-lira:before,.fa-try:before{content:"\f195"}.fa-plus-square-o:before{content:"\f196"}.fa-space-shuttle:before{content:"\f197"}.fa-slack:before{content:"\f198"}.fa-envelope-square:before{content:"\f199"}.fa-wordpress:before{content:"\f19a"}.fa-openid:before{content:"\f19b"}.fa-institution:before,.fa-bank:before,.fa-university:before{content:"\f19c"}.fa-mortar-board:before,.fa-graduation-cap:before{content:"\f19d"}.fa-yahoo:before{content:"\f19e"}.fa-google:before{content:"\f1a0"}.fa-reddit:before{content:"\f1a1"}.fa-reddit-square:before{content:"\f1a2"}.fa-stumbleupon-circle:before{content:"\f1a3"}.fa-stumbleupon:before{content:"\f1a4"}.fa-delicious:before{content:"\f1a5"}.fa-digg:before{content:"\f1a6"}.fa-pied-piper:before{content:"\f1a7"}.fa-pied-piper-alt:before{content:"\f1a8"}.fa-drupal:before{content:"\f1a9"}.fa-joomla:before{content:"\f1aa"}.fa-language:before{content:"\f1ab"}.fa-fax:before{content:"\f1ac"}.fa-building:before{content:"\f1ad"}.fa-child:before{content:"\f1ae"}.fa-paw:before{content:"\f1b0"}.fa-spoon:before{content:"\f1b1"}.fa-cube:before{content:"\f1b2"}.fa-cubes:before{content:"\f1b3"}.fa-behance:before{content:"\f1b4"}.fa-behance-square:before{content:"\f1b5"}.fa-steam:before{content:"\f1b6"}.fa-steam-square:before{content:"\f1b7"}.fa-recycle:before{content:"\f1b8"}.fa-automobile:before,.fa-car:before{content:"\f1b9"}.fa-cab:before,.fa-taxi:before{content:"\f1ba"}.fa-tree:before{content:"\f1bb"}.fa-spotify:before{content:"\f1bc"}.fa-deviantart:before{content:"\f1bd"}.fa-soundcloud:before{content:"\f1be"}.fa-database:before{content:"\f1c0"}.fa-file-pdf-o:before{content:"\f1c1"}.fa-file-word-o:before{content:"\f1c2"}.fa-file-excel-o:before{content:"\f1c3"}.fa-file-powerpoint-o:before{content:"\f1c4"}.fa-file-photo-o:before,.fa-file-picture-o:before,.fa-file-image-o:before{content:"\f1c5"}.fa-file-zip-o:before,.fa-file-archive-o:before{content:"\f1c6"}.fa-file-sound-o:before,.fa-file-audio-o:before{content:"\f1c7"}.fa-file-movie-o:before,.fa-file-video-o:before{content:"\f1c8"}.fa-file-code-o:before{content:"\f1c9"}.fa-vine:before{content:"\f1ca"}.fa-codepen:before{content:"\f1cb"}.fa-jsfiddle:before{content:"\f1cc"}.fa-life-bouy:before,.fa-life-buoy:before,.fa-life-saver:before,.fa-support:before,.fa-life-ring:before{content:"\f1cd"}.fa-circle-o-notch:before{content:"\f1ce"}.fa-ra:before,.fa-rebel:before{content:"\f1d0"}.fa-ge:before,.fa-empire:before{content:"\f1d1"}.fa-git-square:before{content:"\f1d2"}.fa-git:before{content:"\f1d3"}.fa-hacker-news:before{content:"\f1d4"}.fa-tencent-weibo:before{content:"\f1d5"}.fa-qq:before{content:"\f1d6"}.fa-wechat:before,.fa-weixin:before{content:"\f1d7"}.fa-send:before,.fa-paper-plane:before{content:"\f1d8"}.fa-send-o:before,.fa-paper-plane-o:before{content:"\f1d9"}.fa-history:before{content:"\f1da"}.fa-circle-thin:before{content:"\f1db"}.fa-header:before{content:"\f1dc"}.fa-paragraph:before{content:"\f1dd"}.fa-sliders:before{content:"\f1de"}.fa-share-alt:before{content:"\f1e0"}.fa-share-alt-square:before{content:"\f1e1"}.fa-bomb:before{content:"\f1e2"}.fa-soccer-ball-o:before,.fa-futbol-o:before{content:"\f1e3"}.fa-tty:before{content:"\f1e4"}.fa-binoculars:before{content:"\f1e5"}.fa-plug:before{content:"\f1e6"}.fa-slideshare:before{content:"\f1e7"}.fa-twitch:before{content:"\f1e8"}.fa-yelp:before{content:"\f1e9"}.fa-newspaper-o:before{content:"\f1ea"}.fa-wifi:before{content:"\f1eb"}.fa-calculator:before{content:"\f1ec"}.fa-paypal:before{content:"\f1ed"}.fa-google-wallet:before{content:"\f1ee"}.fa-cc-visa:before{content:"\f1f0"}.fa-cc-mastercard:before{content:"\f1f1"}.fa-cc-discover:before{content:"\f1f2"}.fa-cc-amex:before{content:"\f1f3"}.fa-cc-paypal:before{content:"\f1f4"}.fa-cc-stripe:before{content:"\f1f5"}.fa-bell-slash:before{content:"\f1f6"}.fa-bell-slash-o:before{content:"\f1f7"}.fa-trash:before{content:"\f1f8"}.fa-copyright:before{content:"\f1f9"}.fa-at:before{content:"\f1fa"}.fa-eyedropper:before{content:"\f1fb"}.fa-paint-brush:before{content:"\f1fc"}.fa-birthday-cake:before{content:"\f1fd"}.fa-area-chart:before{content:"\f1fe"}.fa-pie-chart:before{content:"\f200"}.fa-line-chart:before{content:"\f201"}.fa-lastfm:before{content:"\f202"}.fa-lastfm-square:before{content:"\f203"}.fa-toggle-off:before{content:"\f204"}.fa-toggle-on:before{content:"\f205"}.fa-bicycle:before{content:"\f206"}.fa-bus:before{content:"\f207"}.fa-ioxhost:before{content:"\f208"}.fa-angellist:before{content:"\f209"}.fa-cc:before{content:"\f20a"}.fa-shekel:before,.fa-sheqel:before,.fa-ils:before{content:"\f20b"}.fa-meanpath:before{content:"\f20c"}
\ No newline at end of file
diff --git a/css/fr.css b/css/fr.css
deleted file mode 100644
index 5538ccfee6..0000000000
--- a/css/fr.css
+++ /dev/null
@@ -1,17 +0,0 @@
-/*
- Copyright (c) 2016 StrongLoop, IBM, and Express Contributors
- License: MIT
-*/
-/* For image callouts in writing-middleware.md */
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 145px;}
-
-#callout5 {top: 165px;}
-
-#callout6 {top: 185px;}
diff --git a/css/it.css b/css/it.css
deleted file mode 100644
index 750fecaef0..0000000000
--- a/css/it.css
+++ /dev/null
@@ -1,17 +0,0 @@
-/*
- Copyright (c) 2016 StrongLoop, IBM, and Express Contributors
- License: MIT
-*/
-/* For image callouts in writing-middleware.md */
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 145px;}
-
-#callout5 {top: 150px;}
-
-#callout6 {top: 160px;}
diff --git a/css/ja.css b/css/ja.css
deleted file mode 100644
index b4b5f80056..0000000000
--- a/css/ja.css
+++ /dev/null
@@ -1,19 +0,0 @@
-/*
- Copyright (c) 2016 StrongLoop, IBM, and Express Contributors
- License: MIT
-*/
-/* For image callouts in writing-middleware.md */
-
-.callout {position: relative;}
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 145px;}
-
-#callout5 {top: 165px;}
-
-#callout6 {top: 185px;}
diff --git a/css/ko.css b/css/ko.css
deleted file mode 100644
index b4b5f80056..0000000000
--- a/css/ko.css
+++ /dev/null
@@ -1,19 +0,0 @@
-/*
- Copyright (c) 2016 StrongLoop, IBM, and Express Contributors
- License: MIT
-*/
-/* For image callouts in writing-middleware.md */
-
-.callout {position: relative;}
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 145px;}
-
-#callout5 {top: 165px;}
-
-#callout6 {top: 185px;}
diff --git a/css/langs/de.css b/css/langs/de.css
new file mode 100644
index 0000000000..df6795b5a2
--- /dev/null
+++ b/css/langs/de.css
@@ -0,0 +1,14 @@
+/* For image callouts in writing-middleware.md */
+
+#callout1 {top: 40px; }
+
+#callout2 {top: 60px;}
+
+#callout3 {top: 75px;}
+
+#callout4 {top: 135px;}
+
+#callout5 {top: 150px;}
+
+#callout6 {top: 160px;}
+
diff --git a/css/langs/en.css b/css/langs/en.css
new file mode 100644
index 0000000000..8f2e5ac2dd
--- /dev/null
+++ b/css/langs/en.css
@@ -0,0 +1,13 @@
+/* For image callouts in writing-middleware.md */
+
+#callout1 {top: 40px; }
+
+#callout2 {top: 60px;}
+
+#callout3 {top: 75px;}
+
+#callout4 {top: 145px;}
+
+#callout5 {top: 170px;}
+
+#callout6 {top: 195px;}
diff --git a/css/langs/es.css b/css/langs/es.css
new file mode 100644
index 0000000000..dd8a578f8e
--- /dev/null
+++ b/css/langs/es.css
@@ -0,0 +1,13 @@
+/* For image callouts in writing-middleware.md */
+
+#callout1 {top: 40px; }
+
+#callout2 {top: 60px;}
+
+#callout3 {top: 75px;}
+
+#callout4 {top: 140px;}
+
+#callout5 {top: 150px;}
+
+#callout6 {top: 160px;}
diff --git a/css/langs/fr.css b/css/langs/fr.css
new file mode 100644
index 0000000000..1c9938c3f7
--- /dev/null
+++ b/css/langs/fr.css
@@ -0,0 +1,13 @@
+/* For image callouts in writing-middleware.md */
+
+#callout1 {top: 40px; }
+
+#callout2 {top: 60px;}
+
+#callout3 {top: 75px;}
+
+#callout4 {top: 145px;}
+
+#callout5 {top: 165px;}
+
+#callout6 {top: 185px;}
diff --git a/css/langs/it.css b/css/langs/it.css
new file mode 100644
index 0000000000..6b0bbc10b8
--- /dev/null
+++ b/css/langs/it.css
@@ -0,0 +1,13 @@
+/* For image callouts in writing-middleware.md */
+
+#callout1 {top: 40px; }
+
+#callout2 {top: 60px;}
+
+#callout3 {top: 75px;}
+
+#callout4 {top: 145px;}
+
+#callout5 {top: 150px;}
+
+#callout6 {top: 160px;}
diff --git a/css/langs/ja.css b/css/langs/ja.css
new file mode 100644
index 0000000000..1c162162cd
--- /dev/null
+++ b/css/langs/ja.css
@@ -0,0 +1,15 @@
+/* For image callouts in writing-middleware.md */
+
+.callout {position: relative;}
+
+#callout1 {top: 40px; }
+
+#callout2 {top: 60px;}
+
+#callout3 {top: 75px;}
+
+#callout4 {top: 145px;}
+
+#callout5 {top: 165px;}
+
+#callout6 {top: 185px;}
diff --git a/css/langs/ko.css b/css/langs/ko.css
new file mode 100644
index 0000000000..d4c2b2ac66
--- /dev/null
+++ b/css/langs/ko.css
@@ -0,0 +1,19 @@
+/* For image callouts in writing-middleware.md */
+
+@import url('../../fonts/ko/pretendard.css');
+
+html, body {font-family: Pretendard, Arial, sans-serif;}
+
+.callout {position: relative;}
+
+#callout1 {top: 40px; }
+
+#callout2 {top: 60px;}
+
+#callout3 {top: 75px;}
+
+#callout4 {top: 145px;}
+
+#callout5 {top: 165px;}
+
+#callout6 {top: 185px;}
diff --git a/css/langs/pt-br.css b/css/langs/pt-br.css
new file mode 100644
index 0000000000..dd8a578f8e
--- /dev/null
+++ b/css/langs/pt-br.css
@@ -0,0 +1,13 @@
+/* For image callouts in writing-middleware.md */
+
+#callout1 {top: 40px; }
+
+#callout2 {top: 60px;}
+
+#callout3 {top: 75px;}
+
+#callout4 {top: 140px;}
+
+#callout5 {top: 150px;}
+
+#callout6 {top: 160px;}
diff --git a/css/langs/zh-cn.css b/css/langs/zh-cn.css
new file mode 100644
index 0000000000..8f2e5ac2dd
--- /dev/null
+++ b/css/langs/zh-cn.css
@@ -0,0 +1,13 @@
+/* For image callouts in writing-middleware.md */
+
+#callout1 {top: 40px; }
+
+#callout2 {top: 60px;}
+
+#callout3 {top: 75px;}
+
+#callout4 {top: 145px;}
+
+#callout5 {top: 170px;}
+
+#callout6 {top: 195px;}
diff --git a/css/langs/zh-tw.css b/css/langs/zh-tw.css
new file mode 100644
index 0000000000..8f2e5ac2dd
--- /dev/null
+++ b/css/langs/zh-tw.css
@@ -0,0 +1,13 @@
+/* For image callouts in writing-middleware.md */
+
+#callout1 {top: 40px; }
+
+#callout2 {top: 60px;}
+
+#callout3 {top: 75px;}
+
+#callout4 {top: 145px;}
+
+#callout5 {top: 170px;}
+
+#callout6 {top: 195px;}
diff --git a/css/nodeinteractive.css b/css/nodeinteractive.css
deleted file mode 100644
index 423d13c824..0000000000
--- a/css/nodeinteractive.css
+++ /dev/null
@@ -1,91 +0,0 @@
-#nodeinteractive {
- max-width: 1024px;
- margin-left: 5%;
- margin-right: 5%;
- border-radius: 7px;
- background-color: rgba(231, 238, 219, 0.6);
- display: inline-flex;
- overflow: hidden;
-}
-
-#nodeinteractive h3 {
- font-weight: 100;
- font-size: 1.3em;
- line-height: 1.2em;
-}
-
-#nodeinteractive p {
- font-weight: normal;
- font-size: 0.95em;
- margin: 3px;
-}
-
-#nodeinteractive-details {
- padding: 15px 20px;
-}
-
-#nodeinteractive-details ul {
- padding: 0;
-}
-
-#nodeinteractive-details li {
- display: inline-flex;
- list-style: none;
- background: rgba(255, 255, 255, 0.9);
- margin-bottom: 5px;
- padding: 3px;
-}
-
-#nodeinteractive-details img {
- display: block;
- width: 70px;
- height: 70px;
- margin-right: 5px;
-}
-
-#nodeinteractive-details li p {
- padding-right: 3px;
-}
-
-#nodeinteractive-details h4 {
- padding: 0;
- margin: 3px 2px;
-}
-
-#nodeinteractive-img {
- width: 300px;
-}
-
-.nodeinteractive-div {
- height: 250px;
-}
-
-/* responsive */
-
-@media all and (max-width: 899px) {
-
- #nodeinteractive {
- margin-top: 20px;
- }
-
- #nodeinteractive-img {
- display: none;
- }
-
-}
-
-@media all and (max-width: 700px) {
- #nodeinteractive img {
- display: none;
- }
-
- #nodeinteractive-details {
- height: auto;
- }
-
- #nodeinteractive-details h4 {
- font-weight: bold;
- margin-bottom: 7px;
- }
-
-}
diff --git a/css/prism.css b/css/prism.css
deleted file mode 100644
index a941010f8a..0000000000
--- a/css/prism.css
+++ /dev/null
@@ -1,142 +0,0 @@
-/* http://prismjs.com/download.html?themes=prism&languages=markup+css+clike+javascript+bash */
-/**
- * prism.js default theme for JavaScript, CSS and HTML
- * Based on dabblet (http://dabblet.com)
- * @author Lea Verou
- */
-
-code[class*="language-"],
-pre[class*="language-"] {
- color: black;
- text-shadow: 0 1px white;
- font-family: Consolas, Monaco, 'Andale Mono', monospace;
- direction: ltr;
- text-align: left;
- white-space: pre;
- word-spacing: normal;
- word-break: normal;
- line-height: 1.5;
-
- -moz-tab-size: 4;
- -o-tab-size: 4;
- tab-size: 4;
-
- -webkit-hyphens: none;
- -moz-hyphens: none;
- -ms-hyphens: none;
- hyphens: none;
-}
-
-pre[class*="language-"]::-moz-selection, pre[class*="language-"] ::-moz-selection,
-code[class*="language-"]::-moz-selection, code[class*="language-"] ::-moz-selection {
- text-shadow: none;
- background: #b3d4fc;
-}
-
-pre[class*="language-"]::selection, pre[class*="language-"] ::selection,
-code[class*="language-"]::selection, code[class*="language-"] ::selection {
- text-shadow: none;
- background: #b3d4fc;
-}
-
-@media print {
- code[class*="language-"],
- pre[class*="language-"] {
- text-shadow: none;
- }
-}
-
-/* Code blocks */
-pre[class*="language-"] {
- padding: 1em;
- margin: .5em 0;
- overflow: auto;
-}
-
-:not(pre) > code[class*="language-"],
-pre[class*="language-"] {
- background: #F7F7F7;
-}
-
-pre.language-sh {
- background-color: #272727;
-}
-
-code.language-sh {
- color: #4fbf40;
- text-shadow: none;
-}
-
-/* Inline code */
-:not(pre) > code[class*="language-"] {
- padding: .1em;
- border-radius: .3em;
-}
-
-.token.comment,
-.token.prolog,
-.token.doctype,
-.token.cdata {
- color: slategray;
-}
-
-.token.punctuation {
- color: #999;
-}
-
-.namespace {
- opacity: .7;
-}
-
-.token.property,
-.token.tag,
-.token.boolean,
-.token.number,
-.token.constant,
-.token.symbol,
-.token.deleted {
- color: #905;
-}
-
-.token.selector,
-.token.attr-name,
-.token.string,
-.token.char,
-.token.builtin,
-.token.inserted {
- color: #690;
-}
-
-.token.operator,
-.token.entity,
-.token.url,
-.language-css .token.string,
-.style .token.string {
- color: #a67f59;
- background: hsla(0, 0%, 100%, .5);
-}
-
-.token.atrule,
-.token.attr-value,
-.token.keyword {
- color: #07a;
-}
-
-.token.function {
- color: #DD4A68;
-}
-
-.token.regex,
-.token.important,
-.token.variable {
- color: #e90;
-}
-
-.token.important {
- font-weight: bold;
-}
-
-.token.entity {
- cursor: help;
-}
-
diff --git a/css/pt-br.css b/css/pt-br.css
deleted file mode 100644
index dfc300a126..0000000000
--- a/css/pt-br.css
+++ /dev/null
@@ -1,17 +0,0 @@
-/*
- Copyright (c) 2016 StrongLoop, IBM, and Express Contributors
- License: MIT
-*/
-/* For image callouts in writing-middleware.md */
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 140px;}
-
-#callout5 {top: 150px;}
-
-#callout6 {top: 160px;}
diff --git a/css/ru.css b/css/ru.css
deleted file mode 100644
index 23c6a2ab7f..0000000000
--- a/css/ru.css
+++ /dev/null
@@ -1,17 +0,0 @@
-/*
- Copyright (c) 2016 StrongLoop, IBM, and Express Contributors
- License: MIT
-*/
-/* For image callouts in writing-middleware.md */
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 145px;}
-
-#callout5 {top: 160px;}
-
-#callout6 {top: 180px;}
diff --git a/css/sintax.css b/css/sintax.css
new file mode 100644
index 0000000000..e33e6fbee9
--- /dev/null
+++ b/css/sintax.css
@@ -0,0 +1,141 @@
+:root {
+ --orange: #953800;
+ --green: #116329;
+ --blue-light: #0550ae;
+ --blue-darker: #0a3069;
+ --pupple: #8250df;
+ --gray: #6e7781;
+ --red: #cf222e;
+ --red-darker: #82071e;
+}
+
+.dark-mode:root {
+ --orange: #ffa657;
+ --green: #79c0ff;
+ --blue-light: #a5d6ff;
+ --blue-darker: #1f6feb;
+ --pupple: #d2a8ff;
+ --gray: #8b949e;
+ --red: #ff7b72;
+ --red-darker: #8e1519;
+}
+
+.highlight table td { padding: 5px; }
+.highlight table pre { margin: 0; }
+
+.highlight, .highlight .w {
+ color: #24292f;
+ background-color: var(--code-bg);
+}
+
+.highlight .k, .highlight .kd, .highlight .kn, .highlight .kp, .highlight .kr, .highlight .kt, .highlight .kv {
+ color: var(--red);
+}
+
+.highlight .gr {
+ color: #f6f8fa;
+}
+
+.highlight .gd {
+ color: var(--red-darker);
+ background-color: #ffebe9;
+}
+
+.highlight .nb,
+.highlight .nc,
+.highlight .no,
+.highlight .nn {
+ color: var(--orange);
+}
+
+.highlight .sr,.highlight .na, .highlight .nt, .highlight .gi {
+ color: var(--green);
+}
+
+.highlight .gi {
+ background-color: #dafbe1;
+}
+
+.highlight .ges {
+ font-weight: bold;
+ font-style: italic;
+}
+
+.highlight .l,
+.highlight .ld,
+.highlight .m,
+.highlight .mb,
+.highlight .mf,
+.highlight .mh,
+.highlight .mi,
+.highlight .il,
+.highlight .mo,
+.highlight .mx,
+.highlight .kc,
+.highlight .sb,
+.highlight .bp,
+.highlight .ne,
+.highlight .nl,
+.highlight .py
+.highlight .nv,
+.highlight .vc,
+.highlight .vg,
+.highlight .vi,
+.highlight .vm,
+.highlight .s1,
+.highlight .o,
+.highlight .ow,
+.highlight .gh,
+.highlight .gu,
+.highlight .s2,
+.highlight .dl {
+ color: var(--blue-light);
+}
+
+.highlight .gh {
+ font-weight: bold;
+}
+.highlight .gu {
+ font-weight: bold;
+}
+.highlight .s, .highlight .sa, .highlight .sc, .highlight .sd, .highlight .se, .highlight .sh, .highlight .sx, .highlight .ss {
+ color: var(--blue-darker);
+}
+.highlight .nd, .highlight .nf, .highlight .fm {
+ color: var(--pupple);
+}
+
+.highlight .err {
+ color: #f6f8fa;
+ background-color: #82071e;
+}
+.highlight .c,
+.highlight .gl
+.highlight .ch,
+.highlight .cd,
+.highlight .cm,
+.highlight .cp,
+.highlight .cpf,
+.highlight .cs,
+.highlight .gt {
+ color: var(--gray);
+}
+
+.highlight .c1 {
+ color: var(--green);
+}
+
+.highlight .ni,
+.highlight .ge,
+.highlight .si,
+.highlight .gs {
+ color: #24292f;
+}
+
+.highlight .ge {
+ font-style: italic;
+}
+
+.highlight .gs {
+ font-weight: bold;
+}
diff --git a/css/sk.css b/css/sk.css
deleted file mode 100644
index 6959da6c31..0000000000
--- a/css/sk.css
+++ /dev/null
@@ -1,21 +0,0 @@
-/*
- Copyright (c) 2016 StrongLoop, IBM, and Express Contributors
- License: MIT
-*/
-/* For image callouts in writing-middleware.md */
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 145px;}
-
-#callout5 {top: 170px;}
-
-#callout6 {top: 195px;}
-
-.dropit .dropit-submenu {
- min-width: 250px;
-}
\ No newline at end of file
diff --git a/css/style.css b/css/style.css
index 3736a9ca6f..1226c519a8 100644
--- a/css/style.css
+++ b/css/style.css
@@ -1,23 +1,50 @@
-/*
- Copyright (c) 2016 StrongLoop, IBM, and Express Contributors
- License: MIT
-*/
-
-/* general */
-
* {
- -webkit-box-sizing: border-box;
- -moz-box-sizing: border-box;
box-sizing: border-box;
- -webkit-tap-highlight-color: rgba(0,0,0,0);
+ -webkit-tap-highlight-color: transparent;
+ scroll-behavior: smooth;
+}
+
+/* handle header offset with scroll-margin */
+h1, h2, h3, h4, h5, h6,
+[id] {
+ scroll-margin-top: 60px;
+}
+
+/* Respect user motion preferences for access */
+@media (prefers-reduced-motion: reduce) {
+ html {
+ scroll-behavior: auto;
+ }
}
body {
font: 400 14px/1.6 "Open Sans", sans-serif;
- background: url(/images/bg.jpg);
+ background: var(--bg);
margin: 0;
padding: 0;
- color: #555;
+ color: var(--fg);
+ display: grid;
+ grid-template-areas:
+ 'header'
+ 'i18n'
+ 'content'
+ 'footer'
+}
+
+header {
+ grid-area: header;
+}
+
+.content {
+ grid-area: content;
+}
+
+footer {
+ grid-area: footer;
+}
+
+body.no-scroll{
+ overflow: hidden;
}
h1 {
@@ -25,23 +52,28 @@ h1 {
line-height: 36px;
}
-#intro h3, #api-doc h1 {
+#intro h2, #api-doc h1 {
font-weight: normal;
}
h1, h2, h3 {
margin: 5px 0;
- color: #353535;
+ color: var(--card-fg);
-webkit-font-smoothing: antialiased;
+
}
.content h1 {
margin-bottom: 20px;
}
+.content table a.ignore-underline {
+ text-decoration: none;
+}
+
p em {
font-weight: bold;
- color: #353535;
+ color: var(--card-fg);
}
p {
@@ -50,25 +82,29 @@ p {
}
strong, th {
- color: #353535;
+ color: var(--card-fg);
}
#overlay {
position: fixed;
left: 0;
top: 0;
- background: #fff;
- opacity: 0.8;
+ opacity: 0.6;
width: 100%;
height: 100%;
display: none;
z-index: 1;
+ background-color: var(--bg);
+}
+
+main.home {
+ max-width: 75rem;
+ margin: 40px auto 2%;
+ padding-inline: 5%;
+ grid-area: content;
}
#home-content {
- margin: 183px 0 2% 5%;
- max-width: 900px;
- padding-right: 9%;
display: flex;
}
@@ -90,13 +126,16 @@ strong, th {
}
#announcements {
- margin: 3px 5% 32px;
- max-width: 1005px;
+ margin-top: 40px;
padding: 0 16px;
- background: #fdfae6;
- border: 1px solid #ebdbb7;
+ background: var(--notice-bg);
+ border: 1px solid var(--notice-accent);
border-radius: 3px;
font-size: 0.9em;
+ & a {
+ color: var(--notice-accent);
+ text-decoration: underline;
+ }
}
#announcements ul {
@@ -117,40 +156,48 @@ strong, th {
margin-right: 12px;
}
-#announcements p:first-child {
+.announcement-title {
font-weight: bold;
- padding-left: 20px;
- background-image: url(/images/announcement-icon.png);
- background-position: 0 3px;
- background-repeat: no-repeat;
- background-size: 14px 14px;
margin-bottom: 11px;
+ display: flex;
+ align-items: center;
+ column-gap: 8px
}
-#install-command {
+.install-command {
font-family: Consolas, Monaco, "Andale Mono", monospace;
- padding: 5px 10px;
- background: #fff;
- border: 1px solid #eee;
+ padding: 10px;
+ border: 1px solid var(--border);
border-radius: 3px;
max-width: 375px;
+ background-color: inherit;
+
+ code {
+ background-color: inherit;
+ }
}
.content {
- margin: 153px 3% 7%;
- max-width: 1090px;
- padding-left: 225px;
+ display: flex;
+ flex-direction: row-reverse;
+ padding-inline-start: 1rem;
+ margin-block-start: 3.5rem;
}
-span.block-section {
- display: block;
+.content main {
+ max-width: 900px;
+ margin-inline: auto;
+}
+
+.flex-row-content {
+ flex-direction: row;
}
-li code {
- color: #333;
+span.block-section {
+ display: block;
}
-#intro h3 {
+#intro h2 {
font-size: 25px;
margin-bottom: 10px;
}
@@ -164,7 +211,7 @@ li code {
padding-bottom: 5px;
font-weight: bold;
font-size: 24px;
- color: #888;
+ color: var(--menu-grey)
}
#api-doc h2 {
@@ -188,54 +235,54 @@ li code {
#api-doc h5 {
font-size: 14px;
font-weight: bold;
- color: #666;
+ color: var(--menu-grey)
}
-/* links */
+/* scroll */
-a {
- color: #259dff;
- text-decoration: none;
+*::-webkit-scrollbar {
+ background-color: opacity(var(--box-fg), 0.145);
+ width: 16px;
}
-.h2:target {
- display: block;
- padding-top: 40px;
+*::-webkit-scrollbar-thumb {
+ border-radius: 8px;
+ border: 4px solid transparent;
+ background-clip: content-box;
+ background-color: var(--menu-grey);
}
-#api-doc *:target, #page-doc *:target {
- margin-top: -120px;
- padding-top: 120px;
- z-index: -1;
+*::-webkit-scrollbar-thumb:hover {
+ background-color: var(--hover-bg);
}
-.outlined-img {
- border: 1px solid #eaeaea;
- width: 90%;
+*::-webkit-scrollbar-thumb:active {
+ background-color: var(--menu-grey);
}
-.current {
- background: #e0f5ff;
+/* links */
+
+a {
+ color: var(--link);
+ text-decoration: underline;
}
-/* logo */
+.h2:target {
+ display: block;
+ padding-top: 40px;
+}
-#logo {
- position: fixed;
- top: 2px;
- margin: 0;
- padding: 10px 25px;
- width: auto;
- border-left: none;
- z-index: 1;
+
+/* logo */
+.logo-container a {
+ text-decoration: none;
+ display: flex;
+ justify-content: center;
+ align-items : center;
}
-#logo .express {
- margin-top: 63px;
- display: block;
- font: 25px "Helvetica Neue", "Open Sans", sans-serif;
- font-weight: 100;
- color: #444;
+.express-logo {
+ fill : var(--card-fg);
}
#description .express {
@@ -245,15 +292,16 @@ a {
margin-bottom: .25em;
}
-#description .express a {
- color: #353535;
+#description .express > span {
+ color: var(--card-fg);
}
-#express-version {
+#description .express a#express-version {
font-size: 0.2em;
margin-left: 0.5em;
- color: #259dff !important;
+ color: var(--link);
font-weight: 400;
+ text-decoration: underline;
}
#description {
@@ -265,109 +313,201 @@ a {
position: relative;
top: -5px;
font: 100 4.1em "Helvetica Neue", "Open Sans", sans-serif;
- color: #aeaeae;
+ color: var(--menu-grey);
line-height: .87;
+ margin: unset
}
-#description em {
- font-style: normal;
- font-weight: 100;
- font-size: 9px;
- color: #999;
- margin-left: 5px;
+#description .description a {
+ text-decoration-thickness: 1px;
+ text-underline-offset: 3px;
}
-#conference {
- display: inline;
- float: right;
- margin-left: 10px;
+.header-right {
+ display: flex;
+ align-items: center;
+ gap: 20px;
}
-#intro {
- margin-left: 5%;
+header {
+ background: var(--card-bg);
+ height: 57px;
+ display: flex;
+ align-items: center;
+ justify-content: space-between;
+ padding-inline: 1rem;
+ border-bottom: 1px solid var(--hover-fg);
}
-#doc-langs {
- text-align: center;
- font-size: 12px;
+.scroll header {
+ box-shadow: 0 0 4px var(--card-bg);
}
-#doc-langs p {
- margin: 3px 0;
+/* code */
+
+code {
+ background-color: var(--code-bg);
+ color: var(--card-fg);
+ margin-block: -.125rem;
+ font-size: 13px;
+ padding: .125rem .375rem;
+ border-radius: 6px;
}
-header {
- position: fixed;
- top: 0;
- left: 0;
- background: #eee;
- width: 100%;
- height: 120px;
- z-index: 100;
- border-bottom: 1px solid #ddd;
+pre {
+ padding: 16px;
+ border-radius: 3px;
+ border: 1px solid var(--border);
+ background-color: var(--code-bg);
+/* keyboard focus offset improve visibility */
+ &:focus {
+ border-color: var(--hover-border);
+ }
}
-.scroll header {
- border-bottom: 1px solid #ddd;
- box-shadow: 0 0 4px #eee;
+pre code {
+ padding: 0;
}
-/* companies using express */
+pre:has(code) {
+ position: relative;
-img.memberlogo {
- vertical-align: middle;
- width: 240px;
- padding: 10px 20px;
+ &:is(:hover, :focus) {
+ button {
+ display: flex;
+ }
+ }
+ /* focus copy btn by keyboard */
+ &:focus-within button {
+ display: flex;
+ }
}
-/* code */
+pre:has(code) button {
+ position: absolute;
+ top: 5px;
+ right: 5px;
+ border: none;
+ z-index: 100;
+ display: none;
+ cursor: pointer;
+ background-color: inherit;
+ padding: 2px;
+ border-radius: 5px;
+
+ &::after {
+ content: "";
+ background-color: var(--card-fg);
+ mask-image: url("/images/copy-btn.svg");
+ mask-size: 1.5rem;
+ mask-repeat: no-repeat;
+ width: 1.5rem;
+ height: 1.5rem;
+ }
-p code, td code {
- color: #333;
+ &:is(:hover, :focus) {
+ background-color: var(--hover-bg);
+ outline: 2px solid var(--hover-border);
+ }
+
+ @media all and (max-width: 370px) {
+ padding: 1px;
+
+ &::after {
+ mask-size: 1rem;
+ width: 1rem;
+ height: 1rem;
+ }
+ }
}
-pre {
- color: #555;
- font-size: 14px;
- line-height: 1.4;
- padding: 16px;
- border-radius: 3px;
- overflow: auto;
- border: 1px solid #ddd;
+pre:has(code) button.copied {
+ outline-color: var(--supported-fg);
+
+ &::after {
+ background-color: var(--supported-fg);
+ }
+
+ &::before {
+ font-size: 0.85rem;
+ position: absolute;
+ left: -58px;
+ content: "copied!";
+
+ width: fit-content;
+ height: fit-content;
+ padding: 4px;
+ border-radius: 2px;
+ color: var(--card-fg);
+ background-color: var(--card-bg);
+ outline: 1px solid var(--supported-fg);
+ }
+
+ @media all and (max-width: 400px) {
+ &::before {
+ left: -50px;
+ font-size: 0.7rem;
+ padding: 3px;
+ }
+ }
}
-pre code {
- overflow: scroll;
- word-break: break-all;
+pre:has(code) button.failed {
+ outline-color: var(--eol-fg);
+
+ &::after {
+ background-color: var(--eol-fg);
+ }
+
+ &::before {
+ font-size: 0.85rem;
+ position: absolute;
+ left: -58px;
+ content: "failed!";
+
+ width: fit-content;
+ height: fit-content;
+ padding: 4px;
+ border-radius: 2px;
+ color: var(--card-fg);
+ background-color: var(--card-bg);
+ outline: 1px solid var(--eol-fg);
+ }
+
+ @media all and (max-width: 400px) {
+ &::before {
+ left: -50px;
+ font-size: 0.7rem;
+ padding: 3px;
+ }
+ }
}
-/* top button */
+/* scroll to top button */
.scroll #top {
- opacity: .2;
+ opacity: .5;
+ display: initial
+}
+
+.scroll #top:hover {
+ opacity: 1;
}
#top {
line-height: 0;
- background: black;
- -webkit-border-radius: 2px;
+ border-radius: 2px;
position: fixed;
bottom: 15px;
right: 15px;
padding: 8px;
text-decoration: none;
- color: white;
opacity: 0;
- -webkit-transition: opacity 300ms;
-}
-
-#top:hover {
- opacity: 1;
-}
-
-#top img {
- width: 8px;
- height: 5px;
+ transition: opacity 300ms;
+ border: 1px solid var(--border);
+ background-color: var(--card-bg);
+ color: var(--card-fg);
+ display: none;
}
/* clearfix */
@@ -396,124 +536,73 @@ html[xmlns] .clearfix {
/* boxes */
#boxes {
+ display: grid;
+ grid-template-columns: repeat(4, 1fr);
+ row-gap: 20px;
+ column-gap: 50px;
margin-top: 30px;
}
-#boxes h3 {
+#boxes h2 {
line-height: 1.25em;
-}
-
-#boxes div {
- width: 215px;
- margin-right: 50px;
- float: left;
- list-style: none;
- padding-bottom: 20px;
-}
-
-#boxes div:last-child {
- margin-right: 0;
-}
-
-
-#boxes h3 {
+ color: var(--card-fg);
background: none;
margin-top: 0;
padding-top: 0;
}
-#boxes section p {
- width: 100%;
- margin-top: 5px;
- margin-bottom: 20px;
-}
-
-/* applications page */
-
-#applications .section {
- display: block;
- margin-bottom: 50px;
-}
-
-.application h2 {
- margin: 0;
-}
-
-.application {
- padding: 80px 0;
- height: 600px;
- position: relative;
-}
-
-.application p {
- float: left;
- width: 30%;
-}
-
-.application img {
- float: right;
-}
-
-.application .link {
- position: absolute;
- bottom: 15px;
- left: 15px;
+#boxes h2 a {
+ text-decoration: none;
+ color: var(--card-fg);
}
-.application .link a {
- margin-left: 4px;
+#boxes div {
+ list-style: none;
}
+/* tables specific */
-/* doc specific */
-
-.doctable, section table {
- margin: 1em 1em 1em 0;
- border: 1px solid #c6c6c6;
+table {
+ margin: 1em 0;
+ border: 1px solid var(--border);
border-collapse: collapse;
- empty-cells: show;
width: 100%;
+ @media screen and (max-width:600px) {
+ font-size: smaller;
+ }
}
-.doctable td, .doctable th, section table td, section table th {
+table td, table th {
padding: 7px;
line-height: 120%;
vertical-align: top;
- border: 1px solid #c6c6c6;
+ border: 1px solid var(--border);
}
-.doctable tr th, section table tr th {
- background-color: #dadada;
+table tr th {
+ background: var(--card-bg);
font-size: 110%;
}
-.doctable td p:first-child {
+table td p:first-child {
margin-top: 0;
}
-.doctable td p, li p {
+table td p, li p {
width: 100% !important;
}
-.doctable ul {
+table ul {
margin: 20px 0
}
/* doc boxes */
.doc-box {
- font-size: 12px;
- line-height: 14px;
- padding: 10px;
- border-radius: 3px;
- margin: 20px 3% 20px 3%;
-}
-
-.doc-box pre {
- font-size: 12px;
- line-height: 14px;
- padding: 0;
- margin: 0;
+ padding: 16px;
+ color: var(--box-fg);
+ border-radius: 0 6px 6px 0;
+ margin-bottom: 1rem;
}
.doc-box p {
@@ -524,53 +613,62 @@ html[xmlns] .clearfix {
margin: 0;
}
-.doc-box pre[class*="language-"] {
- background: none repeat scroll 0 0 #fff;
+.doc-title {
+ display: flex;
+ align-items: center;
+ gap: 3px;
+ font-weight: 600;
}
-/* English pages use backticks for code blocks */
-.en-doc .page pre[class*="language-"] {
- padding-top: 10px !important;
+/* i18n box */
+.doc-notice {
+ padding-block: 1rem;
+ padding-inline: 2.5rem;
+ color: var(--box-fg);
+ border-radius: 0 6px 6px 0;
+ background: var(--notice-bg);
+ border-left: 3px solid var(--notice-accent);
+ margin-inline: auto;
+ margin-block-start: 2rem;
+ position: relative;
+ grid-area: i18n;
+ display: block;
}
-/* Non-English pages use pre and code tags for code blocks */
-.non-en-doc .page pre[class*="language-"] {
- padding-top: 0 !important;
- padding-bottom: 0 !important;
+.doc-notice a{
+ color: var(--notice-accent);
+ text-decoration: underline;
}
-
-.page pre.plain-text, .page code.plain-text {
- padding-top: 0 !important;
- color: #000;
+.doc-notice[hidden] {
+ display: none;
}
-
-.doc-notice {
- background: #faf6e8;
- border: 1px solid #ded8c1;
+.doc-info {
+ background: var(--info-bg);
+ border-left: 3px solid var(--info-accent);
}
-.doc-info {
- background: #f7faec;
- border: 1px solid #dfe2d3;
+.doc-info a{
+ color: var(--info-accent);
+ text-decoration: underline;
}
.doc-warn {
- background: #f9f1f1;
- border: 1px solid #e2d3d3;
+ background: var(--warn-bg);
+ border-left: 3px solid var(--warn-accent);
}
-#i18n-notice-box {
- margin-top: 150px;
- position: relative;
+.doc-warn a {
+ color: var(--warn-accent);
+ text-decoration: underline;
}
#close-i18n-notice-box {
position: absolute;
top: 3px;
- right: 4px;
- color: #550000;
+ right: 9px;
+ color: var(--notice-accent);
cursor: pointer;
}
@@ -580,215 +678,347 @@ html[xmlns] .clearfix {
width: 200px;
}
-.button {
- display: block;
- padding: 3px 5px;
- border: 1px solid #ccc;
+div.header-btn {
+ display: flex;
+ padding: 3px;
border-radius: 3px;
cursor: pointer;
- color: #555;
+ color: var(--box-fg);
+}
+
+a.edit-github-btn{
+ display: flex;
+ gap: 0.5rem;
+ align-items: center;
+ width: fit-content;
+ padding: 0.5rem;
+ border-radius: 0.3rem;
+
+ &:is(:hover, :active, :focus) {
+ color: var(--fg);
+ background-color: var(--hover-bg);
+ outline: 1px solid var(--card-fg);
+ }
}
#mobile-menu {
display: none;
position: relative;
- top: 9px;
- left: 0;
-}
-
-#nav-button {
- position: absolute;
- left: 16px;
}
pre, code {
white-space: pre-wrap !important;
}
-#strongloop-header {
- font-size: 0.7em;
- display: block;
- position: absolute;
- right: 2%;
- top: 11px;
- width: 150px;
- border-radius: 3px;
- color: #08592B;
- padding: 3px;
-}
+/* footer */
footer {
- font-size: 11px;
- margin: 60px 10px 30px 10px;
- padding-left: 5%;
- max-width: 1090px;
+ font-size: 12px;
+ display: flex;
+ gap: 24px;
+ flex-direction: column;
+ padding-block: 2rem;
+ padding-inline: 3rem;
+
+ @media screen and (max-width : 360px) {
+ padding: 1rem;
+ }
}
#footer-content {
- display: table;
- margin: 20px auto 0;
+ width: 100%;
+ justify-content: space-between;
+ gap: 32px;
+ display: flex;
}
-#footer-content div {
- float: left;
- margin-right: 20px;
- background-repeat: no-repeat;
- background-position: 0 1px;
- padding-bottom: 4px;
+#footer-copyright {
+ display: flex;
+ flex-direction: column;
+ justify-content: center;
+ gap: 20px;
}
-#github {
- margin-right: 5px !important;
+#footer-policy {
+ display: flex;
+ flex-wrap: wrap;
+ column-gap: 20px;
+ row-gap: 8px;
+ justify-content: center;
+ font-size: 15px;
}
-#license {
- text-align: center;
- margin-top: -5px;
+#footer-links {
+ display: flex;
+ gap: 20px;
+ flex-wrap: wrap;
+ align-items: center;
+ justify-content: center;
}
-#license img {
- position: relative;
- top: 3px;
+.footer-social {
+ display: flex;
+ gap: 20px;
}
-#fork {
- background-image: url(/images/fork-icon.png);
- background-size: 11px 16px;
- padding-left: 15px;
+.footer-social a {
+ color: inherit;
}
-@media only screen and (-moz-min-device-pixel-ratio: 1.5), only screen and (-o-min-device-pixel-ratio: 3/2), only screen and (-webkit-min-device-pixel-ratio: 1.5), only screen and (min-devicepixel-ratio: 1.5), only screen and (min-resolution: 1.5dppx) {
+/* icons */
+a.openjs-logo {
+ display: inline-block;
+ width: 125px;
+ height: 39px;
+ cursor: pointer;
+}
- #fork {
- background-image: url(/images/fork-icon@2x.png);
- }
+/* theme and lang btn */
+button.theme-btn {
+ width: 2rem;
+ height: 2rem;
+ border: none;
+ cursor: pointer;
+ color: var(--fg);
+ background-color: inherit;
+ display: flex;
+ justify-content: center;
+ align-items: center;
+}
- #announcements p:first-child {
- background-image: url(/images/announcement-icon@2x.png);
- }
+#icon-moon,
+#icon-sun {
+ display: none;
+ align-self: center;
+}
+html.light-mode #icon-moon {
+ display: inline;
+}
+button.lang-btn {
+ appearance: none;
+ background-color: inherit;
+ border: 0;
+ cursor: pointer;
+ color: var(--card-fg);
+ padding: 0.2rem;
+ width: fit-content;
+ aspect-ratio: 1;
}
-/* navigation */
+div.desktop-lang-switcher {
+ position: relative;
+
+ > ul.lang-list {
+ display: none;
+ opacity: 0;
+ position: absolute;
+ list-style: none;
+ visibility: hidden;
+ left: -75px;
+ z-index: 100;
+ background-color: var(--card-bg);
+ border: 1px solid;
+ border-radius: 10px;
+ padding: 0px;
+ min-width: max-content;
+
+ li a {
+ display: block;
+ padding: 5px 20px 5px 20px;
+ text-decoration: none;
+ color: var(--card-fg);
+ &:is(:hover, :focus) {
+ background: var(--hover-bg);
+ }
+ }
+
+ > li:first-child > a {
+ border-start-start-radius: 10px;
+ border-start-end-radius: 10px;
+ }
+
+ > li:last-child > a {
+ border-end-start-radius: 10px;
+ border-end-end-radius: 10px;
+ }
+ }
+
+ > ul.lang-list.open {
+ display: block;
+ opacity: 1;
+ visibility: visible;
+ }
+}
+/* navigation */
#navbar {
- padding-left: 5%;
- max-width: 1000px;
- position: relative;
+ line-height: 30px;
display: flex;
- justify-content: flex-end;
- align-items: flex-start;
- top: 15px;
- box-sizing: content-box;
+ align-items: center;
}
#navbar a {
- color: #666;
- padding-left: 20px;
- -webkit-font-smoothing: subpixel-antialiased;
+ color: var(--card-fg);
+ text-decoration: none;
}
#navbar a.active {
font-weight: bold;
- color: #353535;
}
-
-/* dropdown menu */
+#navbar ul {
+ list-style: none;
+}
#navmenu {
- padding: 0;
- margin: 0;
- right: 0px;
- z-index: 1000;
- margin-right: 15px;
+ display: flex;
+ gap: 20px;
}
-#navmenu > li {
- list-style: none;
- padding: 0;
- float: left;
+/* content doc */
+
+#blog-doc {
+ padding: 0.5rem;
+ width: fit-content;
}
-#navmenu a:hover {
- text-decoration: none;
+/* dropdown menu */
+
+.submenu {
+ position: relative;
+ list-style: none;
}
-.menu ul {
+.submenu-content {
+ position: absolute;
+ top: 100%;
+ left: 50%;
+ transform: translate(-50%);
+ margin: auto;
+ box-shadow: 1px 2px var(--hover-fg);
+ z-index: 1000;
+ min-width: max-content;
+ width: fit-content;
+ border: 1px solid var(--border);
+ border-radius: 12px;
+ background-color: var(--bg);
+ padding: 0;
display: none;
}
-.menu ul.dropit-submenu {
- background-color: #fcfcfa;
- border: 1px solid #b2b2b2;
- padding: 6px 0;
- margin: 0 0 0 1px;
- border-radius: 3px;
- box-shadow: 0px 1px 3px rgba(0,0,0,0.15);
+.submenu-content li:first-child a {
+ border-radius: 12px 12px 0 0;
+}
+
+.submenu-content li:last-child a {
+ border-radius: 0px 0px 12px 12px;
}
-.menu ul.dropit-submenu a {
+.submenu.open .submenu-content {
+ display: initial;
+}
+
+#navmenu {
+ padding: 0;
+ margin: 0;
+ right: 0px;
+ z-index: 1000;
+ margin-right: 15px;
+}
+
+.submenu-content li a {
display: block;
- color: #777;
- padding: 0 8px 2px 8px;
+ padding: 2px 20px 2px 20px;
}
-.menu ul.dropit-submenu a:hover {
- background: #259dff;
- color: #fff !important;
+#navbar .submenu-content a:hover {
+ background: var(--hover-bg);
text-decoration: none;
}
-/* secondary menu */
+
+/* TOC side menu */
+
+.toc-container {
+ position: sticky;
+ top: 100px;
+ width: 270px
+}
#menu {
- position: fixed;
- margin: 0;
- padding: 0 10px 0 0;
- top: 153px;
- left: 30px;
- height: 500px;
- text-align: left;
- font-size: 13px;
+ min-width: 13rem;
+ padding-inline: 0.5rem;
+ font-size: 1rem;
overflow-y: auto;
+ max-height: 65vh;
+ padding-block-end: 0.5rem;
+ margin-block: 0;
+}
+
+#menu.blog-side-menu {
+ max-width: 20rem;
+ max-height: fit-content;
+}
+
+#menu ul a,
+#menu > li > a {
+ display: block;
+ color: var(--menu-grey);
+ padding-inline: 0.5rem;
+ text-decoration: none;
+
+ &:is(:hover,:active,:focus) {
+ border-radius: 0.3rem;
+ color: var(--fg);
+ outline: 1px solid var(--card-fg);
+ }
+}
+
+#menu ul a.active {
+ border-radius: 0.3rem;
+ color: var(--fg);
+ outline: 1px solid var(--card-fg);
}
#menu em {
font-weight: bold;
- color: #888;
+ color: var(--menu-em);
+ font-size: 1rem;
}
#menu li {
+ cursor: pointer;
list-style: none;
+ margin-block-start: 0.3rem;
}
-#menu ul {
+#menu ul,
+ul#side-menu {
+ display: none;
+ opacity: 0;
height: 0;
overflow: hidden;
}
-#menu ul.active {
+#menu ul.active,
+ul#side-menu.active {
height: auto;
- padding: 0;
+ padding-inline: 0.5rem;
+ display: block;
+ opacity: 1;
+ padding-block: 0.5rem;
}
#menu > li > a {
- color: #353535;
font-weight: bold;
- font-size: 15px;
-}
-
-#menu ul a {
- color: #555;
- padding-right: 7px;
-}
-
-#menu ul a.active {
- color: #259dff;
+ font-size: 1rem;
+ padding-inline-start: 1rem;
}
+/* can't find this in proj*/
h2 a {
- color: #353535 !important;
+ color: var(--card-fg) !important;
}
/* search */
@@ -796,33 +1026,180 @@ h2 a {
#q {
display: none;
height: 2.5em;
- min-width: 100%;
+ max-width: 100%;
padding: 5px;
-}
+}
.algolia-autocomplete {
- min-width: 12em;
- top: -0.2em;
+ max-width: 9em;
+ > input {
+ color: var(--fg);
+ background-color: var(--bg);
+ }
+ > input::placeholder {
+ color: var(--fg);
+ }
+ #q {
+ display: initial;
+ border-radius: 8px;
+ border: 1px solid var(--border);
+ transition: color .3s ease;
+ padding-inline: 12px;
+ outline: none;
+ &:focus-visible,
+ &:focus {
+ border-color: var(--hover-border);
+ border-width: 2px;
+ }
+ }
+}
+
+ #navbar {
+ .ds-dropdown-menu .ds-dataset-1 {
+ background-color: var(--bg);
+ .ds-suggestions {
+ /* background-color: var(--bg); */
+ color: var(--fg);
+ }
+ .ds-suggestion a {
+ background-color: var(--bg);
+ color: var(--fg);
+ }
+ .ds-suggestion a {
+ background-color: var(--bg);
+ color: var(--fg);
+ }
+ .algolia-docsearch-suggestion--category-header {
+ color: var(--fg);
+ }
+ .algolia-docsearch-suggestion--wrapper {
+ background-color: var(--bg);
+ .algolia-docsearch-suggestion--subcategory-column {
+ color: var(--menu-grey);
+
+ }
+ .algolia-docsearch-suggestion--title,
+ .algolia-docsearch-suggestion--text {
+ color: var(--fg);
+ }
+ .algolia-docsearch-suggestion--highlight {
+ color: var(--link);
+ background-color: initial;
+ }
+ }
+ .algolia-docsearch-suggestion {
+ background-color: initial;
+ }
+ .algolia-docsearch-suggestion--content .algolia-docsearch-suggestion--no-results{
+ background-color: initial;
+ }
+
+ }
+ .ds-suggestion.ds-cursor .algolia-docsearch-suggestion--title,
+ .ds-suggestion.ds-cursor .algolia-docsearch-suggestion--content {
+ background-color: var(--hover-bg);
+ }
+ }
+
+
+.content-404 {
+ height: 70vh;
+ padding: 153px 32px 7%;
+ text-align: center;
+ display: flex;
+ justify-content: center;
+ flex-direction: column;
+ grid-area: content;
}
-.algolia-autocomplete #q {
- display: initial
+.content-404 p {
+ font-size: 16px;
+}
+
+/* search-bar desktop re-sizing */
+@media all and (min-width: 950px) {
+ .algolia-autocomplete {
+ margin-right:15px;
+ max-width: 12em;
+ }
+}
+
+/* toc title */
+.toc-heading {
+ display: block;
+ cursor: default;
+ padding-inline-start: 1rem;
+ & > em {
+ font-weight: bold;
+ color: var(--menu-em);
+ font-size: 1rem;
+ }
+}
+
+
+/* TOC btn */
+
+#menu-toggle {
+ cursor: pointer;
+ display: none;
+ font-size: 1rem;
+ padding: 0.5rem;
+ opacity: 0;
+ width: fit-content;
+ border: 1px solid #000;
+ border-radius: 0.3rem;
+ color: #000;
+ background-color: #fff;
+
+ &::after {
+ content: "";
+ display: block;
+ width: 0.8em;
+ height: 0.5em;
+ background-color: var(--card-bg);
+ clip-path: polygon(100% 0%, 0 0%, 50% 100%);
+ cursor: pointer;
+ pointer-events: none;
+ transition: transform 0.2s ease-in-out;
+ transform: rotate(-90deg);
+ }
+
+ &:is(:hover, :active, :focus) {
+ background-color: #ebf2f5;
+ }
+}
+
+/* routing methods columns */
+.methods-columns {
+ display: flex;
+ gap: 2rem;
+ justify-content: space-between;
+ flex-wrap: wrap;
+
+ @media screen and (max-width: 460px) {
+ flex-direction: column;
+ gap: 0.3rem;
+ }
}
/* responsive */
-@media all and (max-width: 899px) {
+@media all and (max-width: 1440px) {
+ #menu{
+ top: 75px;
+ }
+}
- #conference a img {
- width: 150px;
- margin-right: 10px;
+@media all and (max-width: 1110px) {
+ #boxes {
+ grid-template-columns: 1fr 1fr;
}
#home-content {
flex-direction: column;
}
- #install-command {
+ .install-command {
display: none;
}
@@ -843,20 +1220,13 @@ h2 a {
.table-scroller {
width: 100%;
overflow: scroll;
- }
-
- #api-doc section {
- padding-left: 0;
+ scrollbar-width: thin;
}
code {
word-break: break-all;
}
- .menu ul.dropit-submenu a {
- font-size: 16px !important;
- }
-
ul {
padding-left: 5%;
}
@@ -883,16 +1253,8 @@ h2 a {
font-weight: normal;
}
- #menu {
- display: none;
- }
-
- .content {
- padding-left: 0;
- }
-
#home-content {
- margin: 150px 0 0 5%;
+ margin: 60px 0 0 5%;
padding-right: 5%;
}
@@ -900,310 +1262,477 @@ h2 a {
margin-bottom: 35px;
}
- #description .express {
- display: none;
- }
-
#description .description {
font-size: 3em;
line-height: .9em;
font-weight: 200;
}
- #install-command {
- width: 100%;
- margin-right: 5%;
+ .logo-container {
+ margin-inline: auto;
}
- #logo {
- position: static;
- width: 100%;
+ #home-menu {
+ display: block;
+ position: absolute;
+ top: 7px;
}
- #logo a {
- display: table !important;
- margin: 0 auto;
+ #overlay.blurs{
+ display: block;
}
- #logo .express {
- margin-top: 0px;
- font-weight: bold;
+ .menu ul {
+ display: block;
}
- .github-fork-ribbon-wrapper {
- display: none;
+ #footer-content {
+ flex-wrap: wrap;
+ justify-content: center;
}
- #mobile-menu {
- display: block;
+ #footer-copyright > a {
+ width: 100%;
+ display: flex;
+ justify-content: center;
}
- #boxes div {
- width: 90%;
+ .header-right {
+ display: flex;
+ gap: 8px;
}
+}
- .content p img {
- width: 98%;
- height: 98%;
+/* TOC responsive */
+@media all and (max-width: 800px) {
+ .content {
+ flex-direction: column;
+ padding-inline-start : 0;
+ margin-block-start: 1rem;
}
- #home-menu {
- display: block;
- position: absolute;
- top: 7px;
+ .content main {
+ padding-inline: 1rem;
+ width: 100vw;
+ margin-top: 0;
+ margin-inline: 0;
+ }
+
+ #api-doc,
+ #blog-doc,
+ #page-doc {
+ width: 100%;
}
- #navbar {
- padding: 0;
- top: 1px;
+ #api-doc section {
+ padding-left: 0;
}
- #navbar a {
- font-size: 19px;
- margin: 0;
- padding-left: 5%;
+ .toc-container {
+ display: flex;
+ flex-direction: column;
+ gap: 0;
+ padding: 1rem;
}
- #navmenu {
- left: 0;
- padding: 0;
- top: 2px;
- background: #fff;
- width: 100%;
+ #menu {
display: none;
+ opacity: 0;
+ max-height: 0;
+ background-color: var(--card-bg);
+ min-width: 100%;
}
- #navmenu > li {
- float: none;
- border-bottom: 1px solid #ccc;
- margin: 0;
- min-height: 47px;
- position: relative;
- background: #eee;
- cursor: pointer;
+ #menu.open {
+ display: block;
+ opacity: 1;
+ max-height: 35vh;
+ padding-inline: 1rem;
+ border-left: 2px solid var(--border);
+ margin-top: 0.3rem;
+ border-bottom-right-radius: 0.5rem;
+ border-top-right-radius: 0.5rem;
}
- #navmenu > li:first-child {
- display: none;
+ .toc-container {
+ width: 100%;
}
- #navmenu > li:hover {
- background: #e9e9e9;
+ #menu-toggle.show {
+ display: flex;
+ gap: 0.5rem;
+ align-items: center;
+ opacity: 1;
}
- #navmenu > li > ul {
- position: static;
+ #menu-toggle.show.rotate::after {
+ transform: rotate(0deg);
}
- .dropit .dropit-submenu {
- position: static !important;
+ #menu > li > a,
+ #menu ul a {
+ padding: 0.5rem;
+ &:is(:hover,:active,:focus) {
+ background: var(--hover-bg);
+ }
}
- .dropit .dropit-trigger {
- padding-top: 7px;
- }
+ #menu li ul li > em {
+ font-size: 0.8rem;
+ padding-inline: 1rem;
+ padding-block: 0.3rem;
+ background-color: var(--hover-bg);
+ border-radius: 0.3rem;
+ }
- .menu ul.dropit-submenu {
- margin-top: 7px;
- background: #ddd;
- padding: 0;
- margin: 0;
- border: none;
- border-radius: 0;
- box-shadow: none;
- max-height: 190px;
- overflow-y: scroll;
- overflow-x: hidden;
+ .toc-heading{
+ display: none;
}
+}
- .dropit-trigger > a {
- display: block;
- margin-bottom: 8px !important;
- }
- .menu ul.dropit-submenu a {
- padding: 5px 5px 5px 5%;
+@media all and (max-width: 540px) {
+ #boxes {
+ grid-template-columns: 1fr;
}
+}
- .dropit-submenu li {
- border-bottom: 1px solid #cdcdcd;
+@media all and (max-width: 420px) {
+ #app-settings-property {
+ width: auto;
}
+}
- .dropit-submenu a {
- padding-left: 10% !important;
- }
- .menu ul {
- display: block;
- }
+@media print {
- .active-mobile-menu {
- border-bottom: none !important;
+ header {
+ position: absolute;
}
+}
- .active-mobile-menu .dropit-trigger {
- margin-bottom: 0 !important;
- }
+/* For image callouts in writing-middleware.md */
- .menu ul.dropit-submenu a:hover {
- background: #cccccc;
- color: #666 !important;
- }
+.callout {position: relative;}
- footer {
- margin: 60px 0px 30px 0px;
- padding: 0 5%;
- }
+#mw-fig {
+ border-collapse: separate;
+ padding: 0;
+ border: 0;
+ width: 960px;
+ margin-bottom: 20px;
+}
+#mw-fig-imgcell {
+ margin: 0;
+ padding: 0px;
+ border: 0;
+ width: 410px;
+}
+#mw-fig-img {
+ margin: 0px;
+ padding: 0px;
+ width: 410px;
+ height: 308px;
+}
- #footer-content {
+.mw-fig-callouts {
+ margin: 0;
+ padding: 0 0 0 5px;
+ border: 0;
+ width: 550px;
+}
+
+/* Blog page styles*/
+#blog-doc {
+ margin: 0 1rem;
+ @media all and (max-width: 800px) {
+ margin: 0;
+ }
+}
+#blog-doc:has(> h1#express-blog),
+#blog-doc:has(> h1#write-a-blog-post) {
+ min-height: 300px;
+}
+#blog-doc .blog-details ~ p > img {
+ width: 200px;
+ float: right;
+ margin: 0.5rem;
+}
+#blog-doc p {
+ font-size: 1.1em;
+}
+.blog-posts {
+ display: flex;
+ flex-direction: column;
+ row-gap: 10px;
+}
+.blog-post {
+ width: 100%;
+ background-color: var(--card-bg);
+ display: flex;
+ padding: 10px;
+ flex-direction: column;
+ justify-content: space-between;
+ border-radius: 5px;
+ border: 1px solid var(--border);
+ box-shadow: 2px 3px var(--hover-fg);
+ transition: 0.3s;
+}
+.blog-post:hover {
+ background-color: var(--hover-bg);
+ border: 1px solid var(--hover-border);
+ box-shadow: 2px 3px var(--menu-grey);
+}
+.blog-post img {
+ max-width: 100%;
+ max-height: 100%;
+ object-fit: cover;
+}
+.blog-post .blog-details {
+ display: flex;
+ flex-direction: column;
+}
+.blog-details div:first-child {
+ margin-bottom: 5px;
+}
+.blog-tag {
+ font-size: 12px;
+}
+.blog-title {
+ font-size: 1.3rem;
+ line-height: 1.5rem;
+ font-weight: 500;
+ padding-right: .2em;
+}
+.blog-title a {
+ color: var(--card-fg)
+}
+.blog-excerpt {
+ font-size: .75rem;
+}
+.blog-img {
+ max-width: 100%;
+ margin: auto;
+}
+.blog-authors {
+ font-style: italic;
+}
+.blog-author-link {
+ color: inherit;
+ margin-left: 0.5ch;
+ text-decoration: none;
+}
+.blog-author-link-label {
+ text-decoration: underline;
+}
+.blog-author-avatar {
+ border-radius: 50%;
+ display: inline-block;
+ vertical-align: middle;
+ width: 1.5em;
+ height: 1.5em;
+}
+.blog-date {
+ font-weight: bold;
+ font-size: 85%;
+}
+/* mobile-only */
+@media (max-width: 500px) {
+ #blog-doc {
display: flex;
flex-wrap: wrap;
- justify-content: center;
+ flex-direction: column;
align-items: center;
+ margin-right: 0;
+ padding-right: 10px;
+ }
+ #blog-doc .blog-details + p > img {
+ margin-bottom: 15px;
}
+}
- #footer-content div {
+
+
+/* blog tablet and up*/
+@media (min-width: 768px) {
+ .blog-post {
+ margin: auto;
+ }
+ .blog-tags {
+ margin-bottom: 20px;
+ }
+ .blog-title {
+ font-size: 1.3rem;
+ margin-bottom: 20px;
+ line-height: 1.5rem;
+ }
+ .blog-post .blog-details {
display: flex;
- flex-wrap: wrap;
- align-items: center;
- white-space: nowrap;
+ flex-direction: row;
+ margin-left: 1rem;
+ font-size: 90%;
}
-
- #footer-content div#sponsor {
- display: block;
+ .blog-post .blog-details div:first-child {
+ margin-right: 20px;
}
-
- #doc-langs {
- font-size: 11px;
+ .blog-details {
+ font-size: 1rem;
}
-
- .algolia-autocomplete {
- display: none !important;
+ .blog-excerpt {
+ line-height: initial;
+ font-size: .85rem;
+ font-weight: 300;
+ margin-top: auto;
+ margin-bottom: 10px;
+ max-width: 80%;
}
+}
+
+strong.supported {
+ color: var(--supported-fg) ;
+}
+strong.eol {
+ color: var(--eol-fg) ;
+}
+.logo-table {
+ display: flex;
+ flex-wrap: wrap;
+ row-gap: 8px;
+ column-gap: 48px;
}
+.logo-table h3{
+ margin-bottom: 12px;
+}
-@media all and (max-width: 420px) {
+blockquote {
+ margin-left: 0;
+ font-weight: 600;
+ font-style: italic;
+ padding-left: 1.2em;
+ border-left: .25rem solid var(--border);
+}
- #conference {
- display:none;
+@media all and (max-width: 1110px) {
+ .algolia-autocomplete {
+ display: none !important;
}
- #app-settings-property {
- width: auto;
+ #mobile-menu {
+ display: block;
}
- #strongloop-header {
- display: none;
+ #navbar {
+ padding: 0;
+ top: 1px;
+ position: static;
}
- #description .express {
+ #navmenu>li:first-child {
display: none;
}
- footer {
- margin-top: 14px;
+ #navmenu>li {
+ border-bottom: 1px solid var(--border);
+ margin: 0;
+ min-height: 47px;
+ background: var(--card-bg);
+ cursor: pointer;
+ display: flex;
+ align-items: center;
}
- #footer-content {
- margin-left: 5%;
+ #navmenu>li.open:hover {
+ background: var(--card-bg);
}
-
- #footer-content div {
- clear: both;
+ #navmenu>li:hover {
+ background: var(--hover-bg);
+ & ul {
+ background-color: var(--card-bg);
+ }
}
- #footer-content div:nth-child(4) {
- white-space: pre-line;
- text-align: center;
+ #navmenu {
+ left: 0;
+ padding: 0;
+ top: 57px;
+ width: 100%;
+ position: absolute;
+ display: none;
}
- #fork {
- margin-left: 7px;
- margin-top: 2px;
- margin-bottom: 30px;
- padding-left: 18px;
+ #navmenu.opens {
+ display: block;
}
-}
-
-@media all and (max-width: 320px) {
-
- #install-command {
- font-size: 12px;
+ #navbar a {
+ font-size: 19px;
+ margin: 0;
+ width: 100%;
+ height: 100%;
+ padding-left: 5%;
}
-}
-@media print {
-
- header {
- position: absolute;
+ #navbar .submenu.open {
+ flex-direction: column;
+ align-items: initial;
+ > a {
+ border-bottom: 1px solid var(--border);
+ }
}
- #mobile-menu {
- display:none;
+ .submenu.open > a {
+ display: flex;
+ align-items: center;
+ min-height: 47px;
}
-}
-
-/* For image callouts in writing-middleware.md */
-
-.callout {position: relative;}
-
-#mw-fig { border-collapse: separate; padding: 0; border: 0; width: 960px; margin-bottom: 20px;}
-#mw-fig-imgcell {margin: 0; padding: 0px; border: 0; width: 410px;}
-#mw-fig-img {margin: 0px; padding: 0px; width: 410px; height: 308px;}
-.mw-fig-callouts {margin: 0; padding: 0 0 0 5px; border: 0; width: 550px;}
-
-/* For middleware pages */
-/*
-#mw-list {
- float: left;
- width: 180px;
- margin: 0;
- padding: 0 10px 0 10px;
- font-size: 13px;
- }
+ .submenu-content {
+ width: 100%;
+ position: static;
+ display: none;
+ margin-top: 7px;
+ background-color: var(--card-bg);
+ padding: 0;
+ margin: 0;
+ border: none;
+ border-radius: 0;
+ box-shadow: none;
+ max-height: 190px;
+ overflow-y: auto;
+ overflow-x: hidden;
+ transform: none;
+ cursor: pointer;
+ }
-#middleware {
- min-width: 300px;
-}
-*/
+ .submenu-content li > a {
+ width: 100%;
+ }
-#mw-container {
- display: flex;
- display: -webkit-flex; /* Safari */
- width: 100%;
-}
+ .submenu-content li:first-child a {
+ border-radius: 0;
+ }
-#mw-list {
- min-width: 180px;
- margin: 0;
- padding: 0 10px 0 10px;
- font-size: 13px;
- overflow-y: auto;
- }
+ .submenu-content li:last-child {
+ border-bottom: 0;
+ }
-#middleware-content {
- /* flex: 0.85; */
- margin-left: 10px;
-}
+ .submenu-content li:last-child a {
+ border-radius: 0;
+ }
-#mw-list ul li {
- margin-left: -20px;
-}
+ .submenu-content.open {
+ display: inline-block;
+ }
-#blm-banner {
- text-align: center;
- background: #010101;
- color: #f1f1f1;
- padding: 5px;
- font-size: 16px;
- width: 100%;
-}
+ #navbar .submenu-content li a {
+ font-size: 16px;
+ padding: 5px 5px 5px 5%;
+ padding-left: 10%;
+ }
-#blm-donate {
- color: #5E80F7;
- text-decoration: none;
+ .submenu-content li {
+ border-bottom: 1px solid var(--border);
+ }
}
diff --git a/css/th.css b/css/th.css
deleted file mode 100644
index c999ef4688..0000000000
--- a/css/th.css
+++ /dev/null
@@ -1,18 +0,0 @@
-@font-face {
- font-family: 'TH SarabunNew';
- src: url("../fonts/th/THSarabunNew.woff")
-}
-
-#description .description {
- position: relative;
- top: -5px;
- font: 100 4.1em "TH SarabunNew", "Helvetica Neue", "Open Sans", sans-serif;
- color: #aeaeae;
- line-height: .87;
- }
-
- /* Non-English pages use pre and code tags for code blocks */
-.non-en-doc .page pre[class*="language-"] {
- padding-top: 10px !important;
- padding-bottom: 10px !important;
-}
\ No newline at end of file
diff --git a/css/themes/dark-theme.css b/css/themes/dark-theme.css
new file mode 100644
index 0000000000..0c6a563696
--- /dev/null
+++ b/css/themes/dark-theme.css
@@ -0,0 +1,21 @@
+html.dark-mode {
+
+ #icon-sun {
+ display: inline;
+ }
+
+ .submenu-content {
+ box-shadow: 1px 2px var(--hover-bg);
+ background-color: var(--card-bg);
+ }
+
+ #navmenu>li:hover {
+ ul {
+ background-color: var(--card-bg);
+ }
+ }
+
+ .blog-excerpt {
+ color: var(--notice-accent);
+ }
+}
\ No newline at end of file
diff --git a/css/tr.css b/css/tr.css
deleted file mode 100644
index 1b920cecdf..0000000000
--- a/css/tr.css
+++ /dev/null
@@ -1,17 +0,0 @@
-/*
- Copyright (c) 2016 StrongLoop, IBM, and Express Contributors
- License: MIT
-*/
-/* For image callouts in writing-middleware.md */
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 145px;}
-
-#callout5 {top: 170px;}
-
-#callout6 {top: 195px;}
diff --git a/css/uk.css b/css/uk.css
deleted file mode 100644
index b4b5f80056..0000000000
--- a/css/uk.css
+++ /dev/null
@@ -1,19 +0,0 @@
-/*
- Copyright (c) 2016 StrongLoop, IBM, and Express Contributors
- License: MIT
-*/
-/* For image callouts in writing-middleware.md */
-
-.callout {position: relative;}
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 145px;}
-
-#callout5 {top: 165px;}
-
-#callout6 {top: 185px;}
diff --git a/css/variables.css b/css/variables.css
new file mode 100644
index 0000000000..5680810934
--- /dev/null
+++ b/css/variables.css
@@ -0,0 +1,52 @@
+:root.light-mode {
+ --grey-fg: #aeaeae;
+ --bg: #ffffff;
+ --fg: #383838;
+ --card-bg: #f0f1f3;
+ --card-fg: #383838;
+ /* text (api side menus h3...) */
+ --menu-grey: #888;
+ --hover-border: #484848;
+ --hover-bg: #D3D3D3;
+ --hover-fg: #fafafa;
+ --border: #d9e1e4;
+ --link: #0e78ce;
+ /* docs related */
+ --box-fg: #181818;
+ --info-bg: #cfd4fc;
+ --info-accent: #0f1c8a;
+ --notice-bg: #fceac5;
+ --notice-accent: #2E1D00;
+ --warn-bg: #fad1df;
+ --warn-accent: #8a0f3a;
+ --code-bg: #f0f1f3;
+ /* support page related */
+ --supported-fg: #009000;
+ --eol-fg: #ff0000;
+}
+:root.dark-mode {
+ --bg: #0c0c0c;
+ --fg: #fafafa;
+ --card-bg: #181818;
+ --card-fg: #f7f4f4;
+ --hover-bg: #262626;
+ --hover-fg: #f2f2f2;
+ --hover-border: #fafafa;
+ --border: #d9e1e4;
+ /* text (api side menus h3...) */
+ --menu-grey: silver;
+ --link: #259dff;
+ --menu-em: #a2a0a0eb;
+ /* docs related */
+ --box-fg: #ffffff;
+ --info-bg: #171d4f;
+ --info-accent: #bdc3ff;
+ --notice-bg: #4e4022;
+ --notice-accent: #f9e8c3;
+ --warn-bg: #4e2232;
+ --warn-accent: #f9c3d6;
+ --code-bg: #2b2b2b;
+ /* support page related */
+ --supported-fg:#299009;
+ --eol-fg: #ff1a1a;
+}
diff --git a/css/zh-cn.css b/css/zh-cn.css
deleted file mode 100644
index 1b920cecdf..0000000000
--- a/css/zh-cn.css
+++ /dev/null
@@ -1,17 +0,0 @@
-/*
- Copyright (c) 2016 StrongLoop, IBM, and Express Contributors
- License: MIT
-*/
-/* For image callouts in writing-middleware.md */
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 145px;}
-
-#callout5 {top: 170px;}
-
-#callout6 {top: 195px;}
diff --git a/css/zh-tw.css b/css/zh-tw.css
deleted file mode 100644
index 1b920cecdf..0000000000
--- a/css/zh-tw.css
+++ /dev/null
@@ -1,17 +0,0 @@
-/*
- Copyright (c) 2016 StrongLoop, IBM, and Express Contributors
- License: MIT
-*/
-/* For image callouts in writing-middleware.md */
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 145px;}
-
-#callout5 {top: 170px;}
-
-#callout6 {top: 195px;}
diff --git a/de/3x/api.md b/de/3x/api.md
old mode 100755
new mode 100644
index 6520d8a199..e3655297ab
--- a/de/3x/api.md
+++ b/de/3x/api.md
@@ -1,32 +1,26 @@
---
-layout: 3x-api
+layout: api
+version: 3x
title: Express 3.x - API-Referenz
+description: Access the API reference for Express.js version 3.x, noting that this version is end-of-life and no longer maintained - includes details on modules and methods.
menu: api
-lang: de
+redirect_from: " "
---
+
**Express 3.x WIRD NICHT MEHR GEWARTET**
- Bekannte und unbekannte Probleme bei Sicherheit und Leistung in 3.x wurden seit dem letzten Update (1. August 2015) noch nicht behoben. Es wird dringend empfohlen, die aktuelle Version von Express zu verwenden.
-
-
- 3.x-API
+Bekannte und unbekannte Probleme bei Sicherheit und Leistung in 3.x wurden seit dem letzten Update (1. August 2015) noch nicht behoben. Es wird dringend empfohlen, die aktuelle Version von Express zu verwenden. - - {% include api/en/3x/express.md %} +If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options). - - {% include api/en/3x/app.md %} - - - {% include api/en/3x/req.md %} +3.x-API
- - {% include api/en/3x/middleware.md %} + +{% include api/en/3x/app.md %}4.x-API
- - {% include api/en/4x/express.md %} +{% capture node-version %} - - {% include api/en/4x/app.md %} +Express 4.0 requires Node.js 0.10 or higher. - - {% include api/en/4x/req.md %} +{% endcapture %} - - {% include api/en/4x/res.md %} +{% include admonitions/note.html content=node-version %} - - {% include api/en/4x/router.md %} + +{% include api/en/4x/app.md %}
+
+
diff --git a/de/advanced/best-practice-performance.md b/de/advanced/best-practice-performance.md
old mode 100755
new mode 100644
index 84462670c7..c66899b35d
--- a/de/advanced/best-practice-performance.md
+++ b/de/advanced/best-practice-performance.md
@@ -1,41 +1,48 @@
---
layout: page
title: Leistungsspezifische Best Practices für Express-Anwendungen in Produktionsumgebungen
+description: Discover performance and reliability best practices for Express apps in production, covering code optimizations and environment setups for optimal performance.
menu: advanced
-lang: de
+redirect_from: " "
---
# Best Practices in Produktionsumgebungen: Leistung und Zuverlässigkeit
-## Überblick
-
In diesem Beitrag werden Best Practices in Bezug auf Leistung und Zuverlässigkeit für Express-Anwendungen behandelt, die in der Produktionsumgebung bereitgestellt werden.
Dieses Thema gehört sicherlich zur "DevOps"-Welt und deckt traditionelle Entwicklungs- und Betriebsprozesse ab. Entsprechend sind die Informationen hier in zwei Teile unterteilt:
-* [Empfehlungen für Maßnahmen an Ihrem Code](#code) (Entwicklung).
-* [Empfehlungen für Maßnahmen an Ihrer Umgebung/Ihrem Setup](#env) (Betrieb).
-
-
-
-## Empfehlungen für Maßnahmen an Ihrem Code
+- Things to do in your code (the dev part):
+ - Für statische Dateien Middleware verwenden
+ - Keine synchronen Funktionen verwenden
+ - [Do logging correctly](#do-logging-correctly)
+ - [Handle exceptions properly](#handle-exceptions-properly)
+- Things to do in your environment / setup (the ops part):
+ - NODE_ENV auf "production" festlegen
+ - Automatischen Neustart Ihrer Anwendung sicherstellen
+ - Anwendung in einem Cluster ausführen
+ - Anforderungsergebnisse im Cache speichern
+ - Load Balancer verwenden
+ - Reverse Proxy verwenden
+
+## Things to do in your code {#in-code}
Dies sind einige Beispiele für Maßnahmen, die Sie an Ihrem Code vornehmen können, um die Anwendungsleistung zu verbessern:
-* GZIP-Komprimierung verwenden
-* Keine synchronen Funktionen verwenden
-* Für statische Dateien Middleware verwenden
-* Auf ordnungsgemäße Protokollierung achten
-* Ausnahmebedingungen ordnungsgemäß handhaben
+- Für statische Dateien Middleware verwenden
+- Keine synchronen Funktionen verwenden
+- [Do logging correctly](#do-logging-correctly)
+- [Handle exceptions properly](#handle-exceptions-properly)
### GZIP-Komprimierung verwenden
Mit der GZIP-Komprimierung lässt sich die Größe des Antworthauptteils deutlich verringern und somit die Geschwindigkeit der Webanwendung erhöhen. Verwenden Sie die Middleware [compression](https://www.npmjs.com/package/compression) für die GZIP-Komprimierung in Ihrer Express-Anwendung. Beispiel:
```js
-var compression = require('compression')
-var express = require('express')
-var app = express()
+const compression = require('compression')
+const express = require('express')
+const app = express()
+
app.use(compression())
```
@@ -47,19 +54,11 @@ Synchrone Funktionen und Methoden belasten den Ausführungsprozess, bis sie zur
Auch wenn Node und viele andere Module synchrone und asynchrone Versionen ihrer Funktionen bieten, sollten Sie in Produktionsumgebungen immer die asynchrone Version verwenden. Nur beim ersten Systemstart ist die Verwendung einer synchronen Funktion begründet.
-Wenn Sie Node.js 4.0 und höher oder io.js 2.1.0 und höher verwenden, können Sie über das Befehlszeilenflag `--trace-sync-io` eine Warnung und einen Stack-Trace ausgeben, wenn Ihre Anwendung eine synchrone API verwendet. Auch wenn Sie diese natürlich nicht in der Produktionsumgebung verwenden werden, soll dadurch trotzdem sichergestellt werden, dass Ihr Code in der Produktionsumgebung eingesetzt werden kann. Weitere Informationen hierzu siehe [Wöchentliches Update für io.js 2.1.0](https://nodejs.org/en/blog/weekly-updates/weekly-update.2015-05-22/#2-1-0).
-
-### Für statische Dateien Middleware verwenden
+You can use the `--trace-sync-io` command-line flag to print a warning and a stack trace whenever your application uses a synchronous API. Auch wenn Sie diese natürlich nicht in der Produktionsumgebung verwenden werden, soll dadurch trotzdem sichergestellt werden, dass Ihr Code in der Produktionsumgebung eingesetzt werden kann. Weitere Informationen hierzu siehe [Wöchentliches Update für io.js 2.1.0](https://nodejs.org/en/blog/weekly-updates/weekly-update.2015-05-22/#2-1-0).
-Bei der Entwicklung können Sie [res.sendFile()](/{{ page.lang }}/4x/api.html#res.sendFile) für statische Dateien verwenden. Dies gilt jedoch nicht für die Produktionsumgebung, da diese Funktion bei jeder Dateianforderung aus dem Dateisystem lesen muss. Dadurch kommt es zu deutlichen Latenzen, die sich negativ auf die Gesamtleistung der Anwendung auswirken. Beachten Sie, dass `res.sendFile()` *nicht* mit dem Systemaufruf [sendfile](http://linux.die.net/man/2/sendfile) implementiert wird, wodurch dieser deutlich effizienter wäre.
+### Do logging correctly
-Verwenden Sie stattdessen die Middleware [serve-static](https://www.npmjs.com/package/serve-static) (oder etwas Vergleichbares), die für die Bereitstellung von Dateien für Express-Anwendungen optimiert ist.
-
-Die bessere Option wäre, für statische Dateien einen Reverse Proxy zu verwenden. Weitere Informationen siehe [Reverse Proxy verwenden](#proxy).
-
-### Auf ordnungsgemäße Protokollierung achten
-
-Im Allgemeinen gibt es für die Protokollierung Ihrer Anwendung zwei Gründe: 1) Debugging und 2) Protokollierung von Anwendungsaktivitäten (im Wesentlichen alles andere, außer Debugging). Die Verwendung von`console.log()` oder `console.err()` zur Ausgabe von Protokollnachrichten an das Terminal ist in der Entwicklung gängige Praxis. [Diese Funktionen sind jedoch synchron](https://nodejs.org/api/console.html#console_console_1), wenn das Ziel ein Terminal oder eine Datei ist. Sie sind also für Produktionsumgebungen nicht geeignet, es sei denn, Sie leiten die Ausgabe per Pipe zu einem anderen Programm um.
+Im Allgemeinen gibt es für die Protokollierung Ihrer Anwendung zwei Gründe: 1) Debugging und 2) Protokollierung von Anwendungsaktivitäten (im Wesentlichen alles andere, außer Debugging). Die Verwendung von`console.log()` oder `console.err()` zur Ausgabe von Protokollnachrichten an das Terminal ist in der Entwicklung gängige Praxis. But [these functions are synchronous](https://nodejs.org/api/console.html#console) when the destination is a terminal or a file, so they are not suitable for production, unless you pipe the output to another program.
#### Für Debuggingzwecke
@@ -67,51 +66,37 @@ Wenn Sie die Protokollierung für Debuggingzwecke nutzen, sollten Sie statt `con
#### Für Anwendungsaktivitäten
-Wenn Sie Anwendungsaktivitäten protokollieren (z. B. den Datenverkehr oder API-Aufrufe aufzeichnen), sollten Sie statt `console.log()` eine Protokollierungsbibliothek wie [Winston](https://www.npmjs.com/package/winston) oder [Bunyan](https://www.npmjs.com/package/bunyan) verwenden. Einen ausführlichen Vergleich dieser beiden Bibliotheken finden Sie im StrongLoop-Blogbeitrag [Vergleich von Winston und Bunyan für die Node.js-Protokollierung](https://strongloop.com/strongblog/compare-node-js-logging-winston-bunyan/).
-
-
+If you're logging app activity (for example, tracking traffic or API calls), instead of using `console.log()`, use a logging library like [Pino](https://www.npmjs.com/package/pino), which is the fastest and most efficient option available.
### Ausnahmebedingungen ordnungsgemäß handhaben
-Node-Anwendungen stürzen ab, wenn eine nicht abgefangene Ausnahmebedingung vorkommt. Wenn diese Ausnahmebedingungen nicht behandelt und entsprechende Maßnahmen eingeleitet werden, stürzt Ihre Express-Anwendung ab und geht offline. Wenn Sie dem nachfolgenden Rat in [Sicherstellen, dass Ihre Anwendung automatisch neu gestartet wird](#restart) folgen, wird Ihre Anwendung nach einem Absturz wiederhergestellt. Glücklicherweise haben Express-Anwendungen nur eine kurze Initialisierungszeit. Nichtsdestotrotz sollten Sie in erster Linie solche Abstürze vermeiden. Und hierzu müssen Sie Ausnahmebedingungen ordnungsgemäß handhaben.
+Node-Anwendungen stürzen ab, wenn eine nicht abgefangene Ausnahmebedingung vorkommt. Wenn diese Ausnahmebedingungen nicht behandelt und entsprechende Maßnahmen eingeleitet werden, stürzt Ihre Express-Anwendung ab und geht offline. Wenn Sie dem nachfolgenden Rat in [Sicherstellen, dass Ihre Anwendung automatisch neu gestartet wird](#restart) folgen, wird Ihre Anwendung nach einem Absturz wiederhergestellt. Glücklicherweise haben Express-Anwendungen nur eine kurze Initialisierungszeit. Nevertheless, you want to avoid crashing in the first place, and to do that, you need to handle exceptions properly.
Mit folgenden Verfahren stellen Sie sicher, dass alle Ausnahmebedingungen gehandhabt werden:
-* ["try-catch" verwenden](#try-catch)
-* ["Promises" verwenden](#promises)
+- ["try-catch" verwenden](#try-catch)
+- ["Promises" verwenden](#promises)
Um näher auf diese Themen eingehen zu können, müssen Sie sich ein grundlegendes Verständnis der Fehlerbehandlung in Node und Express aneignen: Verwendung von Error-first-Callbacks und Propagieren von Fehlern in Middleware. Node verwendet die Konvention "Error-first-Callback" für die Rückgabe von Fehlern von asynchronen Funktionen, bei denen der erste Parameter zur Callback-Funktion das Fehlerobjekt ist, gefolgt von Ergebnisdaten in den nachfolgenden Parametern. Um anzugeben, dass kein Fehler vorliegt, müssen Sie "null" als ersten Parameter übergeben. Die Callback-Funktion muss der Konvention "Error-first-Callback" folgen, um den Fehler sinnvoll bearbeiten zu können. In Express hat sich bewährt, die Funktion "next()" zu verwenden, um Fehler über die Middleware-Chain zu propagieren.
Weitere Informationen zu den Grundlagen der Fehlerbehandlung siehe:
-* [Fehlerbehandlung in Node.js](https://www.joyent.com/developers/node/design/errors)
-* [Aufbau leistungsfähiger Node-Anwendungen: Fehlerbehandlung](https://strongloop.com/strongblog/robust-node-applications-error-handling/) (StrongLoop-Blog)
-
-#### Was Sie unterlassen sollten
-
-Sie sollten *auf keinen* Fall per Listener das Ereignis `uncaughtException` überwachen, das ausgegeben wird, wenn eine Ausnahmebedingung bis zurück zur Ereignisschleife bestehen bleibt. Durch das Hinzufügen eines Ereignislisteners für `uncaughtException` verändert sich das Standardverhalten des Prozesses, über das eine Ausnahmebedingung festgestellt wird. Der Prozess läuft dann trotz der Ausnahmebedingung weiter. Dies mag sich vielleicht gut anhören, um einem Absturz Ihrer Anwendung vorzubeugen. Das Ausführen einer Anwendung nach einer nicht abgefangenen Ausnahmebedingung ist aber eine durchaus riskante Vorgehensweise und wird nicht empfohlen, da der Prozessstatus störanfällig und unvorhersehbar wird.
-
-Außerdem wird die Verwendung von `uncaughtException` offiziell als [grobes Vorgehen](https://nodejs.org/api/process.html#process_event_uncaughtexception) angesehen, sodass es den [Vorschlag](https://github.com/nodejs/node-v0.x-archive/issues/2582) gibt, die Funktion aus dem Kern zu entfernen. Das Überwachen von `uncaughtException` per Listener ist also keine gute Idee. Daher empfehlen wir Dinge wie Mehrfachprozesse und Supervisoren: Ein Absturz und anschließender Neustart ist häufig die zuverlässigste Art der Fehlerbehebung.
-
-Zudem empfehlen wir, [domains](https://nodejs.org/api/domain.html) nicht zu verwenden. Mit diesem Modul, das zudem veraltet ist, lässt sich das Problem in der Regel nicht lösen.
-
-
+- [Fehlerbehandlung in Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
#### "try-catch" verwenden
"try-catch" ist ein JavaScript-Sprachkonstrukt, mit dem Sie Ausnahmebedingungen in synchronem Code abfangen können. Verwenden Sie "try-catch" beispielsweise, um JSON-Parsing-Fehler wie unten gezeigt zu bearbeiten.
-Verwenden Sie ein Tool wie [JSHint](http://jshint.com/) oder [JSLint](http://www.jslint.com/), um implizite Ausnahmebedingungen wie [Referenzfehler bei nicht definierten Variablen](http://www.jshint.com/docs/options/#undef) zu finden.
-
-Dies ist ein Beispiel zur Verwendung von "try-catch", um eine potenzielle "process-crashing"-Ausnahmebedingung zu handhaben. Diese Middlewarefunktion akzeptiert einen Abfragefeldparameter mit dem Namen "params", der ein JSON-Objekt ist.
+Dies ist ein Beispiel zur Verwendung von "try-catch", um eine potenzielle "process-crashing"-Ausnahmebedingung zu handhaben.
+Diese Middlewarefunktion akzeptiert einen Abfragefeldparameter mit dem Namen "params", der ein JSON-Objekt ist.
```js
app.get('/search', (req, res) => {
// Simulating async operation
setImmediate(() => {
- var jsonStr = req.query.params
+ const jsonStr = req.query.params
try {
- var jsonObj = JSON.parse(jsonStr)
+ const jsonObj = JSON.parse(jsonStr)
res.send('Success')
} catch (e) {
res.status(400).send('Invalid JSON string')
@@ -122,107 +107,84 @@ app.get('/search', (req, res) => {
"try-catch" funktioniert jedoch nur in synchronem Code. Da die Node-Plattform primär asynchron ist (insbesondere in einer Produktionsumgebung), lassen sich mit "try-catch" nicht besonders viele Ausnahmebedingungen abfangen.
-
-
#### "Promises" verwenden
-Mit "Promises" werden alle Ausnahmebedingungen (explizite und implizite) in asynchronen Codeblöcken gehandhabt, die `then()` verwenden. Sie müssen nur `.catch(next)` am Ende der Promises-Ketten hinzufügen. Beispiel:
+When an error is thrown in an `async` function or a rejected promise is awaited inside an `async` function, those errors will be passed to the error handler as if calling `next(err)`
```js
-app.get('/', (req, res, next) => {
- // do some sync stuff
- queryDb()
- .then((data) => makeCsv(data)) // handle data
- .then((csv) => { /* handle csv */ })
- .catch(next)
+app.get('/', async (req, res, next) => {
+ const data = await userData() // If this promise fails, it will automatically call `next(err)` to handle the error.
+
+ res.send(data)
})
app.use((err, req, res, next) => {
- // handle error
+ res.status(err.status ?? 500).send({ error: err.message })
})
```
-Jetzt werden alle asynchronen und synchronen Fehler zur Middleware "error" propagiert.
-
-Es gibt jedoch zwei Vorbehalte:
-
-1. Der gesamte asynchrone Code muss "Promises" zurückgeben (außer Emitter). Wenn eine bestimmte Bibliothek keine "Promises" zurückgibt, müssen Sie das Basisobjekt mit einer Helper-Funktion wie [Bluebird.promisifyAll()](http://bluebirdjs.com/docs/api/promise.promisifyall.html) konvertieren.
-2. Ereignisemitter (wie Streams) können nach wie vor nicht abgefangene Ausnahmebedingungen verursachen. Sie müssen also sicherstellen, dass Sie das Fehlerereignis ordnungsgemäß handhaben. Beispiel:
+Also, you can use asynchronous functions for your middleware, and the router will handle errors if the promise fails, for example:
```js
-const wrap = fn => (...args) => fn(...args).catch(args[2])
+app.use(async (req, res, next) => {
+ req.locals.user = await getUser(req)
-app.get('/', wrap(async (req, res, next) => {
- const company = await getCompanyById(req.query.id)
- const stream = getLogoStreamById(company.id)
- stream.on('error', next).pipe(res)
-}))
+ next() // This will be called if the promise does not throw an error.
+})
```
-Weitere Informationen zur Fehlerbehandlung mithilfe von "Promises" siehe:
+Best practice is to handle errors as close to the site as possible. So while this is now handled in the router, it’s best to catch the error in the middleware and handle it without relying on separate error-handling middleware.
+
+#### What not to do
-* [Asynchrone Fehlerbehandlung in Express mit "Promises", Generatoren und ES7](https://strongloop.com/strongblog/async-error-handling-expressjs-es7-promises-generators/)
-* ["Promises" in Node.js mit Q – eine Alternative zu Callbacks](https://strongloop.com/strongblog/promises-in-node-js-with-q-an-alternative-to-callbacks/)
+Sie sollten _auf keinen_ Fall per Listener das Ereignis `uncaughtException` überwachen, das ausgegeben wird, wenn eine Ausnahmebedingung bis zurück zur Ereignisschleife bestehen bleibt. Durch das Hinzufügen eines Ereignislisteners für `uncaughtException` verändert sich das Standardverhalten des Prozesses, über das eine Ausnahmebedingung festgestellt wird. Das Ausführen einer Anwendung nach einer nicht abgefangenen Ausnahmebedingung ist aber eine durchaus riskante Vorgehensweise und wird nicht empfohlen, da der Prozessstatus störanfällig und unvorhersehbar wird.
+
+Außerdem wird die Verwendung von `uncaughtException` offiziell als [grobes Vorgehen](https://nodejs.org/api/process.html#process_event_uncaughtexception) angesehen, sodass es den [Vorschlag](https://github.com/nodejs/node-v0.x-archive/issues/2582) gibt, die Funktion aus dem Kern zu entfernen. Das Überwachen von `uncaughtException` per Listener ist also keine gute Idee. Daher empfehlen wir Dinge wie Mehrfachprozesse und Supervisoren: Ein Absturz und anschließender Neustart ist häufig die zuverlässigste Art der Fehlerbehebung.
-
+Zudem empfehlen wir, [domains](https://nodejs.org/api/domain.html) nicht zu verwenden. Mit diesem Modul, das zudem veraltet ist, lässt sich das Problem in der Regel nicht lösen.
-## Empfehlungen für Maßnahmen an Ihrer Umgebung/Ihrem Setup
+## Things to do in your environment / setup {#in-environment}
Dies sind einige Beispiele für Maßnahmen, die Sie an Ihrer Systemumgebung vornehmen können, um die Anwendungsleistung zu verbessern:
-* NODE_ENV auf "production" festlegen
-* Automatischen Neustart Ihrer Anwendung sicherstellen
-* Anwendung in einem Cluster ausführen
-* Anforderungsergebnisse im Cache speichern
-* Load Balancer verwenden
-* Reverse Proxy verwenden
+- NODE_ENV auf "production" festlegen
+- Automatischen Neustart Ihrer Anwendung sicherstellen
+- Anwendung in einem Cluster ausführen
+- Anforderungsergebnisse im Cache speichern
+- Load Balancer verwenden
+- Reverse Proxy verwenden
### NODE_ENV auf "production" festlegen
-In der Umgebungsvariablen NODE_ENV wird die Umgebung angegeben, in der eine Anwendung ausgeführt wird (in der Regel ist dies die Entwicklungs- oder Produktionsumgebung). Am einfachsten lässt sich die Leistung verbessern, indem NODE_ENV auf "production" festgelegt wird.
+In der Umgebungsvariablen NODE_ENV wird die Umgebung angegeben, in der eine Anwendung ausgeführt wird (in der Regel ist dies die Entwicklungs- oder Produktionsumgebung). One of the simplest things you can do to improve performance is to set NODE_ENV to `production`.
Durch das Festlegen von NODE_ENV auf "production" führt Express Folgendes aus:
-* Speichern von Anzeigevorlagen im Cache.
-* Speichern von CSS-Dateien, die aus CSS-Erweiterungen generiert wurden, im Cache.
-* Generieren von weniger ausführlichen Fehlernachrichten.
-
-[Tests deuten darauf hin](http://apmblog.dynatrace.com/2015/07/22/the-drastic-effects-of-omitting-node_env-in-your-express-js-applications/), dass alleine dadurch die Anwendungsleistung um den Faktor 3 verbessert werden kann!
-
-Wenn Sie umgebungsspezifischen Code schreiben müssen, können Sie den Wert von NODE_ENV mit `process.env.NODE_ENV` überprüfen. Beachten Sie, dass die Überprüfung des Werts seiner Umgebungsvariablen eine leistungsbezogene Penalisierung nach sich zieht. Sie sollten also sehr sparsam damit umgehen.
+- Speichern von Anzeigevorlagen im Cache.
+- Speichern von CSS-Dateien, die aus CSS-Erweiterungen generiert wurden, im Cache.
+- Generieren von weniger ausführlichen Fehlernachrichten.
-In einer Entwicklungsumgebung wird die Umgebungsvariable in der Regel in Ihrer interaktiven Shell festgelegt, indem Sie beispielsweise `export` oder Ihre Datei `.bash_profile` verwenden. Im Allgemeinen sollten Sie dies nicht auf dem Produktionsserver vornehmen. Verwenden Sie stattdessen das Init-System (systemd oder Upstart) Ihres Betriebssystems. Der nächste Abschnitt enthält weitere Details zur Verwendung des Init-Systems im Allgemeinen. Die Festlegung von NODE_ENV ist jedoch für das Leistungsverhalten so wichtig (und so einfach durchzuführen), dass hier besonders darauf eingegangen wird.
+[Tests indicate](https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/) that just doing this can improve app performance by a factor of three!
-Verwenden Sie bei Upstart das Schlüsselwort `env` in Ihrer Jobdatei. Beispiel:
+Wenn Sie umgebungsspezifischen Code schreiben müssen, können Sie den Wert von NODE_ENV mit `process.env.NODE_ENV` überprüfen. Beachten Sie, dass die Überprüfung des Werts seiner Umgebungsvariablen eine leistungsbezogene Penalisierung nach sich zieht.
-5.x API
+ +{% capture node-version %} + +Express 5.0 requires Node.js 18 or higher. + +{% endcapture %} + +{% include admonitions/note.html content=node-version %} + +{% include api/en/5x/express.md %} +{% include api/en/5x/app.md %} +{% include api/en/5x/req.md %} +{% include api/en/5x/res.md %} +{% include api/en/5x/router.md %} + +
-
-# /etc/init/env.conf
- env NODE_ENV=production
-
-
-
-Weitere Informationen hierzu siehe [Upstart Intro, Cookbook and Best Practices](http://upstart.ubuntu.com/cookbook/#environment-variables).
+In einer Entwicklungsumgebung wird die Umgebungsvariable in der Regel in Ihrer interaktiven Shell festgelegt, indem Sie beispielsweise `export` oder Ihre Datei `.bash_profile` verwenden. But in general, you shouldn't do that on a production server; instead, use your OS's init system (systemd). Der nächste Abschnitt enthält weitere Details zur Verwendung des Init-Systems im Allgemeinen. Die Festlegung von NODE_ENV ist jedoch für das Leistungsverhalten so wichtig (und so einfach durchzuführen), dass hier besonders darauf eingegangen wird.
Verwenden Sie bei systemd die Anweisung `Environment` in Ihrer Einheitendatei. Beispiel:
-
-
+```sh
# /etc/systemd/system/myservice.service
Environment=NODE_ENV=production
-
-
-
-Weitere Informationen siehe [Umgebungsvariablen in systemd-Einheiten verwenden](https://coreos.com/os/docs/latest/using-environment-variables-in-systemd-units.html).
+```
-Wenn Sie StrongLoop Process Manager verwenden, können Sie auch die [Umgebungsvariable festlegen, wenn Sie StrongLoop Process Manager als Service installieren](https://docs.strongloop.com/display/SLC/Setting+up+a+production+host#Settingupaproductionhost-Setenvironmentvariables).
+For more information, see [Using Environment Variables In systemd Units](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/).
### Automatischen Neustart Ihrer Anwendung sicherstellen
In der Produktionsumgebung sollte die Anwendung nie offline sein. Das bedeutet, dass Sie sicherstellen müssen, dass die Anwendung bei einem Absturz der Anwendung oder des Servers immer wieder neu gestartet wird. Auch wenn man hofft, das keines dieser Ereignisse jemals eintritt, muss man doch mit beiden Möglichkeiten rechnen und:
-* einen Prozessmanager verwenden, um die Anwendung (und Node) bei einem Absturz neu zu starten.
-* das Init-System Ihres Betriebssystems verwenden, um den Prozessmanager bei einem Absturz des Betriebssystems neu zu starten. Außerdem kann das Init-System auch ohne einen Prozessmanager verwendet werden.
+- einen Prozessmanager verwenden, um die Anwendung (und Node) bei einem Absturz neu zu starten.
+- das Init-System Ihres Betriebssystems verwenden, um den Prozessmanager bei einem Absturz des Betriebssystems neu zu starten. Außerdem kann das Init-System auch ohne einen Prozessmanager verwendet werden.
Node-Anwendungen stürzen ab, wenn eine nicht abgefangene Ausnahmebedingung auftritt. Als Erstes müssen Sie in einem solchen Fall sicherstellen, dass Ihre Anwendung ausreichend getestet wurde und in der Lage ist, alle Ausnahmebedingungen zu handhaben (weitere Informationen siehe [Ausnahmebedingungen ordnungsgemäß handhaben](#exceptions)). Die sicherste Maßnahme ist jedoch, einen Mechanismus zu implementieren, über den bei einem Absturz der Anwendung ein automatischer Neustart der Anwendung ausgeführt wird.
@@ -232,55 +194,35 @@ In Entwicklungumgebungen wird die Anwendung einfach über die Befehlszeile mit `
Neben einem Neustart der Anwendung nach einem Absturz bietet ein Prozessmanager noch weitere Möglichkeiten:
-* Einblicke in die Laufzeitleistung und die Ressourcennutzung
-* Dynamische Änderung der Einstellungen zur Verbesserung des Leistungsverhaltens
-* Steuerung des Clustering (StrongLoop PM und PM2)
-
-Die gängigsten Prozessmanager für Node sind:
-
-* [StrongLoop Process Manager](http://strong-pm.io/)
-* [PM2](https://github.com/Unitech/pm2)
-* [Forever](https://www.npmjs.com/package/forever)
-
-Einen Vergleich der Features und Funktionen dieser Prozessmanager finden Sie hier: [http://strong-pm.io/compare/](http://strong-pm.io/compare/). Eine ausführliche Einführung in diese drei Prozessmanager finden Sie hier: [Prozessmanager für Express-Anwendungen](/{{ page.lang }}/advanced/pm.html).
-
-Die Verwendung eines dieser Prozessmanager reicht aus, um Ihre Anwendung betriebsbereit zu halten, selbst wenn sie hin und wieder abstürzt.
+- Einblicke in die Laufzeitleistung und die Ressourcennutzung
+- Dynamische Änderung der Einstellungen zur Verbesserung des Leistungsverhaltens
+- Control clustering (pm2).
-StrongLoop PM verfügt jedoch über zahlreiche Features und Funktionen, die sich speziell auf Implementierungen in der Produktionsumgebung beziehen. Sie können diesen Prozessmanager und die zugehörigen StrongLoop-Tools für folgende Zwecke verwenden:
-
-* Lokales Erstellen und Packen Ihrer Anwendung mit anschließender sicherer Bereitstellung auf Ihrem Produktionssystem
-* Automatischer Neustart Ihrer Anwendung nach einem Absturz aus irgendeinem Grund
-* Verwaltung Ihrer Cluster über Fernzugriff
-* Anzeige von CPU-Profilen und Heapspeichermomentaufnahmen (Heap-Snapshots) zur Optimierung der Leistung und Diagnose von Speicherlecks
-* Anzeige von Leistungsmessdaten für Ihre Anwendung
-* Einfache Skalierung auf mehrere Hosts mit integrierter Steuerung für Nginx Load Balancer
-
-Wie unten beschrieben, erfolgt ein automatischer Neustart beim Systemwiederanlauf, wenn Sie StrongLoop Process Manager über Ihr Init-System als Betriebssystemservice installieren. Dadurch bleiben Ihre Anwendungsprozesse und Cluster dauerhaft betriebsbereit.
+Historically, it was popular to use a Node.js process manager like [PM2](https://github.com/Unitech/pm2). See their documentation if you wish to do this. However, we recommend using your init system for process management.
#### Init-System verwenden
-Als nächste Ebene der Zuverlässigkeit müssen Sie sicherstellen, dass Ihre Anwendung bei einem Serverneustart neu gestartet wird. Systeme können immer wieder aus verschiedenen Gründen abstürzen. Um sicherzustellen, dass Ihre Anwendung bei einem Serverabsturz neu gestartet wird, können Sie das in Ihr Betriebssystem integrierte Init-System verwenden. Die beiden wichtigsten Init-Systeme sind aktuell [systemd](https://wiki.debian.org/systemd) und [Upstart](http://upstart.ubuntu.com/).
+Als nächste Ebene der Zuverlässigkeit müssen Sie sicherstellen, dass Ihre Anwendung bei einem Serverneustart neu gestartet wird. Systeme können immer wieder aus verschiedenen Gründen abstürzen. Um sicherzustellen, dass Ihre Anwendung bei einem Serverabsturz neu gestartet wird, können Sie das in Ihr Betriebssystem integrierte Init-System verwenden. The main init system in use today is [systemd](https://wiki.debian.org/systemd).
Es gibt zwei Möglichkeiten, Init-Systeme mit Ihrer Express-Anwendung zu verwenden:
-* Ausführung Ihrer Anwendung in einem Prozessmanager und Installation des Prozessmanagers als Service mit dem Init-System. Der Prozessmanager wird neu gestartet, wenn Ihre Anwendung abstürzt. Das Init-System startet dann den Prozessmanager neu, sobald das Betriebssystem neu gestartet wird. Dies ist die empfohlene Vorgehensweise.
-* Ausführung Ihrer Anwendung (und von Node) direkt mit dem Init-System. Diese Vorgehensweise ist zwar etwas einfacher, Sie profitieren jedoch nicht von den zusätzlichen Vorteilen des Einsatzes eines Prozessmanagers.
+- Ausführung Ihrer Anwendung in einem Prozessmanager und Installation des Prozessmanagers als Service mit dem Init-System. Der Prozessmanager wird neu gestartet, wenn Ihre Anwendung abstürzt. Dies ist die empfohlene Vorgehensweise.
+- Ausführung Ihrer Anwendung (und von Node) direkt mit dem Init-System. Diese Vorgehensweise ist zwar etwas einfacher, Sie profitieren jedoch nicht von den zusätzlichen Vorteilen des Einsatzes eines Prozessmanagers.
##### systemd
"systemd" ist ein Linux-System und Service-Manager. Die meisten wichtigen Linux-Distributionen haben "systemd" als Init-Standardsystem übernommen.
-Eine "systemd"-Servicekonfigurationsdatei wird als *Einheitendatei* bezeichnet, die die Endung ".service" hat. Dies ist ein Beispiel für eine Einheitendatei zur direkten Verwaltung einer Node-Anwendung (ersetzen Sie den Text in Fettdruck durch Werte für Ihr System und Ihre Anwendung):
+Eine "systemd"-Servicekonfigurationsdatei wird als _Einheitendatei_ bezeichnet, die die Endung ".service" hat. Dies ist ein Beispiel für eine Einheitendatei zur direkten Verwaltung einer Node-Anwendung (ersetzen Sie den Text in Fettdruck durch Werte für Ihr System und Ihre Anwendung): Replace the values enclosed in `
-
+```sh
[Unit]
-Description=Awesome Express App
+Description=
[Service]
Type=simple
-ExecStart=/usr/local/bin/node /projects/myapp/index.js
-WorkingDirectory=/projects/myapp
+ExecStart=/usr/local/bin/node
+WorkingDirectory=
User=nobody
Group=nogroup
@@ -301,111 +243,15 @@ Restart=always
[Install]
WantedBy=multi-user.target
-
-
-Weitere Informationen zu "systemd" siehe [systemd-Referenz (Man-Page)](http://www.freedesktop.org/software/systemd/man/systemd.unit.html).
-##### StrongLoop Process Manager als "systemd"-Service
-
-Sie können StrongLoop Process Manager problemlos als "systemd"-Service installieren. Dadurch wird beim Serverneustart StrongLoop Process Manager automatisch neu gestartet. Dadurch wiederum werden alle Anwendungen neu gestartet, die von diesem Prozessmanager verwaltet werden.
-
-So installieren Sie StrongLoop Process Manager als "systemd"-Service:
-
-
-
-$ sudo sl-pm-install --systemd
-
-
-
-Starten Sie dann den Service mit:
-
-
-
-$ sudo /usr/bin/systemctl start strong-pm
-
-
-
-Weitere Informationen hierzu finden Sie im Thema [Produktionshost einrichten (in der StrongLoop-Dokumentation)](https://docs.strongloop.com/display/SLC/Setting+up+a+production+host#Settingupaproductionhost-RHEL7+,Ubuntu15.04or15.10).
-
-##### Upstart
-
-"Upstart" ist ein Systemtool, das auf vielen Linux-Distributionen verfügbar ist. Mit diesem Tool können Aufgaben (Tasks) und Services beim Systemstart gestartet, beim Herunterfahren gestoppt und auch überwacht werden. Sie können Ihre Express-Anwendung oder einen Prozessmanager als Service konfigurieren. "Upstart" startet diese dann bei einem Absturz automatisch neu.
-
-Ein "Upstart"-Service wird als Jobkonfigurationsdatei (auch als "Job" bezeichnet) definiert, deren Dateiname mit `.conf` endet. Das folgende Beispiel zeigt, wie ein Job namens "myapp" für eine Anwendung namens "myapp" erstellt wird, wobei sich die Hauptdatei im Verzeichnis `/projects/myapp/index.js` befindet.
-
-Erstellen Sie eine Datei namens `myapp.conf` unter `/etc/init/` mit dem folgenden Inhalt (ersetzen Sie den Text in Fettdruck durch Werte für Ihr System und Ihre Anwendung):
-
-
-
-# When to start the process
-start on runlevel [2345]
-
-# When to stop the process
-stop on runlevel [016]
-
-# Increase file descriptor limit to be able to handle more requests
-limit nofile 50000 50000
-
-# Use production mode
-env NODE_ENV=production
-
-# Run as www-data
-setuid www-data
-setgid www-data
-
-# Run from inside the app dir
-chdir /projects/myapp
-
-# The process to start
-exec /usr/local/bin/node /projects/myapp/index.js
-
-# Restart the process if it is down
-respawn
-
-# Limit restart attempt to 10 times within 10 seconds
-respawn limit 10 10
-
-
-
-Hinweis: Dieses Script erfordert Upstart 1.4 oder höher mit Unterstützung auf Ubuntu 12.04-14.10.
-
-Da der Job so konfiguriert ist, dass er beim Systemstart ausgeführt wird, wird Ihre Anwendung zusammen mit dem Betriebssystem gestartet und automatisch neu gestartet, wenn die Anwendung abstürzt oder das System heruntergefahren wird.
-
-Neben dem automatischen Neustart der Anwendung können Sie mit Upstart die folgenden Befehle verwenden:
-
-* `start myapp` – Anwendung starten
-* `restart myapp` – Anwendung neu starten
-* `stop myapp` – Anwendung stoppen
-
-Weitere Informationen zu "Upstart" siehe [Upstart Intro, Cookbook and Best Practises](http://upstart.ubuntu.com/cookbook).
-
-##### StrongLoop Process Manager als "Upstart"-Service
-
-Sie können StrongLoop Process Manager problemlos als "Upstart"-Service installieren. Dadurch wird beim Serverneustart StrongLoop Process Manager automatisch neu gestartet. Dadurch wiederum werden alle Anwendungen neu gestartet, die von diesem Prozessmanager verwaltet werden.
-
-So installieren Sie StrongLoop Process Manager als "Upstart 1.4"-Service:
-
-
-
-$ sudo sl-pm-install
-
-
-
-Fühen Sie dann den Service aus mit:
-
-
-
-$ sudo /sbin/initctl start strong-pm
-
-
+```
-Hinweis: Auf Systemen, die Upstart 1.4 nicht unterstützen, sind die Befehle leicht unterschiedlich. Weitere Informationen hierzu siehe das
-Thema [Einrichtung eines Produktionshosts (in der StrongLoop-Dokumentation)](https://docs.strongloop.com/display/SLC/Setting+up+a+production+host#Settingupaproductionhost-RHELLinux5and6,Ubuntu10.04-.10,11.04-.10).
+Weitere Informationen zu "systemd" siehe [systemd-Referenz (Man-Page)](http://www.freedesktop.org/software/systemd/man/systemd.unit.html).
### Anwendung in einem Cluster ausführen
-In einem Multi-Core-System können Sie die Leistung einer Node-Anwendung mehrmals erhöhen, indem Sie einen Cluster von Prozessen starten. Ein Cluster führt mehrere Instanzen der Anwendung aus, idealerweise eine Instanz auf jedem CPU-Core. Dadurch werden die Arbeitslasten und die Tasks auf die Instanzen verteilt.
+In einem Multi-Core-System können Sie die Leistung einer Node-Anwendung mehrmals erhöhen, indem Sie einen Cluster von Prozessen starten. Ein Cluster führt mehrere Instanzen der Anwendung aus, idealerweise eine Instanz auf jedem CPU-Core.
-
+
Wichtig. Da die Anwendungsinstanzen als separate Prozesse ausgeführt werden, nutzen sie nicht dieselbe Hauptspeicherkapazität gemeinsam. Das heißt, Objekte befinden sich für jede Instanz der Anwendung auf lokaler Ebene. Daher kann der Status im Anwendungscode nicht beibehalten werden. Sie können jedoch einen speicherinternen Datenspeicher wie [Redis](http://redis.io/) verwenden, um sitzungsrelevante Daten und Statusinformationen zu speichern. Diese Einschränkung trifft im Wesentlichen auf alle Formen der horizontalen Skalierung zu, unabhängig davon, ob es sich um Clustering mit mehreren Prozessen oder mehreren physischen Servern handelt.
@@ -413,45 +259,52 @@ Bei in Gruppen zusammengefassten Anwendungen (geclusterte Anwendungen) können V
#### Clustermodule von Node verwenden
-Das Clustering erfolgt über das [Clustermodul](https://nodejs.org/docs/latest/api/cluster.html) von Node. Dadurch wird ein Masterprozess eingeleitet, um Verarbeitungsprozesse zu starten und eingehende Verbindungen auf die Verarbeitungsprozesse zu verteilen. Anstatt dieses Modul jedoch direkt zu verwenden, ist es deutlich besser, eines der vielen angebotenen Tools einzusetzen, das diesen Vorgang automatisch für Sie ausführt, wie beispielsweise [node-pm](https://www.npmjs.com/package/node-pm) oder [cluster-service](https://www.npmjs.com/package/cluster-service).
+Clustering is made possible with Node's [cluster module](https://nodejs.org/api/cluster.html). Dadurch wird ein Masterprozess eingeleitet, um Verarbeitungsprozesse zu starten und eingehende Verbindungen auf die Verarbeitungsprozesse zu verteilen.
-#### StrongLoop Process Manager verwenden
+#### Using PM2
-Wenn Sie Ihre Anwendung auf StrongLoop Process Manager (PM) bereitstellen, können Sie die Vorteile des Clustering nutzen, *ohne* Ihren Anwendungscode ändern zu müssen.
+If you deploy your application with PM2, then you can take advantage of clustering _without_ modifying your application code. You should ensure your [application is stateless](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) first, meaning no local data is stored in the process (such as sessions, websocket connections and the like).
-Wenn StrongLoop Process Manager (PM) eine Anwendung ausführt, wird diese automatisch in einem Cluster ausgeführt. Die Anzahl der Verarbeitungsprozesse entspricht dabei der Anzahl der CPU-Cores im System. Sie können die Anzahl der Verarbeitungsprozesse manuell im Cluster ändern. Hierfür verwenden Sie das Befehlszeilentool "slc", ohne die Anwendung stoppen zu müssen.
+When running an application with PM2, you can enable **cluster mode** to run it in a cluster with a number of instances of your choosing, such as the matching the number of available CPUs on the machine. You can manually change the number of processes in the cluster using the `pm2` command line tool without stopping the app.
-Beispiel: Angenommen, Sie haben Ihre Anwendung auf prod.foo.com bereitgestellt, und StrongLoop PM ist auf Port 8701 (Standardport) empfangsbereit. Dann müssen Sie die Clustergröße mithilfe von "slc" auf "8" einstellen.
+To enable cluster mode, start your application like so:
-
-
-$ slc ctl -C http://prod.foo.com:8701 set-size my-app 8
-
-
+```bash
+# Start 4 worker processes
+$ pm2 start npm --name my-app -i 4 -- start
+# Auto-detect number of available CPUs and start that many worker processes
+$ pm2 start npm --name my-app -i max -- start
+```
-Weitere Informationen zum Clustering mit StrongLoop PM finden Sie im Thema [Clustering](https://docs.strongloop.com/display/SLC/Clustering) in der StrongLoop-Dokumentation.
+This can also be configured within a PM2 process file (`ecosystem.config.js` or similar) by setting `exec_mode` to `cluster` and `instances` to the number of workers to start.
+
+Once running, the application can be scaled like so:
+
+```bash
+# Add 3 more workers
+$ pm2 scale my-app +3
+# Scale to a specific number of workers
+$ pm2 scale my-app 2
+```
+
+For more information on clustering with PM2, see [Cluster Mode](https://pm2.keymetrics.io/docs/usage/cluster-mode/) in the PM2 documentation.
### Anforderungsergebnisse im Cache speichern
Eine weitere Strategie zur Verbesserung des Leistungsverhaltens in Produktionsumgebungen ist das Speichern von Anforderungergebnissen im Cache. Ihre Anwendung muss also diese Operation nicht wiederholt ausführen, um dieselbe Anforderung wiederholt zu bedienen.
-Mithilfe eines Caching-Servers wie [Varnish](https://www.varnish-cache.org/) oder [Nginx](https://www.nginx.com/resources/wiki/start/topics/examples/reverseproxycachingexample/) (siehe auch [Nginx Caching](https://serversforhackers.com/nginx-caching/)) lassen sich Geschwindigkeit und Leistung Ihrer Anwendung hervorragend verbessern.
+Use a caching server like [Varnish](https://www.varnish-cache.org/) or [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) (see also [Nginx Caching](https://serversforhackers.com/nginx-caching/)) to greatly improve the speed and performance of your app.
### Load Balancer verwenden
-Unabhängig davon, wie gut eine Anwendung optimiert wurde, kann eine Einzelinstanz nur eine begrenzte Arbeitslast oder einen begrenzten Datenverkehr handhaben. Eine Möglichkeit, eine Anwendung zu skalieren, ist die Ausführung mehrerer Instanzen dieser Anwendung und die Verteilung des Datenverkehrs über eine Lastausgleichsfunktion (Load Balancer) vorzunehmen. Die Einrichtung eines solchen Load Balancer kann helfen, Leistung und Geschwindigkeit Ihrer Anwendung zu verbessern. Zudem lässt sich dadurch die Anwendung besser skalieren als mit einer Einzelinstanz.
-
-Ein Load Balancer ist in der Regel ein Reverse Proxy, der den Datenverkehr zu und von mehreren Anwendungsinstanzen und Servern koordiniert. Sie können ohne großen Aufwand einen Load Balancer für Ihre Anwendung einrichten. Verwenden Sie hierzu [Nginx](http://nginx.org/en/docs/http/load_balancing.html) oder [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
-
-Bei einer solchen Lastverteilung müssen Sie sicherstellen, dass Anforderungen, die einer bestimmten Sitzungs-ID zugeordnet sind, mit dem Prozess verbunden sind, von dem sie ursprünglich stammen. Dies wird auch als *Sitzungsaffinität* oder *Affine Sitzungen* bezeichnet und kann durch den obigen Vorschlag, einen Datenspeicher wie Redis für Sitzungsdaten zu verwenden (je nach Anwendung), umgesetzt werden. Eine Beschreibung hierzu siehe [Mehrere Knoten verwenden](http://socket.io/docs/using-multiple-nodes/).
+Unabhängig davon, wie gut eine Anwendung optimiert wurde, kann eine Einzelinstanz nur eine begrenzte Arbeitslast oder einen begrenzten Datenverkehr handhaben. Eine Möglichkeit, eine Anwendung zu skalieren, ist die Ausführung mehrerer Instanzen dieser Anwendung und die Verteilung des Datenverkehrs über eine Lastausgleichsfunktion (Load Balancer) vorzunehmen. Die Einrichtung eines solchen Load Balancer kann helfen, Leistung und Geschwindigkeit Ihrer Anwendung zu verbessern.
-#### StrongLoop Process Manager mit einem Nginx Load Balancer verwenden
+Ein Load Balancer ist in der Regel ein Reverse Proxy, der den Datenverkehr zu und von mehreren Anwendungsinstanzen und Servern koordiniert. You can easily set up a load balancer for your app by using [Nginx](https://nginx.org/en/docs/http/load_balancing.html) or [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
-[StrongLoop Process Manager](http://strong-pm.io/) lässt sich in einen Nginx-Controller integrieren und erleichtert dadurch das Konfigurieren von Produktionsumgebungen mit mehreren Hosts. Weitere Informationen finden Sie im Thema zum [Skalieren auf mehrere Server](https://docs.strongloop.com/display/SLC/Scaling+to+multiple+servers) (in der StrongLoop-Dokumentation).
-
+Bei einer solchen Lastverteilung müssen Sie sicherstellen, dass Anforderungen, die einer bestimmten Sitzungs-ID zugeordnet sind, mit dem Prozess verbunden sind, von dem sie ursprünglich stammen. Dies wird auch als _Sitzungsaffinität_ oder _Affine Sitzungen_ bezeichnet und kann durch den obigen Vorschlag, einen Datenspeicher wie Redis für Sitzungsdaten zu verwenden (je nach Anwendung), umgesetzt werden. Eine Beschreibung hierzu siehe [Mehrere Knoten verwenden](https://socket.io/docs/v4/using-multiple-nodes/).
### Reverse Proxy verwenden
-Ein Reverse Proxy befindet sich vor einer Webanwendung und führt Unterstützungsoperationen für die Anforderungen aus (außer das Weiterleiten von Anforderungen an die Anwendung). Er kann u. a. Fehlerseiten, Komprimierungen und Caching bearbeiten, Dateien bereitstellen und Lastverteilungen vornehmen.
+Ein Reverse Proxy befindet sich vor einer Webanwendung und führt Unterstützungsoperationen für die Anforderungen aus (außer das Weiterleiten von Anforderungen an die Anwendung). Fehlerseiten, Komprimierungen und Caching bearbeiten, Dateien bereitstellen und Lastverteilungen vornehmen.
-Durch die Übergabe von Tasks, die keine Kenntnis des Anwendungsstatus erfordern, an einen Reverse Proxy muss Express keine speziellen Anwendungstasks mehr ausführen. Aus diesem Grund wird empfohlen, in Produktionsumgebungen Express hinter einem Reverse Proxy wie [Nginx](https://www.nginx.com/) oder [HAProxy](http://www.haproxy.org/) auszuführen.
+Durch die Übergabe von Tasks, die keine Kenntnis des Anwendungsstatus erfordern, an einen Reverse Proxy muss Express keine speziellen Anwendungstasks mehr ausführen. For this reason, it is recommended to run Express behind a reverse proxy like [Nginx](https://www.nginx.org/) or [HAProxy](https://www.haproxy.org/) in production.
diff --git a/de/advanced/best-practice-security.md b/de/advanced/best-practice-security.md
old mode 100755
new mode 100644
index 7d6fd4cba5..8f4f23219d
--- a/de/advanced/best-practice-security.md
+++ b/de/advanced/best-practice-security.md
@@ -1,20 +1,46 @@
---
layout: page
title: Sicherheitsspezifische Best Practices für Express-Anwendungen in Produktionsumgebungen
+description: Discover crucial security best practices for Express apps in production, including using TLS, input validation, secure cookies, and preventing vulnerabilities.
menu: advanced
-lang: de
+redirect_from: " "
---
# Best Practices in Produktionsumgebungen: Sicherheit
## Überblick
-Der Begriff *"Produktion"* bezieht sich auf die Phase im Softwarelebenszyklus, in der eine Anwendung oder API für Endbenutzer oder Verbraucher allgemein verfügbar ist. Im Gegensatz dazu wird in der Phase *"Entwicklung"* noch aktiv Code geschrieben und getestet. Die Anwendung ist in dieser Phase noch nicht für externen Zugriff verfügbar. Die entsprechenden Systemumgebungen werden als *Produktionsumgebungen* und *Entwicklungsumgebungen* bezeichnet.
+Der Begriff _"Produktion"_ bezieht sich auf die Phase im Softwarelebenszyklus, in der eine Anwendung oder API für Endbenutzer oder Verbraucher allgemein verfügbar ist. Im Gegensatz dazu wird in der Phase _"Entwicklung"_ noch aktiv Code geschrieben und getestet. Die Anwendung ist in dieser Phase noch nicht für externen Zugriff verfügbar. Die entsprechenden Systemumgebungen werden als _Produktionsumgebungen_ und _Entwicklungsumgebungen_ bezeichnet.
Entwicklungs- und Produktionsumgebungen werden in der Regel unterschiedlich konfiguriert und weisen deutliche Unterschiede bei den Anforderungen auf. Was in der Entwicklung funktioniert, muss in der Produktion nicht unbedingt akzeptabel sein. Beispiel: In einer Entwicklungsumgebung ist eine ausführliche Protokollierung von Fehlern für Debuggingzwecke sinnvoll. Dieselbe Vorgehensweise kann in einer Produktionsumgebung jedoch zu einem Sicherheitsproblem führen. In einer Entwicklungsumgebung müssen Sie sich keine Gedanken zu Themen wie Skalierbarkeit, Zuverlässigkeit und Leistung machen, während dies in einer Produktionsumgebung kritische Faktoren sind.
+{% capture security-note %}
+
+If you believe you have discovered a security vulnerability in Express, please see
+[Security Policies and Procedures](/en/resources/contributing.html#security-policies-and-procedures).
+
+{% endcapture %}
+
+{% include admonitions/note.html content=security-note %}
+
In diesem Beitrag werden einige der Best Practices in Bezug auf das Thema Sicherheit für Express-Anwendungen behandelt, die in der Produktionsumgebung bereitgestellt werden.
+- [Production Best Practices: Security](#production-best-practices-security)
+ - [Overview](#overview)
+ - [Don't use deprecated or vulnerable versions of Express](#dont-use-deprecated-or-vulnerable-versions-of-express)
+ - Über [hsts](https://github.com/helmetjs/hsts) werden `Strict-Transport-Security`-Header festgelegt, über die sichere (HTTP over SSL/TLS) Verbindungen zum Server durchgesetzt werden.
+ - [Do not trust user input](#do-not-trust-user-input)
+ - [Prevent open redirects](#prevent-open-redirects)
+ - "Helmet" ist eine Ansammlung von neun kleineren Middlewarefunktionen, über die sicherheitsrelevante HTTP-Header festgelegt werden.
+ - [Reduce fingerprinting](#reduce-fingerprinting)
+ - Über [xssFilter](https://github.com/helmetjs/x-xss-protection) werden `X-XSS-Protection`-Header festgelegt, um XSS-Filter (Cross-site Scripting) in den meisten aktuellen Web-Browsern zu aktivieren.
+ - Über [noCache](https://github.com/helmetjs/nocache) werden `Cache-Control`- und Pragma-Header festgelegt, um clientseitiges Caching zu deaktivieren.
+ - Über [ieNoOpen](https://github.com/helmetjs/ienoopen) werden `X-Download-Options`-Header für IE8+ festgelegt.
+ - [Prevent brute-force attacks against authorization](#prevent-brute-force-attacks-against-authorization)
+ - [Ensure your dependencies are secure](#ensure-your-dependencies-are-secure)
+ - [Avoid other known vulnerabilities](#avoid-other-known-vulnerabilities)
+ - [Additional considerations](#additional-considerations)
+
## Verwenden Sie keine veralteten oder anfälligen Versionen von Express
Express 2.x und 3.x werden nicht mehr gepflegt. Sicherheits- und Leistungsprobleme in diesen Versionen werden nicht mehr behoben. Verwenden Sie diese Versionen nicht! Wenn Sie noch nicht auf Version 4 umgestellt haben, befolgen Sie die Anweisungen im [Migrationshandbuch](/{{ page.lang }}/guide/migrating-4.html).
@@ -25,57 +51,121 @@ Stellen Sie außerdem sicher, dass Sie keine anfälligen Express-Versionen verwe
Wenn über Ihre Anwendung vertrauliche Daten bearbeitet oder übertragen werden, sollten Sie [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (TLS) verwenden, um die Verbindung und die Daten zu schützen. Diese Technologie verschlüsselt Daten, bevor sie vom Client zum Server gesendet werden. Dadurch lassen sich einige gängige (und einfache) Hackerattacken vermeiden. Auch wenn Ajax- und POST-Anforderungen nicht sofort offensichtlich und in Browsern "versteckt" zu sein scheinen, ist deren Netzverkehr anfällig für das [Ausspionieren von Paketen](https://en.wikipedia.org/wiki/Packet_analyzer) und [Man-in-the-Middle-Attacken](https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
-Möglicherweise sind Sie mit SSL-Verschlüsselung (Secure Socket Layer) bereits vertraut. [TLS ist einfach der nächste Entwicklungsschritt bei SSL](https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515(v=vs.85).aspx). In anderen Worten: Wenn Sie bisher SSL verwendet haben, sollten Sie ein Upgrade auf TLS in Erwägung ziehen. Generell empfehlen wir für TLS den Nginx-Server. Eine gute Referenz zum Konfigurieren von TLS auf Nginx (und anderen Servern) ist [Empfohlene Serverkonfigurationen (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
+Möglicherweise sind Sie mit SSL-Verschlüsselung (Secure Socket Layer) bereits vertraut. [TLS ist einfach der nächste Entwicklungsschritt bei SSL](https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515\(v=vs.85\).aspx). In anderen Worten: Wenn Sie bisher SSL verwendet haben, sollten Sie ein Upgrade auf TLS in Erwägung ziehen. Generell empfehlen wir für TLS den Nginx-Server. Eine gute Referenz zum Konfigurieren von TLS auf Nginx (und anderen Servern) ist [Empfohlene Serverkonfigurationen (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
Ein handliches Tool zum Abrufen eines kostenloses TLS-Zertifikats ist außerdem [Let's Encrypt](https://letsencrypt.org/about/), eine kostenlose, automatisierte und offene Zertifizierungsstelle der [Internet Security Research Group (ISRG)](https://letsencrypt.org/isrg/).
+## Do not trust user input
+
+For web applications, one of the most critical security requirements is proper user input validation and handling. This comes in many forms and we will not cover all of them here.
+Ultimately, the responsibility for validating and correctly handling the types of user input your application accepts is yours.
+
+### Prevent open redirects
+
+An example of potentially dangerous user input is an _open redirect_, where an application accepts a URL as user input (often in the URL query, for example `?url=https://example.com`) and uses `res.redirect` to set the `location` header and
+return a 3xx status.
+
+An application must validate that it supports redirecting to the incoming URL to avoid sending users to malicious links such as phishing websites, among other risks.
+
+Here is an example of checking URLs before using `res.redirect` or `res.location`:
+
+```js
+app.use((req, res) => {
+ try {
+ if (new Url(req.query.url).host !== 'example.com') {
+ return res.status(400).end(`Unsupported redirect to host: ${req.query.url}`)
+ }
+ } catch (e) {
+ return res.status(400).end(`Invalid url: ${req.query.url}`)
+ }
+ res.redirect(req.query.url)
+})
+```
+
## "Helmet" verwenden
[Helmet](https://www.npmjs.com/package/helmet) kann beim Schutz Ihrer Anwendung gegen einige gängige Schwachstellen hilfreiche Dienste leisten, indem die HTTP-Header entsprechend konfiguriert werden.
-"Helmet" ist eine Ansammlung von neun kleineren Middlewarefunktionen, über die sicherheitsrelevante HTTP-Header festgelegt werden.
+Helmet is a middleware function that sets security-related HTTP response headers. Helmet sets the following headers by default:
+
+- `Content-Security-Policy`: A powerful allow-list of what can happen on your page which mitigates many attacks
+- `Cross-Origin-Opener-Policy`: Helps process-isolate your page
+- `Cross-Origin-Resource-Policy`: Blocks others from loading your resources cross-origin
+- `Origin-Agent-Cluster`: Changes process isolation to be origin-based
+- `Referrer-Policy`: Controls the [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer) header
+- `Strict-Transport-Security`: Tells browsers to prefer HTTPS
+- `X-Content-Type-Options`: Avoids [MIME sniffing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
+- `X-DNS-Prefetch-Control`: Controls DNS prefetching
+- `X-Download-Options`: Forces downloads to be saved (Internet Explorer only)
+- `X-Frame-Options`: Legacy header that mitigates [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking) attacks
+- `X-Permitted-Cross-Domain-Policies`: Controls cross-domain behavior for Adobe products, like Acrobat
+- `X-Powered-By`: Info about the web server. Removed because it could be used in simple attacks
+- `X-XSS-Protection`: Legacy header that tries to mitigate [XSS attacks](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting), but makes things worse, so Helmet disables it
-* Über [csp](https://github.com/helmetjs/csp) wird der `Content-Security-Policy`-Header festgelegt, um Cross-Site Scripting-Attacken und anderen standortübergreifenden Injektionen vorzubeugen.
-* Über [hidePoweredBy](https://github.com/helmetjs/hide-powered-by) wird der `X-Powered-By`-Header entfernt.
-* Über [hsts](https://github.com/helmetjs/hsts) werden `Strict-Transport-Security`-Header festgelegt, über die sichere (HTTP over SSL/TLS) Verbindungen zum Server durchgesetzt werden.
-* Über [ieNoOpen](https://github.com/helmetjs/ienoopen) werden `X-Download-Options`-Header für IE8+ festgelegt.
-* Über [noCache](https://github.com/helmetjs/nocache) werden `Cache-Control`- und Pragma-Header festgelegt, um clientseitiges Caching zu deaktivieren.
-* Über [noSniff](https://github.com/helmetjs/dont-sniff-mimetype) werden `X-Content-Type-Options`-Header festgelegt, um bei Browsern MIME-Sniffing von Antworten weg vom deklarierten Inhaltstyp (declared content-type) vorzubeugen.
-* Über [frameguard](https://github.com/helmetjs/frameguard) wird der `X-Frame-Options`-Header festgelegt, um [Clickjacking](https://www.owasp.org/index.php/Clickjacking)-Schutz zu gewährleisten.
-* Über [xssFilter](https://github.com/helmetjs/x-xss-protection) werden `X-XSS-Protection`-Header festgelegt, um XSS-Filter (Cross-site Scripting) in den meisten aktuellen Web-Browsern zu aktivieren.
+Each header can be configured or disabled. To read more about it please go to [its documentation website][helmet].
Installieren Sie "Helmet" wie alle anderen Module:
-
-
-$ npm install --save helmet
-
-
+```bash
+$ npm install helmet
+```
So verwenden Sie "Helmet" in Ihrem Code:
-
-
-...
-var helmet = require('helmet');
-app.use(helmet());
-...
-
-
+```js
+// ...
+
+const helmet = require('helmet')
+app.use(helmet())
+
+// ...
+```
-### Deaktivieren Sie mindestens den X-Powered-By-Header
+## Reduce fingerprinting
-Wenn Sie "Helmet" nicht verwenden wollen, sollten Sie mindestens den `X-Powered-By`-Header deaktivieren. Angreifer können diesen Header (der standardmäßig aktiviert ist) zum Erkennen von Anwendungen mit Express verwenden und dann gezielte Attacken in die Wege leiten.
+It can help to provide an extra layer of security to reduce the ability of attackers to determine
+the software that a server uses, known as "fingerprinting." Though not a security issue itself,
+reducing the ability to fingerprint an application improves its overall security posture.
+Server software can be fingerprinted by quirks in how it responds to specific requests, for example in
+the HTTP response headers.
Ein bewährtes Verfahren ist also, diesen Header mit der Methode `app.disable()` zu deaktivieren:
-
-
-app.disable('x-powered-by');
-
-
+```js
+app.disable('x-powered-by')
+```
+
+{% capture powered-advisory %}
+
+Disabling the `X-Powered-By header` does not prevent
+a sophisticated attacker from determining that an app is running Express. It may
+discourage a casual exploit, but there are other ways to determine an app is running
+Express.
+
+{% endcapture %}
+
+{% include admonitions/note.html content=powered-advisory %}
+
+Express also sends its own formatted "404 Not Found" messages and formatter error
+response messages. These can be changed by
+[adding your own not found handler](/en/starter/faq.html#how-do-i-handle-404-responses)
+and
+[writing your own error handler](/en/guide/error-handling.html#writing-error-handlers):
-Wenn Sie `helmet.js` verwenden, kümmert sich das Tool darum.
+```js
+// last app.use calls right before app.listen():
+
+// custom 404
+app.use((req, res, next) => {
+ res.status(404).send("Sorry can't find that!")
+})
+
+// custom error handler
+app.use((err, req, res, next) => {
+ console.error(err.stack)
+ res.status(500).send('Something broke!')
+})
+```
## Cookies sicher verwenden
@@ -83,8 +173,8 @@ Um sicherzustellen, dass Cookies Ihre Anwendung nicht für Angriffsmöglichkeite
Es gibt zwei wesentliche Middleware-Cookie-Sitzungsmodule:
-* [express-session](https://www.npmjs.com/package/express-session), das in Express 3.x integrierte `express.session`-Middleware ersetzt.
-* [cookie-session](https://www.npmjs.com/package/cookie-session), das in Express 3.x integrierte `express.cookieSession`-Middleware ersetzt.
+- [express-session](https://www.npmjs.com/package/express-session), das in Express 3.x integrierte `express.session`-Middleware ersetzt.
+- [cookie-session](https://www.npmjs.com/package/cookie-session), das in Express 3.x integrierte `express.cookieSession`-Middleware ersetzt.
Der Hauptunterschied zwischen diesen beiden Modulen liegt darin, wie die Cookie-Sitzungsdaten gespeichert werden. Die [express-session](https://www.npmjs.com/package/express-session)-Middleware speichert Sitzungsdaten auf dem Server. Sie speichert nur die Sitzungs-ID im Cookie und nicht die Sitzungsdaten. Standardmäßig wird dabei der speicherinterne Speicher verwendet. Eine Verwendung der Middleware in der Produktionsumgebung ist nicht vorgesehen. In der Produktionsumgebung müssen Sie einen skalierbaren "Session-Store" einrichten. Siehe hierzu die Liste der [kompatiblen Session-Stores](https://github.com/expressjs/session#compatible-session-stores).
@@ -94,67 +184,98 @@ Im Gegensatz dazu implementiert die [cookie-session](https://www.npmjs.com/packa
Die Verwendung des standardmäßigen Namens des Sitzungscookies kann Ihre Anwendung anfällig für Attacken machen. Das mögliche Sicherheitsproblem ist vergleichbar mit `X-Powered-By`: ein potenzieller Angreifer kann diesen Header verwenden, um einen elektronischen Fingerabdruck des Servers zu erstellen und Attacken entsprechend zu platzieren.
-Dieses Problem lässt sich vermeiden, wenn Sie allgemeine Cookienamen verwenden; z. B. durch Verwendung der [express-session](https://www.npmjs.com/package/express-session)-Middleware:
+Über [noSniff](https://github.com/helmetjs/dont-sniff-mimetype) werden `X-Content-Type-Options`-Header festgelegt, um bei Browsern MIME-Sniffing von Antworten weg vom deklarierten Inhaltstyp (declared content-type) vorzubeugen.
-
-
-var session = require('express-session');
+```js
+const session = require('express-session')
app.set('trust proxy', 1) // trust first proxy
-app.use( session({
- secret : 's3Cur3',
- name : 'sessionId',
- })
-);
-
-
+app.use(session({
+ secret: 's3Cur3',
+ name: 'sessionId'
+}))
+```
### Cookie-Sicherheitsoptionen festlegen
Legen Sie die folgenden Cookieoptionen fest, um die Sicherheit zu erhöhen:
-* `secure` - Stellt sicher, dass der Browser das Cookie nur über HTTPS sendet.
-* `httpOnly` - Stellt sicher, dass das Cookie nur über HTTP(S) und nicht über das Client-JavaScript gesendet wird und dadurch Schutz gegen Cross-Site Scripting-Attacken besteht.
-* `domain` - Gibt die Domäne des Cookies an, die für den Vergleich mit der Domäne des Servers verwendet wird, in der die URL angefordert wird. Stimmen diese beiden überein, müssen Sie das Pfadattribut überprüfen.
-* `path` - Gibt den Pfad des Cookies an, der für den Vergleich mit dem Anforderungspfad verwendet wird. Wenn dieser Pfad und die Domäne übereinstimmen, können Sie das Cookie in der Anforderung senden.
-* `expires` - Wird verwendet, um das Ablaufdatum für persistente Cookies festzulegen.
+- `secure` - Stellt sicher, dass der Browser das Cookie nur über HTTPS sendet.
+- `httpOnly` - Stellt sicher, dass das Cookie nur über HTTP(S) und nicht über das Client-JavaScript gesendet wird und dadurch Schutz gegen Cross-Site Scripting-Attacken besteht.
+- `domain` - Gibt die Domäne des Cookies an, die für den Vergleich mit der Domäne des Servers verwendet wird, in der die URL angefordert wird. Stimmen diese beiden überein, müssen Sie das Pfadattribut überprüfen.
+- `path` - Gibt den Pfad des Cookies an, der für den Vergleich mit dem Anforderungspfad verwendet wird. Wenn dieser Pfad und die Domäne übereinstimmen, können Sie das Cookie in der Anforderung senden.
+- `expires` - Wird verwendet, um das Ablaufdatum für persistente Cookies festzulegen.
Dies ist ein Beispiel zur Verwendung der [cookie-session](https://www.npmjs.com/package/cookie-session)-Middleware:
-
-
-var session = require('cookie-session');
-var express = require('express');
-var app = express();
+```js
+const session = require('cookie-session')
+const express = require('express')
+const app = express()
-var expiryDate = new Date( Date.now() + 60 * 60 * 1000 ); // 1 hour
+const expiryDate = new Date(Date.now() + 60 * 60 * 1000) // 1 hour
app.use(session({
name: 'session',
keys: ['key1', 'key2'],
- cookie: { secure: true,
- httpOnly: true,
- domain: 'example.com',
- path: 'foo/bar',
- expires: expiryDate
- }
- })
-);
-
-
+ cookie: {
+ secure: true,
+ httpOnly: true,
+ domain: 'example.com',
+ path: 'foo/bar',
+ expires: expiryDate
+ }
+}))
+```
-## Weitere Überlegungen
+## Prevent brute-force attacks against authorization
+
+Make sure login endpoints are protected to make private data more secure.
+
+A simple and powerful technique is to block authorization attempts using two metrics:
+
+1. The number of consecutive failed attempts by the same user name and IP address.
+2. The number of failed attempts from an IP address over some long period of time. For example, block an IP address if it makes 100 failed attempts in one day.
+
+[rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) package provides tools to make this technique easy and fast. You can find [an example of brute-force protection in the documentation](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
+
+## Ensure your dependencies are secure
+
+Using npm to manage your application's dependencies is powerful and convenient. But the packages that you use may contain critical security vulnerabilities that could also affect your application. The security of your app is only as strong as the "weakest link" in your dependencies.
-Dies sind einige weitere Empfehlungen aus der hervorragenden [Node.js Security Checklist](https://blog.risingstack.com/node-js-security-checklist/). In diesem Blogbeitrag finden Sie alle Details zu diesen Empfehlungen:
+Since npm@6, npm automatically reviews every install request. Also, you can use `npm audit` to analyze your dependency tree.
-* Implementieren Sie Rate-Limiting, um Brute-Force-Attacken gegen Authentifizierungen zu verhindern. Hierfür können Sie beispielsweise das [StrongLoop API Gateway](https://strongloop.com/node-js/api-gateway/) verwenden, um eine Rate-Limiting-Richtlinie durchzusetzen. Alternativ können Sie eine Middleware wie [express-limiter](https://www.npmjs.com/package/express-limiter) verwenden. Hierzu müssen Sie jedoch Ihren Code etwas modifizieren.
-* Verwenden Sie die [csurf](https://www.npmjs.com/package/csurf)-Middleware, um CSRF-Attacken (Cross-Site Request Forgery) vorzubeugen.
-* Filtern und bereinigen Sie immer Benutzereingaben, um sich gegen XS-Angriffe (Cross-Site Scripting) und Befehlsinjektionsattacken zu schützen.
-* Implementieren Sie Verteidungsmaßnahmen gegen SQL-Injection-Attacken, indem sie parametrisierte Abfragen oder vorbereitete Anweisungen einsetzen.
-* Nutzen Sie das Open-Source-Tool [sqlmap](http://sqlmap.org/), um SQL-Injection-Schwachstellen in Ihrer Anwendung zu erkennen.
-* Verwenden Sie die Tools [nmap](https://nmap.org/) und [sslyze](https://github.com/nabla-c0d3/sslyze), um die Konfiguration Ihrer SSL-Verschlüsselungen, -Schlüssel und Neuvereinbarungen sowie die Gültigkeit Ihres Zertifikats zu testen.
-* Verwenden Sie [safe-regex](https://www.npmjs.com/package/safe-regex), um sicherzustellen, dass Ihre regulären Ausdrücke nicht für [Denial-of-Service-Attacken](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS) anfällig sind.
+```bash
+$ npm audit
+```
-## Vermeiden Sie andere Schwachstellen
+If you want to stay more secure, consider [Snyk](https://snyk.io/).
+
+Snyk offers both a [command-line tool](https://www.npmjs.com/package/snyk) and a [Github integration](https://snyk.io/docs/github) that checks your application against [Snyk's open source vulnerability database](https://snyk.io/vuln/) for any known vulnerabilities in your dependencies. Install the CLI as follows:
+
+```bash
+$ npm install -g snyk
+$ cd your-app
+```
+
+Use this command to test your application for vulnerabilities:
+
+```bash
+$ snyk test
+```
+
+### Vermeiden Sie andere Schwachstellen
Achten Sie auf [Node Security Project](https://npmjs.com/advisories)-Empfehlungen, die Express oder andere Module, die Ihre Anwendung nutzt, beeinträchtigen können. Im Allgemeinen ist Node Security Project aber eine exzellente Ressource mit Wissen und Tools zur Sicherheit von Node.
-Letztendlich können Express-Anwendungen – wie viele andere Webanwendungen auch – anfällig für eine Vielzahl webbasierter Attacken sein. Machen Sie sich deshalb mit bekannten [webspezifischen Schwachstellen](https://www.owasp.org/index.php/Top_10_2013-Top_10) vertraut und treffen Sie die geeigneten Vorkehrungen, um diese zu vermeiden.
+Letztendlich können Express-Anwendungen – wie viele andere Webanwendungen auch – anfällig für eine Vielzahl webbasierter Attacken sein. Machen Sie sich deshalb mit bekannten [webspezifischen Schwachstellen](https://www.owasp.org/www-project-top-ten/) vertraut und treffen Sie die geeigneten Vorkehrungen, um diese zu vermeiden.
+
+## Weitere Überlegungen
+
+Dies sind einige weitere Empfehlungen aus der hervorragenden [Node.js Security Checklist](https://blog.risingstack.com/node-js-security-checklist/). In diesem Blogbeitrag finden Sie alle Details zu diesen Empfehlungen:
+
+- Filtern und bereinigen Sie immer Benutzereingaben, um sich gegen XS-Angriffe (Cross-Site Scripting) und Befehlsinjektionsattacken zu schützen.
+- Implementieren Sie Verteidungsmaßnahmen gegen SQL-Injection-Attacken, indem sie parametrisierte Abfragen oder vorbereitete Anweisungen einsetzen.
+- Nutzen Sie das Open-Source-Tool [sqlmap](http://sqlmap.org/), um SQL-Injection-Schwachstellen in Ihrer Anwendung zu erkennen.
+- Verwenden Sie die Tools [nmap](https://nmap.org/) und [sslyze](https://github.com/nabla-c0d3/sslyze), um die Konfiguration Ihrer SSL-Verschlüsselungen, -Schlüssel und Neuvereinbarungen sowie die Gültigkeit Ihres Zertifikats zu testen.
+- Verwenden Sie [safe-regex](https://www.npmjs.com/package/safe-regex), um sicherzustellen, dass Ihre regulären Ausdrücke nicht für [Denial-of-Service-Attacken](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS) anfällig sind.
+
+[helmet]:
-
-var fs = require('fs'); // this engine requires the fs module
-app.engine('ntl', function (filePath, options, callback) { // define the template engine
- fs.readFile(filePath, function (err, content) {
- if (err) return callback(new Error(err));
+```js
+const fs = require('fs') // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => { // define the template engine
+ fs.readFile(filePath, (err, content) => {
+ if (err) return callback(err)
// this is an extremely simple template engine
- var rendered = content.toString().replace('#title#', ''+ options.title +' ')
- .replace('#message#', ''+ options.message +'
');
- return callback(null, rendered);
- });
-});
-app.set('views', './views'); // specify the views directory
-app.set('view engine', 'ntl'); // register the template engine
-
-
+ const rendered = content.toString()
+ .replace('#title#', `${options.message}
`) + return callback(null, rendered) + }) +}) +app.set('views', './views') // specify the views directory +app.set('view engine', 'ntl') // register the template engine +``` Ihre Anwendung ist jetzt in der Lage, `.ntl`-Dateien auszugeben. Erstellen Sie im Verzeichnis `views` eine Datei namens `index.ntl` mit dem folgenden Inhalt. -
-
+```pug
#title#
#message#
-
-
+```
+
Erstellen Sie dann in Ihrer Anwendung die folgende Route.
-
-
-app.get('/', function (req, res) {
- res.render('index', { title: 'Hey', message: 'Hello there!'});
-});
-
-
-Wenn Sie eine Anforderung zur Homepage einleiten, wird `index.ntl` im HTML-Format ausgegeben.
+
+```js
+app.get('/', (req, res) => {
+ res.render('index', { title: 'Hey', message: 'Hello there!' })
+})
+```
+
+Wenn Sie eine Anforderung zur Homepage einleiten, wird `index.ntl` im HTML-Format ausgegeben.
\ No newline at end of file
diff --git a/de/advanced/healthcheck-graceful-shutdown.md b/de/advanced/healthcheck-graceful-shutdown.md
new file mode 100644
index 0000000000..c1da62bfca
--- /dev/null
+++ b/de/advanced/healthcheck-graceful-shutdown.md
@@ -0,0 +1,33 @@
+---
+layout: page
+title: Health Checks and Graceful Shutdown
+description: Learn how to implement health checks and graceful shutdown in Express apps to enhance reliability, manage deployments, and integrate with load balancers like Kubernetes.
+menu: advanced
+redirect_from: " "
+---
+
+# Health Checks and Graceful Shutdown
+
+## Graceful shutdown
+
+When you deploy a new version of your application, you must replace the previous version. The process manager you're using will first send a SIGTERM signal to the application to notify it that it will be killed. Once the application gets this signal, it should stop accepting new requests, finish all the ongoing requests, clean up the resources it used, including database connections and file locks then exit.
+
+### Beispiel
+
+```js
+const server = app.listen(port)
+
+process.on('SIGTERM', () => {
+ debug('SIGTERM signal received: closing HTTP server')
+ server.close(() => {
+ debug('HTTP server closed')
+ })
+})
+```
+
+## Health checks
+
+A load balancer uses health checks to determine if an application instance is healthy and can accept requests. For example, [Kubernetes has two health checks](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
+
+- `liveness`, that determines when to restart a container.
+- `readiness`, that determines when a container is ready to start accepting traffic. When a pod is not ready, it is removed from the service load balancers.
\ No newline at end of file
diff --git a/de/advanced/pm.md b/de/advanced/pm.md
deleted file mode 100755
index c59e40eb87..0000000000
--- a/de/advanced/pm.md
+++ /dev/null
@@ -1,282 +0,0 @@
----
-layout: page
-title: Prozessmanager für Express-Anwendungen
-menu: advanced
-lang: de
----
-
-# Prozessmanager für Express-Anwendungen
-
-Wenn Sie Express-Anwendungen für Produktionsumgebungen ausführen, ist der Einsatz eines *Prozessmanagers* hilfreich, um folgende Aufgaben (Tasks) auszuführen:
-
-- Automatischer Neustart der Anwendung nach einem Absturz
-- Einblicke in die Laufzeitleistung und die Ressourcennutzung
-- Dynamische Änderung der Einstellungen zur Verbesserung des Leistungsverhaltens
-- Steuerung des Clustering
-
-Ein Prozessmanager ist vergleichbar mit einem Anwendungsserver: er ist ein "Container" für Anwendungen, der die Bereitstellung erleichtert, eine hohe Verfügbarkeit sicherstellt und die Verwaltung der Anwendung zur Laufzeit ermöglicht.
-
-Die gängigsten Prozessmanager für Express- und andere Node.js-Anwendungen sind:
-
-- [StrongLoop Process Manager](#sl)
-- [PM2](#pm2)
-- [Forever](#forever)
-
-
-Der Einsatz eines dieser drei Tools kann sehr hilfreich sein. StrongLoop Process Manager ist jedoch das einzige Tool, dass eine umfassende Laufzeit- und Bereitstellungslösung bietet, die den gesamten Node.js-Anwendungslebenszyklus abdeckt. Für jeden Schritt vor und nach der Produktion steht über eine einheitliche Schnittstelle ein Tool zur Verfügung.
-
-Nachfolgend finden Sie einen Kurzbeschreibung zu jedem dieser Tools.
-Einen ausführlichen Vergleich der Tools finden Sie unter [http://strong-pm.io/compare/](http://strong-pm.io/compare/).
-
-## StrongLoop Process Manager
-
-StrongLoop Process Manager (StrongLoop PM) ist ein Prozessmanager für Node.js-Anwendungen in Produktionsumgebungen. StrongLoop PM verfügt über integrierte Funktionen für Lastverteilung, Überwachung und Bereitstellung auf mehreren Hosts sowie eine grafische Konsole. Mit StrongLoop PM lassen sich die folgenden Aufgaben (Tasks) ausführen:
-
-- Erstellen, Packen und Bereitstellen Ihrer Node.js-Anwendung auf einem lokalen oder fernen System
-- Anzeige von CPU-Profilen und Heapspeichermomentaufnahmen (Heap-Snapshots) zur Optimierung der Leistung und Diagnose von Speicherlecks
-- Herstellen der dauerhaften Betriebsbereitschaft von Prozessen und Clustern
-- Anzeige von Leistungsmessdaten für Ihre Anwendung
-- Einfache Verwaltung von Bereitstellungen auf mehreren Hosts inkl. Nginx-Integration
-- Vereinheitlichung mehrerer StrongLoop PMs auf einer über Arc verwalteten verteilten Microservices-Laufzeitumgebung
-
-StrongLoop PM kann über ein leistungsfähiges Befehlszeilen-Schnittstellentool namens `slc` oder das grafisch orientierte Tool Arc genutzt werden. Arc ist ein Open-Source-Tool, das von StrongLoop kompetent unterstützt wird.
-
-Weitere Informationen siehe [http://strong-pm.io/](http://strong-pm.io/).
-
-Vollständige Dokumentation
-
-- [Node-Anwendungen im Betrieb (in der StrongLoop-Dokumentation)](http://docs.strongloop.com/display/SLC)
-- [StrongLoop Process Manager verwenden](http://docs.strongloop.com/display/SLC/Using+Process+Manager)
-
-### Installation
-
-
-$ [sudo] npm install -g strongloop
-
-
-
-### Grundlegende Verwendung
-
-
-$ cd my-app
-$ slc start
-
-
-
-Anzeigen des Status von Process Manager und allen bereitgestellten Anwendungen:
-
-
-
-$ slc ctl
-Service ID: 1
-Service Name: my-app
-Environment variables:
- No environment variables defined
-Instances:
- Version Agent version Cluster size
- 4.1.13 1.5.14 4
-Processes:
- ID PID WID Listening Ports Tracking objects? CPU profiling?
- 1.1.57692 57692 0
- 1.1.57693 57693 1 0.0.0.0:3001
- 1.1.57694 57694 2 0.0.0.0:3001
- 1.1.57695 57695 3 0.0.0.0:3001
- 1.1.57696 57696 4 0.0.0.0:3001
-
-
-
-Auflisten aller verwalteten Anwendungen (Services):
-
-
-
-$ slc ctl ls
-Id Name Scale
- 1 my-app 1
-
-
-
-Stoppen einer Anwendung:
-
-
-
-$ slc ctl stop my-app
-
-
-
-Neustart einer Anwendung:
-
-
-
-$ slc ctl restart my-app
-
-
-
-Sie können auch einen "Soft Restart" durchführen, damit die Verarbeitungsprozesse eine Karenzzeit zum Schließen bestehender Verbindungen erhalten. Dann kann die aktuelle Anwendung neu gestartet werden:
-
-
-
-$ slc ctl soft-restart my-app
-
-
-
-Entfernen einer Anwendung aus dem Verwaltungsprozess:
-
-
-
-$ slc ctl remove my-app
-
-
-
-## PM2
-
-PM2 ist ein Prozessmanager für Node.js-Anwendungen in Produktionsumgebungen, der über eine integrierte Lastausgleichsfunktion verfügt. Mit PM2 lässt sich die dauerhafte Betriebsbereitschaft von Anwendungen sicherstellen. So können die Anwendungen ohne Ausfallzeiten erneut geladen werden, wodurch die Ausführung allgemeiner Systemverwaltungsaufgaben erleichtert wird. Über PM2 können auch Protokollierung, Überwachung und Clustering von Anwendungen vorgenommen werden.
-
-Weitere Informationen siehe [https://github.com/Unitech/pm2](https://github.com/Unitech/pm2).
-
-### Installation
-
-
-
-$ [sudo] npm install pm2 -g
-
-
-
-### Grundlegende Verwendung
-
-Wenn Sie eine Anwendung mit dem Befehl `pm2` starten, müssen Sie den Pfad zur Anwendung angeben. Wenn Sie eine Anwendung jedoch stoppen, neu starten oder löschen, können Sie auch nur den Namen oder die ID der Anwendung angeben.
-
-
-
-$ pm2 start npm --name my-app -- start
-[PM2] restartProcessId process id 0
-┌──────────┬────┬──────┬───────┬────────┬─────────┬────────┬─────────────┬──────────┐
-│ App name │ id │ mode │ pid │ status │ restart │ uptime │ memory │ watching │
-├──────────┼────┼──────┼───────┼────────┼─────────┼────────┼─────────────┼──────────┤
-│ my-app │ 0 │ fork │ 64029 │ online │ 1 │ 0s │ 17.816 MB │ disabled │
-└──────────┴────┴──────┴───────┴────────┴─────────┴────────┴─────────────┴──────────┘
- Use the `pm2 show ` command to get more details about an app.
-
-
-
-Wenn Sie eine Anwendung mit dem Befehl `pm2` starten, wird die Anwendung sofort in den Hintergrund gestellt. Sie können diese im Hintergrund laufende Anwendung über die Befehlszeile mit verschiedenen `pm2`-Befehlen steuern.
-
-nach dem Starten einer Anwendung mit dem Befehl `pm2` wird diese in der PM2-Prozessliste mit einer ID registriert. Sie können also Anwendungen mit demselben Namen aus verschiedenen Verzeichnissen auf dem System über deren ID verwalten.
-
-Beachten Sie Folgendes: Wenn mehrere Anwendungen mit demselben Namen ausgeführt werden, gelten die `pm2`-Befehle für alle Anwendungen. Verwenden Sie daher für das Verwalten einzelner Anwendungen IDs anstelle von Namen.
-
-Erstellen einer Liste aller aktiven Prozesse:
-
-
-
-$ pm2 list
-
-
-
-Stoppen einer Anwendung:
-
-
-
-$ pm2 stop 0
-
-
-
-Neustart einer Anwendung:
-
-
-
-$ pm2 restart 0
-
-
-
-Anzeige detaillierter Informationen zu einer Anwendung:
-
-
-
-$ pm2 show 0
-
-
-
-Entfernen einer Anwendung aus dem PM2-Register:
-
-
-
-$ pm2 delete 0
-
-
-
-
-## Forever
-
-Forever ist ein einfaches Befehlszeilen-Schnittstellentool, mit dem sichergestellt wird, dass ein Script kontinuierlich ausgeführt wird. Die einfache Benutzerschnittstelle von Forever eignet sich ideal für einfachere Bereitstellungen von Node.js-Anwendungen und Scripts.
-
-Weitere Informationen siehe [https://github.com/foreverjs/forever](https://github.com/foreverjs/forever).
-
-### Installation
-
-
-
-$ [sudo] npm install forever -g
-
-
-
-### Grundlegende Verwendung
-
-Verwenden Sie zum Starten eines Scripts den Befehl `forever start` und geben Sie den Pfad zum Script an:
-
-
-
-$ forever start script.js
-
-
-
-Dieser Befehl führt das Script im Dämonmodus (im Hintergrund) aus.
-
-Wenn Sie das Script so ausführen wollen, dass es an das Terminal angehängt wird, müssen Sie `start` weglassen:
-
-
-
-$ forever script.js
-
-
-
-Es ist sinnvoll, Ausgaben des Forever-Tools und des Scripts mit den Protokollierungsoptionen `-l`, `-o` und `-e` zu protokollieren (wie in diesem Beispiel gezeigt):
-
-
-
-$ forever start -l forever.log -o out.log -e err.log script.js
-
-
-
-Anzeigen der Liste mit Scripts, die über Forever gestartet wurden:
-
-
-
-$ forever list
-
-
-
-Stoppen eines Scripts, das über Forever gestartet wurde. Verwenden Sie hierzu den Befehl `forever stop` und geben Sie den Prozessindex an (der über den Befehl `forever list` erstellt wird).
-
-
-
-$ forever stop 1
-
-
-
-Geben Sie alternativ den Pfad zur Datei an:
-
-
-
-$ forever stop script.js
-
-
-
-Stoppen aller Scripts, die über Forever gestartet wurden:
-
-
-
-$ forever stopall
-
-
-
-Forever verfügt über eine Vielzahl von Optionen sowie eine programmgesteuerte API.
diff --git a/de/advanced/security-updates.md b/de/advanced/security-updates.md
old mode 100755
new mode 100644
index d63be11648..e882a9af54
--- a/de/advanced/security-updates.md
+++ b/de/advanced/security-updates.md
@@ -1,44 +1,87 @@
---
layout: page
title: Express-Sicherheitsupdates
+description: Review the latest security updates and patches for Express.js, including detailed vulnerability lists for different versions to help maintain a secure application.
menu: advanced
-lang: de
+redirect_from: " "
---
# Sicherheitsupdates
-Schwachstellen bei Node.js wirken sich direkt auf Express aus. Daher sollten Sie [ein Auge auf Schwachstellen bei Node.js haben](http://blog.nodejs.org/vulnerability/) und sicherstellen, dass Sie die aktuelle stabile Version von Node.js haben.
+Schwachstellen bei Node.js wirken sich direkt auf Express aus. Daher sollten Sie [ein Auge auf Schwachstellen bei Node.js haben](https://nodejs.org
+/en/blog/vulnerability/) und sicherstellen, dass Sie die aktuelle stabile Version von Node.js haben.
Die folgende Liste enthält die Express-Schwachstellen, die im angegebenen Versionsupdate behoben wurden.
+{% capture security-policy %}
+If you believe you have discovered a security vulnerability in Express, please see
+[Security Policies and Procedures](/{{page.lang}}/resources/contributing.html#security-policies-and-procedures).
+{% endcapture %}
+
+{% include admonitions/note.html content=security-policy %}
+
## 4.x
- * 4.11.1
- * Offenlegungsgefahr beim Rootpfad in `express.static`, `res.sendfile` und `res.sendFile` behoben.
- * 4.10.7
- * Offene Umadressierungsschwachstelle in `express.static` ([Empfehlung](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)) behoben.
- * 4.8.8
- * Schwachstellen durch Directory-Traversal-Technik in `express.static` ([Empfehlung](http://npmjs.com/advisories/32) , [CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)) behoben.
- * 4.8.4
- * Node.js 0.10 kann in bestimmten Situationen Lecks bei `fd` aufweisen, die sich auf `express.static` und `res.sendfile` auswirken. Böswillige Anforderungen können zu Lecks bei `fd` führen und letztendlich `EMFILE`-Fehler nach sich ziehen und bewirken, dass Server nicht antworten.
- * 4.8.0
- * Sparse-Arrays mit extrem hohen Indizes in der Abfragezeichenfolge können bewirken, dass für die Prozessausführung nicht genügend Arbeitsspeicher zur Verfügung steht und es zu einem Serverabsturz kommt.
- * Extrem verschachtelte Abfragezeichenfolgenobjekte können bewirken, dass der Prozess blockiert und der Server dadurch vorübergehend nicht antwortet.
+- 4.21.2
+ - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
+- 4.21.1
+ - The dependency `cookie` has been updated to address a [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), This may affect your application if you use `res.cookie`.
+- 4.20.0
+ - Fixed XSS vulnerability in `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
+ - The dependency `serve-static` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p).
+ - The dependency `send` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
+ - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
+ - The dependency `body-parser` has been updated to addres a [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), This may affect your application if you had url enconding activated.
+- 4.19.0, 4.19.1
+ - Fixed open redirect vulnerability in `res.location` and `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
+- 4.17.3
+ - The dependency `qs` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp). This may affect your application if the following APIs are used: `req.query`, `req.body`, `req.param`.
+- 4.16.0
+ - The dependency `forwarded` has been updated to address a [vulnerability](https://npmjs.com/advisories/527). This may affect your application if the following APIs are used: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
+ - The dependency `mime` has been updated to address a [vulnerability](https://npmjs.com/advisories/535), but this issue does not impact Express.
+ - The dependency `send` has been updated to provide a protection against a [Node.js 8.5.0 vulnerability](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/). This only impacts running Express on the specific Node.js version 8.5.0.
+- 4.15.5
+ - The dependency `debug` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:debug:20170905), but this issue does not impact Express.
+ - The dependency `fresh` has been updated to address a [vulnerability](https://npmjs.com/advisories/526). This will affect your application if the following APIs are used: `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`.
+- 4.15.3
+ - The dependency `ms` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:ms:20170412). This may affect your application if untrusted string input is passed to the `maxAge` option in the following APIs: `express.static`, `res.sendfile`, and `res.sendFile`.
+- 4.15.2
+ - The dependency `qs` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:qs:20170213), but this issue does not impact Express. Updating to 4.15.2 is a good practice, but not required to address the vulnerability.
+- 4.11.1
+ - Offenlegungsgefahr beim Rootpfad in `express.static`, `res.sendfile` und `res.sendFile` behoben.
+- 4.10.7
+ - Offene Umadressierungsschwachstelle in `express.static` ([Empfehlung](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)) behoben.
+- 4.8.8
+ - Schwachstellen durch Directory-Traversal-Technik in `express.static` ([Empfehlung](http://npmjs.com/advisories/32) , [CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)) behoben.
+- 4.8.4
+ - Node.js 0.10 kann in bestimmten Situationen Lecks bei `fd` aufweisen, die sich auf `express.static` und `res.sendfile` auswirken. Böswillige Anforderungen können zu Lecks bei `fd` führen und letztendlich `EMFILE`-Fehler nach sich ziehen und bewirken, dass Server nicht antworten.
+- 4.8.0
+ - Sparse-Arrays mit extrem hohen Indizes in der Abfragezeichenfolge können bewirken, dass für die Prozessausführung nicht genügend Arbeitsspeicher zur Verfügung steht und es zu einem Serverabsturz kommt.
+ - Extrem verschachtelte Abfragezeichenfolgenobjekte können bewirken, dass der Prozess blockiert und der Server dadurch vorübergehend nicht antwortet.
## 3.x
- * 3.19.1
- * Offenlegungsgefahr beim Rootpfad in `express.static`, `res.sendfile` und `res.sendFile` behoben.
- * 3.19.0
- * Offene Umadressierungsschwachstelle in `express.static` ([Empfehlung](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)) behoben.
- * 3.16.10
- * Schwachstellen durch Directory-Traversal-Technik in `express.static` behoben.
- * 3.16.6
- * Node.js 0.10 kann in bestimmten Situationen Lecks bei `fd` aufweisen, die sich auf `express.static` und `res.sendfile` auswirken. Böswillige Anforderungen können zu Lecks bei `fd` führen und letztendlich `EMFILE`-Fehler nach sich ziehen und bewirken, dass Server nicht antworten.
- * 3.16.0
- * Sparse-Arrays mit extrem hohen Indizes in der Abfragezeichenfolge können bewirken, dass für die Prozessausführung nicht genügend Arbeitsspeicher zur Verfügung steht und es zu einem Serverabsturz kommt.
- * Extrem verschachtelte Abfragezeichenfolgenobjekte können bewirken, dass der Prozess blockiert und der Server dadurch vorübergehend nicht antwortet.
- * 3.3.0
- * Die Antwort 404 bei einem nicht unterstützten Überschreibungsversuch war anfällig gegen Cross-Site Scripting-Attacken.
+
+ **Express 3.x WIRD NICHT MEHR GEWARTET**
+
+Bekannte und unbekannte Probleme bei Sicherheit und Leistung in 3.x wurden seit dem letzten Update (1. August 2015) noch nicht behoben. Es wird dringend empfohlen, die aktuelle Version von Express zu verwenden.
+
+If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
+
+
+
+- 3.19.1
+ - Offenlegungsgefahr beim Rootpfad in `express.static`, `res.sendfile` und `res.sendFile` behoben.
+- 3.19.0
+ - Offene Umadressierungsschwachstelle in `express.static` ([Empfehlung](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)) behoben.
+- 3.16.10
+ - Schwachstellen durch Directory-Traversal-Technik in `express.static` behoben.
+- 3.16.6
+ - Node.js 0.10 kann in bestimmten Situationen Lecks bei `fd` aufweisen, die sich auf `express.static` und `res.sendfile` auswirken. Böswillige Anforderungen können zu Lecks bei `fd` führen und letztendlich `EMFILE`-Fehler nach sich ziehen und bewirken, dass Server nicht antworten.
+- 3.16.0
+ - Sparse-Arrays mit extrem hohen Indizes in der Abfragezeichenfolge können bewirken, dass für die Prozessausführung nicht genügend Arbeitsspeicher zur Verfügung steht und es zu einem Serverabsturz kommt.
+ - Extrem verschachtelte Abfragezeichenfolgenobjekte können bewirken, dass der Prozess blockiert und der Server dadurch vorübergehend nicht antwortet.
+- 3.3.0
+ - Die Antwort 404 bei einem nicht unterstützten Überschreibungsversuch war anfällig gegen Cross-Site Scripting-Attacken.
\ No newline at end of file
diff --git a/de/api.md b/de/api.md
old mode 100755
new mode 100644
index fc5a006732..815162cbec
--- a/de/api.md
+++ b/de/api.md
@@ -1,25 +1,21 @@
---
-layout: 4x-api
-title: Express 4.x - API-Referenz
-lang: de
+layout: api
+version: 5x
+title: Express 5.x - API-Referenz
+description: Access the API reference for Express.js detailing all modules, methods, and properties for building web applications with this version.
+menu: api
+redirect_from: " "
---
-
-
-
-Die Festlegung eines anderen `trust proxy`-Werts als `false` resultiert in drei wichtigen Änderungen:
+Enabling `trust proxy` will have the following impact:
+When an error is written, the following information is added to the
+response:
+
+- The `res.statusCode` is set from `err.status` (or `err.statusCode`). If
+ this value is outside the 4xx or 5xx range, it will be set to 500.
+- The `res.statusMessage` is set according to the status code.
+- The body will be the HTML of the status code message when in production
+ environment, otherwise will be `err.stack`.
+- Any headers specified in an `err.headers` object.
+
Wenn `next()` mit einem Fehler aufgerufen wird, nachdem Sie mit dem Schreiben der Antwort begonnen haben (z. B., wenn Sie beim Streamen der Antwort zum Client einen Fehler feststellen), schließt die Standardfehlerbehandlungsroutine in Express die Verbindung, und die Anforderung schlägt fehl.
Wenn Sie also einen angepassten Error-Handler hinzufügen, empfiehlt es sich, eine Delegierung zur Standardfehlerbehandlungsroutine in Express vorzunehmen, wenn die Header bereits an den Client gesendet wurden:
-4.x-API
- - - {% include api/en/4x/express.md %} +
+
diff --git a/de/changelog/index.md b/de/changelog/index.md
new file mode 100644
index 0000000000..2456265b18
--- /dev/null
+++ b/de/changelog/index.md
@@ -0,0 +1,634 @@
+---
+layout: page
+title: Express changelog
+description: Stay updated with the release changelog for Express.js, detailing new features, bug fixes, and important changes across versions.
+sitemap: false
+redirect_from:
+ - " "
+ - " "
+---
+
+
+
+5.x API
+ {% include api/en/5x/express.md %} - {% include api/en/4x/app.md %} - + {% include api/en/5x/app.md %} - {% include api/en/4x/req.md %} - + {% include api/en/5x/req.md %} - {% include api/en/4x/res.md %} - + {% include api/en/5x/res.md %} - {% include api/en/4x/router.md %} - + {% include api/en/5x/router.md %}
+
+# Release changelog
+
+All the latest updates, improvements, and fixes to Express
+
+## Express v5
+
+{: id="5.x"}
+
+### 5.1.0 - Release date: 2025-03-31
+
+{: id="5.0.1"}
+
+The 5.1.0 minor release includes some new features and improvements:
+
+- Support for sending responses as Uint8Array
+- Added support for ETag option in `res.sendFile()`
+- Added support for adding multiple links with the same rel with `res.links()`
+- Performance: Use loop for acceptParams
+- [body-parser@2.2.0](https://github.com/expressjs/body-parser/releases/tag/v2.2.0)
+ - Remove legacy node.js support checks for Brotli & `AsyncLocalStorage`
+ - Remove `unpipe` & `destroy`
+- [router@2.2.0](https://github.com/pillarjs/router/releases/tag/v2.2.0)
+ - Restore `debug`. Now with the `router` scope instead of `express`.
+ - Remove legacy node.js support checks for `setImmediate`
+ - Deprecate non-native promise support
+ - Remove `after`, `safe-buffer`, `array-flatten`, `setprotoypeof`, `methods`, `utils-merge`
+- [finalhandler@2.1.0](https://github.com/pillarjs/finalhandler/releases/tag/v2.1.0)
+ - Remove legacy node.js support checks for `headersSent`, `setImmediate`, & http2 support
+ - Remove `unpipe`
+- Transitioned all remaining dependencies to use `^` ranges instead of locked versions
+- Add package.json funding field to highlight our OpenCollective
+- See [Changelog v5.1.0](https://github.com/expressjs/express/releases/tag/v5.1.0)
+
+### 5.0.1 - Release date: 2024-10-08
+
+{: id="5.0.1"}
+
+The 5.0.1 patch release includes one security fix:
+
+- Update [jshttps/cookie](https://www.npmjs.com/package/cookie) to address a [vulnerability](https://github.com/advisories/GHSA-pxg6-pf52-xh8x).
+
+### 5.0.0 - Release date: 2024-09-09
+
+{: id="5.0.0"}
+
+Check the [migration guide](/{{page.lang}}/guide/migrating-5.html) with all the changes in this new version of Express.
+
+## Express v4
+
+{: id="4.x"}
+
+### 4.21.2 - Release date: 2024-11-06
+
+{: id="4.21.2"}
+
+The 4.21.2 patch release includes one security fix:
+
+- Update [pillajs/path-to-regexp](https://www.npmjs.com/package/path-to-regexp) to address a [vulnerability](https://github.com/advisories/GHSA-rhx6-c78j-4q9w).
+
+### 4.21.1 - Release date: 2024-10-08
+
+{: id="4.21.1"}
+
+The 4.21.1 patch release includes one security fix:
+
+- Update [jshttps/cookie](https://www.npmjs.com/package/cookie) to address a [vulnerability](https://github.com/advisories/GHSA-pxg6-pf52-xh8x).
+
+### 4.21.0 - Release date: 2024-09-11
+
+{: id="4.21.0"}
+
+The 4.21.0 minor release includes one new feature:
+
+- Deprecate `res.location("back")` and `res.redirect("back")` magic string
+
+### 4.20.0 - Release date: 2024-09-10
+
+{: id="4.20.0"}
+
+The 4.20.0 minor release includes bug fixes and some new features, including:
+
+- The [`res.clearCookie()` method](/{{ page.lang }}/4x/api.html#res.clearCookie) deprecates `options.maxAge` and `options.expires` options.
+- The [`res.redirect()` method](/{{ page.lang }}/4x/api.html#res.redirect) removes HTML link rendering.
+- The [`express.urlencoded()` method](/{{ page.lang }}/4x/api.html#express.urlencoded) method now has a depth level of `32`, whereas it was previously `Infinity`.
+- Adds support for named matching groups in the routes using a regex
+- Removes encoding of `\`, `|`, and `^` to align better with URL spec
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4200--2024-09-10)
+
+### 4.19.2 - Release date: 2024-03-25
+
+{: id="4.19.2"}
+
+- Improved fix for open redirect allow list bypass
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4192--2024-03-25)
+
+### 4.19.1 - Release date: 2024-03-20
+
+{: id="4.19.1"}
+
+- Allow passing non-strings to res.location with new encoding handling checks
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4191--2024-03-20)
+
+### 4.19.0 - Release date: 2024-03-20
+
+{: id="4.19.0"}
+
+- Prevent open redirect allow list bypass due to encodeurl
+- deps: cookie@0.6.0
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4190--2024-03-20)
+
+### 4.18.3 - Release date: 2024-02-29
+
+{: id="4.18.3"}
+
+The 4.18.3 patch release includes the following bug fix:
+
+
diff --git a/de/guide/behind-proxies.md b/de/guide/behind-proxies.md
old mode 100755
new mode 100644
index 581aaca165..6dab4f9521
--- a/de/guide/behind-proxies.md
+++ b/de/guide/behind-proxies.md
@@ -1,73 +1,88 @@
---
layout: page
title: Express hinter Proxys
+description: Learn how to configure Express.js applications to work correctly behind reverse proxies, including using the trust proxy setting to handle client IP addresses.
menu: guide
-lang: de
+redirect_from: " "
---
# Express hinter Proxys
-Bei der Ausführung einer Express-Anwendung hinter einem Proxy legen Sie die Anwendungsvariable `trust proxy` (mithilfe von [app.set()](/{{ page.lang }}/4x/api.html#app.set)) auf einen der in der folgenden Tabelle enthaltenen Werte fest:
+When running an Express app behind a reverse proxy, some of the Express APIs may return different values than expected. In order to adjust for this, the `trust proxy` application setting may be used to expose information provided by the reverse proxy in the Express APIs. The most common issue is express APIs that expose the client's IP address may instead show an internal IP address of the reverse proxy.
-
+
- + Fix routing requests without method. ([commit](https://github.com/expressjs/express/commit/74beeac0718c928b4ba249aba3652c52fbe32ca8)) + +
-
+
- + Fix regression routing a large stack in a single route. ([commit](https://github.com/expressjs/express/commit/7ec5dd2b3c5e7379f68086dae72859f5573c8b9b)) + +
-
+
- + Fix the condition where if an Express application is created with a very large stack of routes, and all of those routes are sync (call `next()` synchronously), then the request processing may hang. + +
-
+
- + The [`app.get()` method](/{{ page.lang }}/4x/api.html#app.get) and the [`app.set()` method](/{{ page.lang }}/4x/api.html#app.set) now ignores properties directly on `Object.prototype` when getting a setting value. + + +
- + The [`res.cookie()` method](/{{ page.lang }}/4x/api.html#res.cookie) now accepts a "priority" option to set the Priority attribute on the Set-Cookie response header. + + +
- + The [`res.cookie()` method](/{{ page.lang }}/4x/api.html#res.cookie) now rejects an Invalid Date object provided as the "expires" option. + + +
- + The [`res.cookie()` method](/{{ page.lang }}/4x/api.html#res.cookie) now works when `null` or `undefined` is explicitly provided as the "maxAge" argument. + + +
- + Starting with this version, Express supports Node.js 18.x. + + +
- + The [`res.download()` method](/{{ page.lang }}/4x/api.html#res.download) now accepts a "root" option to match [`res.sendFile()`](/{{ page.lang }}/4x/api.html#res.sendFile). + + +
- + The [`res.download()` method](/{{ page.lang }}/4x/api.html#res.download) can be supplied with an `options` object without providing a `filename` argument, simplifying calls when the default `filename` is desired. + + +
- + The [`res.format()` method](/{{ page.lang }}/4x/api.html#res.format) now invokes the provided "default" handler with the same arguments as the type handlers (`req`, `res`, and `next`). + + +
- + The [`res.send()` method](/{{ page.lang }}/4x/api.html#res.send) will not attempt to send a response body when the response code is set to 205. + + +
- + The default error handler will now remove certain response headers that will break the error response rendering, if they were set previously. + + +
- + The status code 425 is now represented as the standard "Too Early" instead of "Unordered Collection". + +
-
+
- + Update to [qs module](https://www.npmjs.com/package/qs) for a fix around parsing `__proto__` properties. + +
-
+
- + Fix handling of `undefined` in `res.jsonp` when a callback is provided. + + +
- + Fix handling of `undefined` in `res.json` and `res.jsonp` when `"json escape"` is enabled. + + +
- + Fix handling of invalid values to the `maxAge` option of `res.cookie()`. + + +
- + Update to [jshttp/proxy-addr module](https://www.npmjs.com/package/proxy-addr) to use `req.socket` over deprecated `req.connection`. + + +
- + Starting with this version, Express supports Node.js 14.x. + + +
-
+
- + The change to the `res.status()` API has been reverted due to causing regressions in existing Express 4 applications. + +
-
+
- + The `express.raw()` and `express.text()` middleware have been added to provide request body parsing for more raw request payloads. This uses the [expressjs/body-parser module](https://www.npmjs.com/package/body-parser) module underneath, so apps that are currently requiring the module separately can switch to the built-in parsers. + + +
- + The `res.cookie()` API now supports the `"none"` value for the `sameSite` option. + + +
- + When the `"trust proxy"` setting is enabled, the `req.hostname` now supports multiple `X-Forwarded-For` headers in a request. + + +
- + Starting with this version, Express supports Node.js 10.x and 12.x. + + +
- + The `res.sendFile()` API now provides and more immediate and easier to understand error when a non-string is passed as the `path` argument. + + +
- + The `res.status()` API now provides and more immediate and easier to understand error when `null` or `undefined` is passed as the argument. + +
-
+
- + Fix issue where `"Request aborted"` may be logged in `res.sendfile`. + +
-
+
- + Fix issue where a plain `%` at the end of the url in the `res.location` method or the `res.redirect` method would not get encoded as `%25`. + + +
- + Fix issue where a blank `req.url` value can result in a thrown error within the default 404 handling. + + +
- + Fix the generated HTML document for `express.static` redirect responses to properly include ``. + +
-
+
- + Fix a `TypeError` that can occur in the `res.send` method when a `Buffer` is passed to `res.send` and the `ETag` header is already set on the response. + +
-
+
- + Update to [pillarjs/send module](https://www.npmjs.com/package/send) to fix an edge case scenario regression that affected certain users of `express.static`. + +
-
+
- + Update to [jshttp/forwarded module](https://www.npmjs.com/package/forwarded) to address a [vulnerability](https://npmjs.com/advisories/527). This may affect your application if the following APIs are used: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`. + + +
- + Update a dependency of the [pillarjs/send module](https://www.npmjs.com/package/send) to address a [vulnerability](https://npmjs.com/advisories/535) in the `mime` dependency. This may affect your application if untrusted string input is passed to the following APIs: `res.type()`. + + +
- + The [pillarjs/send module](https://www.npmjs.com/package/send) has implemented a protection against the Node.js 8.5.0 [vulnerability](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/). Using any prior version of Express with Node.js 8.5.0 (that specific Node.js version) will make the following APIs vulnerable: `express.static`, `res.sendfile`, and `res.sendFile`. + + +
- + Starting with this version, Express supports Node.js 8.x. + + +
- + The new setting `"json escape"` can be enabled to escape characters in `res.json()`, `res.jsonp()` and `res.send()` responses that can trigger clients to sniff the response as HTML instead of honoring the `Content-Type`. This can help protect an Express app from a class of persistent XSS-based attacks. + + +
- + The [`res.download()` method](/{{ page.lang }}/4x/api.html#res.download) now accepts an optional `options` object. + + +
- + The `express.json()` and `express.urlencoded()` middleware have been added to provide request body parsing support out-of-the-box. This uses the [expressjs/body-parser module](https://www.npmjs.com/package/body-parser) module underneath, so apps that are currently requiring the module separately can switch to the built-in parsers. + + +
- + The [`express.static()` middleware](/{{ page.lang }}/4x/api.html#express.static) and [`res.sendFile()` method](/{{ page.lang }}/4x/api.html#res.sendFile) now support setting the `immutable` directive on the `Cache-Control` header. Setting this header with an appropriate `maxAge` will prevent supporting web browsers from sending any request to the server when the file is still in their cache. + + +
- + The [pillarjs/send module](https://www.npmjs.com/package/send) has an updated list of MIME types to better set the `Content-Type` of more files. There are 70 new types for file extensions. + +
-
+
- + Update to [debug module](https://www.npmjs.com/package/debug) to address a [vulnerability](https://snyk.io/vuln/npm:debug:20170905), but this issue does not impact Express. + + +
- + Update to [jshttp/fresh module](https://www.npmjs.com/package/fresh) to address a [vulnerability](https://npmjs.com/advisories/526). This will affect your application if the following APIs are used: `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`. + + +
- + Update to [jshttp/fresh module](https://www.npmjs.com/package/fresh) fixes handling of modified headers with invalid dates and makes parsing conditional headers (like `If-None-Match`) faster. + +
-
+
- + Fix array being set for `"trust proxy"` value being manipulated in certain conditions. + +
-
+
- + Update a dependency of the [pillarjs/send module](https://www.npmjs.com/package/send) to address a [vulnerability](https://snyk.io/vuln/npm:ms:20170412). This may affect your application if untrusted string input is passed to the `maxAge` option in the following APIs: `express.static`, `res.sendfile`, and `res.sendFile`. + + +
- + Fix error when `res.set` cannot add charset to `Content-Type`. + + +
- + Fix missing `` in HTML document. + +
-
+
- + Fix regression parsing keys starting with `[` in the extended (default) query parser. + +
-
+
- + Fix compatibility issue when using the datejs 1.x library where the [`express.static()` middleware](/{{ page.lang }}/4x/api.html#express.static) and [`res.sendFile()` method](/{{ page.lang }}/4x/api.html#res.sendFile) would incorrectly respond with 412 Precondition Failed. + +
-
+
- + Starting with this version, Express supports Node.js 7.x. + + +
- + The [`express.static()` middleware](/{{ page.lang }}/4x/api.html#express.static) and [`res.sendFile()` method](/{{ page.lang }}/4x/api.html#res.sendFile) now support the `If-Match` and `If-Unmodified-Since` request headers. + + +
- + Update to [jshttp/etag module](https://www.npmjs.com/package/etag) to generate the default ETags for responses which work when Node.js has [FIPS-compliant crypto enabled](https://nodejs.org/dist/latest/docs/api/cli.html#cli_enable_fips). + + +
- + Various auto-generated HTML responses like the default not found and error handlers will respond with complete HTML 5 documents and additional security headers. + +
-
+
- + Update to [pillarjs/finalhandler module](https://www.npmjs.com/package/finalhandler) fixes an exception when Express handles an `Error` object which has a `headers` property that is not an object. + +
-
+
- + Starting with this version, Express supports Node.js 6.x. + + +
- + Update to [jshttp/negotiator module](https://www.npmjs.com/package/negotiator) fixes a [regular expression denial of service vulnerability](https://npmjs.com/advisories/106). + + +
- + The [`res.sendFile()` method](/{{ page.lang }}/4x/api.html#res.sendFile) now accepts two new options: `acceptRanges` and `cacheControl`. + +- `acceptRanges` (defaut is `true`), enables or disables accepting ranged requests. When disabled, the response does not send the `Accept-Ranges` header and ignores the contents of the `Range` request header. + +- `cacheControl`, (default is `true`), enables or disables the `Cache-Control` response header. Disabling it will ignore the `maxAge` option. + +- `res.sendFile` has also been updated to handle `Range` header and redirections better. + + + +
- + The [`res.location()` method](/{{ page.lang }}/4x/api.html#res.location) and [`res.redirect()` method](/{{ page.lang }}/4x/api.html#res.redirect) will now URL-encode the URL string, if it is not already encoded. + + +
- + The performance of the [`res.json()` method](/{{ page.lang }}/4x/api.html#res.json) and [`res.jsonp()` method](/{{ page.lang }}/4x/api.html#res.jsonp) have been improved in the common cases. + + +
- + The [jshttp/cookie module](https://www.npmjs.com/package/cookie) (in addition to a number of other improvements) has been updated and now the [`res.cookie()` method](/{{ page.lang }}/4x/api.html#res.cookie) supports the `sameSite` option to let you specify the [SameSite cookie attribute](https://tools.ietf.org/html/draft-west-first-party-cookies-07). + +{% capture note-4-14-0 %} + +``` +This attribute has not yet been fully standardized, may change in the future, and many clients may ignore it. +``` + +{% endcapture %} +{% include admonitions/note.html content=note-4-14-0 %} + +The possible value for the `sameSite` option are: + +- `true`, which sets the `SameSite` attribute to `Strict` for strict same site enforcement. +- `false`, which does not set the `SameSite` attribute. +- `'lax'`, which sets the `SameSite` attribute to `Lax` for lax same site enforcement. +- `'strict'`, which sets the `SameSite` attribute to `Strict` for strict same site enforcement. + + + +
- + Absolute path checking on Windows, which was incorrect for some cases, has been fixed. + + +
- + IP address resolution with proxies has been greatly improved. + + +
- + The [`req.range()` method](/{{ page.lang }}/4x/api.html#req.range) options object now supports a `combine` option (`false` by default), which when `true`, combines overlapping and adjacent ranges and returns them as if they were specified that way in the header. + +
-Auch wenn die Anwendungsausführung nicht fehlschlägt, wenn die Anwendungsvariable `trust proxy` nicht festgelegt wurde, wird die IP-Adresse des Proxys nicht ordnungsgemäß als Client-IP-Adresse eingetragen, es sei denn, `trust proxy` wurde konfiguriert.
+When configuring the `trust proxy` setting, it is important to understand the exact setup of the reverse proxy. Since this setting will trust values provided in the request, it is important that the combination of the setting in Express matches how the reverse proxy operates.
+Bei der Ausführung einer Express-Anwendung hinter einem Proxy legen Sie die Anwendungsvariable `trust proxy` (mithilfe von [app.set()](/{{ page.lang }}/4x/api.html#app.set)) auf einen der in der folgenden Tabelle enthaltenen Werte fest:
+
| Typ | Wert | |
|---|---|---|
| Boolesch | --Wenn `true` angegeben wird, wird die IP-Adresse des Clients als der äußerst rechte Eintrag im Header `X-Forwarded-*` interpretiert. + | Wenn `true` angegeben wird, wird die IP-Adresse des Clients als der äußerst rechte Eintrag im Header `X-Forwarded-*` interpretiert.
+
Wenn `false` angegeben wird, wird die Anwendung als direkte Verbindung zum Internet gesehen. Die IP-Adresse des Clients wird dann von `req.connection.remoteAddress` abgeleitet. Dies ist die Standardeinstellung.
+
+
+When setting to `true`, it is important to ensure that the last reverse proxy trusted is removing/overwriting all of the following HTTP headers: `X-Forwarded-For`, `X-Forwarded-Host`, and `X-Forwarded-Proto`, otherwise it may be possible for the client to provide any value.
+
|
| IP-Adressen | +IP addresses |
-Eine einzelne IP-Adresse, ein Teilnetz oder ein Array von IP-Adressen und Teilnetzen, denen vertraut werden kann. Die folgende Liste zeigt die vorkonfigurierten Teilnetznamen:
-* loopback - `127.0.0.1/8`, `::1/128`
-* linklocal - `169.254.0.0/16`, `fe80::/10`
-* uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`.
+An IP address, subnet, or an array of IP addresses and subnets to trust as being a reverse proxy. The following list shows the pre-configured subnet names:
+
+- loopback - `127.0.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
Sie können IP-Adressen wie folgt festlegen:
-
-
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']) // specify multiple subnets as an array
+```
+
+Sobald die Werte angegeben wurden, werden die betreffenden IP-Adressen und Teilnetze aus dem Adressfeststellungsprozess ausgeschlossen. Die nicht vertrauenswürdige IP-Adresse, die am nächsten zum Anwendungsserver liegt, wird als IP-Adresse des Clients festgelegt. This works by checking if `req.socket.remoteAddress` is trusted. If so, then each address in `X-Forwarded-For` is checked from right to left until the first non-trusted address.
-Sobald die Werte angegeben wurden, werden die betreffenden IP-Adressen und Teilnetze aus dem Adressfeststellungsprozess ausgeschlossen. Die nicht vertrauenswürdige IP-Adresse, die am nächsten zum Anwendungsserver liegt, wird als IP-Adresse des Clients festgelegt.
|
| Zahl |
-Dem `n`-ten Hop vom Proxy-Server soll als Client vertraut werden.
+Use the address that is at most `n` number of hops away from the Express application. `req.socket.remoteAddress` is the first hop, and the rest are looked for in the `X-Forwarded-For` header from right to left. A value of `0` means that the first untrusted address would be `req.socket.remoteAddress`, i.e. there is no reverse proxy.
+
+
+When using this setting, it is important to ensure there are not multiple, different-length paths to the Express application such that the client can be less than the configured number of hops away, otherwise it may be possible for the client to provide any value.
+
|
|
| Funktion | +Function |
-Individuell angepasste, vertrauenswürdige Implementierung. Dies sollten Sie nur verwenden, wenn Sie genau wissen, was Sie tun.
-
+Custom trust implementation.
+
+```js
+app.set('trust proxy', (ip) => {
+ if (ip === '127.0.0.1' || ip === '123.123.123.123') return true // trusted IPs
+ else return false
+})
+```
+
|
-
-
- Der Wert für [req.hostname](/{{ page.lang }}/api.html#req.hostname) wird vom Wert abgeleitet, der im Header `X-Forwarded-Host` festgelegt wurde. Dieser Wert kann vom Client oder Proxy festgelegt werden. - +
- Der Wert für [req.hostname](/{{ page.lang }}/api.html#req.hostname) wird vom Wert abgeleitet, der im Header `X-Forwarded-Host` festgelegt wurde. Dieser Wert kann vom Client oder Proxy festgelegt werden.
- `X-Forwarded-Proto` kann vom Reverse Proxy festgelegt werden, um der Anwendung mitzuteilen, ob es sich um `https` oder `http` oder sogar um einen ungültigen Namen handelt. Dieser Wert wird durch [req.protocol](/{{ page.lang }}/api.html#req.protocol) abgebildet.
- Als Werte für [req.ip](/{{ page.lang }}/api.html#req.ip) und [req.ips](/{{ page.lang }}/api.html#req.ips) wird die Liste der Adressen aus `X-Forwarded-For` herangezogen.
diff --git a/de/guide/database-integration.md b/de/guide/database-integration.md
old mode 100755
new mode 100644
index 1a43023cc4..3b20abc348
--- a/de/guide/database-integration.md
+++ b/de/guide/database-integration.md
@@ -1,225 +1,266 @@
---
layout: page
title: Datenbankintegration in Express
+description: Discover how to integrate various databases with Express.js applications, including setup examples for MongoDB, MySQL, PostgreSQL, and more.
menu: guide
-lang: de
+redirect_from: " "
---
# Datenbankintegration
Die Herstellung einer Verbindung zwischen Datenbanken und Express-Anwendungen erfolgt einfach durch Laden eines geeigneten Node.js-Treibers für die Datenbank in Ihre Anwendung. In diesem Dokument wird in Kurzform beschrieben, wie einige der gängigsten Node.js-Module für Datenbanksysteme Ihrer Express-Anwendung hinzugefügt und verwendet werden:
-* [Cassandra](#cassandra)
-* [CouchDB](#couchdb)
-* [LevelDB](#leveldb)
-* [MySQL](#mysql)
-* [MongoDB](#mongo)
-* [Neo4j](#neo4j)
-* [Oracle](#oracle)
-* [PostgreSQL](#postgres)
-* [Redis](#redis)
-* [SQLite](#sqlite)
-* [ElasticSearch](#elasticsearch)
+- [Cassandra](#cassandra)
+- [Couchbase](#couchbase)
+- [CouchDB](#couchdb)
+- [LevelDB](#leveldb)
+- [MySQL](#mysql)
+- [MongoDB](#mongo)
+- [Neo4j](#neo4j)
+- [Oracle](#oracle)
+- [PostgreSQL](#postgres)
+- [Redis](#redis)
+-
+- [SQLite](#sqlite)
+- [ElasticSearch](#elasticsearch)
Diese Datenbanktreiber sind neben zahlreichen anderen Treibern verfügbar. Weitere Optionen finden Sie auf der [npm](https://www.npmjs.com/)-Site.- - ## Cassandra **Modul**: [cassandra-driver](https://github.com/datastax/nodejs-driver) **Installation** -
-
+``` -**Beispiel** +### Beispiel -+### Installation + +```bash $ npm install cassandra-driver ---
+## Couchbase - +**Module**: [couchnode](https://github.com/couchbase/couchnode) + +### Installation + +```bash +$ npm install couchbase +``` + +### Beispiel + +```js +const couchbase = require('couchbase') +const bucket = (new couchbase.Cluster('http://localhost:8091')).openBucket('bucketName') + +// add a document to a bucket +bucket.insert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => { + if (err) { + console.log(err) + } else { + console.log(result) + } +}) + +// get all documents with shoe size 13 +const n1ql = 'SELECT d.* FROM `bucketName` d WHERE shoeSize = $1' +const query = N1qlQuery.fromString(n1ql) +bucket.query(query, [13], (err, result) => { + if (err) { + console.log(err) + } else { + console.log(result) + } +}) +``` ## CouchDB **Modul**: [nano](https://github.com/dscape/nano) **Installation** --var cassandra = require('cassandra-driver'); -var client = new cassandra.Client({ contactPoints: ['localhost']}); +```js +const cassandra = require('cassandra-driver') +const client = new cassandra.Client({ contactPoints: ['localhost'] }) + +client.execute('select key from system.local', (err, result) => { + if (err) throw err + console.log(result.rows[0]) +}) +``` -client.execute('select key from system.local', function(err, result) { - if (err) throw err; - console.log(result.rows[0]); -}); ---
+``` -**Beispiel** +### Beispiel -+### Installation + +```bash $ npm install nano ---
- - +// Get a list of all books +books.list((err, body) => { + if (err) { + console.log(err) + } else { + console.log(body.rows) + } +}) +``` ## LevelDB **Modul**: [levelup](https://github.com/rvagg/node-levelup) **Installation** --var nano = require('nano')('http://localhost:5984'); -nano.db.create('books'); -var books = nano.db.use('books'); +```js +const nano = require('nano')('http://localhost:5984') +nano.db.create('books') +const books = nano.db.use('books') -//Insert a book document in the books database -books.insert({name: 'The Art of war'}, null, function(err, body) { - if (!err){ - console.log(body); +// Insert a book document in the books database +books.insert({ name: 'The Art of war' }, null, (err, body) => { + if (err) { + console.log(err) + } else { + console.log(body) } -}); +}) -//Get a list of all books -books.list(function(err, body){ - console.log(body.rows); -}); ---
+### Installation -**Beispiel** +```bash +$ npm install level levelup leveldown +``` --$ npm install level levelup leveldown ---
+ db.get('name', (err, value) => { + if (err) return console.log('Ooops!', err) - + console.log(`name=${value}`) + }) +}) +``` ## MySQL **Modul**: [mysql](https://github.com/felixge/node-mysql/) **Installation** --var levelup = require('levelup'); -var db = levelup('./mydb'); +### Beispiel -db.put('name', 'LevelUP', function (err) { +```js +const levelup = require('levelup') +const db = levelup('./mydb') - if (err) return console.log('Ooops!', err); - db.get('name', function (err, value) { - if (err) return console.log('Ooops!', err); - console.log('name=' + value); - }); +db.put('name', 'LevelUP', (err) => { + if (err) return console.log('Ooops!', err) -}); ---
+``` -**Beispiel** +### Beispiel -+### Installation + +```bash $ npm install mysql ---
+ console.log('The solution is: ', rows[0].solution) +}) - +connection.end() +``` ## MongoDB **Modul**: [mongodb](https://github.com/mongodb/node-mongodb-native) **Installation** --var mysql = require('mysql'); -var connection = mysql.createConnection({ - host : 'localhost', - user : 'dbuser', - password : 's3kreee7' -}); +```js +const mysql = require('mysql') +const connection = mysql.createConnection({ + host: 'localhost', + user: 'dbuser', + password: 's3kreee7', + database: 'my_db' +}) -connection.connect(); +connection.connect() -connection.query('SELECT 1 + 1 AS solution', function(err, rows, fields) { - if (err) throw err; - console.log('The solution is: ', rows[0].solution); -}); +connection.query('SELECT 1 + 1 AS solution', (err, rows, fields) => { + if (err) throw err -connection.end(); ---
+``` -**Beispiel** +### Example (v2.\*) -+### Installation + +```bash $ npm install mongodb ---
+MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => { + if (err) throw err -Wenn Sie nach einem Objektmodelltreiber für MongoDB suchen, schauen Sie unter [Mongoose](https://github.com/LearnBoost/mongoose) nach. + db.collection('mammals').find().toArray((err, result) => { + if (err) throw err + + console.log(result) + }) +}) +``` + +### Example (v3.\*) - +```js +const MongoClient = require('mongodb').MongoClient + +MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => { + if (err) throw err + + const db = client.db('animals') + + db.collection('mammals').find().toArray((err, result) => { + if (err) throw err + + console.log(result) + }) +}) +``` + +Wenn Sie nach einem Objektmodelltreiber für MongoDB suchen, schauen Sie unter [Mongoose](https://github.com/LearnBoost/mongoose) nach. ## Neo4j -**Modul**: [apoc](https://github.com/hacksparrow/apoc) -**Installation** +**Module**: [neo4j-driver](https://github.com/neo4j/neo4j-javascript-driver) --var MongoClient = require('mongodb').MongoClient; +```js +const MongoClient = require('mongodb').MongoClient -MongoClient.connect('mongodb://localhost:27017/animals', function(err, db) { - if (err) { - throw err; - } - db.collection('mammals').find().toArray(function(err, result) { - if (err) { - throw err; - } - console.log(result); - }); -}); ---
+### Installation -**Beispiel** +```bash +$ npm install neo4j-driver +``` --$ npm install apoc ---
+```js +const neo4j = require('neo4j-driver') +const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.basic('neo4j', 'letmein')) - +const session = driver.session() + +session.readTransaction((tx) => { + return tx.run('MATCH (n) RETURN count(n) AS count') + .then((res) => { + console.log(res.records[0].get('count')) + }) + .catch((error) => { + console.log(error) + }) +}) +``` ## Oracle @@ -229,7 +270,7 @@ apoc.query('match (n) return n').exec().then( Anmerkung: [Siehe Installations-Voraussetzungen](https://github.com/oracle/node-oracledb#-installation). -```sh +```bash $ npm install oracledb ``` @@ -267,137 +308,182 @@ async function getEmployee (empId) { getEmployee(101) ``` - - ## PostgreSQL **Modul**: [pg-promise](https://github.com/vitaly-t/pg-promise) **Installation** --var apoc = require('apoc'); +### Beispiel -apoc.query('match (n) return n').exec().then( - function (response) { - console.log(response); - }, - function (fail) { - console.log(fail); - } -); ---
- -**Beispiel** +### Installation --$ npm install pg-promise ---
+### Beispiel - +```js +const pgp = require('pg-promise')(/* options */) +const db = pgp('postgres://username:password@host:port/database') + +db.one('SELECT $1 AS value', 123) + .then((data) => { + console.log('DATA:', data.value) + }) + .catch((error) => { + console.log('ERROR:', error) + }) +``` ## Redis **Modul**: [redis](https://github.com/mranney/node_redis) **Installation** --var pgp = require("pg-promise")(/*options*/); -var db = pgp("postgres://username:password@host:port/database"); +```bash +$ npm install pg-promise +``` -db.one("SELECT $1 AS value", 123) - .then(function (data) { - console.log("DATA:", data.value); - }) - .catch(function (error) { - console.log("ERROR:", error); - }); ---
+``` + +### Beispiel -**Beispiel** +```js +const redis = require('redis') +const client = redis.createClient() + +client.on('error', (err) => { + console.log(`Error ${err}`) +}) -+### Installation + +```bash $ npm install redis ---
+```bash +$ npm install tedious +``` - +### Beispiel + +```js +const Connection = require('tedious').Connection +const Request = require('tedious').Request + +const config = { + server: 'localhost', + authentication: { + type: 'default', + options: { + userName: 'your_username', // update me + password: 'your_password' // update me + } + } +} + +const connection = new Connection(config) + +connection.on('connect', (err) => { + if (err) { + console.log(err) + } else { + executeStatement() + } +}) + +function executeStatement () { + request = new Request("select 123, 'hello world'", (err, rowCount) => { + if (err) { + console.log(err) + } else { + console.log(`${rowCount} rows`) + } + connection.close() + }) + + request.on('row', (columns) => { + columns.forEach((column) => { + if (column.value === null) { + console.log('NULL') + } else { + console.log(column.value) + } + }) + }) + + connection.execSql(request) +} +``` ## SQLite **Modul**: [sqlite3](https://github.com/mapbox/node-sqlite3) **Installation** --var client = require('redis').createClient(); +client.set('string key', 'string val', redis.print) +client.hset('hash key', 'hashtest 1', 'some value', redis.print) +client.hset(['hash key', 'hashtest 2', 'some other value'], redis.print) -client.on('error', function (err) { - console.log('Error ' + err); -}); +client.hkeys('hash key', (err, replies) => { + console.log(`${replies.length} replies:`) -client.set('string key', 'string val', redis.print); -client.hset('hash key', 'hashtest 1', 'some value', redis.print); -client.hset(['hash key', 'hashtest 2', 'some other value'], redis.print); + replies.forEach((reply, i) => { + console.log(` ${i}: ${reply}`) + }) + + client.quit() +}) +``` -client.hkeys('hash key', function (err, replies) { +## SQL Server - console.log(replies.length + ' replies:'); - replies.forEach(function (reply, i) { - console.log(' ' + i + ': ' + reply); - }); +**Module**: [tedious](https://github.com/tediousjs/tedious) - client.quit(); +### Installation -}); ---
+### Installation -**Beispiel** +```bash +$ npm install sqlite3 +``` --$ npm install sqlite3 ---
- - +db.close() +``` ## ElasticSearch **Modul**: [elasticsearch](https://github.com/elastic/elasticsearch-js) **Installation** --var sqlite3 = require('sqlite3').verbose(); -var db = new sqlite3.Database(':memory:'); +### Beispiel -db.serialize(function() { +```js +const sqlite3 = require('sqlite3').verbose() +const db = new sqlite3.Database(':memory:') - db.run('CREATE TABLE lorem (info TEXT)'); - var stmt = db.prepare('INSERT INTO lorem VALUES (?)'); +db.serialize(() => { + db.run('CREATE TABLE lorem (info TEXT)') + const stmt = db.prepare('INSERT INTO lorem VALUES (?)') - for (var i = 0; i < 10; i++) { - stmt.run('Ipsum ' + i); + for (let i = 0; i < 10; i++) { + stmt.run(`Ipsum ${i}`) } - stmt.finalize(); + stmt.finalize() - db.each('SELECT rowid AS id, info FROM lorem', function(err, row) { - console.log(row.id + ': ' + row.info); - }); -}); + db.each('SELECT rowid AS id, info FROM lorem', (err, row) => { + console.log(`${row.id}: ${row.info}`) + }) +}) -db.close(); ---
+``` -**Beispiel** +### Beispiel -+### Installation + +```bash $ npm install elasticsearch ---
+}).then((response) => { + const hits = response.hits.hits +}, (error) => { + console.trace(error.message) +}) +``` diff --git a/de/guide/debugging.md b/de/guide/debugging.md old mode 100755 new mode 100644 index d88cfad7ab..0661aaf8b3 --- a/de/guide/debugging.md +++ b/de/guide/debugging.md @@ -1,39 +1,28 @@ --- layout: page title: Debugging bei Express +description: Learn how to enable and use debugging logs in Express.js applications by setting the DEBUG environment variable for enhanced troubleshooting. menu: guide -lang: de +redirect_from: " " --- # Debugging bei Express -Express verwendet das Modul [debug](https://www.npmjs.com/package/debug) intern, um Informationen zu Weiterleitungsübereinstimmungen, verwendete Middlewarefunktionen, Anwendungsmodi und den Verlauf des Anforderung/Antwort-Zyklus zu protokollieren. - --var elasticsearch = require('elasticsearch'); -var client = elasticsearch.Client({ +```js +const elasticsearch = require('elasticsearch') +const client = elasticsearch.Client({ host: 'localhost:9200' -}); +}) client.search({ index: 'books', @@ -410,10 +496,9 @@ client.search({ } } } -}).then(function(response) { - var hits = response.hits.hits; -}, function(error) { - console.trace(error.message); -}); ---`debug` ist praktisch eine erweiterte Version von `console.log`. Im Gegensatz zu `console.log` müssen jedoch -keine `debug`-Protokolle im Produktionscode auskommentiert werden. Die Protokollierung wird standardmäßig inaktiviert und kann über die Umgebungsvariable `DEBUG` bedingt aktiviert werden. -- Wenn Sie alle in Express verwendeten internen Protokolle anzeigen wollen, legen Sie beim Starten Ihrer Anwendung die Umgebungsvariable `DEBUG` auf `express:*` fest. --
+``` Verwenden Sie unter Windows den entsprechenden Befehl. -+```bash $ DEBUG=express:* node index.js ---
+```bash +> $env:DEBUG = "express:*"; node index.js +``` Die Ausführung dieses Befehls für die durch [express generator](/{{ page.lang }}/starter/generator.html) generierte Standardanwendung resultiert in folgender Ausgabe: --> set DEBUG=express:* & node index.js ---
+``` Bei einer Anforderung an die Anwendung sind die Protokolle im Express-Code angegeben: -+```bash $ DEBUG=express:* node ./bin/www express:router:route new / +0ms express:router:layer new / +1ms @@ -69,19 +58,17 @@ $ DEBUG=express:* node ./bin/www express:router:layer new / +1ms express:router use /users router +0ms express:router:layer new /users +0ms - express:router use / <anonymous> +0ms + express:router use / <anonymous> +0ms express:router:layer new / +0ms - express:router use / <anonymous> +0ms + express:router use / <anonymous> +0ms express:router:layer new / +0ms - express:router use / <anonymous> +0ms + express:router use / <anonymous> +0ms express:router:layer new / +0ms ---
+``` Wenn Sie nur die Protokolle von der Routerimplementierung sehen wollen, legen Sie den Wert für `DEBUG` auf `express:router` fest. Gleichermaßen gilt: Wenn Sie nur die Protokolle von der Anwendungsimplementierung sehen wollen, legen Sie den Wert für `DEBUG` auf `express:application` fest, usw. ## Von `express` generierte Anwendungen -Eine über den Befehl `express` generierte Anwendung verwendet ebenfalls das Modul `debug`. Der Debug-Namespace wird auf den Namen der Anwendung erweitert. +An application generated by the `express` command uses the `debug` module and its debug namespace is scoped to the name of the application. Beispiel: Wenn Sie die Anwendung mit `$ express sample-app` generiert haben, können Sie die Debuganweisungen mit dem folgenden Befehl aktivieren: -+```bash express:router dispatching GET / +4h express:router query : / +2ms express:router expressInit : / +0ms @@ -97,29 +84,46 @@ Bei einer Anforderung an die Anwendung sind die Protokolle im Express-Code angeg express:view lookup "index.pug" +338ms express:view stat "/projects/example/views/index.pug" +0ms express:view render "/projects/example/views/index.pug" +1ms ---
+``` Sie können mehrere Debug-Namespaces in einer durch Kommas getrennten Namensliste angeben: -+```bash $ DEBUG=sample-app:* node ./bin/www ---
+``` + +## Advanced options + +When running through Node.js, you can set a few environment variables that will change the behavior of the debug logging: + +| Name | Purpose | +| ------------------- | ----------------------------------------------------------------- | +| `DEBUG` | Enables/disables specific debugging namespaces. | +| `DEBUG_COLORS` | Whether or not to use colors in the debug output. | +| `DEBUG_DEPTH` | Object inspection depth. | +| `DEBUG_FD` | File descriptor to write debug output to. | +| `DEBUG_SHOW_HIDDEN` | Shows hidden properties on inspected objects. | + +{% capture debug-text %} + +The environment variables beginning with `DEBUG_` end up being +converted into an Options object that gets used with `%o`/`%O` formatters. +See the Node.js documentation for +[`util.inspect()`](https://nodejs.org/api/util.html#util_util_inspect_object_options) +for the complete list. + +{% endcapture %} -Weitere Informationen zu `debug` finden Sie unter [debug](https://www.npmjs.com/package/debug). +{% include admonitions/note.html content=debug-text %} diff --git a/de/guide/error-handling.md b/de/guide/error-handling.md old mode 100755 new mode 100644 index 186081978f..1ffb0f9738 --- a/de/guide/error-handling.md +++ b/de/guide/error-handling.md @@ -1,119 +1,143 @@ --- layout: page title: Fehlerbehandlung in Express +description: Understand how Express.js handles errors in synchronous and asynchronous code, and learn to implement custom error handling middleware for your applications. menu: guide -lang: de +redirect_from: " " --- # Fehlerbehandlung -Middlewarefunktionen für die Fehlerbehandlung werden in derselben Weise definiert wie andere Middlewarefunktionen, nur, dass Fehlerbehandlungsfunktionen vier anstatt drei Argumente aufweisen: -`(err, req, res, next)`. Beispiel: +_Error Handling_ refers to how Express catches and processes errors that +occur both synchronously and asynchronously. Express comes with a default error +handler so you don't need to write your own to get started. -+```bash $ DEBUG=http,mail,express:* node index.js ---
- -Middleware für die Fehlerbehandlung wird ganz zuletzt nach allen anderen `app.use()`- und Weiterleitungsaufrufen definiert. Beispiel: - --app.use(function(err, req, res, next) { - console.error(err.stack); - res.status(500).send('Something broke!'); -}); ---
+## Catching Errors -Antworten von der Middlewarefunktion können das von Ihnen gewünschte Format aufweisen wie beispielsweise eine Fehlerseite im HTML-Format, eine einfache Nachricht oder eine JSON-Zeichenfolge. +It's important to ensure that Express catches all errors that occur while +running route handlers and middleware. -Für organisatorische Zwecke (und Frameworks der höheren Ebene) können Sie mehrere Middlewarefunktionen für die Fehlerbehandlung definieren, wie Sie dies bei regulären Middlewarefunktionen auch tun würden. Wenn Sie beispielsweise eine Fehlerbehandlungsroutine (Error-Handler) für Anforderungen über `XHR` und andere Anforderungen definieren wollen, können Sie die folgenden Befehle verwenden: +Errors that occur in synchronous code inside route handlers and middleware +require no extra work. If synchronous code throws an error, then Express will +catch and process it. Beispiel: --var bodyParser = require('body-parser'); -var methodOverride = require('method-override'); - -app.use(bodyParser()); -app.use(methodOverride()); -app.use(function(err, req, res, next) { - // logic -}); ---
+Middlewarefunktionen für die Fehlerbehandlung werden in derselben Weise definiert wie andere Middlewarefunktionen, nur, dass Fehlerbehandlungsfunktionen vier anstatt drei Argumente aufweisen: +`(err, req, res, next)`. Beispiel: -In diesem Beispiel kann die generische `logErrors`-Funktion Anforderungs- und Fehlerinformationen in `stderr` schreiben: +```js +app.get('/', (req, res, next) => { + fs.readFile('/file-does-not-exist', (err, data) => { + if (err) { + next(err) // Pass errors to Express. + } else { + res.send(data) + } + }) +}) +``` --var bodyParser = require('body-parser'); -var methodOverride = require('method-override'); +```js +app.get('/', (req, res) => { + throw new Error('BROKEN') // Express will catch this on its own. +}) +``` -app.use(bodyParser()); -app.use(methodOverride()); -app.use(logErrors); -app.use(clientErrorHandler); -app.use(errorHandler); ---
+Middleware für die Fehlerbehandlung wird ganz zuletzt nach allen anderen `app.use()`- und Weiterleitungsaufrufen definiert. +Beispiel: -In diesem Beispiel wird `clientErrorHandler` wie folgt definiert. In diesem Fall wird der Fehler explizit an den nächsten Error-Handler übergeben: +```js +app.get('/user/:id', async (req, res, next) => { + const user = await getUserById(req.params.id) + res.send(user) +}) +``` --function logErrors(err, req, res, next) { - console.error(err.stack); - next(err); -} ---
+If `getUserById` throws an error or rejects, `next` will be called with either +the thrown error or the rejected value. If no rejected value is provided, `next` +will be called with a default Error object provided by the Express router. -Die `errorHandler`-Funktion "catch-all" kann wie folgt implementiert werden: +Wenn Sie Übergaben an die Funktion `next()` vornehmen (außer die Zeichenfolge `'route'`), sieht Express die aktuelle Anforderung als Fehler an und überspringt alle verbleibenden fehlerfreien Behandlungsroutinen und Middlewarefunktionen. --function clientErrorHandler(err, req, res, next) { - if (req.xhr) { - res.status(500).send({ error: 'Something failed!' }); - } else { - next(err); - } -} ---
+If the callback in a sequence provides no data, only errors, you can simplify +this code as follows: -Wenn Sie Übergaben an die Funktion `next()` vornehmen (außer die Zeichenfolge `'route'`), sieht Express die aktuelle Anforderung als Fehler an und überspringt alle verbleibenden fehlerfreien Behandlungsroutinen und Middlewarefunktionen. Wenn Sie den Fehler bearbeiten wollen, müssen Sie (wie im nächsten Abschnitt beschrieben) eine Fehlerbehandlungsweiterleitung erstellen. +```js +app.get('/', [ + function (req, res, next) { + fs.writeFile('/inaccessible-path', 'data', next) + }, + function (req, res) { + res.send('OK') + } +]) +``` -Bei einem Routenhandler mit mehreren Callback-Funktionen können Sie den Parameter `route` verwenden, um den nächsten Routenhandler zu überspringen. Beispiel: +In the above example, `next` is provided as the callback for `fs.writeFile`, +which is called with or without errors. If there is no error, the second +handler is executed, otherwise Express catches and processes the error. --function errorHandler(err, req, res, next) { - res.status(500); - res.render('error', { error: err }); -} ---
+ }, 100) +}) +``` -In diesem Beispiel wird der Handler `getPaidContent` übersprungen. Alle verbleibenden Handler in `app` für `/a_route_behind_paywall` werden jedoch weiter ausgeführt. +The above example uses a `try...catch` block to catch errors in the +asynchronous code and pass them to Express. If the `try...catch` +block were omitted, Express would not catch the error since it is not part of the synchronous +handler code. --app.get('/a_route_behind_paywall', - function checkIfPaidSubscriber(req, res, next) { - if(!req.user.hasPaid) { +Bei einem Routenhandler mit mehreren Callback-Funktionen können Sie den Parameter `route` verwenden, um den nächsten Routenhandler zu überspringen. Beispiel: - // continue handling this request - next('route'); +```js +app.get('/', (req, res, next) => { + setTimeout(() => { + try { + throw new Error('BROKEN') + } catch (err) { + next(err) } - }, function getPaidContent(req, res, next) { - PaidContent.find(function(err, doc) { - if(err) return next(err); - res.json(doc); - }); - }); ---Aufrufe zu `next()` und `next(err)` geben an, dass der aktuelle Handler abgeschlossen ist und welchen Status er aufweist. Durch `next(err)` werden alle verbleibenden Handler in der Kette übersprungen. Ausgenommen hiervor sind die Handler, die konfiguriert sind, um Fehler wie oben beschrieben zu behandeln. -+Use promises to avoid the overhead of the `try...catch` block or when using functions +that return promises. Beispiel: + +```js +app.get('/', (req, res, next) => { + Promise.resolve().then(() => { + throw new Error('BROKEN') + }).catch(next) // Errors will be passed to Express. +}) +``` + +Since promises automatically catch both synchronous errors and rejected promises, +you can simply provide `next` as the final catch handler and Express will catch errors, +because the catch handler is given the error as the first argument. + +You could also use a chain of handlers to rely on synchronous error +catching, by reducing the asynchronous code to something trivial. Beispiel: + +```js +app.get('/', [ + function (req, res, next) { + fs.readFile('/maybe-valid-file', 'utf-8', (err, data) => { + res.locals.data = data + next(err) + }) + }, + function (req, res) { + res.locals.data = res.locals.data.split(',')[1] + res.send(res.locals.data) + } +]) +``` + +The above example has a couple of trivial statements from the `readFile` +call. If `readFile` causes an error, then it passes the error to Express, otherwise you +quickly return to the world of synchronous error handling in the next handler +in the chain. Then, the example above tries to process the data. If this fails, then the +synchronous error handler will catch it. If you had done this processing inside +the `readFile` callback, then the application might exit and the Express error +handlers would not run. + +Whichever method you use, if you want Express error handlers to be called in and the +application to survive, you must ensure that Express receives the error. ## Die Standardfehlerbehandlungsroutine (Default Error Handler) @@ -125,18 +149,135 @@ Wenn Sie einen Fehler an `next()` übergeben und diesen nicht mit einem Error-Ha Legen Sie die Umgebungsvariable `NODE_ENV` auf `production` fest, um die Anwendung im Produktionsmodus auszuführen.
-
-function errorHandler(err, req, res, next) {
+```js
+function errorHandler (err, req, res, next) {
if (res.headersSent) {
- return next(err);
+ return next(err)
}
- res.status(500);
- res.render('error', { error: err });
+ res.status(500)
+ res.render('error', { error: err })
}
-
-
+```
+
+Note that the default error handler can get triggered if you call `next()` with an error
+in your code more than once, even if custom error handling middleware is in place.
+
+Other error handling middleware can be found at [Express middleware](/{{ page.lang }}/resources/middleware.html).
+
+## Writing error handlers
+
+Define error-handling middleware functions in the same way as other middleware functions,
+except error-handling functions have four arguments instead of three:
+`(err, req, res, next)`. Beispiel:
+
+```js
+app.use((err, req, res, next) => {
+ console.error(err.stack)
+ res.status(500).send('Something broke!')
+})
+```
+
+You define error-handling middleware last, after other `app.use()` and routes calls; for example:
+
+```js
+const bodyParser = require('body-parser')
+const methodOverride = require('method-override')
+
+app.use(bodyParser.urlencoded({
+ extended: true
+}))
+app.use(bodyParser.json())
+app.use(methodOverride())
+app.use((err, req, res, next) => {
+ // logic
+})
+```
+
+Antworten von der Middlewarefunktion können das von Ihnen gewünschte Format aufweisen wie beispielsweise eine Fehlerseite im HTML-Format, eine einfache Nachricht oder eine JSON-Zeichenfolge.
+
+Für organisatorische Zwecke (und Frameworks der höheren Ebene) können Sie mehrere Middlewarefunktionen für die Fehlerbehandlung definieren, wie Sie dies bei regulären Middlewarefunktionen auch tun würden. Wenn Sie beispielsweise eine Fehlerbehandlungsroutine (Error-Handler) für Anforderungen über `XHR` und andere Anforderungen definieren wollen, können Sie die folgenden Befehle verwenden:
+
+```js
+const bodyParser = require('body-parser')
+const methodOverride = require('method-override')
+
+app.use(bodyParser.urlencoded({
+ extended: true
+}))
+app.use(bodyParser.json())
+app.use(methodOverride())
+app.use(logErrors)
+app.use(clientErrorHandler)
+app.use(errorHandler)
+```
+
+In diesem Beispiel kann die generische `logErrors`-Funktion Anforderungs- und Fehlerinformationen in `stderr` schreiben:
+
+```js
+function logErrors (err, req, res, next) {
+ console.error(err.stack)
+ next(err)
+}
+```
+
+In diesem Beispiel wird `clientErrorHandler` wie folgt definiert. In diesem Fall wird der Fehler explizit an den nächsten Error-Handler übergeben:
+
+Notice that when _not_ calling "next" in an error-handling function, you are responsible for writing (and ending) the response. Otherwise, those requests will "hang" and will not be eligible for garbage collection.
+
+```js
+function clientErrorHandler (err, req, res, next) {
+ if (req.xhr) {
+ res.status(500).send({ error: 'Something failed!' })
+ } else {
+ next(err)
+ }
+}
+```
+
+Die `errorHandler`-Funktion "catch-all" kann wie folgt implementiert werden:
+
+```js
+function errorHandler (err, req, res, next) {
+ res.status(500)
+ res.render('error', { error: err })
+}
+```
+
+If you have a route handler with multiple callback functions, you can use the `route` parameter to skip to the next route handler. Beispiel:
+
+```js
+app.get('/a_route_behind_paywall',
+ (req, res, next) => {
+ if (!req.user.hasPaid) {
+ // continue handling this request
+ next('route')
+ } else {
+ next()
+ }
+ }, (req, res, next) => {
+ PaidContent.find((err, doc) => {
+ if (err) return next(err)
+ res.json(doc)
+ })
+ })
+```
+
+In diesem Beispiel wird der Handler `getPaidContent` übersprungen. Alle verbleibenden Handler in `app` für `/a_route_behind_paywall` werden jedoch weiter ausgeführt.
+
+
+Aufrufe zu `next()` und `next(err)` geben an, dass der aktuelle Handler abgeschlossen ist und welchen Status er aufweist. Durch `next(err)` werden alle verbleibenden Handler in der Kette übersprungen. Ausgenommen hiervor sind die Handler, die konfiguriert sind, um Fehler wie oben beschrieben zu behandeln.
+
diff --git a/de/guide/migrating-4.md b/de/guide/migrating-4.md
old mode 100755
new mode 100644
index 53a5049801..ddfe05f09a
--- a/de/guide/migrating-4.md
+++ b/de/guide/migrating-4.md
@@ -1,8 +1,9 @@
---
layout: page
title: Migration auf Express 4
+description: A guide to migrating your Express.js applications from version 3 to 4, covering changes in middleware, routing, and how to update your codebase effectively.
menu: guide
-lang: de
+redirect_from: " "
---
# Wechsel zu Express 4
@@ -24,15 +25,16 @@ In diesem Beitrag werden folgende Themen behandelt:
In Express 4 wurden einige signifikante Änderungen vorgenommen:
-
-
- Änderungen am Express-Core- und Middlewaresystem. Die Abhängigkeiten bei Connect und der integrierten Middleware wurden entfernt. Sie müssen also Middleware selbst hinzufügen. +
- Changes to Express core and middleware system. The dependencies on Connect and built-in middleware were removed, so you must add middleware yourself. +
- Änderungen am Weiterleitungssystem (Routingsystem).
- Weitere Änderungen.
Änderungen am Express-Core- und Middlewaresystem
@@ -48,7 +50,7 @@ Ohne integrierte Middleware müssen Sie explizit alle Middlewarefunktionen hinzu In der folgenden Tabelle sind Express 3-Middlewarefunktionen und deren Entsprechungen in Express 4 aufgelistet.| Express 3 | Express 4 |
|---|---|
| Express 3 | Express 4 |
express.bodyParser |
body-parser + multer | serve-index |
express.static |
serve-static |
app.use akzeptiert Parameter.
-In Version 4 können Sie über einen Variablenparameter den Pfad definieren, in den Middlewarefunktionen geladen werden. Dann können Sie den Wert des Parameters aus dem Routenhandler laden. Beispiel:
+In Version 4 können Sie über einen Variablenparameter den Pfad definieren, in den Middlewarefunktionen geladen werden. Dann können Sie den Wert des Parameters aus dem Routenhandler laden.
+Beispiel:
+
+```js
+app.use('/book/:id', (req, res, next) => {
+ console.log('ID:', req.params.id)
+ next()
+})
+```
-
-
-app.use('/book/:id', function(req, res, next) {
- console.log('ID:', req.params.id);
- next();
-});
-
-
Das Routingsystem
Anwendungen laden nun implizit Routing-Middleware. Sie müssen sich also keine Gedanken mehr über die Reihenfolge machen, in der die Middleware in Bezug auf die `router`-Middleware geladen wird. -Die Art und Weise, wie Weiterleitungen (Routen) definiert werden, bleibt unverändert. Das Routingsystem verfügt jedoch über zwei neue Funktionen, die beim Organisieren Ihrer Weiterleitungen helfen: +Das Routingsystem verfügt jedoch über zwei neue Funktionen, die beim Organisieren Ihrer Weiterleitungen helfen: {: .doclist } -* Die neue Methode `app.route()` zum Erstellen verkettbarer Routenhandler für einen Weiterleitungspfad -* Die neue Klasse `express.Router` zum Erstellen modular einbindbarer Routenhandler + +- Die neue Methode `app.route()` zum Erstellen verkettbarer Routenhandler für einen Weiterleitungspfad +- Die neue Klasse `express.Router` zum Erstellen modular einbindbarer RoutenhandlerDie Methode app.route()
@@ -116,20 +119,18 @@ Die neue Methode `app.route()` hilft beim Erstellen verkettbarer Routenhandler f
Dies ist ein Beispiel für verkettete Routenhandler, die mit der Funktion `app.route()` definiert werden.
-
-
+```js
app.route('/book')
- .get(function(req, res) {
- res.send('Get a random book');
+ .get((req, res) => {
+ res.send('Get a random book')
})
- .post(function(req, res) {
- res.send('Add a book');
+ .post((req, res) => {
+ res.send('Add a book')
})
- .put(function(req, res) {
- res.send('Update the book');
- });
-
-
+ .put((req, res) => {
+ res.send('Update the book')
+ })
+```
Die Klasse express.Router
@@ -139,38 +140,36 @@ Im folgenden Beispiel wird ein Router als Modul erstellt, Middleware in das Modu
Beispiel: Erstellen Sie eine Routerdatei namens `birds.js` mit dem folgenden Inhalt im Anwendungsverzeichnis:
-
-
-var express = require('express');
-var router = express.Router();
+```js
+var express = require('express')
+var router = express.Router()
// middleware specific to this router
-router.use(function timeLog(req, res, next) {
- console.log('Time: ', Date.now());
- next();
-});
+router.use((req, res, next) => {
+ console.log('Time: ', Date.now())
+ next()
+})
// define the home page route
-router.get('/', function(req, res) {
- res.send('Birds home page');
-});
+router.get('/', (req, res) => {
+ res.send('Birds home page')
+})
// define the about route
-router.get('/about', function(req, res) {
- res.send('About birds');
-});
+router.get('/about', (req, res) => {
+ res.send('About birds')
+})
-module.exports = router;
-
-
+module.exports = router
+```
Laden Sie dann das Routermodul in die Anwendung:
-
-
-var birds = require('./birds');
-...
-app.use('/birds', birds);
-
-
+```js
+var birds = require('./birds')
+
+// ...
+
+app.use('/birds', birds)
+```
Die Anwendung kann nun Anforderungen an die Pfade `/birds` und `/birds/about` bearbeiten und ruft die Middleware `timeLog` auf, die speziell für diese Weiterleitung bestimmt ist.
@@ -180,7 +179,7 @@ Weitere Änderungen
In der folgenden Tabelle sind andere kleinere, aber trotzdem wichtige Änderungen in Express 4 aufgeführt:
| Objekt | Beschreibung | -Die Funktion `app.configure()` wurde entfernt. Verwenden Sie die Funktion `process.env.NODE_ENV` oder `app.get('env')`, um die Umgebung zu erkennen und die Anwendung entsprechend zu konfigurieren. +Die Funktion `app.configure()` wurde entfernt. Verwenden Sie die Funktion `process.env.NODE_ENV` oder `app.get('env')`, um die Umgebung zu erkennen und die Anwendung entsprechend zu konfigurieren. |
|---|---|
Beispiel für eine Anwendungsmigration
-Dies ist ein Beispiel für die Migration einer Express 3-Anwendung auf Express 4. Die dabei interessanten Dateien sind `app.js` und `package.json`. +Dies ist ein Beispiel für die Migration einer Express 3-Anwendung auf Express 4. +Die dabei interessanten Dateien sind `app.js` und `package.json`.
Anwendung der Version 3
@@ -300,48 +300,45 @@ Anwendung der Version 3
Es wird eine Express v.3-Anwendung mit der folgenden Datei `app.js` angenommen:
-
-
-var express = require('express');
-var routes = require('./routes');
-var user = require('./routes/user');
-var http = require('http');
-var path = require('path');
+```js
+var express = require('express')
+var routes = require('./routes')
+var user = require('./routes/user')
+var http = require('http')
+var path = require('path')
-var app = express();
+var app = express()
// all environments
-app.set('port', process.env.PORT || 3000);
-app.set('views', path.join(__dirname, 'views'));
-app.set('view engine', 'pug');
-app.use(express.favicon());
-app.use(express.logger('dev'));
-app.use(express.methodOverride());
-app.use(express.session({ secret: 'your secret here' }));
-app.use(express.bodyParser());
-app.use(app.router);
-app.use(express.static(path.join(__dirname, 'public')));
+app.set('port', process.env.PORT || 3000)
+app.set('views', path.join(__dirname, 'views'))
+app.set('view engine', 'pug')
+app.use(express.favicon())
+app.use(express.logger('dev'))
+app.use(express.methodOverride())
+app.use(express.session({ secret: 'your secret here' }))
+app.use(express.bodyParser())
+app.use(app.router)
+app.use(express.static(path.join(__dirname, 'public')))
// development only
-if ('development' == app.get('env')) {
- app.use(express.errorHandler());
+if (app.get('env') === 'development') {
+ app.use(express.errorHandler())
}
-app.get('/', routes.index);
-app.get('/users', user.list);
+app.get('/', routes.index)
+app.get('/users', user.list)
-http.createServer(app).listen(app.get('port'), function(){
- console.log('Express server listening on port ' + app.get('port'));
-});
-
-
+http.createServer(app).listen(app.get('port'), () => {
+ console.log('Express server listening on port ' + app.get('port'))
+})
+```
package.json
Die zugehörige `package.json`-Datei der Version 3 sieht in etwa wie folgt aus:
-
-
+```json
{
"name": "application-name",
"version": "0.0.1",
@@ -354,8 +351,7 @@ Die zugehörige `package.json`-Datei der Version 3 sieht in etwa wie folgt aus:
"pug": "*"
}
}
-
-
+```
Prozess
@@ -363,20 +359,19 @@ Prozess
Beginnen Sie den Migrationsprozess mit der Installation der erforderlichen Middleware für die Express 4-Anwendung und der Aktualisierung von Express und Pug auf die aktuellen Versionen. Verwenden Sie hierzu den folgenden Befehl:
-
-
+```bash
$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
-
-
+```
Nehmen Sie an `app.js` die folgenden Änderungen vor:
1. Die integrierten Express-Middlewarefunktionen `express.favicon`,
- `express.logger`, `express.methodOverride`,
- `express.session`, `express.bodyParser` und
- `express.errorHandler` sind im Objekt `express` nicht mehr verfügbar. Sie müssen deren Alternativen manuell installieren und in die Anwendung laden.
+ `express.logger`, `express.methodOverride`,
+ `express.session`, `express.bodyParser` und
+ `express.errorHandler` sind im Objekt `express` nicht mehr verfügbar. Sie müssen deren Alternativen manuell installieren und in die Anwendung laden.
-2. Sie müssen die Funktion `app.router` nicht mehr laden. Sie ist kein gültiges Express 4-Anwendungsobjekt. Entfernen Sie also den Code `app.use(app.router);`.
+2. Sie müssen die Funktion `app.router` nicht mehr laden.
+ Sie ist kein gültiges Express 4-Anwendungsobjekt. Entfernen Sie also den Code `app.use(app.router);`.
3. Stellen Sie sicher, dass die Middlewarefunktionen in der richtigen Reihenfolge geladen werden – laden Sie `errorHandler` nach dem Laden der Anwendungsweiterleitungen.
@@ -386,8 +381,7 @@ Nehmen Sie an `app.js` die folgenden Änderungen vor:
Durch Ausführung des Befehls `npm` wird `package.json` wie folgt aktualisiert:
-
-
+```json
{
"name": "application-name",
"version": "0.0.1",
@@ -400,87 +394,84 @@ Durch Ausführung des Befehls `npm` wird `package.json` wie folgt aktualisiert:
"errorhandler": "^1.1.1",
"express": "^4.8.0",
"express-session": "^1.7.2",
- "pug": "^2.0.0-beta6",
+ "pug": "^2.0.0",
"method-override": "^2.1.2",
"morgan": "^1.2.2",
"multer": "^0.1.3",
"serve-favicon": "^2.0.1"
}
}
-
-
+```
app.js
Entfernen Sie dann ungültigen Code, laden Sie die erforderliche Middleware und nehmen Sie andere Änderungen nach Bedarf vor. Die Datei `app.js` sieht dann wie folgt aus:
-
-
-var http = require('http');
-var express = require('express');
-var routes = require('./routes');
-var user = require('./routes/user');
-var path = require('path');
+```js
+var http = require('http')
+var express = require('express')
+var routes = require('./routes')
+var user = require('./routes/user')
+var path = require('path')
-var favicon = require('serve-favicon');
-var logger = require('morgan');
-var methodOverride = require('method-override');
-var session = require('express-session');
-var bodyParser = require('body-parser');
-var multer = require('multer');
-var errorHandler = require('errorhandler');
+var favicon = require('serve-favicon')
+var logger = require('morgan')
+var methodOverride = require('method-override')
+var session = require('express-session')
+var bodyParser = require('body-parser')
+var multer = require('multer')
+var errorHandler = require('errorhandler')
-var app = express();
+var app = express()
// all environments
-app.set('port', process.env.PORT || 3000);
-app.set('views', path.join(__dirname, 'views'));
-app.set('view engine', 'pug');
-app.use(favicon(__dirname + '/public/favicon.ico'));
-app.use(logger('dev'));
-app.use(methodOverride());
-app.use(session({ resave: true,
- saveUninitialized: true,
- secret: 'uwotm8' }));
-app.use(bodyParser.json());
-app.use(bodyParser.urlencoded({ extended: true }));
-app.use(multer());
-app.use(express.static(path.join(__dirname, 'public')));
-
-app.get('/', routes.index);
-app.get('/users', user.list);
+app.set('port', process.env.PORT || 3000)
+app.set('views', path.join(__dirname, 'views'))
+app.set('view engine', 'pug')
+app.use(favicon(path.join(__dirname, '/public/favicon.ico')))
+app.use(logger('dev'))
+app.use(methodOverride())
+app.use(session({
+ resave: true,
+ saveUninitialized: true,
+ secret: 'uwotm8'
+}))
+app.use(bodyParser.json())
+app.use(bodyParser.urlencoded({ extended: true }))
+app.use(multer())
+app.use(express.static(path.join(__dirname, 'public')))
+
+app.get('/', routes.index)
+app.get('/users', user.list)
// error handling middleware should be loaded after the loading the routes
-if ('development' == app.get('env')) {
- app.use(errorHandler());
+if (app.get('env') === 'development') {
+ app.use(errorHandler())
}
-var server = http.createServer(app);
-server.listen(app.get('port'), function(){
- console.log('Express server listening on port ' + app.get('port'));
-});
-
-
-
-
-Wenn Sie nicht direkt mit dem Modul `http` arbeiten müssen (socket.io/SPDY/HTTPS), ist das Laden des Moduls nicht erforderlich. Die Anwendung kann dann einfach wie folgt gestartet werden:
-
-app.listen(app.get('port'), function(){
- console.log('Express server listening on port ' + app.get('port'));
-});
-
-
+var server = http.createServer(app)
+server.listen(app.get('port'), () => {
+ console.log('Express server listening on port ' + app.get('port'))
+})
+```
+
+Wenn Sie nicht direkt mit dem Modul `http` arbeiten müssen (socket.io/SPDY/HTTPS), ist das Laden des Moduls nicht erforderlich. Die Anwendung kann dann einfach wie folgt gestartet werden:
+
+```js
+app.listen(app.get('port'), () => {
+ console.log('Express server listening on port ' + app.get('port'))
+})
+```
+
Anwendung ausführen
Der Migrationsprozess ist abgeschlossen und die Anwendung ist nun eine Express 4-Anwendung. Zum Bestätigen starten Sie die Anwendung mit dem folgenden Befehl:
-
-
+```bash
$ node .
-
-
+```
Laden Sie [http://localhost:3000](http://localhost:3000) und sehen Sie, wie die Homepage von Express 4 wiedergegeben wird.
@@ -492,23 +483,20 @@ Das Befehlszeilentool zum Generieren einer Express-Anwendung ist nach wie vor `e
Wenn der Express 3 App Generator bereits auf Ihrem System installiert ist, müssen Sie diesen deinstallieren:
-
-
+```bash
$ npm uninstall -g express
-
-
+```
+
Abhängig davon, wie Ihre Datei- und Verzeichnissberechtigungen konfiguriert sind, müssen Sie diesen Befehl möglicherweise mit `sudo` ausführen.
+
Installieren Sie nun den neuen Generator:
-
-
+```bash
$ npm install -g express-generator
-
-
+```
Abhängig davon, wie Ihre Datei- und Verzeichnissberechtigungen konfiguriert sind, müssen Sie diesen Befehl möglicherweise mit `sudo` ausführen.
-
Nun wird der Befehl `express` auf Ihrem System auf den Express 4 App Generator aktualisiert.
Änderungen am App Generator
@@ -516,19 +504,18 @@ Nun wird der Befehl `express` auf Ihrem System auf den Express 4 App Generator a
Befehlsoptionen und -nutzung bleiben größtenteils unverändert. Es gelten jedoch folgende Ausnahmen:
{: .doclist }
-* Option `--sessions` wurde entfernt.
-* Option `--jshtml` wurde entfernt.
-* Option `--hogan` wurde hinzugefügt, um [Hogan.js](http://twitter.github.io/hogan.js/) zu unterstützen.
+
+- Option `--sessions` wurde entfernt.
+- Option `--jshtml` wurde entfernt.
+- Option `--hogan` wurde hinzugefügt, um [Hogan.js](http://twitter.github.io/hogan.js/) zu unterstützen.
Beispiel
Führen Sie den folgenden Befehl aus, um eine Express 4-Anwendung zu erstellen:
-
-
+```bash
$ express app4
-
-
+```
Wenn Sie sich den Inhalt der Datei `app4/app.js` ansehen, werden Sie feststellen, dass alle Middlewarefunktionen (außer `express.static`), die für die Anwendung erforderlich sind, als unabhängige Module geladen werden und die Middleware `router` nicht mehr explizit in die Anwendung geladen wird.
@@ -536,11 +523,9 @@ Sie werden auch feststellen, dass die Datei `app.js` nun ein Node.js-Modul ist
Starten Sie nach der Installation der Abhängigkeiten die Anwendung mit dem folgenden Befehl:
-
-
+```bash
$ npm start
-
-
+```
Wenn Sie sich das npm-Startscript in der Datei `package.json` näher ansehen, werden Sie feststellen, dass der eigentliche Befehl, der die Anwendung startet, `node ./bin/www` heißt. Dieser Befehl lautete in Express 3 `node app.js`.
@@ -550,23 +535,19 @@ Weder das Verzeichnis `bin` noch die erweiterungslose Datei `www` ist für das E
Um das Verzeichnis `www` zu löschen und alles im "Express 3-Stil" zu belassen, löschen Sie die Zeile mit dem Eintrag `module.exports = app;` am Ende der Datei `app.js`. Fügen Sie dann stattdessen den folgenden Code an derselben Position ein:
-
-
-app.set('port', process.env.PORT || 3000);
+```js
+app.set('port', process.env.PORT || 3000)
-var server = app.listen(app.get('port'), function() {
- debug('Express server listening on port ' + server.address().port);
-});
-
-
+var server = app.listen(app.get('port'), () => {
+ debug('Express server listening on port ' + server.address().port)
+})
+```
Stellen Sie sicher, dass Sie das Modul `debug` am Anfang der Datei `app.js` laden. Verwenden Sie dazu den folgenden Code:
-
-
-var debug = require('debug')('app4');
-
-
+```js
+var debug = require('debug')('app4')
+```
Ändern Sie als Nächstes `"start": "node ./bin/www"` in der Datei `package.json` in `"start": "node app.js"`.
diff --git a/de/guide/migrating-5.md b/de/guide/migrating-5.md
old mode 100755
new mode 100644
index 837fdea897..af9d495fd5
--- a/de/guide/migrating-5.md
+++ b/de/guide/migrating-5.md
@@ -1,31 +1,44 @@
---
layout: page
title: Migration auf Express 5
+description: A comprehensive guide to migrating your Express.js applications from version 4 to 5, detailing breaking changes, deprecated methods, and new improvements.
menu: guide
-lang: de
+redirect_from: " "
---
# Wechsel zu Express 5
Überblick
-Express 5.0 befindet sich noch in der Alpha-Release-Phase. Hier finden Sie jedoch bereits eine Vorschau zu den Änderungen in diesem Release und zur Migration Ihrer Express 4-Anwendung auf Express 5.
+Express 5.0 befindet sich noch in der Beta-Release-Phase. Hier finden Sie jedoch bereits eine Vorschau zu den Änderungen in diesem Release und zur Migration Ihrer Express 4-Anwendung auf Express 5.
-Express 5 unterscheidet sich nicht allzu sehr von Express 4: Die Änderungen an der API sind nicht so signifikant wie von 3.0 zu 4.0. Auch wenn die Basis-API unverändert bleibt, wird es doch einige grundlegende Veränderungen geben. In anderen Worten: Ein vorhandenes Express 4-Programm funktioniert möglicherweise nicht mehr, wenn Sie es für Express 5 aktualisieren.
+To install this version, you need to have a Node.js version 18 or higher. Then, execute the following command in your application directory:
-Zum Installieren der aktuellen Alpha-Version und zur Vorschau von Express 5 geben Sie den folgenden Befehl im Stammverzeichnis Ihrer Anwendung ein:
-
-
-
-$ npm install express@5.0.0-alpha.2 --save
-
-
+```sh
+npm install "express@5"
+```
Sie können Ihre automatisierten Tests ausführen, um zu sehen, was fehlschlägt, und Probleme gemäß den folgenden Updates beheben. Nachdem Sie alle Testfehler behoben haben, führen Sie Ihre Anwendung aus, um zu sehen, welche Fehler noch auftreten. Sie werden sofort feststellen, ob die Anwendung Methoden oder Eigenschaften verwendet, die nicht unterstützt werden.
-Änderungen in Express 5
+## Express 5 Codemods
+
+To help you migrate your express server, we have created a set of codemods that will help you automatically update your code to the latest version of Express.
+
+Run the following command for run all the codemods available:
+
+```sh
+npx @expressjs/codemod upgrade
+```
+
+If you want to run a specific codemod, you can run the following command:
+
+```sh
+npx @expressjs/codemod name-of-the-codemod
+```
+
+You can find the list of available codemods [here](https://github.com/expressjs/codemod?tab=readme-ov-file#available-codemods).
-Nachfolgend finden Sie eine Liste mit Änderungen (Stand: Alpha-2-Release), die sich auf Sie als Express-Benutzer auswirken werden. Siehe hierzu auch die [Pull-Anforderung](https://github.com/expressjs/express/pull/2237) mit einer Liste aller geplanten Features und Funktionen.
+Änderungen in Express 5
**Entfernte Methoden und Eigenschaften**
@@ -37,95 +50,497 @@ Nachfolgend finden Sie eine Liste mit Änderungen (Stand: Alpha-2-Release), die
req.param(name)
res.json(obj, status)
res.jsonp(obj, status)
+ res.redirect('back') and res.location('back')
+ res.redirect(url, status)
res.send(body, status)
res.send(status)
res.sendfile()
+ router.param(fn)
+ express.static.mime
+ express:router debug logs
-**Geändert**
+**Verbesserungen**
+ - Path route matching syntax
+ - Rejected promises handled from middleware and handlers
+ - express.urlencoded
+ - express.static dotfiles
+ - app.listen
- app.router
+ - req.body
- req.host
- req.query
+ - res.clearCookie
+ - res.status
+ - res.vary
-**Verbesserungen**
+**Geändert**
-Entfernte Methoden und Eigenschaften
+## Entfernte Methoden und Eigenschaften
Wenn Sie eine dieser Methoden oder Eigenschaften in Ihrer Anwendung verwenden, stürzt die Anwendung ab. Sie müssen also Ihre Anwendung ändern, wenn Sie auf Version 5 umgestellt haben.
-app.del()
+app.del()
Express 5 unterstützt die Funktion `app.del()` nicht mehr. Wenn Sie diese Funktion verwenden, wird ein Fehler ausgelöst. Für die Registrierung von HTTP DELETE-Weiterleitungen verwenden Sie stattdessen die Funktion `app.delete()`.
-Anfänglich wurde `del` statt `delete` verwendet, weil `delete` in JavaScript ein reserviertes Schlüsselwort ist. Ab ECMAScript 6 jedoch können `delete` und andere reservierte Schlüsselwörter legal als Eigenschaftsnamen verwendet werden. Lesen hier auch die Diskussion, die zur Einstellung der Unterstützung der Funktion `app.del` geführt hat.
+Anfänglich wurde `del` statt `delete` verwendet, weil `delete` in JavaScript ein reserviertes Schlüsselwort ist. Ab ECMAScript 6 jedoch können `delete` und andere reservierte Schlüsselwörter legal als Eigenschaftsnamen verwendet werden.
+
+{% capture codemod-deprecated-signatures %}
+You can replace the deprecated signatures with the following command:
+
+```plain-text
+npx @expressjs/codemod v4-deprecated-signatures
+```
+
+{% endcapture %}
-app.param(fn)
+{% include admonitions/note.html content=codemod-deprecated-signatures %}
-Die Signatur `app.param(fn)` wurde für die Änderung der Verhaltensweise der Funktion `app.param(name, fn)` verwendet. Seit v4.11.0 wurde sie nicht mehr verwendet. In Express 5 wird sie überhaupt nicht mehr unterstützt.
+```js
+// v4
+app.del('/user/:id', (req, res) => {
+ res.send(`DELETE /user/${req.params.id}`)
+})
-Pluralisierte Methodennamen
+// v5
+app.delete('/user/:id', (req, res) => {
+ res.send(`DELETE /user/${req.params.id}`)
+})
+```
+
+app.param(fn)
+
+Die Signatur `app.param(fn)` wurde für die Änderung der Verhaltensweise der Funktion `app.param(name, fn)` verwendet. Seit v4.11.0 wurde sie nicht mehr verwendet. In Express 5 wird sie überhaupt nicht mehr unterstützt.
+
+Pluralisierte Methodennamen
Die folgenden Methodennamen wurden pluralisiert. In Express 4 wurde bei Verwendung der alten Methoden eine Warnung zur Einstellung der Unterstützung ausgegeben. Express 5 unterstützt diese Methoden nicht mehr.
+`req.acceptsLanguage()` wird durch `req.acceptsLanguages()` ersetzt.
+
`req.acceptsCharset()` wird durch `req.acceptsCharsets()` ersetzt.
`req.acceptsEncoding()` wird durch `req.acceptsEncodings()` ersetzt.
-`req.acceptsLanguage()` wird durch `req.acceptsLanguages()` ersetzt.
+{% capture codemod-pluralized-methods %}
+You can replace the deprecated signatures with the following command:
+
+```plain-text
+npx @expressjs/codemod pluralized-methods
+```
+
+{% endcapture %}
-Führender Doppelpunkt (:) im Namen für app.param(name, fn)
+{% include admonitions/note.html content=codemod-pluralized-methods %}
+
+```js
+// v4
+app.all('/', (req, res) => {
+ req.acceptsCharset('utf-8')
+ req.acceptsEncoding('br')
+ req.acceptsLanguage('en')
+
+ // ...
+})
+
+// v5
+app.all('/', (req, res) => {
+ req.acceptsCharsets('utf-8')
+ req.acceptsEncodings('br')
+ req.acceptsLanguages('en')
+
+ // ...
+})
+```
+
+Führender Doppelpunkt (:) im Namen für app.param(name, fn)
Ein führendes Doppelpunktzeichen (:) im Namen für die Funktion `app.param(name, fn)` ist ein Überbleibsel aus Express 3. Aus Gründen der Abwärtskompatibilität wurde dieser Name in Express 4 mit einem Hinweis zu veralteten Versionen weiter unterstützt. In Express 5 wird dieser Name stillschwiegend ignoriert und der Namensparameter ohne einen vorangestellten Doppelpunkt verwendet.
Dies dürfte keine Auswirkungen auf Ihren Code haben, wenn Sie die Express 4-Dokumentation zu [app.param](/{{ page.lang }}/4x/api.html#app.param) befolgen, da dort der führende Doppelpunkt nicht erwähnt wird.
-req.param(name)
+req.param(name)
Dieses potenziell verwirrende und durchaus riskante Verfahren des Abrufens von Formulardaten wurde entfernt. Sie müssen nun ganz speziell nach dem übergebenen Parameternamen im Objekt `req.params`, `req.body` oder `req.query` suchen.
-res.json(obj, status)
+{% capture codemod-req-param %}
+You can replace the deprecated signatures with the following command:
+
+```plain-text
+npx @expressjs/codemod req-param
+```
+
+{% endcapture %}
+
+{% include admonitions/note.html content=codemod-req-param %}
+
+```js
+// v4
+app.post('/user', (req, res) => {
+ const id = req.param('id')
+ const body = req.param('body')
+ const query = req.param('query')
+
+ // ...
+})
+
+// v5
+app.post('/user', (req, res) => {
+ const id = req.params.id
+ const body = req.body
+ const query = req.query
+
+ // ...
+})
+```
+
+res.json(obj, status)
Express 5 unterstützt die Signatur `res.json(obj, status)` nicht mehr. Stattdessen müssen Sie den Status festlegen und diesen dann mit `res.json()`-Methoden wie dieser verketten: `res.status(status).json(obj)`.
-res.jsonp(obj, status)
+{% include admonitions/note.html content=codemod-deprecated-signatures %}
+
+```js
+// v4
+app.post('/user', (req, res) => {
+ res.json({ name: 'Ruben' }, 201)
+})
+
+// v5
+app.post('/user', (req, res) => {
+ res.status(201).json({ name: 'Ruben' })
+})
+```
+
+res.jsonp(obj, status)
Express 5 unterstützt die Signatur `res.jsonp(obj, status)` nicht mehr. Stattdessen müssen Sie den Status festlegen und diesen dann mit `res.jsonp()`-Methoden wie dieser verketten: `res.status(status).jsonp(obj)`.
-res.send(body, status)
+{% include admonitions/note.html content=codemod-deprecated-signatures %}
+
+```js
+// v4
+app.post('/user', (req, res) => {
+ res.jsonp({ name: 'Ruben' }, 201)
+})
+
+// v5
+app.post('/user', (req, res) => {
+ res.status(201).jsonp({ name: 'Ruben' })
+})
+```
+
+res.redirect(url, status)
Express 5 unterstützt die Signatur `res.send(obj, status)` nicht mehr. Stattdessen müssen Sie den Status festlegen und diesen dann mit `res.send()`-Methoden wie dieser verketten: `res.status(status).send(obj)`.
-res.send(status)
+{% include admonitions/note.html content=codemod-deprecated-signatures %}
+
+```js
+// v4
+app.get('/user', (req, res) => {
+ res.redirect('/users', 301)
+})
+
+// v5
+app.get('/user', (req, res) => {
+ res.redirect(301, '/users')
+})
+```
+
+res.redirect('back') and res.location('back')
+
+Express 5 no longer supports the magic string `back` in the `res.redirect()` and `res.location()` methods. Instead, use the `req.get('Referrer') || '/'` value to redirect back to the previous page. In Express 4, the res.`redirect('back')` and `res.location('back')` methods were deprecated.
+
+{% capture codemod-magic-redirect %}
+You can replace the deprecated signatures with the following command:
+
+```plain-text
+npx @expressjs/codemod magic-redirect
+```
+
+{% endcapture %}
+
+{% include admonitions/note.html content=codemod-magic-redirect %}
+
+```js
+// v4
+app.get('/user', (req, res) => {
+ res.redirect('back')
+})
+
+// v5
+app.get('/user', (req, res) => {
+ res.redirect(req.get('Referrer') || '/')
+})
+```
+
+res.send(body, status)
+
+Express 5 no longer supports the signature `res.send(obj, status)`. Instead, set the status and then chain it to the `res.send()` method like this: `res.status(status).send(obj)`.
+
+{% include admonitions/note.html content=codemod-deprecated-signatures %}
+
+```js
+// v4
+app.get('/user', (req, res) => {
+ res.send({ name: 'Ruben' }, 200)
+})
+
+// v5
+app.get('/user', (req, res) => {
+ res.status(200).send({ name: 'Ruben' })
+})
+```
+
+res.send(status)
+
+Express 5 unterstützt die Signatur res.send(status), nicht mehr, wobei _`status`_ für eine Zahl steht. Verwenden Sie stattdessen die Funktion `res.sendStatus(statusCode)`, mit der der Statuscode für den HTTP-Antwort-Header festgelegt und die Textversion des Codes gesendet wird: "Not Found" (Nicht gefunden), "Internal Server Error" (Interner Serverfehler) usw.
+Wenn Sie eine Zahl senden und hierfür die Funktion `res.send()` verwenden müssen, müssen Sie die Zahl in Anführungszeichen setzen, um diese in eine Zeichenfolge zu konvertieren. Dadurch interpretiert Express diese Zahl nicht als Versuch, die nicht mehr unterstützte alte Signatur zu verwenden.
+
+{% include admonitions/note.html content=codemod-deprecated-signatures %}
-Express 5 unterstützt die Signatur res.send(status), nicht mehr, wobei *`status`* für eine Zahl steht. Verwenden Sie stattdessen die Funktion `res.sendStatus(statusCode)`, mit der der Statuscode für den HTTP-Antwort-Header festgelegt und die Textversion des Codes gesendet wird: "Not Found" (Nicht gefunden), "Internal Server Error" (Interner Serverfehler) usw. Wenn Sie eine Zahl senden und hierfür die Funktion `res.send()` verwenden müssen, müssen Sie die Zahl in Anführungszeichen setzen, um diese in eine Zeichenfolge zu konvertieren. Dadurch interpretiert Express diese Zahl nicht als Versuch, die nicht mehr unterstützte alte Signatur zu verwenden.
+```js
+// v4
+app.get('/user', (req, res) => {
+ res.send(200)
+})
-res.sendfile()
+// v5
+app.get('/user', (req, res) => {
+ res.sendStatus(200)
+})
+```
+
+res.sendfile()
Die Funktion `res.sendfile()` wurde durch eine Version in Camel-Schreibweise von `res.sendFile()` in Express 5 ersetzt.
-Geändert
+**Note:** In Express 5, `res.sendFile()` uses the `mime-types` package for MIME type detection, which returns different Content-Type values than Express 4 for several common file types:
+
+- JavaScript files (.js): now "text/javascript" instead of "application/javascript"
+- JSON files (.json): now "application/json" instead of "text/json"
+- CSS files (.css): now "text/css" instead of "text/plain"
+- XML files (.xml): now "application/xml" instead of "text/xml"
+- Font files (.woff): now "font/woff" instead of "application/font-woff"
+- SVG files (.svg): now "image/svg+xml" instead of "application/svg+xml"
+
+{% include admonitions/note.html content=codemod-deprecated-signatures %}
+
+```js
+// v4
+app.get('/user', (req, res) => {
+ res.sendfile('/path/to/file')
+})
+
+// v5
+app.get('/user', (req, res) => {
+ res.sendFile('/path/to/file')
+})
+```
+
+router.param(fn)
+
+The `router.param(fn)` signature was used for modifying the behavior of the `router.param(name, fn)` function. Seit v4.11.0 wurde sie nicht mehr verwendet. In Express 5 wird sie überhaupt nicht mehr unterstützt.
+
+express.static.mime
+
+In Express 5, `mime` is no longer an exported property of the `static` field.
+Use the [`mime-types` package](https://github.com/jshttp/mime-types) to work with MIME type values.
+
+**Important:** This change affects not only direct usage of `express.static.mime` but also other Express methods that rely on MIME type detection, such as `res.sendFile()`. The following MIME types have changed from Express 4:
+
+- JavaScript files (.js): now served as "text/javascript" instead of "application/javascript"
+- JSON files (.json): now served as "application/json" instead of "text/json"
+- CSS files (.css): now served as "text/css" instead of "text/plain"
+- HTML files (.html): now served as "text/html; charset=utf-8" instead of just "text/html"
+- XML files (.xml): now served as "application/xml" instead of "text/xml"
+- Font files (.woff): now served as "font/woff" instead of "application/font-woff"
+
+```js
+// v4
+express.static.mime.lookup('json')
+
+// v5
+const mime = require('mime-types')
+mime.lookup('json')
+```
+
+express:router debug logs
+
+In Express 5, router handling logic is performed by a dependency. Therefore, the
+debug logs for the router are no longer available under the `express:` namespace.
+In v4, the logs were available under the namespaces `express:router`, `express:router:layer`,
+and `express:router:route`. All of these were included under the namespace `express:*`.
+In v5.1+, the logs are available under the namespaces `router`, `router:layer`, and `router:route`.
+The logs from `router:layer` and `router:route` are included in the namespace `router:*`.
+To achieve the same detail of debug logging when using `express:*` in v4, use a conjunction of
+`express:*`, `router`, and `router:*`.
+
+```sh
+# v4
+DEBUG=express:* node index.js
+
+# v5
+DEBUG=express:*,router,router:* node index.js
+```
+
+## Geändert
+
+Path route matching syntax
+
+Path route matching syntax is when a string is supplied as the first parameter to the `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()`, and `router.use()` APIs. The following changes have been made to how the path string is matched to an incoming request:
+
+- The wildcard `*` must have a name, matching the behavior of parameters `:`, use `/*splat` instead of `/*`
+
+```js
+// v4
+app.get('/*', async (req, res) => {
+ res.send('ok')
+})
+
+// v5
+app.get('/*splat', async (req, res) => {
+ res.send('ok')
+})
+```
+
+{% capture note_wildcard %}
+`*splat` matches any path without the root path. If you need to match the root path as well `/`, you can use `/{*splat}`, wrapping the wildcard in braces.
+
+```js
+// v5
+app.get('/{*splat}', async (req, res) => {
+ res.send('ok')
+})
+```
+
+{% endcapture %}
+{% include admonitions/note.html content=note_wildcard %}
+
+- The optional character `?` is no longer supported, use braces instead.
+
+```js
+// v4
+app.get('/:file.:ext?', async (req, res) => {
+ res.send('ok')
+})
+
+// v5
+app.get('/:file{.:ext}', async (req, res) => {
+ res.send('ok')
+})
+```
+
+- Regexp characters are not supported. Beispiel:
-app.router
+```js
+app.get('/[discussion|page]/:slug', async (req, res) => {
+ res.status(200).send('ok')
+})
+```
+
+should be changed to:
+
+```js
+app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
+ res.status(200).send('ok')
+})
+```
+
+- Some characters have been reserved to avoid confusion during upgrade (`()[]?+!`), use `\` to escape them.
+- Parameter names now support valid JavaScript identifiers, or quoted like `:"this"`.
+
+Rejected promises handled from middleware and handlers
+
+Request middleware and handlers that return rejected promises are now handled by forwarding the rejected value as an `Error` to the error handling middleware. This means that using `async` functions as middleware and handlers are easier than ever. When an error is thrown in an `async` function or a rejected promise is `await`ed inside an async function, those errors will be passed to the error handler as if calling `next(err)`.
+
+Details of how Express handles errors is covered in the [error handling documentation](/en/guide/error-handling.html).
+
+express.urlencoded
+
+The `express.urlencoded` method makes the `extended` option `false` by default.
+
+express.static dotfiles
+
+In Express 5, the `express.static` middleware's `dotfiles` option now defaults to `"ignore"`. This is a change from Express 4, where dotfiles were served by default. As a result, files inside a directory that starts with a dot (`.`), such as `.well-known`, will no longer be accessible and will return a **404 Not Found** error. This can break functionality that depends on serving dot-directories, such as Android App Links, and Apple Universal Links.
+
+Example of breaking code:
+
+```js
+// v4
+app.use(express.static('public'))
+```
+
+After migrating to Express 5, a request to `/.well-known/assetlinks.json` will result in a **404 Not Found**.
+
+To fix this, serve specific dot-directories explicitly using the `dotfiles: "allow"` option:
+
+```js
+// v5
+app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }))
+app.use(express.static('public'))
+```
+
+This approach allows you to safely serve only the intended dot-directories while keeping the default secure behavior for other dotfiles, which remain inaccessible.
+
+app.listen
+
+In Express 5, the `app.listen` method will invoke the user-provided callback function (if provided) when the server receives an error event. In Express 4, such errors would be thrown. This change shifts error-handling responsibility to the callback function in Express 5. If there is an error, it will be passed to the callback as an argument.
+Beispiel:
+
+```js
+const server = app.listen(8080, '0.0.0.0', (error) => {
+ if (error) {
+ throw error // e.g. EADDRINUSE
+ }
+ console.log(`Listening on ${JSON.stringify(server.address())}`)
+})
+```
+
+app.router
Das Objekt `app.router`, das in Express 4 entfernt wurde, ist in Express 5 wieder verfügbar. In der neuen Version fungiert dieses Objekt nur als Referenz zum Express-Basisrouter – im Gegensatz zu Express 3, wo die Anwendung dieses Objekt explizit laden musste.
-req.host
+req.body
+
+The `req.body` property returns `undefined` when the body has not been parsed. In Express 4, it returns `{}` by default.
+
+req.host
In Express 4 übergab die Funktion `req.host` nicht ordnungsgemäß eine eventuell vorhandene Portnummer. In Express 5 wird die Portnummer beibehalten.
-req.query
+req.query
+
+The `req.query` property is no longer a writable property and is instead a getter. The default query parser has been changed from "extended" to "simple".
-In Express 4.7 und ab Express 5 kann die Abfrageparser-Option `false` akzeptieren, um das Parsing von Abfragezeichenfolgen zu deaktivieren, wenn Sie Ihre eigene Funktion für die Parsinglogik bei Abfragezeichenfolgen verwenden wollen.
+res.clearCookie
-Verbesserungen
+The `res.clearCookie` method ignores the `maxAge` and `expires` options provided by the user.
-res.render()
+res.status
+
+The `res.status` method only accepts integers in the range of `100` to `999`, following the behavior defined by Node.js, and it returns an error when the status code is not an integer.
+
+res.vary
+
+The `res.vary` throws an error when the `field` argument is missing. In Express 4, if the argument was omitted, it gave a warning in the console
+
+## Verbesserungen
+
+res.render()
Diese Methode erzwingt nun asynchrones Verhalten für alle View-Engines, sodass durch View-Engines mit synchroner Implementierung verursachte Fehler vermieden werden, durch die die empfohlene Schnittstelle nicht verwendet werden konnte.
+
+Brotli encoding support
+
+Express 5 supports Brotli encoding for requests received from clients that support it.
diff --git a/de/guide/overriding-express-api.md b/de/guide/overriding-express-api.md
new file mode 100644
index 0000000000..032e3dd625
--- /dev/null
+++ b/de/guide/overriding-express-api.md
@@ -0,0 +1,72 @@
+---
+layout: page
+title: Overriding the Express API
+description: Discover how to customize and extend the Express.js API by overriding methods and properties on the request and response objects using prototypes.
+menu: guide
+---
+
+# Overriding the Express API
+
+The Express API consists of various methods and properties on the request and response objects. These are inherited by prototype. There are two extension points for the Express API:
+
+1. The global prototypes at `express.request` and `express.response`.
+2. App-specific prototypes at `app.request` and `app.response`.
+
+Altering the global prototypes will affect all loaded Express apps in the same process. If desired, alterations can be made app-specific by only altering the app-specific prototypes after creating a new app.
+
+## Methods
+
+You can override the signature and behavior of existing methods with your own, by assigning a custom function.
+
+Following is an example of overriding the behavior of [res.sendStatus](/4x/api.html#res.sendStatus).
+
+```js
+app.response.sendStatus = function (statusCode, type, message) {
+ // code is intentionally kept simple for demonstration purpose
+ return this.contentType(type)
+ .status(statusCode)
+ .send(message)
+}
+```
+
+The above implementation completely changes the original signature of `res.sendStatus`. It now accepts a status code, encoding type, and the message to be sent to the client.
+
+The overridden method may now be used this way:
+
+```js
+res.sendStatus(404, 'application/json', '{"error":"resource not found"}')
+```
+
+## Properties
+
+Properties in the Express API are either:
+
+1. Assigned properties (ex: `req.baseUrl`, `req.originalUrl`)
+2. Defined as getters (ex: `req.secure`, `req.ip`)
+
+Since properties under category 1 are dynamically assigned on the `request` and `response` objects in the context of the current request-response cycle, their behavior cannot be overridden.
+
+Properties under category 2 can be overwritten using the Express API extensions API.
+
+The following code rewrites how the value of `req.ip` is to be derived. Now, it simply returns the value of the `Client-IP` request header.
+
+```js
+Object.defineProperty(app.request, 'ip', {
+ configurable: true,
+ enumerable: true,
+ get () { return this.get('Client-IP') }
+})
+```
+
+## Prototype
+
+In order to provide the Express API, the request/response objects passed to Express (via `app(req, res)`, for example) need to inherit from the same prototype chain. By default, this is `http.IncomingRequest.prototype` for the request and `http.ServerResponse.prototype` for the response.
+
+Unless necessary, it is recommended that this be done only at the application level, rather than globally. Also, take care that the prototype that is being used matches the functionality as closely as possible to the default prototypes.
+
+```js
+// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
+// for the given app reference
+Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype)
+Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype)
+```
diff --git a/de/guide/routing.md b/de/guide/routing.md
old mode 100755
new mode 100644
index 42c4a90989..29fdb6431c
--- a/de/guide/routing.md
+++ b/de/guide/routing.md
@@ -1,27 +1,38 @@
---
layout: page
title: Weiterleitung in Express
+description: Learn how to define and use routes in Express.js applications, including route methods, route paths, parameters, and using Router for modular routing.
menu: guide
-lang: de
+redirect_from: " "
---
# Weiterleitung (Routing)
-Der Begriff *Weiterleitung* (Routing) bezieht sich auf die Definition von Anwendungsendpunkten (URIs) und deren Antworten auf Clientanforderungen. Eine Einführung in dieses Routing siehe [Basisrouting](/{{ page.lang }}/starter/basic-routing.html).
+Der Begriff _Weiterleitung_ (Routing) bezieht sich auf die Definition von Anwendungsendpunkten (URIs) und deren Antworten auf Clientanforderungen.
+Eine Einführung in dieses Routing siehe [Basisrouting](/{{ page.lang }}/starter/basic-routing.html).
+
+You define routing using methods of the Express `app` object that correspond to HTTP methods;
+for example, `app.get()` to handle GET requests and `app.post` to handle POST requests. For a full list,
+see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD). You can also use [app.all()](/{{ page.lang }}/5x/api.html#app.all) to handle all HTTP methods and [app.use()](/{{ page.lang }}/5x/api.html#app.use) to
+specify middleware as the callback function (See [Using middleware](/{{ page.lang }}/guide/using-middleware.html) for details).
+
+These routing methods specify a callback function (sometimes called "handler functions") called when the application receives a request to the specified route (endpoint) and HTTP method. In other words, the application "listens" for requests that match the specified route(s) and method(s), and when it detects a match, it calls the specified callback function.
+
+In fact, the routing methods can have more than one callback function as arguments.
+With multiple callback functions, it is important to provide `next` as an argument to the callback function and then call `next()` within the body of the function to hand off control
+to the next callback.
Der folgende Code ist ein Beispiel für ein sehr einfaches Basisrouting.
-
-
-var express = require('express');
-var app = express();
+```js
+const express = require('express')
+const app = express()
// respond with "hello world" when a GET request is made to the homepage
-app.get('/', function(req, res) {
- res.send('hello world');
-});
-
-
+app.get('/', (req, res) => {
+ res.send('hello world')
+})
+```
Weiterleitungsmethoden
@@ -29,150 +40,205 @@ Eine Weiterleitungsmethode wird von einer HTTP-Methode abgeleitet und an eine In
Der folgende Code ist ein Beispiel für Weiterleitungen, die für die Methoden GET und POST zum Stamm (Root) der Anwendung definiert werden.
-
-
+```js
// GET method route
-app.get('/', function (req, res) {
- res.send('GET request to the homepage');
-});
+app.get('/', (req, res) => {
+ res.send('GET request to the homepage')
+})
// POST method route
-app.post('/', function (req, res) {
- res.send('POST request to the homepage');
-});
-
-
-
-Express unterstützt die folgenden Weiterleitungsmethoden, die den HTTP-Methoden entsprechen: `get`, `post`, `put`, `head`, `delete`, `options`, `trace`, `copy`, `lock`, `mkcol`, `move`, `purge`, `propfind`, `proppatch`, `unlock`, `report`, `mkactivity`, `checkout`, `merge`, `m-search`, `notify`, `subscribe`, `unsubscribe`, `patch`, `search` und `connect`.
+app.post('/', (req, res) => {
+ res.send('POST request to the homepage')
+})
+```
-
-Verwenden Sie zum Weiterleiten von Methoden, die zu den JavaScript-Variablennamen führen, die Notation "Eckige Klammer". Beispiel: `app['m-search']('/', function ...`
-
-
-Es gibt eine spezielle Weiterleitungsmethode, `app.all()`, die nicht von einer HTTP-Methode abgeleitet wird. Diese Methode wird zum Laden von Middlewarefunktionen bei einem Pfad für alle Anforderungsmethoden verwendet.
+Express supports methods that correspond to all HTTP request methods: `get`, `post`, and so on.
+For a full list, see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD).
-Im folgenden Beispiel wird der Handler für Anforderungen zur Weiterleitung "/secret" ausgeführt, um herauszufinden, ob Sie GET-, POST-, PUT-, DELETE- oder andere HTTP-Anforderungsmethoden verwenden, die im [HTTP-Modul](https://nodejs.org/api/http.html#http_http_methods) unterstützt werden.
+Es gibt eine spezielle Weiterleitungsmethode, `app.all()`, die nicht von einer HTTP-Methode abgeleitet wird. Diese Methode wird zum Laden von Middlewarefunktionen bei einem Pfad für alle Anforderungsmethoden verwendet. Im folgenden Beispiel wird der Handler für Anforderungen zur Weiterleitung "/secret" ausgeführt, um herauszufinden, ob Sie GET-, POST-, PUT-, DELETE- oder andere HTTP-Anforderungsmethoden verwenden, die im [HTTP-Modul](https://nodejs.org/api/http.html#http_http_methods) unterstützt werden.
-
-
-app.all('/secret', function (req, res, next) {
- console.log('Accessing the secret section ...');
- next(); // pass control to the next handler
-});
-
-
+```js
+app.all('/secret', (req, res, next) => {
+ console.log('Accessing the secret section ...')
+ next() // pass control to the next handler
+})
+```
Weiterleitungspfade
Über Weiterleitungspfade werden in Kombination mit einer Anforderungsmethode die Endpunkte definiert, bei denen Anforderungen erfolgen können. Weiterleitungspfade können Zeichenfolgen, Zeichenfolgemuster oder reguläre Ausdrücke sein.
-
-Express verwendet für den Abgleich der Weiterleitungspfade [path-to-regexp](https://www.npmjs.com/package/path-to-regexp). In der Dokumentation zu "path-to-regexp" finden Sie alle Möglichkeiten zum Definieren von Weiterleitungspfaden. [Express Route Tester](http://forbeslindesay.github.io/express-route-tester/) ist ein handliches Tool zum Testen von Express-Basisweiterleitungen, auch wenn dieses Tool keine Musterabgleiche unterstützt.
-
+{% capture caution-character %} In express 5, the characters `?`, `+`, `*`, `[]`, and `()` are handled differently than in version 4, please review the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-Abfragezeichenfolgen sind nicht Teil des Weiterleitungspfads.
-
+{% include admonitions/caution.html content=caution-character %}
-Dies sind einige Beispiele für Weiterleitungspfade auf Basis von Zeichenfolgen.
+{% capture note-dollar-character %}In express 4, regular expression characters such as `$` need to be escaped with a `\`.
+{% endcapture %}
+
+{% include admonitions/caution.html content=note-dollar-character %}
+
+{% capture note-path-to-regexp %}
+
+Express uses [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) for matching the route paths; see the path-to-regexp documentation for all the possibilities in defining route paths. [Express Route Tester](http://forbeslindesay.github.io/express-route-tester/) ist ein handliches Tool zum Testen von Express-Basisweiterleitungen, auch wenn dieses Tool keine Musterabgleiche unterstützt.
+
+{% endcapture %}
+
+{% include admonitions/note.html content=note-path-to-regexp %}
+
+{% capture query-string-note %}
+
+Query strings are not part of the route path.
+
+{% endcapture %}
+
+{% include admonitions/warning.html content=query-string-note %}
+
+### Route paths based on strings
Dieser Weiterleitungspfad gleicht Weiterleitungsanforderungen zum Stammverzeichnis (`/`) ab.
-
-
-app.get('/', function (req, res) {
- res.send('root');
-});
-
-
+```js
+app.get('/', (req, res) => {
+ res.send('root')
+})
+```
Dieser Weiterleitungspfad gleicht Anforderungen mit `/about` ab.
-
-
-app.get('/about', function (req, res) {
- res.send('about');
-});
-
-
+```js
+app.get('/about', (req, res) => {
+ res.send('about')
+})
+```
Dieser Weiterleitungspfad gleicht Anforderungen mit `/random.text` ab.
-
-
-app.get('/random.text', function (req, res) {
- res.send('random.text');
-});
-
-
+```js
+app.get('/random.text', (req, res) => {
+ res.send('random.text')
+})
+```
-Dies sind einige Beispiele für Weiterleitungspfade auf Basis von Zeichenfolgemustern.
+### Route paths based on string patterns
+
+{% capture caution-string-patterns %} The string patterns in Express 5 no longer work. Please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
+
+{% include admonitions/caution.html content=caution-string-patterns %}
Dieser Weiterleitungspfad gleicht `acd` und `abcd` ab.
-
-
-app.get('/ab?cd', function(req, res) {
- res.send('ab?cd');
-});
-
-
-
-Dieser Weiterleitungspfad gleicht `abcd`, `abbcd`, `abbbcd` usw. ab.
-
-
-
-app.get('/ab+cd', function(req, res) {
- res.send('ab+cd');
-});
-
-
-
-Dieser Weiterleitungspfad gleicht `abcd`, `abxcd`, `abRABDOMcd`, `ab123cd` usw. ab.
-
-
-
-app.get('/ab*cd', function(req, res) {
- res.send('ab*cd');
-});
-
-
+```js
+app.get('/ab?cd', (req, res) => {
+ res.send('ab?cd')
+})
+```
+
+Dies sind einige Beispiele für Weiterleitungspfade auf Basis von Zeichenfolgemustern.
+
+```js
+app.get('/ab+cd', (req, res) => {
+ res.send('ab+cd')
+})
+```
+
+Dies sind einige Beispiele für Weiterleitungspfade auf Basis von Zeichenfolgen.
+
+```js
+app.get('/ab*cd', (req, res) => {
+ res.send('ab*cd')
+})
+```
Dieser Weiterleitungspfad gleicht `/abe` und `/abcde` ab.
-
-
-app.get('/ab(cd)?e', function(req, res) {
- res.send('ab(cd)?e');
-});
-
-
+```js
+app.get('/ab(cd)?e', (req, res) => {
+ res.send('ab(cd)?e')
+})
+```
+
+### Route paths based on regular expressions
-
-Die Zeichen ?, +, * und () sind Subsets ihrer Entsprechungen in regulären Ausdrücken. Der Bindestrich (-) und der Punkt (.) werden von zeichenfolgebasierten Pfaden förmlich interpretiert.
+Dieser Weiterleitungspfad gleicht alle Weiterleitungsnamen ab, die den Buchstaben "a" enthalten.
+
+```js
+app.get(/a/, (req, res) => {
+ res.send('/a/')
+})
+```
+
+Dieser Weiterleitungspfad gleicht `butterfly` und `dragonfly`, jedoch nicht `butterflyman`, `dragonfly man` usw.
+
+```js
+app.get(/.*fly$/, (req, res) => {
+ res.send('/.*fly$/')
+})
+```
+
+Route parameters
+
+Route parameters are named URL segments that are used to capture the values specified at their position in the URL. The captured values are populated in the `req.params` object, with the name of the route parameter specified in the path as their respective keys.
+
+```
+Route path: /users/:userId/books/:bookId
+Request URL: http://localhost:3000/users/34/books/8989
+req.params: { "userId": "34", "bookId": "8989" }
+```
+
+To define routes with route parameters, simply specify the route parameters in the path of the route as shown below.
+
+```js
+app.get('/users/:userId/books/:bookId', (req, res) => {
+ res.send(req.params)
+})
+```
+
+
+The name of route parameters must be made up of "word characters" ([A-Za-z0-9_]).
-Beispiele für Weiterleitungspfade auf Basis regulärer Ausdrücke:
+Since the hyphen (`-`) and the dot (`.`) are interpreted literally, they can be used along with route parameters for useful purposes.
-Dieser Weiterleitungspfad gleicht alle Weiterleitungsnamen ab, die den Buchstaben "a" enthalten.
+```
+Route path: /flights/:from-:to
+Request URL: http://localhost:3000/flights/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+Route path: /plantae/:genus.:species
+Request URL: http://localhost:3000/plantae/Prunus.persica
+req.params: { "genus": "Prunus", "species": "persica" }
+```
+
+{% capture warning-regexp %}
+In express 5, Regexp characters are not supported in route paths, for more information please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax).{% endcapture %}
+
+{% include admonitions/caution.html content=warning-regexp %}
-
-
-app.get(/a/, function(req, res) {
- res.send('/a/');
-});
-
-
+To have more control over the exact string that can be matched by a route parameter, you can append a regular expression in parentheses (`()`):
-Dieser Weiterleitungspfad gleicht `butterfly` und `dragonfly`, jedoch nicht `butterflyman`, `dragonfly man` usw. ab.
+```
+Route path: /user/:userId(\d+)
+Request URL: http://localhost:3000/user/42
+req.params: {"userId": "42"}
+```
-
-
-app.get(/.*fly$/, function(req, res) {
- res.send('/.*fly$/');
-});
-
-
+{% capture escape-advisory %}
+
+Because the regular expression is usually part of a literal string, be sure to escape any `\` characters with an additional backslash, for example `\\d+`.
+
+{% endcapture %}
+
+{% include admonitions/warning.html content=escape-advisory %}
+
+{% capture warning-version %}
+
+In Express 4.x, the `*` character in regular expressions is not interpreted in the usual way. As a workaround, use `{0,}` instead of `*`. This will likely be fixed in Express 5.
+
+{% endcapture %}
+
+{% include admonitions/warning.html content=warning-version %}
Routenhandler (Weiterleitungsroutinen)
@@ -182,108 +248,99 @@ Routenhandler können eine Funktion und/oder ein Funktionsarray sein, wie in den
Eine einzelne Callback-Funktion kann eine Weiterleitung verarbeiten. Beispiel:
-
-
-app.get('/example/a', function (req, res) {
- res.send('Hello from A!');
-});
-
-
+```js
+app.get('/example/a', (req, res) => {
+ res.send('Hello from A!')
+})
+```
Mehrere Callback-Funktionen können eine Weiterleitung verarbeiten (achten Sie darauf, dass Sie das Objekt `next` angeben). Beispiel:
-
-
-app.get('/example/b', function (req, res, next) {
- console.log('the response will be sent by the next function ...');
- next();
-}, function (req, res) {
- res.send('Hello from B!');
-});
-
-
+```js
+app.get('/example/b', (req, res, next) => {
+ console.log('the response will be sent by the next function ...')
+ next()
+}, (req, res) => {
+ res.send('Hello from B!')
+})
+```
Ein Array von Callback-Funktionen kann eine Weiterleitung verarbeiten. Beispiel:
-
-
-var cb0 = function (req, res, next) {
- console.log('CB0');
- next();
+```js
+const cb0 = function (req, res, next) {
+ console.log('CB0')
+ next()
}
-var cb1 = function (req, res, next) {
- console.log('CB1');
- next();
+const cb1 = function (req, res, next) {
+ console.log('CB1')
+ next()
}
-var cb2 = function (req, res) {
- res.send('Hello from C!');
+const cb2 = function (req, res) {
+ res.send('Hello from C!')
}
-app.get('/example/c', [cb0, cb1, cb2]);
-
-
+app.get('/example/c', [cb0, cb1, cb2])
+```
Eine Kombination aus unabhängigen Funktionen und Funktionsarrays kann eine Weiterleitung verarbeiten. Beispiel:
-
-
-var cb0 = function (req, res, next) {
- console.log('CB0');
- next();
+```js
+const cb0 = function (req, res, next) {
+ console.log('CB0')
+ next()
}
-var cb1 = function (req, res, next) {
- console.log('CB1');
- next();
+const cb1 = function (req, res, next) {
+ console.log('CB1')
+ next()
}
-app.get('/example/d', [cb0, cb1], function (req, res, next) {
- console.log('the response will be sent by the next function ...');
- next();
-}, function (req, res) {
- res.send('Hello from D!');
-});
-
-
+app.get('/example/d', [cb0, cb1], (req, res, next) => {
+ console.log('the response will be sent by the next function ...')
+ next()
+}, (req, res) => {
+ res.send('Hello from D!')
+})
+```
Antwortmethoden
Über die Methoden für das Antwortobjekt (`res`) in der folgenden Tabelle kann eine Antwort an den Client gesendet und der Anforderung/Antwort-Zyklus beendet werden. Wenn keine dieser Methoden über einen Routenhandler aufgerufen wird, bleibt die Clientanforderung im Status "blockiert".
-| Methode | Beschreibung
-|----------------------|--------------------------------------
-| [res.download()](/{{ page.lang }}/4x/api.html#res.download) | Gibt eine Eingabeaufforderung zum Herunterladen einer Datei aus.
-| [res.end()](/{{ page.lang }}/4x/api.html#res.end) | Beendet den Prozess "Antwort".
-| [res.json()](/{{ page.lang }}/4x/api.html#res.json) | Sendet eine JSON-Antwort.
-| [res.jsonp()](/{{ page.lang }}/4x/api.html#res.jsonp) | Sendet eine JSON-Antwort mit JSONP-Unterstützung.
-| [res.redirect()](/{{ page.lang }}/4x/api.html#res.redirect) | Leitet eine Anforderung um.
-| [res.render()](/{{ page.lang }}/4x/api.html#res.render) | Gibt eine Anzeigevorlage aus.
-| [res.send()](/{{ page.lang }}/4x/api.html#res.send) | Sendet eine Antwort mit unterschiedlichen Typen.
-| [res.sendFile](/{{ page.lang }}/4x/api.html#res.sendFile) | Sendet eine Datei als Oktett-Stream.
-| [res.sendStatus()](/{{ page.lang }}/4x/api.html#res.sendStatus) | Legt den Antwortstatuscode fest und sendet dessen Zeichenfolgedarstellung als Antworthauptteil.
+| Methode | Beschreibung |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
+| [res.download()](/{{ page.lang }}/4x/api.html#res.download) | Gibt eine Eingabeaufforderung zum Herunterladen einer Datei aus. |
+| [res.end()](/{{ page.lang }}/4x/api.html#res.end) | End the response process. |
+| [res.json()](/{{ page.lang }}/4x/api.html#res.json) | Sendet eine JSON-Antwort. |
+| [res.jsonp()](/{{ page.lang }}/4x/api.html#res.jsonp) | Sendet eine JSON-Antwort mit JSONP-Unterstützung. |
+| [res.redirect()](/{{ page.lang }}/4x/api.html#res.redirect) | Leitet eine Anforderung um. |
+| [res.render()](/{{ page.lang }}/4x/api.html#res.render) | Render a view template. |
+| [res.send()](/{{ page.lang }}/4x/api.html#res.send) | Sendet eine Antwort mit unterschiedlichen Typen. |
+| [res.sendFile](/{{ page.lang }}/4x/api.html#res.sendFile) | Sendet eine Datei als Oktett-Stream. |
+| [res.sendStatus()](/{{ page.lang }}/4x/api.html#res.sendStatus) | Legt den Antwortstatuscode fest und sendet dessen Zeichenfolgedarstellung als Antworthauptteil. |
app.route()
-Sie können mithilfe von `app.route()` verkettbare Routenhandler für einen Weiterleitungspfad erstellen. Da der Pfad an einer einzelnen Position angegeben wird, ist das Erstellen modularer Weiterleitungen hilfreich, da Redundanzen und Schreibfehler reduziert werden. Weitere Informationen zu Weiterleitungen finden Sie in der Dokumentation zu [Router()](/{{ page.lang }}/4x/api.html#router).
+Sie können mithilfe von `app.route()` verkettbare Routenhandler für einen Weiterleitungspfad erstellen.
+Da der Pfad an einer einzelnen Position angegeben wird, ist das Erstellen modularer Weiterleitungen hilfreich, da Redundanzen und Schreibfehler reduziert werden. Weitere Informationen zu Weiterleitungen finden Sie in der Dokumentation zu [Router()](/{{ page.lang }}/4x/api.html#router).
Dies ist ein Beispiel für verkettete Routenhandler, die mit der Funktion `app.route()` definiert werden.
-
-
+```js
app.route('/book')
- .get(function(req, res) {
- res.send('Get a random book');
+ .get((req, res) => {
+ res.send('Get a random book')
})
- .post(function(req, res) {
- res.send('Add a book');
+ .post((req, res) => {
+ res.send('Add a book')
})
- .put(function(req, res) {
- res.send('Update the book');
- });
-
-
+ .put((req, res) => {
+ res.send('Update the book')
+ })
+```
express.Router
@@ -293,37 +350,43 @@ Im folgenden Beispiel wird ein Router als Modul erstellt, eine Middlewarefunktio
Erstellen Sie eine Routerdatei namens `birds.js` mit dem folgenden Inhalt im Anwendungsverzeichnis:
-
-
-var express = require('express');
-var router = express.Router();
+```js
+const express = require('express')
+const router = express.Router()
// middleware that is specific to this router
-router.use(function timeLog(req, res, next) {
- console.log('Time: ', Date.now());
- next();
-});
+const timeLog = (req, res, next) => {
+ console.log('Time: ', Date.now())
+ next()
+}
+router.use(timeLog)
+
// define the home page route
-router.get('/', function(req, res) {
- res.send('Birds home page');
-});
+router.get('/', (req, res) => {
+ res.send('Birds home page')
+})
// define the about route
-router.get('/about', function(req, res) {
- res.send('About birds');
-});
+router.get('/about', (req, res) => {
+ res.send('About birds')
+})
-module.exports = router;
-
-
+module.exports = router
+```
Laden Sie dann das Routermodul in die Anwendung:
-
-
-var birds = require('./birds');
-...
-app.use('/birds', birds);
-
-
+```js
+const birds = require('./birds')
+
+// ...
+
+app.use('/birds', birds)
+```
Die Anwendung kann nun Anforderungen an die Pfade `/birds` und `/birds/about` bearbeiten und ruft die Middlewarefunktion `timeLog` auf, die speziell für diese Weiterleitung bestimmt ist.
+
+But if the parent route `/birds` has path parameters, it will not be accessible by default from the sub-routes. To make it accessible, you will need to pass the `mergeParams` option to the Router constructor [reference](/{{ page.lang }}/5x/api.html#app.use).
+
+```js
+const router = express.Router({ mergeParams: true })
+```
diff --git a/de/guide/using-middleware.md b/de/guide/using-middleware.md
old mode 100755
new mode 100644
index a1eddb6b0a..0d1baea51c
--- a/de/guide/using-middleware.md
+++ b/de/guide/using-middleware.md
@@ -1,183 +1,229 @@
---
layout: page
title: Express-Middleware verwenden
+description: Learn how to use middleware in Express.js applications, including application-level and router-level middleware, error handling, and integrating third-party middleware.
menu: guide
-lang: de
+redirect_from: " "
---
# Middleware verwenden
Express ist ein Weiterleitungs- und Middleware-Web-Framework, das selbst nur minimale Funktionalität aufweist: Eine Express-Anwendung besteht im Wesentlichen aus einer Reihe von Middlewarefunktionsaufrufen.
-*Middlewarefunktionen* sind Funktionen, die Zugriff auf das [Anforderungsobjekt](/{{ page.lang }}/4x/api.html#req) (`req`), das [Antwortobjekt](/{{ page.lang }}/4x/api.html#res) (`res`) und die nächste Middlewarefunktion im Anforderung/Antwort-Zyklus der Anwendung haben. Die nächste Middlewarefunktion wird im Allgemeinen durch die Variable `next` bezeichnet.
+_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the next middleware function in the application's request-response cycle. Die nächste Middlewarefunktion wird im Allgemeinen durch die Variable `next` bezeichnet.
Über Middlewarefunktionen lassen sich die folgenden Tasks ausführen:
-* Ausführen von Code
-* Vornehmen von Änderungen an der Anforderung und an Antwortobjekten
-* Beenden des Anforderung/Antwort-Zyklus
-* Aufrufen der nächsten Middlewarefunktion im Stack
+- Ausführen von Code
+- Vornehmen von Änderungen an der Anforderung und an Antwortobjekten
+- End the request-response cycle.
+- Aufrufen der nächsten Middlewarefunktion im Stack
Wenn über die aktuelle Middlewarefunktion der Anforderung/Antwort-Zyklus nicht beendet werden kann, muss `next()` aufgerufen werden, um die Steuerung an die nächste Middlewarefunktion zu übergeben. Andernfalls geht die Anforderung in den Status "Blockiert" über.
Eine Express-Anwendung kann die folgenden Middlewaretypen verwenden:
- - [Middleware auf Anwendungsebene](#middleware.application)
- - [Middleware auf Routerebene](#middleware.router)
- - [Middleware für die Fehlerbehandlung](#middleware.error-handling)
- - [Integrierte Middleware](#middleware.built-in)
- - [Middleware anderer Anbieter](#middleware.third-party)
+- [Middleware auf Anwendungsebene](#middleware.application)
+- [Middleware auf Routerebene](#middleware.router)
+- [Middleware für die Fehlerbehandlung](#middleware.error-handling)
+- [Integrierte Middleware](#middleware.built-in)
+- [Middleware anderer Anbieter](#middleware.third-party)
-Sie können Middleware auf Anwendungsebene und Routerebene mit einem optionalen Mountpfad laden. Sie können auch eine Reihe von Middlewarefunktionen zusammen laden. Dadurch wird ein Sub-Stack des Middlewaresystems am Mountpunkt erstellt.
+Sie können Middleware auf Anwendungsebene und Routerebene mit einem optionalen Mountpfad laden.
+Sie können auch eine Reihe von Middlewarefunktionen zusammen laden. Dadurch wird ein Sub-Stack des Middlewaresystems am Mountpunkt erstellt.
Middleware auf Anwendungsebene
-Binden Sie Middleware auf Anwendungsebene zu einer Instanz des [Anwendungsobjekts](/{{ page.lang }}/4x/api.html#app), indem Sie die Funktionen `app.use()` und `app.METHOD()` verwenden. `METHOD` ist dabei die HTTP-Methode der Anforderung, die die Middlewarefunktion in Kleinschreibung verarbeitet (wie GET, PU oder POST).
+Bind application-level middleware to an instance of the [app object](/{{ page.lang }}/5x/api.html#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase.
Dieses Beispiel zeigt eine Middlewarefunktion ohne Mountpfad. Die Funktion wird immer dann ausgeführt, wenn die Anwendung eine Anforderung erhält.
-
-
-var app = express();
+```js
+const express = require('express')
+const app = express()
-app.use(function (req, res, next) {
- console.log('Time:', Date.now());
- next();
-});
-
-
+app.use((req, res, next) => {
+ console.log('Time:', Date.now())
+ next()
+})
+```
Dieses Beispiel zeigt eine Middlewarefunktion mit dem Mountpfad `/user/:id`. Die Funktion wird für jede Art von HTTP-Anforderung auf dem Pfad `/user/:id` ausgeführt.
-
-
-app.use('/user/:id', function (req, res, next) {
- console.log('Request Type:', req.method);
- next();
-});
-
-
+```js
+app.use('/user/:id', (req, res, next) => {
+ console.log('Request Type:', req.method)
+ next()
+})
+```
Dieses Beispiel zeigt eine Weiterleitung und deren Handlerfunktion (Middlewaresystem). Die Funktion verarbeitet GET-Anforderungen zum Pfad `/user/:id`.
-
-
-app.get('/user/:id', function (req, res, next) {
- res.send('USER');
-});
-
-
-
-Dies ist ein Beispiel zum Laden einer Reihe von Middlewarefunktionen an einem Mountpunkt mit einem Mountpfad. Das Beispiel veranschaulicht einen Middleware-Stack, über den Anforderungsinformationen zu einer HTTP-Anforderung zum Pfad `/user/:id` ausgegeben werden.
-
-
-
-app.use('/user/:id', function(req, res, next) {
- console.log('Request URL:', req.originalUrl);
- next();
-}, function (req, res, next) {
- console.log('Request Type:', req.method);
- next();
-});
-
-
+```js
+app.get('/user/:id', (req, res, next) => {
+ res.send('USER')
+})
+```
+
+Dies ist ein Beispiel zum Laden einer Reihe von Middlewarefunktionen an einem Mountpunkt mit einem Mountpfad.
+Das Beispiel veranschaulicht einen Middleware-Stack, über den Anforderungsinformationen zu einer HTTP-Anforderung zum Pfad `/user/:id` ausgegeben werden.
+
+```js
+app.use('/user/:id', (req, res, next) => {
+ console.log('Request URL:', req.originalUrl)
+ next()
+}, (req, res, next) => {
+ console.log('Request Type:', req.method)
+ next()
+})
+```
Mit einem Routenhandler können Sie mehrere Weiterleitungen für einen Pfad definieren. Im folgenden Beispiel werden zwei Weiterleitungen für GET-Anforderungen zum Pfad `/user/:id` definiert. Die zweite Weiterleitung verursacht zwar keine Probleme, wird jedoch nie aufgerufen, da durch die erste Weiterleitung der Anforderung/Antwort-Zyklus beendet wird.
Dieses Beispiel zeigt einen Middleware-Sub-Stack, über den GET-Anforderungen zum Pfad `/user/:id` verarbeitet werden.
-
-
-app.get('/user/:id', function (req, res, next) {
- console.log('ID:', req.params.id);
- next();
-}, function (req, res, next) {
- res.send('User Info');
-});
+```js
+app.get('/user/:id', (req, res, next) => {
+ console.log('ID:', req.params.id)
+ next()
+}, (req, res, next) => {
+ res.send('User Info')
+})
// handler for the /user/:id path, which prints the user ID
-app.get('/user/:id', function (req, res, next) {
- res.end(req.params.id);
-});
-
-
+app.get('/user/:id', (req, res, next) => {
+ res.send(req.params.id)
+})
+```
-Wenn Sie den Rest der Middlewarefunktionen eines Weiterleitungs-Middleware-Stack überspringen wollen, rufen Sie `next('route')` auf, um die Steuerung an die nächste Weiterleitung zu übergeben. **HINWEIS**: `next('route')` funktioniert nur in Middlewarefunktionen, die über die Funktionen `app.METHOD()` oder `router.METHOD()` geladen wurden.
+Wenn Sie den Rest der Middlewarefunktionen eines Weiterleitungs-Middleware-Stack überspringen wollen, rufen Sie `next('route')` auf, um die Steuerung an die nächste Weiterleitung zu übergeben.
+
+{% capture next-function %}
+
+`next('route')` will work only in middleware functions that were loaded by using the `app.METHOD()` or `router.METHOD()` functions.
+
+{% endcapture %}
+
+{% include admonitions/note.html content=next-function %}
Dieses Beispiel zeigt einen Middleware-Sub-Stack, über den GET-Anforderungen zum Pfad `/user/:id` verarbeitet werden.
-
-
-app.get('/user/:id', function (req, res, next) {
+```js
+app.get('/user/:id', (req, res, next) => {
// if the user ID is 0, skip to the next route
- if (req.params.id == 0) next('route');
+ if (req.params.id === '0') next('route')
// otherwise pass the control to the next middleware function in this stack
- else next(); //
-}, function (req, res, next) {
- // render a regular page
- res.render('regular');
-});
+ else next()
+}, (req, res, next) => {
+ // send a regular response
+ res.send('regular')
+})
-// handler for the /user/:id path, which renders a special page
-app.get('/user/:id', function (req, res, next) {
- res.render('special');
-});
-
-
+// handler for the /user/:id path, which sends a special response
+app.get('/user/:id', (req, res, next) => {
+ res.send('special')
+})
+```
+
+Middleware can also be declared in an array for reusability.
+
+Dies ist ein Beispiel zur Verwendung der Middlewarefunktion `express.static` mit einem ausführlich dargestellten Optionsobjekt:
+
+```js
+function logOriginalUrl (req, res, next) {
+ console.log('Request URL:', req.originalUrl)
+ next()
+}
+
+function logMethod (req, res, next) {
+ console.log('Request Type:', req.method)
+ next()
+}
+
+const logStuff = [logOriginalUrl, logMethod]
+app.get('/user/:id', logStuff, (req, res, next) => {
+ res.send('User Info')
+})
+```
Middleware auf Routerebene
Middleware auf Routerebene funktioniert in der gleichen Weise wie Middleware auf Anwendungsebene, mit dem einzigen Unterschied, dass sie an eine Instanz von `express.Router()` gebunden ist.
-
-
-var router = express.Router();
-
-
+```js
+const router = express.Router()
+```
+
Laden Sie Middleware auf Routerebene über die Funktionen `router.use()` und `router.METHOD()`.
+
Der folgende Beispielcode repliziert das Middlewaresystem, das oben für die Middleware auf Anwendungsebene gezeigt wird, durch Verwendung von Middleware auf Routerebene.
-
-
-var app = express();
-var router = express.Router();
+```js
+const express = require('express')
+const app = express()
+const router = express.Router()
// a middleware function with no mount path. This code is executed for every request to the router
-router.use(function (req, res, next) {
- console.log('Time:', Date.now());
- next();
-});
+router.use((req, res, next) => {
+ console.log('Time:', Date.now())
+ next()
+})
// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
-router.use('/user/:id', function(req, res, next) {
- console.log('Request URL:', req.originalUrl);
- next();
-}, function (req, res, next) {
- console.log('Request Type:', req.method);
- next();
-});
+router.use('/user/:id', (req, res, next) => {
+ console.log('Request URL:', req.originalUrl)
+ next()
+}, (req, res, next) => {
+ console.log('Request Type:', req.method)
+ next()
+})
// a middleware sub-stack that handles GET requests to the /user/:id path
-router.get('/user/:id', function (req, res, next) {
+router.get('/user/:id', (req, res, next) => {
// if the user ID is 0, skip to the next router
- if (req.params.id == 0) next('route');
+ if (req.params.id === '0') next('route')
// otherwise pass control to the next middleware function in this stack
- else next(); //
-}, function (req, res, next) {
+ else next()
+}, (req, res, next) => {
// render a regular page
- res.render('regular');
-});
+ res.render('regular')
+})
// handler for the /user/:id path, which renders a special page
-router.get('/user/:id', function (req, res, next) {
- console.log(req.params.id);
- res.render('special');
-});
+router.get('/user/:id', (req, res, next) => {
+ console.log(req.params.id)
+ res.render('special')
+})
// mount the router on the app
-app.use('/', router);
-
-
+app.use('/', router)
+```
+
+To skip the rest of the router's middleware functions, call `next('router')`
+to pass control back out of the router instance.
+
+Dieses Beispiel zeigt einen Middleware-Sub-Stack, über den GET-Anforderungen zum Pfad `/user/:id` verarbeitet werden.
+
+```js
+const express = require('express')
+const app = express()
+const router = express.Router()
+
+// predicate the router with a check and bail out when needed
+router.use((req, res, next) => {
+ if (!req.headers['x-auth']) return next('router')
+ next()
+})
+
+router.get('/user/:id', (req, res) => {
+ res.send('hello, user!')
+})
+
+// use the router and 401 anything falling through
+app.use('/admin', router, (req, res) => {
+ res.sendStatus(401)
+})
+```
Middleware für die Fehlerbehandlung
@@ -187,14 +233,12 @@ Middleware für die Fehlerbehandlung benötigt immer *vier* Argumente. Sie müss
Middlewarefunktionen für die Fehlerbehandlung werden in derselben Weise definiert wie andere Middlewarefunktionen, außer dass Fehlerbehandlungsfunktionen speziell bei Signaturen vier anstatt drei Argumente aufweisen `(err, req, res, next)`:
-
-
-app.use(function(err, req, res, next) {
- console.error(err.stack);
- res.status(500).send('Something broke!');
-});
-
-
+```js
+app.use((err, req, res, next) => {
+ console.error(err.stack)
+ res.status(500).send('Something broke!')
+})
+```
Details zu Middleware für die Fehlerbehandlung siehe [Fehlerbehandlung](/{{ page.lang }}/guide/error-handling.html).
@@ -202,56 +246,11 @@ Details zu Middleware für die Fehlerbehandlung siehe [Fehlerbehandlung](/{{ pag
Seit Version 4.x bestehen bei Express keine Abhängigkeiten zu [Connect](https://github.com/senchalabs/connect) mehr. Mit Ausnahme von `express.static` befinden sich nun alle Middlewarefunktionen, die bisher in Express enthalten waren, in separaten Modulen. Sehen Sie sich hierzu auch die [Liste der Middlewarefunktionen](https://github.com/senchalabs/connect#middleware) an.
-express.static(root, [options])
-
-Die einzige integrierte Middlewarefunktion in Express ist `express.static`. Diese Funktion basiert auf [serve-static](https://github.com/expressjs/serve-static) und ist zuständig für die statischen Assets einer Express-Anwendung.
-
-Das Argument `root` gibt das Stammverzeichnis an, von dem aus statische Assets bedient werden.
-
-Das optionale Objekt `options` kann folgende Eigenschaften aufweisen:
-
-| Eigenschaft | Beschreibung | Typ | Standard |
-|---------------|-----------------------------------------------------------------------|-------------|-----------------|
-| `dotfiles` | Option für Dateien mit Punkterweiterung (dotfiles). Mögliche Werte sind "allow", "deny" und "ignore" | Zeichenfolge | "ignore" |
-| `etag` | Aktiviert oder inaktiviert die etag-Generierung. | Boolesch | `true` |
-| `extensions` | Legt Dateierweiterungs-Fallbacks fest. | Bereich | `[]` |
-| `index` | Sendet die verzeichnissspezifische indexierte Datei. Bei `false` wird die Verzeichnisindexierung inaktiviert. | Gemischt | "index.html" |
- `lastModified` | Legt den Header `Last-Modified` auf das Datum der letzten Änderung der Datei im Betriebssystem fest. Mögliche Werte sind`true` und `false`. | Boolesch | `true` |
-| `maxAge` | Legt die Eigenschaft "max-age" des Headers "Cache-Control" in Millisekunden oder als Zeichenfolge im [ms-Format](https://www.npmjs.org/package/ms) fest. | Zahl | 0 |
-| `redirect` | Umleitung zu einem abschließenden "/", wenn der Pfadname ein Verzeichnis ist. | Boolesch | `true` |
-| `setHeaders` | Funktion zum Festlegen von HTTP-Headern für die Datei. | Funktion | |
-
-Dies ist ein Beispiel zur Verwendung der Middlewarefunktion `express.static` mit einem ausführlich dargestellten Optionsobjekt:
-
-
-
-var options = {
- dotfiles: 'ignore',
- etag: false,
- extensions: ['htm', 'html'],
- index: false,
- maxAge: '1d',
- redirect: false,
- setHeaders: function (res, path, stat) {
- res.set('x-timestamp', Date.now());
- }
-}
-
-app.use(express.static('public', options));
-
-
-
-Es sind mehrere statische Verzeichnisse pro Anwendung möglich:
-
-
-
-app.use(express.static('public'));
-app.use(express.static('uploads'));
-app.use(express.static('files'));
-
-
+Die einzige integrierte Middlewarefunktion in Express ist `express.static`.
-Details zur Funktion `serve-static` und deren Optionen finden Sie in der Dokumentation zu [serve-static](https://github.com/expressjs/serve-static).
+- [express.static](/en/5x/api.html#express.static) serves static assets such as HTML files, images, and so on.
+- [express.json](/en/5x/api.html#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
+- [express.urlencoded](/en/5x/api.html#express.urlencoded) parses incoming requests with URL-encoded payloads. **NOTE: Available with Express 4.16.0+**
Middleware anderer Anbieter
@@ -261,21 +260,17 @@ Installieren Sie das Modul Node.js für die erforderliche Funktionalität. Laden
Das folgende Beispiel veranschaulicht das Installieren und Laden der Middlewarefunktion `cookie-parser` für das Cookie-Parsing.
-
-
+```bash
$ npm install cookie-parser
-
-
+```
-
-
-var express = require('express');
-var app = express();
-var cookieParser = require('cookie-parser');
+```js
+const express = require('express')
+const app = express()
+const cookieParser = require('cookie-parser')
// load the cookie-parsing middleware
-app.use(cookieParser());
-
-
+app.use(cookieParser())
+```
Eine nicht vollständige Liste zu den Middlewarefunktionen anderer Anbieter, die im Allgemeinen mit Express verwendet werden, finden Sie unter [Middleware anderer Anbieter](../resources/middleware.html).
diff --git a/de/guide/using-template-engines.md b/de/guide/using-template-engines.md
old mode 100755
new mode 100644
index 5850860b81..abce1f7ffd
--- a/de/guide/using-template-engines.md
+++ b/de/guide/using-template-engines.md
@@ -1,59 +1,61 @@
---
layout: page
title: Template-Engines in Express verwenden
+description: Discover how to integrate and use template engines like Pug, Handlebars, and EJS with Express.js to render dynamic HTML pages efficiently.
menu: guide
-lang: de
+redirect_from: " "
---
# Template-Engines in Express verwenden
-Bevor über Express Vorlagendateien ausgegeben werden können, müssen die folgenden Anwendungseinstellungen festgelegt werden:
+A _template engine_ enables you to use static template files in your application. At runtime, the template engine replaces
+variables in a template file with actual values, and transforms the template into an HTML file sent to the client.
+This approach makes it easier to design an HTML page.
-* `views`, das Verzeichnis, in dem sich die Vorlagendateien befinden. Beispiel: `app.set('views', './views')`
-* `view engine`, die zu verwendende Template-Engine. Beispiel: `app.set('view engine', 'pug')`
+The [Express application generator](/{{ page.lang }}/starter/generator.html) uses [Pug](https://pugjs.org/api/getting-started.html) as its default, but it also supports [Handlebars](https://www.npmjs.com/package/handlebars), and [EJS](https://www.npmjs.com/package/ejs), among others.
+
+To render template files, set the following [application setting properties](/{{ page.lang }}/4x/api.html#app.set), in the default `app.js` created by the generator:
+
+- `views`, das Verzeichnis, in dem sich die Vorlagendateien befinden. Beispiel: `app.set('views', './views')`
+ This defaults to the `views` directory in the application root directory.
+- `view engine`, die zu verwendende Template-Engine. Beispiel: `app.set('view engine', 'pug')`
Installieren Sie dann das entsprechende npm-Paket für die Template-Engine:
-
-
+```bash
$ npm install pug --save
-
-
+```
+
+Express-konforme Template-Engines wie Pug exportieren eine Funktion namens `__express(filePath, options, callback)`, die über die Funktion `res.render()` aufgerufen wird, um den Vorlagencode ausgeben zu können.
+
+Einige Template-Engines folgen dieser Konvention nicht. Die Bibliothek [Consolidate.js](https://www.npmjs.org/package/consolidate) folgt dieser Konvention, indem alle gängigen Node.js-Template-Engines zugeordnet werden. Daher ist eine reibungslose Funktion in Express gewährleistet.
-
-Express-konforme Template-Engines wie Pug exportieren eine Funktion namens `__express(filePath, options, callback)`, die über die Funktion `res.render()` aufgerufen wird, um den Vorlagencode ausgeben zu können. Einige Template-Engines folgen dieser Konvention nicht. Die Bibliothek [Consolidate.js](https://www.npmjs.org/package/consolidate) folgt dieser Konvention, indem alle gängigen Node.js-Template-Engines zugeordnet werden. Daher ist eine reibungslose Funktion in Express gewährleistet.
Nach der Festlegung der View-Engine muss die Engine nicht angegeben oder das Template-Engine-Modul nicht in Ihre Anwendung geladen werden. Express lädt das Modul intern (wie unten für das obige Beispiel gezeigt).
-
-
-app.set('view engine', 'pug');
-
-
+```js
+app.set('view engine', 'pug')
+```
Erstellen Sie eine Pug-Vorlagendatei namens `index.pug` im Verzeichnis `views` mit dem folgenden Inhalt:
-
-
+```pug
html
head
title= title
body
h1= message
-
-
+```
Dann erstellen Sie eine Weiterleitung, um die Datei `index.pug` auszugeben. Wenn die Eigenschaft `view engine` nicht festgelegt wurde, müssen Sie die Erweiterung der Datei `view` angeben. Andernfalls müssen Sie diese Erweiterung nicht angeben.
-
-
-app.get('/', function (req, res) {
- res.render('index', { title: 'Hey', message: 'Hello there!'});
-});
-
-
+```js
+app.get('/', (req, res) => {
+ res.render('index', { title: 'Hey', message: 'Hello there!' })
+})
+```
Wenn Sie eine Anforderung zur Homepage ausführen, wird die Datei `index.pug` im HTML-Format ausgegeben.
-Weitere Informationen zur Funktionsweise von Template-Engines in Express siehe ["Template-Engines für Express entwickeln"](/{{ page.lang }}/advanced/developing-template-engines.html).
+The view engine cache does not cache the contents of the template's output, only the underlying template itself. The view is still re-rendered with every request even when the cache is on.
diff --git a/de/guide/writing-middleware.md b/de/guide/writing-middleware.md
old mode 100755
new mode 100644
index 283fbeaac8..c4d5653244
--- a/de/guide/writing-middleware.md
+++ b/de/guide/writing-middleware.md
@@ -1,33 +1,35 @@
---
layout: page
title: Middleware für die Verwendung in Express-Anwendungen schreiben
+description: Learn how to write custom middleware functions for Express.js applications, including examples and best practices for enhancing request and response handling.
menu: guide
-lang: de
+redirect_from: " "
---
# Middleware für die Verwendung in Express-Anwendungen schreiben
Überblick
-*Middlewarefunktionen* sind Funktionen, die Zugriff auf das [Anforderungsobjekt](/{{ page.lang }}/4x/api.html#req) (`req`), das [Antwortobjekt](/{{ page.lang }}/4x/api.html#res) (`res`) und die nächste Middlewarefunktion im Anforderung/Antwort-Zyklus der Anwendung haben. Die nächste Middlewarefunktion wird im Allgemeinen durch die Variable `next` bezeichnet.
+_Middlewarefunktionen_ sind Funktionen, die Zugriff auf das [Anforderungsobjekt](/{{ page.lang }}/4x/api.html#req) (`req`), das [Antwortobjekt](/{{ page.lang }}/4x/api.html#res) (`res`) und die nächste Middlewarefunktion im Anforderung/Antwort-Zyklus der Anwendung haben. Die nächste Middlewarefunktion wird im Allgemeinen durch die Variable `next` bezeichnet.
Über Middlewarefunktionen lassen sich die folgenden Tasks ausführen:
-* Ausführen von Code
-* Vornehmen von Änderungen an der Anforderung und an Antwortobjekten
-* Beenden des Anforderung/Antwort-Zyklus
-* Aufrufen der nächsten Middleware im Stack
+- Ausführen von Code
+- Vornehmen von Änderungen an der Anforderung und an Antwortobjekten
+- End the request-response cycle.
+- Aufrufen der nächsten Middleware im Stack
Wenn über die aktuelle Middlewarefunktion der Anforderung/Antwort-Zyklus nicht beendet werden kann, muss `next()` aufgerufen werden, um die Steuerung an die nächste Middlewarefunktion zu übergeben. Andernfalls geht die Anforderung in den Status "Blockiert" über.
Das folgende Beispiel zeigt die Elemente eines Middlewarefunktionsaufrufs:
-
-
-
+
+
+
+
-
-HTTP-Methode, für die die Middlewarefunktion angewendet wird.
+
+HTTP-Methode, für die die Middlewarefunktion angewendet wird.
+
+
+Starting with Express 5, middleware functions that return a Promise will call `next(value)` when they reject or throw an error. `next` will be called with either the rejected value or the thrown Error.
-Dies ist ein Beispiel einer einfachen Express-Anwendung namens "Hello World", für die Sie zwei Middlewarefunktionen definieren:
+Beispiel
-
-var express = require('express');
-var app = express();
+Here is an example of a simple "Hello World" Express application.
+The remainder of this article will define and add three middleware functions to the application:
+one called `myLogger` that prints a simple log message, one called `requestTime` that
+displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
-app.get('/', function (req, res) {
- res.send('Hello World!');
-});
+```js
+const express = require('express')
+const app = express()
-app.listen(3000);
-
+app.get('/', (req, res) => {
+ res.send('Hello World!')
+})
-Entwicklung
+app.listen(3000)
+```
+Dies ist ein Beispiel einer einfachen Express-Anwendung namens "Hello World", für die Sie zwei Middlewarefunktionen definieren:
Dies ist ein einfaches Beispiel einer Middlewarefunktion namens "myLogger". Diese Funktion gibt lediglich "LOGGED" aus, wenn eine Anforderung zur Anwendung über diese Funktion läuft. Die Middlewarefunktion ist der Variablen `myLogger` zugeordnet.
-
-
-var myLogger = function (req, res, next) {
- console.log('LOGGED');
- next();
-};
-
-
+```js
+const myLogger = function (req, res, next) {
+ console.log('LOGGED')
+ next()
+}
+```
-Beachten Sie den Aufruf oben zu `next()`. Durch den Aufruf dieser Funktion wird die nächste Middlewarefunktion in der Anwendung aufgerufen. Die Funktion `next()` ist nicht Teil der Node.js- oder Express-API, sondern das dritte Argument, das an die Middlewarefunktion übergeben wird. Die Funktion `next()` kann jeden beliebigen Namen haben, per Konvention erhält sie jedoch immer den Namen "next". Um Unklarheiten zu vermeiden, sollten Sie immer diese Konvention verwenden.
+Beachten Sie den Aufruf oben zu `next()`. Durch den Aufruf dieser Funktion wird die nächste Middlewarefunktion in der Anwendung aufgerufen.
+Die Funktion `next()` ist nicht Teil der Node.js- oder Express-API, sondern das dritte Argument, das an die Middlewarefunktion übergeben wird. Die Funktion `next()` kann jeden beliebigen Namen haben, per Konvention erhält sie jedoch immer den Namen "next".
+Um Unklarheiten zu vermeiden, sollten Sie immer diese Konvention verwenden.
+Zum Laden der Middlewarefunktion rufen Sie `app.use()` auf und geben die Middlewarefunktion an.
+Beispiel: Durch den folgenden Code wird die Middlewarefunktion `myLogger` vor der Weiterleitung zum Stammverzeichnispfad (/) geladen.
-Zum Laden der Middlewarefunktion rufen Sie `app.use()` auf und geben die Middlewarefunktion an. Beispiel: Durch den folgenden Code wird die Middlewarefunktion `myLogger` vor der Weiterleitung zum Stammverzeichnispfad (/) geladen.
+```js
+const express = require('express')
+const app = express()
-
-
-var express = require('express');
-var app = express();
+const myLogger = function (req, res, next) {
+ console.log('LOGGED')
+ next()
+}
-var myLogger = function (req, res, next) {
- console.log('LOGGED');
- next();
-};
+app.use(myLogger)
-app.use(myLogger);
+app.get('/', (req, res) => {
+ res.send('Hello World!')
+})
-app.get('/', function (req, res) {
- res.send('Hello World!');
-});
-
-app.listen(3000);
-
-
+app.listen(3000)
+```
Sobald die Anwendung eine Anforderung erhält, gibt sie die Nachricht "LOGGED" an das Terminal aus.
@@ -102,43 +109,112 @@ Wenn `myLogger` nach der Weiterleitung zum Stammverzeichnispfad geladen wird, er
Die Middlewarefunktion `myLogger` gibt einfach eine Nachricht aus und übergibt dann die Anforderung zur nächsten Middlewarefunktion im Stack durch Aufruf der Funktion `next()`.
+Middleware function requestTime
+
Im nächsten Beispiel wird die Eigenschaft `requestTime` zum Anforderungsobjekt hinzugefügt. Diese Middlewarefunktion erhält den Namen "requestTime".
-
-
-var requestTime = function (req, res, next) {
- req.requestTime = Date.now();
- next();
-};
-
-
+```js
+const requestTime = function (req, res, next) {
+ req.requestTime = Date.now()
+ next()
+}
+```
Die Anwendung verwendet nun die Middlewarefunktion `requestTime`. Außerdem verwendet die Callback-Funktion der Weiterleitung zum Stammverzeichnispfad die Eigenschaft, die die Middlewarefunktion zu `req` (dem Anforderungsobjekt) hinzufügt.
-
-
-var express = require('express');
-var app = express();
+```js
+const express = require('express')
+const app = express()
-var requestTime = function (req, res, next) {
- req.requestTime = Date.now();
- next();
-};
+const requestTime = function (req, res, next) {
+ req.requestTime = Date.now()
+ next()
+}
-app.use(requestTime);
+app.use(requestTime)
-app.get('/', function (req, res) {
- var responseText = 'Hello World!
';
- responseText += 'Requested at: ' + req.requestTime + '';
- res.send(responseText);
-});
+app.get('/', (req, res) => {
+ let responseText = 'Hello World!
'
+ responseText += `Requested at: ${req.requestTime}`
+ res.send(responseText)
+})
-app.listen(3000);
-
-
+app.listen(3000)
+```
Wenn Sie eine Anforderung zum Stammverzeichnis der Anwendung einleiten, zeigt die Anwendung nun die Zeitmarke Ihrer Anforderung im Browser an.
+Middleware function validateCookies
+
+Finally, we'll create a middleware function that validates incoming cookies and sends a 400 response if cookies are invalid.
+
+Here's an example function that validates cookies with an external async service.
+
+```js
+async function cookieValidator (cookies) {
+ try {
+ await externallyValidateCookie(cookies.testCookie)
+ } catch {
+ throw new Error('Invalid cookies')
+ }
+}
+```
+
+Here, we use the [`cookie-parser`](/resources/middleware/cookie-parser.html) middleware to parse incoming cookies off the `req` object and pass them to our `cookieValidator` function. The `validateCookies` middleware returns a Promise that upon rejection will automatically trigger our error handler.
+
+```js
+const express = require('express')
+const cookieParser = require('cookie-parser')
+const cookieValidator = require('./cookieValidator')
+
+const app = express()
+
+async function validateCookies (req, res, next) {
+ await cookieValidator(req.cookies)
+ next()
+}
+
+app.use(cookieParser())
+
+app.use(validateCookies)
+
+// error handler
+app.use((err, req, res, next) => {
+ res.status(400).send(err.message)
+})
+
+app.listen(3000)
+```
+
+
+Note how `next()` is called after `await cookieValidator(req.cookies)`. This ensures that if `cookieValidator` resolves, the next middleware in the stack will get called. If you pass anything to the `next()` function (except the string `'route'` or `'router'`), Express regards the current request as being an error and will skip any remaining non-error handling routing and middleware functions.
+
+
Da Sie Zugriff auf das Anforderungsobjekt, das Antwortobjekt, die nächste Middlewarefunktion im Stack und die gesamte Node.js-API haben, sind die Möglichkeiten, die Sie mit Middlewarefunktionen haben, nahezu unendlich.
Weitere Informationen zur Verwendung von Middleware in Express siehe [ Express-Middleware verwenden](/{{ page.lang }}/guide/using-middleware.html).
+
+Configurable middleware
+
+If you need your middleware to be configurable, export a function which accepts an options object or other parameters, which, then returns the middleware implementation based on the input parameters.
+
+File: `my-middleware.js`
+
+```js
+module.exports = function (options) {
+ return function (req, res, next) {
+ // Implement the middleware function based on the options object
+ next()
+ }
+}
+```
+
+The middleware can now be used as shown below.
+
+```js
+const mw = require('./my-middleware.js')
+
+app.use(mw({ option1: '1', option2: '2' }))
+```
+
+Refer to [cookie-session](https://github.com/expressjs/cookie-session) and [compression](https://github.com/expressjs/compression) for examples of configurable middleware.
diff --git a/de/index.md b/de/index.md
index a52f08bb5b..ffacc291f9 100644
--- a/de/index.md
+++ b/de/index.md
@@ -1,50 +1,61 @@
---
layout: home
-title: Express - Node.js-Framework von Webanwendungen
+title: Express - Node.js Web Application Framework
+description: "Express is a fast, unopinionated, minimalist web framework for Node.js, providing a robust set of features for web and mobile applications."
menu: home
-lang: de
+redirect_from: " "
---
+
- {% include header/header-{{ page.lang }}.html %}
-
-
+
-
- Schnelles, offenes, unkompliziertes Web-Framework für Node.js
+
+ Fast, unopinionated, minimalist web framework for Node.js
- $ npm install express --save
-
-
-
+ $ npm install express --save
-
-
+
-
+```javascript
+const express = require('express')
+const app = express()
+const port = 3000
-
-
- Webanwendungen
Express ist ein einfaches und flexibles Node.js-Framework von Webanwendungen, das zahlreiche leistungsfähige Features und Funktionen für Webanwendungen und mobile Anwendungen bereitstellt.
-
-
-
- APIs
Mithilfe unzähliger HTTP-Dienstprogrammmethoden und Middlewarefunktionen gestaltet sich das Erstellen einer leistungsfähigen API schnell und einfach.
+app.get('/', (req, res) => {
+ res.send('Hello World!')
+})
-
- Leistung
Express bietet eine Thin-Layer-Ebene mit grundlegenden Webanwendungsfunktionen, ohne die bekannten Node.js-Features zu überlagern.
+app.listen(port, () => {
+ console.log(`Example app listening on port ${port}`)
+})
+```
-
-
-
diff --git a/de/resources/community.md b/de/resources/community.md
old mode 100755
new mode 100644
index 084bc9a468..17ff7d1257
--- a/de/resources/community.md
+++ b/de/resources/community.md
@@ -1,35 +1,88 @@
---
layout: page
title: Express-Community
+description: Connect with the Express.js community, learn about the technical committee, find resources, explore community-contributed modules, and get involved in discussions.
menu: resources
-lang: de
+redirect_from: " "
---
# Community
-## Mailing-Liste
+## Technical committee
-Werden Sie Teil von über 2000 Express-Benutzern oder durchsuchen Sie über 5000
-Diskussionen in der [Google Group](https://groups.google.com/group/express-js).
+The Express technical committee meets online every two weeks (as needed) to discuss development and maintenance of Express,
+and other issues relevant to the Express project. Each meeting is typically announced in an
+[expressjs/discussions issue](https://github.com/expressjs/discussions/issues) with a link to join or view the meeting, which is
+open to all observers.
-## Gitter
+The meetings are recorded; for a list of the recordings, see the [Express.js YouTube channel](https://www.youtube.com/channel/UCYjxjAeH6TRik9Iwy5nXw7g).
-Der [expressjs/express-Chatroom](https://gitter.im/expressjs/express) eignet sich besonders für Entwickler, die sich für die täglichen Diskussionen zu Express interessieren.
+Members of the Express technical committee are:
-## IRC-Channel
+**Active:**
-Hunderte von Entwicklern, die jeden Tag in #express auf freenode auf Ihre Fragen warten. Wenn Sie Fragen zum Framework haben, schauen Sie doch einfach vorbei und holen Sie sich dazu geeignetes Feedback.
+- [@blakeembrey](https://github.com/blakeembrey) - Blake Embrey
+- [@crandmck](https://github.com/crandmck) - Rand McKinney
+- [@LinusU](https://github.com/LinusU) - Linus Unnebäck
+- [@ulisesgascon](https://github.com/ulisesGascon) - Ulises Gascón
+- [@sheplu](https://github.com/sheplu) - Jean Burellier
+- [@wesleytodd](https://github.com/wesleytodd) - Wes Todd
+- [@jonchurch](https://github.com/jonchurch) - Jon Church
+- [@ctcpip](https://github.com/ctcpip/) - Chris de Almeida
-## Beispiele
+**Inactive:**
-Zeigen Sie Dutzende von [Beispielen](https://github.com/expressjs/express/tree/master/examples) zu Express-Anwendungen im Repository an, das alles abdeckt – von API-Design und Authentifizierung bis zur Einbindung von Template-Engines.
+- [@dougwilson](https://github.com/dougwilson) - Douglas Wilson
+- [@hacksparrow](https://github.com/hacksparrow) - Hage Yaapa
+- [@jonathanong](https://github.com/jonathanong) - jongleberry
+- [@niftylettuce](https://github.com/niftylettuce) - niftylettuce
+- [@troygoode](https://github.com/troygoode) - Troy Goode
+
+## Express is made of many modules
+
+Unsere lebhafte Community hat zu einer Vielzahl von Erweiterungen, [Middlewaremodulen](/{{ page.lang }}/resources/middleware.html) und Frameworks der höheren Ebene geführt.
+
+Additionally, the Express community maintains modules in these two GitHub orgs:
+
+- [jshttp](https://jshttp.github.io/) modules providing useful utility functions; see [Utility modules](/{{ page.lang }}/resources/utils.html).
+- [pillarjs](https://pillarjs.github.io/): low-level modules that Express uses internally.
+
+To keep up with what is going on in the whole community, check out the [ExpressJS StatusBoard](https://expressjs.github.io/statusboard/).
## Probleme
Wenn Sie Ihrer Meinung nach einen Fehler festgestellt haben oder lediglich ein Feature/eine Funktion anfordern wollen, können Sie in der [Issue Queue](https://github.com/expressjs/express/issues) ein Ticket öffnen.
-## Andere Anbieter
+## Beispiele
+
+Zeigen Sie Dutzende von [Beispielen](https://github.com/expressjs/express/tree/master/examples) zu Express-Anwendungen im Repository an, das alles abdeckt – von API-Design und Authentifizierung bis zur Einbindung von Template-Engines.
+
+## Github Discussions
+
+The [GitHub Discussions](https://github.com/expressjs/discussions) section is an excellent space to engage in conversations about the development and maintenance of Express, as well as to share ideas and discuss topics related to its usage.
+
+# Branding of Express.js
+
+## Express.js Logo
-Unsere lebhafte Community hat zu einer Vielzahl von Erweiterungen, [Middlewaremodulen](/{{ page.lang }}/resources/middleware.html) und Frameworks der höheren Ebene geführt. Diese können Sie im
-[Wiki](https://github.com/expressjs/express/wiki) genauer begutachten.
+Express is a project of the OpenJS Foundation. Please review the [trademark policy](https://trademark-policy.openjsf.org/) for information about permissible use of Express.js logos and marks.
+
+
+
+
+
\ No newline at end of file
diff --git a/de/resources/contributing.md b/de/resources/contributing.md
new file mode 100644
index 0000000000..e37cee3122
--- /dev/null
+++ b/de/resources/contributing.md
@@ -0,0 +1,466 @@
+---
+layout: page
+title: Contributing to Express
+description: Find out how to contribute to Express.js, including guidelines for reporting issues, submitting pull requests, becoming a collaborator, and understanding security policies.
+menu: resources
+redirect_from: " "
+---
+
+# Contributing to Express
+
+### Looking to contribute to Expressjs.com? Click [here](#expressjs-website-contributing).
+
+Express and the other projects in the [expressjs organization on GitHub](https://github.com/expressjs) are projects of the [OpenJs Foundation](https://openjsf.org/).
+These projects are governed under the general policies and guidelines of the Node.js Foundation along with the additional guidelines below.
+
+- [Technical committee](#technical-committee)
+- [Community contributing guide](#community-contributing-guide)
+- [Collaborator's guide](#collaborators-guide)
+- [Security policies and procedures](#security-policies-and-procedures)
+
+## Technical committee
+
+The Express technical committee consists of active project members, and guides development and maintenance of the Express project. For more information, see [Express Community - Technical committee](community.html#technical-committee).
+
+## Community contributing guide
+
+
+
+The goal of this document is to create a contribution process that:
+
+- Encourages new contributions.
+- Encourages contributors to remain involved.
+- Avoids unnecessary processes and bureaucracy whenever possible.
+- Creates a transparent decision making process that makes it clear how
+ contributors can be involved in decision making.
+
+### Vocabulary
+
+- A **Contributor** is any individual creating or commenting on an issue or pull request.
+- A **Committer** is a subset of contributors who have been given write access to the repository.
+- A **Project Captain** is the lead maintainer of a repository.
+- A **TC (Technical Committee)** is a group of committers representing the required technical
+ expertise to resolve rare disputes.
+- A **Triager** is a subset of contributors who have been given triage access to the repository.
+
+### Logging Issues
+
+Log an issue for any question or problem you might have. When in doubt, log an issue, and
+any additional policies about what to include will be provided in the responses. The only
+exception is security disclosures which should be sent privately.
+
+Committers may direct you to another repository, ask for additional clarifications, and
+add appropriate metadata before the issue is addressed.
+
+Please be courteous and respectful. Every participant is expected to follow the
+project's Code of Conduct.
+
+### Contributions
+
+Any change to resources in this repository must be through pull requests. This applies to all changes
+to documentation, code, binary files, etc. Even long term committers and TC members must use
+pull requests.
+
+No pull request can be merged without being reviewed.
+
+For non-trivial contributions, pull requests should sit for at least 36 hours to ensure that
+contributors in other timezones have time to review. Consideration should also be given to
+weekends and other holiday periods to ensure active committers all have reasonable time to
+become involved in the discussion and review process if they wish.
+
+The default for each contribution is that it is accepted once no committer has an objection.
+During a review, committers may also request that a specific contributor who is most versed in a
+particular area gives a "LGTM" before the PR can be merged. There is no additional "sign off"
+process for contributions to land. Once all issues brought by committers are addressed it can
+be landed by any committer.
+
+In the case of an objection being raised in a pull request by another committer, all involved
+committers should seek to arrive at a consensus by way of addressing concerns being expressed
+by discussion, compromise on the proposed change, or withdrawal of the proposed change.
+
+If a contribution is controversial and committers cannot agree about how to get it to land
+or if it should land then it should be escalated to the TC. TC members should regularly
+discuss pending contributions in order to find a resolution. It is expected that only a
+small minority of issues be brought to the TC for resolution and that discussion and
+compromise among committers be the default resolution mechanism.
+
+### Becoming a Triager
+
+Anyone can become a triager! Read more about the process of being a triager in
+[the triage process document](https://github.com/expressjs/discussions/blob/master/docs/contributing/triager-guide.md).
+
+Currently, any existing [organization member](https://github.com/orgs/expressjs/people) can nominate
+a new triager. If you are interested in becoming a triager, our best advice is to actively participate
+in the community by helping triaging issues and pull requests. As well we recommend
+to engage in other community activities like attending the TC meetings, and participating in the Slack
+discussions. If you feel ready and have been helping triage some issues, reach out to an active member of the organization to ask if they'd
+be willing to support you. If they agree, they can create a pull request to formalize your nomination. In the case of an objection to the nomination, the triage team is responsible for working with the individuals involved and finding a resolution.
+
+You can also reach out to any of the [organization members](https://github.com/orgs/expressjs/people)
+if you have questions or need guidance.
+
+### Becoming a Committer
+
+All contributors who have landed significant and valuable contributions should be onboarded in a timely manner,
+and added as a committer, and be given write access to the repository.
+
+Committers are expected to follow this policy and continue to send pull requests, go through
+proper review, and have other committers merge their pull requests.
+
+### TC Process
+
+The TC uses a "consensus seeking" process for issues that are escalated to the TC.
+The group tries to find a resolution that has no open objections among TC members.
+If a consensus cannot be reached that has no objections then a majority wins vote
+is called. It is also expected that the majority of decisions made by the TC are via
+a consensus seeking process and that voting is only used as a last-resort.
+
+Resolution may involve returning the issue to project captains with suggestions on
+how to move forward towards a consensus. It is not expected that a meeting of the TC
+will resolve all issues on its agenda during that meeting and may prefer to continue
+the discussion happening among the project captains.
+
+Members can be added to the TC at any time. Any TC member can nominate another committer
+to the TC and the TC uses its standard consensus seeking process to evaluate whether or
+not to add this new member. The TC will consist of a minimum of 3 active members and a
+maximum of 10. If the TC should drop below 5 members the active TC members should nominate
+someone new. If a TC member is stepping down, they are encouraged (but not required) to
+nominate someone to take their place.
+
+TC members will be added as admin's on the Github orgs, npm orgs, and other resources as
+necessary to be effective in the role.
+
+To remain "active" a TC member should have participation within the last 12 months and miss
+no more than six consecutive TC meetings. Our goal is to increase participation, not punish
+people for any lack of participation, this guideline should be only be used as such
+(replace an inactive member with a new active one, for example). Members who do not meet this
+are expected to step down. If A TC member does not step down, an issue can be opened in the
+discussions repo to move them to inactive status. TC members who step down or are removed due
+to inactivity will be moved into inactive status.
+
+Inactive status members can become active members by self nomination if the TC is not already
+larger than the maximum of 10. They will also be given preference if, while at max size, an
+active member steps down.
+
+### Project Captains
+
+The Express TC can designate captains for individual projects/repos in the
+organizations. These captains are responsible for being the primary
+day-to-day maintainers of the repo on a technical and community front.
+Repo captains are empowered with repo ownership and package publication rights.
+When there are conflicts, especially on topics that effect the Express project
+at large, captains are responsible to raise it up to the TC and drive
+those conflicts to resolution. Captains are also responsible for making sure
+community members follow the community guidelines, maintaining the repo
+and the published package, as well as in providing user support.
+
+Like TC members, Repo captains are a subset of committers.
+
+To become a captain for a project the candidate is expected to participate in that
+project for at least 6 months as a committer prior to the request. They should have
+helped with code contributions as well as triaging issues. They are also required to
+have 2FA enabled on both their GitHub and npm accounts.
+
+Any TC member or an existing captain on the **same** repo can nominate another committer
+to the captain role. To do so, they should submit a PR to this document, updating the
+**Active Project Captains** section (while maintaining the sort order) with the project
+name, the nominee's GitHub handle, and their npm username (if different).
+
+- Repos can have as many captains as make sense for the scope of work.
+- A TC member or an existing repo captain **on the same project** can nominate a new captain.
+ Repo captains from other projects should not nominate captains for a different project.
+
+The PR will require at least 2 approvals from TC members and 2 weeks hold time to allow
+for comment and/or dissent. When the PR is merged, a TC member will add them to the
+proper GitHub/npm groups.
+
+#### Active Projects and Captains
+
+The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members)
+
+#### Current Initiative Captains
+
+The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains)
+
+### Developer's Certificate of Origin 1.1
+
+```text
+By making a contribution to this project, I certify that:
+
+ (a) The contribution was created in whole or in part by me and I
+ have the right to submit it under the open source license
+ indicated in the file; or
+
+ (b) The contribution is based upon previous work that, to the best
+ of my knowledge, is covered under an appropriate open source
+ license and I have the right under that license to submit that
+ work with modifications, whether created in whole or in part
+ by me, under the same open source license (unless I am
+ permitted to submit under a different license), as indicated
+ in the file; or
+
+ (c) The contribution was provided directly to me by some other
+ person who certified (a), (b) or (c) and I have not modified
+ it.
+
+ (d) I understand and agree that this project and the contribution
+ are public and that a record of the contribution (including all
+ personal information I submit with it, including my sign-off) is
+ maintained indefinitely and may be redistributed consistent with
+ this project or the open source license(s) involved.
+```
+
+## Collaborator's guide
+
+
+
+### Website Issues
+
+Open issues for the expressjs.com website in https://github.com/expressjs/expressjs.com.
+
+For issues in other Express managed repos (everything in `expressjs`, `pillarjs` or `jshttp` other than `expressjs/express`), be sure to check their contributing guide and open issues and PRs in the appropriate repository.
+
+### PRs and Code contributions
+
+- Tests must pass.
+- Follow the [JavaScript Standard Style](https://standardjs.com/) and `npm run lint`.
+- If you fix a bug, add a test.
+
+### Branches
+
+Use the `master` branch for bug fixes or minor work that is intended for the
+current release stream.
+
+Use the correspondingly named branch, e.g. `6.x`, for anything intended for
+a future release of Express.
+
+### Steps for contributing
+
+1. Create an issue for the
+ bug you want to fix or the feature that you want to add.
+2. Create your own fork on GitHub, then
+ checkout your fork.
+3. Write your code in your local copy. It's good practice to create a branch for
+ each new issue you work on, although not compulsory.
+4. To run the test suite, first install the dependencies by running `npm install`,
+ then run `npm test`.
+5. Ensure your code is linted by running `npm run lint` -- fix any issue you
+ see listed.
+6. If the tests pass, you can commit your changes to your fork and then create
+ a pull request from there. Make sure to reference your issue from the pull
+ request comments by including the issue number e.g. `#123`.
+
+### Issues which are questions
+
+We will typically close any vague issues or questions that are specific to some
+app you are writing. Please double check the docs and other references before
+being trigger happy with posting a question issue.
+
+Things that will help get your question issue looked at:
+
+- Full and runnable JS code.
+- Clear description of the problem or unexpected behavior.
+- Clear description of the expected result.
+- Steps you have taken to debug it yourself.
+
+If you post a question and do not outline the above items or make it easy for
+us to understand and reproduce your issue, it will be closed.
+
+If your question meets all of the above requirements but you do not believe it needs to be looked at
+by the maintainers
+(for example, if you are just looking for community input) please open it as a discussion topic instead
+of an issue. If you
+are unsure and open an issue, we may move it to discussions if we triage them and decide they do
+not need high
+visibility or maintainer input.
+
+## Security Policies and Procedures
+
+
+
+This document outlines security procedures and general policies for the Express
+project.
+
+- [Reporting a Bug](#reporting-a-bug)
+- [Disclosure Policy](#disclosure-policy)
+- [Comments on this Policy](#comments-on-this-policy)
+
+### Reporting a Bug
+
+The Express team and community take all security bugs in Express seriously.
+Thank you for improving the security of Express. We appreciate your efforts and
+responsible disclosure and will make every effort to acknowledge your
+contributions.
+
+Report security bugs by emailing `express-security@lists.openjsf.org`.
+
+To ensure the timely response to your report, please ensure that the entirety
+of the report is contained within the email body and not solely behind a web
+link or an attachment.
+
+The lead maintainer will acknowledge your email within 48 hours, and will send a
+more detailed response within 48 hours indicating the next steps in handling
+your report. After the initial reply to your report, the security team will
+endeavor to keep you informed of the progress towards a fix and full
+announcement, and may ask for additional information or guidance.
+
+Report security bugs in third-party modules to the person or team maintaining
+the module.
+
+### Pre-release Versions
+
+Alpha and Beta releases are unstable and **not suitable for production use**.
+Vulnerabilities found in pre-releases should be reported according to the [Reporting a Bug](#reporting-a-bug) section.
+Due to the unstable nature of the branch it is not guaranteed that any fixes will be released in the next pre-release.
+
+### Disclosure Policy
+
+When the security team receives a security bug report, they will assign it to a
+primary handler. This person will coordinate the fix and release process,
+involving the following steps:
+
+- Confirm the problem and determine the affected versions.
+- Audit code to find any potential similar problems.
+- Prepare fixes for all releases still under maintenance. These fixes will be
+ released as fast as possible to npm.
+
+### The Express Threat Model
+
+We are currently working on a new version of the security model, the most updated version can be found [here](https://github.com/expressjs/security-wg/blob/main/docs/ThreatModel.md)
+
+### Comments on this Policy
+
+If you have suggestions on how this process could be improved please submit a
+pull request.
+
+----
+
+# Contributing to Expressjs.com {#expressjs-website-contributing}
+
+
+
+### The Official Documentation of the Express JS Framework
+
+This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
+
+#### Need some ideas? These are some typical issues.
+
+1. **Website issues**: If you see anything on the site that could use a tune-up, think about how to fix it.
+ - Display or screen sizing problems
+ - Mobile responsiveness issues
+ - Missing or broken accessibility features
+ - Website outages
+ - Broken links
+ - Page structure or user interface enhancements
+
+2. **Content Issues**: Fix anything related to site content or typos.
+ - Spelling errors
+ - Incorrect/outdated Express JS documentation
+ - Missing content
+
+3. **Translation Issues**: Fix any translation errors or contribute new content.
+ - Fix spelling errors
+ - Fix incorrect/poorly translated words
+ - Check out the [Contributing translations](#contributing-translations) section below for a contributing guide.
+
+#### Want to work on a backlog issue?
+
+We often have bugs or enhancements that need work. You can find these under our repo's [Issues tab](https://github.com/expressjs/expressjs.com/issues). Check out the tags to find something that's a good match for you.
+
+#### Have an idea? Found a bug?
+
+If you've found a bug or a typo, or if you have an idea for an enhancement, you can:
+
+- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
+
+- Make a [Github pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work and it's ready to go, feel free to send it our way.
+
+## Getting Started
+
+The steps below will guide you through the Expressjs.com contribution process.
+
+#### Step 1: (OPTIONAL) Open a New Issue
+
+So you've found a problem that you want to fix, or have a site enhancement you want to make.
+
+1. If you want to get feedback or discuss, open a discussion [issue](https://github.com/expressjs/expressjs.com/issues/new/choose) prior to starting work. This is not required, but encouraged for larger proposals.
+ - While we highly encourage this step, it is only for submissions proposing significant change. It helps us to clarify and focus the work, and ensure it aligns with overall project priorities.
+ - For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
+ - When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
+
+2. After receiving your issue the Express JS documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
+ - For submissions proposing significant change, we encourage you to follow the review process before starting work.
+
+#### Step 2: Get the Application Code Base
+
+Clone the repo and get the code:
+
+```sh
+git clone https://github.com/expressjs/expressjs.com.git
+```
+
+After you've got the code you're ready to start making your changes!
+
+But just in case you need a little extra explanation, this section below outlines the main sections of the code base, where most changes are likely to be made.
+
+**Markdown Page Files**:
+
+- These files render to html and make up the individual pages of the site. Most of the site's documentation text content is written in `md` files.
+- Change these to make changes to individual pages' content/text or markup.
+- Each language has its own complete set of pages, located under their respective language directories - all the Spanish markdown content is found in the `es` directory, for example.
+
+**Includes Partials and Layout Templates**
+
+- `_includes` are partials that are imported and reused across multiple pages.
+ - These are used to import text content for reuse across pages, such as the API documentation, e.g., `_includes > api > en > 5x`, which is included in every language.
+ - These are used to include the page components that make up site-wide user interface and periphery structure, e.g., Header, Footer, etc.
+- `_layouts` are the templates used to wrap the site's individual pages.
+ - These are used to display the structure of the site's periphery, such as the header and footer, and for injecting and displaying individual markdown pages inside the `content` tag.
+
+**Blog Markdown Files**
+
+- These files make up the individual blog posts. If you want to contribute a blog post please
+ follow the specific instructions for [How to write a blog post.](https://expressjs.com/en/blog/write-post.html)
+- Located under the `_posts` directory.
+
+**CSS or Javascript**
+
+- All css and js files are kept in `css` and `js` folders on the project root.
+
+The Express JS website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [Github Pages](https://pages.github.com/).
+
+#### Step 3: Running the Application
+
+Now you'll need a way to see your changes, which means you'll need a running version of the application. You have two options.
+
+1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
+ - This is the recommended option for moderate to complex work.
+
+2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/site-deploys/deploy-previews/).
+ 1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
+ 2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
+ 3. After you are completely done your work and it's ready for review, remove the draft status on your pull request and submit your work.
+
+## Contributing translations
+
+We use Crowdin to manage our translations in multiple languages and achieve automatic translation with artificial intelligence. Since these translations can be inefficient in some cases, we need help from the community to provide accurate and helpful translations.
+
+The documentation is translated into these languages:
+
+- Chinese Simplified (`zh-cn`)
+- Chinese Traditional (`zh-tw`)
+- English (`en`)
+- French (`fr`)
+- German (`de`)
+- Italian (`it`)
+- Japanese (`ja`)
+- Korean (`ko`)
+- Brazilian Portuguese (`pt-br`)
+- Spanish (`es`)
+
+### How to translate
+
+1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
+2. [Select the language you want to translate](https://support.crowdin.com/joining-translation-project/#starting-translation)
+3. [Start translating](https://support.crowdin.com/online-editor/)
+
diff --git a/de/resources/glossary.md b/de/resources/glossary.md
old mode 100755
new mode 100644
index 71f78f6ef1..991a7a584a
--- a/de/resources/glossary.md
+++ b/de/resources/glossary.md
@@ -1,23 +1,16 @@
---
layout: page
title: Express-Glossar
+description: A comprehensive glossary of terms related to Express.js, Node.js, middleware, routing, and other key concepts to help you understand and use Express effectively.
menu: resources
-lang: de
+redirect_from: " "
---
# Glossar
-### Anforderung
-
-Eine HTTP-Anforderung. Ein Client übergibt eine HTTP-Anforderungsnachricht an einen Server, der wiederum eine Antwort zurückgibt. Bei der Anforderung muss eine der [Anforderungsmethoden](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) wie GET, POST usw. verwendet werden.
-
-### Antwort
-
-Eine HTTP-Antwort. Ein Server gibt eine HTTP-Antwortnachricht an den Client zurück. Die Antwort enthält Informationen zum Beendigungsstatus in Bezug auf die Anforderung und kann im Nachrichtenhauptteil auch angeforderten Inhalt enthalten.
-
### Anwendung
-Im Allgemeinen besteht eine Anwendung aus einem oder mehreren Programmen, über die Operationen für bestimmte Zwecke ausgeführt werden. Im Zusammenhang mit Express ist eine Anwendung ein Programm, das die auf der Node.js-Plattform laufende Express-API nutzt. Wird auch als [Anwendungsobjekt](/{{ page.lang }}/api.html#express) bezeichnet.
+Im Allgemeinen besteht eine Anwendung aus einem oder mehreren Programmen, über die Operationen für bestimmte Zwecke ausgeführt werden. Im Zusammenhang mit Express ist eine Anwendung ein Programm, das die auf der Node.js-Plattform laufende Express-API nutzt. Wird auch als [Anwendungsobjekt](/{{ page.lang }}/api.html#express) bezeichnet.
### API
@@ -31,26 +24,42 @@ Schnelles, offenes, unkompliziertes Web-Framework für Node.js-Anwendungen. Im A
Eine plattformübergreifende Unterstützungsbibliothek, bei der die asynchrone Ein-/Ausgabe im Mittelpunkt steht. Sie wurde in erster Linie für die Verwendung in Node.js entwickelt.
-### Middleware
+### middleware
Eine Funktion, die über die Weiterleitungsebene in Express vor dem letzten Anforderungshandler aufgerufen wird. Deshalb befindet sich diese Funktion in der Mitte zwischen einer unformatierten Anforderung und der endgültigen beabsichtigten Weiterleitung. Nachfolgend finden Sie einige Details zur Middlewareterminologie:
- * `var foo = require('middleware')` bedeutet, dass ein Node.js-Modul *benötigt* oder *verwendet* wird. Dann gibt die Anweisung `var mw = foo()` in der Regel die Middleware zurück.
- * `app.use(mw)` bedeutet, dass die *Middleware dem globalen Verarbeitungsstack hinzugefügt wird*.
- * `app.get('/foo', mw, function (req, res) { ... })` bedeutet, dass die *Middleware dem "GET /foo"-Verarbeitungsstack hinzugefügt wird*.
+- `var foo = require('middleware')` bedeutet, dass ein Node.js-Modul _benötigt_ oder _verwendet_ wird. Dann gibt die Anweisung `var mw = foo()` in der Regel die Middleware zurück.
+- `app.use(mw)` bedeutet, dass die _Middleware dem globalen Verarbeitungsstack hinzugefügt wird_.
+- `app.get('/foo', mw, function (req, res) { ... })` bedeutet, dass die _Middleware dem "GET /foo"-Verarbeitungsstack hinzugefügt wird_.
### Node.js
-Eine Softwareplattform, die für die Erstellung skalierbarer Netzanwendungen verwendet wird. Node.js verwendet JavaScript als Scripting-Sprache und erzielt den hohen Durchsatz durch nicht blockierende Ein-/Ausgabe und eine Ereignisschleife mit einem Thread. Siehe auch [nodejs.org](http://nodejs.org/). **Hinweis**: Der ursprüngliche Name lautet "Node.js". Mittlerweile ist die Bezeichnung "Node" geläufig.
+Eine Softwareplattform, die für die Erstellung skalierbarer Netzanwendungen verwendet wird. Node.js verwendet JavaScript als Scripting-Sprache und erzielt den hohen Durchsatz durch nicht blockierende Ein-/Ausgabe und eine Ereignisschleife mit einem Thread. Siehe auch [nodejs.org](http://nodejs.org/). **Hinweis**: Der ursprüngliche Name lautet "Node.js".
### Open-Source
Bei Verwendung als Adjektiv muss dieser Begriff mit Bindestrichen gekoppelt werden: Beispiel: "Dies ist eine Open-Source-Software." Siehe auch [Open-Source-Software in Wikipedia](http://en.wikipedia.org/wiki/Open-source_software).
-### Router
+{% capture english-rules %}
-Siehe [Router](/{{ page.lang }}/4x/api.html#router) in der API-Referenz.
+Although it is common not to hyphenate this term, we are using the standard English rules for hyphenating a compound adjective.
+
+{% endcapture %}
+
+{% include admonitions/note.html content=english-rules %}
+
+### Anforderung
+
+Eine HTTP-Antwort. Ein Server gibt eine HTTP-Antwortnachricht an den Client zurück. Die Antwort enthält Informationen zum Beendigungsstatus in Bezug auf die Anforderung und kann im Nachrichtenhauptteil auch angeforderten Inhalt enthalten.
+
+### Antwort
+
+Eine HTTP-Anforderung. Ein Client übergibt eine HTTP-Anforderungsnachricht an einen Server, der wiederum eine Antwort zurückgibt. The response contains completion status information about the request and might also contain requested content in its message body.
### Weiterleitung (Route)
Teil einer URL, die eine Ressource angibt. Beispiel: In `http://foo.com/products/id` ist "/products/id" die Weiterleitung.
+
+### Router
+
+Siehe [Router](/{{ page.lang }}/4x/api.html#router) in der API-Referenz.
diff --git a/de/resources/learning.md b/de/resources/learning.md
deleted file mode 100755
index 5529984543..0000000000
--- a/de/resources/learning.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-layout: page
-title: Zusätzliches Lernen
-menu: resources
-lang: de
----
-
-# Zusätzliches Lernen
-
-Disclaimer: Unendorsed community content.
-
-## Books
-
-Here are a few of the many books on Express:
-
- - **[Getting MEAN with Mongo, Express, Angular, and Node](http://www.manning.com/sholmes/)**,
-Manning Publications, early 2015.
- - **[Express.js in Action](http://www.manning.com/hahn/)**,
-Manning Publications, early 2015.
- - **[Mastering Web Application Development with Express](https://www.packtpub.com/web-development/mastering-web-application-development-express-raw)**,
-Packt Publishing, September 2014.
- - **[Web Development with Node and Express](http://shop.oreilly.com/product/0636920032977.do)**,
-O'Reilly Media, July 2014.
- - **[Node.js in Action](http://www.manning.com/cantelon/)**,
-Manning Publications, October 2013.
- - **[Express Web Application Development](https://www.packtpub.com/web-development/express-web-application-development)**,
-Packt Publishing, June 2013.
-- **[express - Middleware für node.js](http://www.amazon.de/express-Middleware-node-js-J%C3%B6rg-Krause/dp/1517281342/ref=sr_1_1?ie=UTF8&qid=1442001556&sr=8-1&keywords=1517281342)**,
-texxtoor, September 2015. In deutscher Sprache / in German language
-- **[JADE - die Template Engine für node.js](http://www.amazon.de/JADE-Die-Template-Engine-node-js/dp/1517282098/ref=sr_1_1?ie=UTF8&qid=1442001592&sr=8-1&keywords=1517282098)**,
-texxtoor, September 2015. In deutscher Sprache / in German language
-- **[Node Web Development, 2nd edition](https://www.packtpub.com/web-development/node-web-development-second-edition)**, Packt Publishing, August 2013
-
-### Add your book here!
-
-[Edit the Markdown file](https://github.com/expressjs/expressjs.com/blob/gh-pages/{{ page.lang }}/resources/learning.md) and add a link to your book, then submit a pull request (GitHub login required). Follow the format of the above listings.
-
-## Blogs
-
-- [StrongLoop Blog: Express category](http://strongloop.com/strongblog/category/express/)
-- [Hage Yaapa's Blog: Express category](http://www.hacksparrow.com/category/express-js)
-- [Codeforgeek Blog: Express category](http://codeforgeek.com/code/nodejs/express/)
-
-### Add your blog here!
-
-[Edit the Markdown file](https://github.com/expressjs/expressjs.com/blob/gh-pages/{{ page.lang }}/resources/learning.md) and add a link to your blog, then submit a pull request (GitHub login required). Follow the format of the above listings.
diff --git a/de/resources/middleware.md b/de/resources/middleware.md
old mode 100755
new mode 100644
index a000551777..6342018377
--- a/de/resources/middleware.md
+++ b/de/resources/middleware.md
@@ -1,64 +1,43 @@
---
-layout: page
+layout: middleware
title: Express-Middleware
+description: Explore a list of Express.js middleware modules maintained by the Express team and the community, including built-in middleware and popular third-party modules.
menu: resources
-lang: de
+redirect_from: " "
+module: mw-home
---
-# Middleware anderer Anbieter
+## Express-Middleware
Nachfolgend sind einige Express-Middlewaremodule aufgeführt:
- - [body-parser](https://github.com/expressjs/body-parser): Bisher: `express.bodyParser`, `json` und `urlencoded`.
- Siehe auch:
- - [body](https://github.com/raynos/body)
- - [co-body](https://github.com/visionmedia/co-body)
- - [raw-body](https://github.com/stream-utils/raw-body)
- - [compression](https://github.com/expressjs/compression): Bisher `express.compress`
- - [connect-image-optimus](https://github.com/msemenistyi/connect-image-optimus): Connect/Express-Middlewaremodule für optimales Image-Serving. Wechselt Images (wenn möglich) zu `.webp` oder `.jxr`.
- - [connect-timeout](https://github.com/expressjs/timeout): Bisher: `express.timeout`
- - [cookie-parser](https://github.com/expressjs/cookie-parser): Bisher: `express.cookieParser`
- - [cookie-session](https://github.com/expressjs/cookie-session): Bisher: `express.cookieSession`
- - [csurf](https://github.com/expressjs/csurf): Bisher: `express.csrf`
- - [errorhandler](https://github.com/expressjs/errorhandler): Bisher: `express.errorHandler`
- - [express-debug](https://github.com/devoidfury/express-debug): Entwicklungstool, mit dem eine Registerkarte mit Informationen zu Vorlagenvariablen (lokalen Variablen), zur aktuellen Sitzung, zu hilfreichen Anforderungsdaten usw. Ihrer Anwendung hinzugefügt werden können.
- - [express-partial-response](https://github.com/nemtsov/express-partial-response): Express-Middlewaremodul für die Filterung von Teilen von JSON-Antworten auf Basis der Abfragezeichenfolge `fields` durch Verwendung der Google-API Partial Response.
- - [express-session](https://github.com/expressjs/session): Bisher: `express.session`
- - [express-simple-cdn](https://github.com/jamiesteven/express-simple-cdn): Express-Middlewaremodul für die Verwendung eines CDN (Content Delivery Network) für statische Assets mit Unterstützung mehrerer Hosts (Beispiel: cdn1.host.com, cdn2.host.com).
- - [express-slash](https://github.com/ericf/express-slash): Express-Middlewaremodul für Benutzer, die hohen Wert auf abschließende Schrägstriche legen.
- - [express-stormpath](https://github.com/stormpath/stormpath-express): Express-Middlewaremodul für Benutzerspeicher, Authentifizierung, Autorisierung, SSO und Datensicherheit.
- - [express-uncapitalize](https://github.com/jamiesteven/express-uncapitalize): Middlewaremodul für die Umleitung von HTTP-Anforderungen mit Großbuchstaben in eine kanonische Form mit Kleinbuchstaben.
- - [helmet](https://github.com/helmetjs/helmet): Modul zur Sicherung Ihrer Anwendungen durch Festlegung verschiedener HTTP-Header.
- - [join-io](https://github.com/coderaiser/join-io "join-io"): Modul für die Verknüpfung von Dateien während der Verarbeitung, um die Anzahl der Anforderungen zu reduzieren.
- - [method-override](https://github.com/expressjs/method-override): Bisher: `express.methodOverride`
- - [morgan](https://github.com/expressjs/morgan): Bisher: `logger`
- - [passport](https://github.com/jaredhanson/passport): Express-Middlewaremodul für die Authentifizierung.
- - [response-time](https://github.com/expressjs/response-time): Bisher: `express.responseTime`
- - [serve-favicon](https://github.com/expressjs/serve-favicon): Bisher: `express.favicon`
- - [serve-index](https://github.com/expressjs/serve-index): Bisher: `express.directory`
- - [serve-static](https://github.com/expressjs/serve-static): Modul für statischen Inhalt.
- - [static-expiry](https://github.com/paulwalker/connect-static-expiry): URLs mit elektronischem Fingerabdruck oder Caching-Headern für statische Assets einschließlich Unterstützung für eine oder mehrere externe Domänen.
- - [vhost](https://github.com/expressjs/vhost): Bisher: `express.vhost`
- - [view-helpers](https://github.com/madhums/node-view-helpers): Express-Middlewaremodul, das allgemeine Helper-Methoden für Ansichten bereitstellt.
- - [sriracha-admin](https://github.com/hdngr/siracha): Express-Middlewaremodul, das eine Administratorsite für Mongoose dynamisch generiert.
+| [express-slash](https://github.com/ericf/express-slash): Express-Middlewaremodul für Benutzer, die hohen Wert auf abschließende Schrägstriche legen. | Beschreibung |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------- |
+| [body-parser](/{{page.lang}}/resources/middleware/body-parser.html) | Parse HTTP request body. |
+| [compression](/{{page.lang}}/resources/middleware/compression.html) | Compress HTTP responses. |
+| [connect-rid](/{{page.lang}}/resources/middleware/connect-rid.html) | Generate unique request ID. |
+| [cookie-parser](/{{page.lang}}/resources/middleware/cookie-parser.html) | Parse cookie header and populate `req.cookies`. See also [cookies](https://github.com/jed/cookies). |
+| [cookie-session](/{{page.lang}}/resources/middleware/cookie-session.html) | Establish cookie-based sessions. |
+| [cors](/{{page.lang}}/resources/middleware/cors.html) | Enable cross-origin resource sharing (CORS) with various options. |
+| [errorhandler](/{{page.lang}}/resources/middleware/errorhandler.html) | Development error-handling/debugging. |
+| [method-override](/{{page.lang}}/resources/middleware/method-override.html) | Override HTTP methods using header. |
+| [morgan](/{{page.lang}}/resources/middleware/morgan.html) | HTTP request logger. |
+| [multer](/{{page.lang}}/resources/middleware/multer.html) | Handle multi-part form data. |
+| [response-time](/{{page.lang}}/resources/middleware/response-time.html) | Record HTTP response time. |
+| [serve-favicon](/{{page.lang}}/resources/middleware/serve-favicon.html) | Serve a favicon. |
+| [serve-index](/{{page.lang}}/resources/middleware/serve-index.html) | Serve directory listing for a given path. |
+| [serve-static](/{{page.lang}}/resources/middleware/serve-static.html) | Serve static files. |
+| [session](/{{page.lang}}/resources/middleware/session.html) | Establish server-based sessions (development only). |
+| [timeout](/{{page.lang}}/resources/middleware/timeout.html) | Set a timeout perioHTTP request processing. |
+| [vhost](/{{page.lang}}/resources/middleware/vhost.html) | Create virtual domains. |
-Einige Middlewaremodule, die bisher zu Connect gehörten, werden vom Connect/Express-Team nicht mehr unterstützt. Diese Module werden durch ein alternatives oder besseres Modul ersetzt. Verwenden Sie eine der folgenden Alternativen:
+## Informationen zu weiteren Middlewaremodulen siehe:
- - express.cookieParser
- - [cookies](https://github.com/jed/cookies) und [keygrip](https://github.com/jed/keygrip)
- - express.limit
- - [raw-body](https://github.com/stream-utils/raw-body)
- - express.multipart
- - [connect-busboy](https://github.com/mscdex/connect-busboy)
- - [multer](https://github.com/expressjs/multer)
- - [connect-multiparty](https://github.com/superjoe30/connect-multiparty)
- - express.query
- - [qs](https://github.com/visionmedia/node-querystring)
- - express.staticCache
- - [st](https://github.com/isaacs/st)
- - [connect-static](https://github.com/andrewrk/connect-static)
+These are some additional popular middleware modules.
-Informationen zu weiteren Middlewaremodulen siehe:
+{% include community-caveat.html %}
- - [http-framework](https://github.com/Raynos/http-framework/wiki/Modules)
- - [expressjs](https://github.com/expressjs)
+| [express-slash](https://github.com/ericf/express-slash): Express-Middlewaremodul für Benutzer, die hohen Wert auf abschließende Schrägstriche legen. | Beschreibung |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [helmet](https://github.com/helmetjs/helmet): Modul zur Sicherung Ihrer Anwendungen durch Festlegung verschiedener HTTP-Header. | Helps secure your apps by setting various HTTP headers. |
+| [passport](https://github.com/jaredhanson/passport): Express-Middlewaremodul für die Authentifizierung. | Authentication using "strategies" such as OAuth, OpenID and many others. See [passportjs.org](https://passportjs.org/) for more information. |
diff --git a/de/resources/middleware/body-parser.md b/de/resources/middleware/body-parser.md
new file mode 100644
index 0000000000..9c3e7e0276
--- /dev/null
+++ b/de/resources/middleware/body-parser.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express body-parser middleware
+menu: resources
+redirect_from: ' '
+module: body-parser
+---
diff --git a/de/resources/middleware/compression.md b/de/resources/middleware/compression.md
new file mode 100644
index 0000000000..d288542a65
--- /dev/null
+++ b/de/resources/middleware/compression.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express compression middleware
+menu: resources
+redirect_from: ' '
+module: compression
+---
diff --git a/de/resources/middleware/connect-rid.md b/de/resources/middleware/connect-rid.md
new file mode 100644
index 0000000000..95b2689265
--- /dev/null
+++ b/de/resources/middleware/connect-rid.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express connect-rid middleware
+menu: resources
+redirect_from: ' '
+module: connect-rid
+---
diff --git a/de/resources/middleware/cookie-parser.md b/de/resources/middleware/cookie-parser.md
new file mode 100644
index 0000000000..55100372e3
--- /dev/null
+++ b/de/resources/middleware/cookie-parser.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express cookie-parser middleware
+menu: resources
+redirect_from: ' '
+module: cookie-parser
+---
diff --git a/de/resources/middleware/cookie-session.md b/de/resources/middleware/cookie-session.md
new file mode 100644
index 0000000000..c6308fa81c
--- /dev/null
+++ b/de/resources/middleware/cookie-session.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express cookie-session middleware
+menu: resources
+redirect_from: ' '
+module: cookie-session
+---
diff --git a/de/resources/middleware/cors.md b/de/resources/middleware/cors.md
new file mode 100644
index 0000000000..4692141929
--- /dev/null
+++ b/de/resources/middleware/cors.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express cors middleware
+menu: resources
+redirect_from: ' '
+module: cors
+---
diff --git a/de/resources/middleware/errorhandler.md b/de/resources/middleware/errorhandler.md
new file mode 100644
index 0000000000..3b11a1208e
--- /dev/null
+++ b/de/resources/middleware/errorhandler.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express errorhandler middleware
+menu: resources
+redirect_from: ' '
+module: errorhandler
+---
diff --git a/de/resources/middleware/method-override.md b/de/resources/middleware/method-override.md
new file mode 100644
index 0000000000..8dff029cd4
--- /dev/null
+++ b/de/resources/middleware/method-override.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express method-override middleware
+menu: resources
+redirect_from: ' '
+module: method-override
+---
diff --git a/de/resources/middleware/morgan.md b/de/resources/middleware/morgan.md
new file mode 100644
index 0000000000..99c4c80fa9
--- /dev/null
+++ b/de/resources/middleware/morgan.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express morgan middleware
+menu: resources
+redirect_from: ' '
+module: morgan
+---
diff --git a/de/resources/middleware/multer.md b/de/resources/middleware/multer.md
new file mode 100644
index 0000000000..2fffab3b73
--- /dev/null
+++ b/de/resources/middleware/multer.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express multer middleware
+menu: resources
+redirect_from: ' '
+module: multer
+---
diff --git a/de/resources/middleware/response-time.md b/de/resources/middleware/response-time.md
new file mode 100644
index 0000000000..78ee67cd32
--- /dev/null
+++ b/de/resources/middleware/response-time.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express response-time middleware
+menu: resources
+redirect_from: ' '
+module: response-time
+---
diff --git a/de/resources/middleware/serve-favicon.md b/de/resources/middleware/serve-favicon.md
new file mode 100644
index 0000000000..7a1c8e6f5c
--- /dev/null
+++ b/de/resources/middleware/serve-favicon.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express serve-favicon middleware
+menu: resources
+redirect_from: ' '
+module: serve-favicon
+---
diff --git a/de/resources/middleware/serve-index.md b/de/resources/middleware/serve-index.md
new file mode 100644
index 0000000000..deeb963c8f
--- /dev/null
+++ b/de/resources/middleware/serve-index.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express serve-index middleware
+menu: resources
+redirect_from: ' '
+module: serve-index
+---
diff --git a/de/resources/middleware/serve-static.md b/de/resources/middleware/serve-static.md
new file mode 100644
index 0000000000..ff9bcc313e
--- /dev/null
+++ b/de/resources/middleware/serve-static.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express serve-static middleware
+menu: resources
+redirect_from: ' '
+module: serve-static
+---
diff --git a/de/resources/middleware/session.md b/de/resources/middleware/session.md
new file mode 100644
index 0000000000..22cf354ae7
--- /dev/null
+++ b/de/resources/middleware/session.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express session middleware
+menu: resources
+redirect_from: ' '
+module: session
+---
diff --git a/de/resources/middleware/timeout.md b/de/resources/middleware/timeout.md
new file mode 100644
index 0000000000..1afa2c5dd3
--- /dev/null
+++ b/de/resources/middleware/timeout.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express timeout middleware
+menu: resources
+redirect_from: ' '
+module: timeout
+---
diff --git a/de/resources/middleware/vhost.md b/de/resources/middleware/vhost.md
new file mode 100644
index 0000000000..2bad4c964f
--- /dev/null
+++ b/de/resources/middleware/vhost.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express vhost middleware
+menu: resources
+redirect_from: ' '
+module: vhost
+---
diff --git a/de/resources/utils.md b/de/resources/utils.md
new file mode 100644
index 0000000000..0fd21eea69
--- /dev/null
+++ b/de/resources/utils.md
@@ -0,0 +1,25 @@
+---
+layout: page
+title: Express utilities
+description: Discover utility modules related to Express.js and Node.js, including tools for cookies, CSRF protection, URL parsing, routing, and more to enhance your applications.
+menu: resources
+redirect_from: " "
+---
+
+## Express utility functions
+
+The [pillarjs](https://github.com/pillarjs) GitHub organization contains a number of modules
+for utility functions that may be generally useful.
+
+| Utility modules | Beschreibung |
+| -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [cookies](https://www.npmjs.com/package/cookies) | Get and set HTTP(S) cookies that can be signed to prevent tampering, using Keygrip. Can be used with the Node.js HTTP library or as Express middleware. |
+| [csrf](https://www.npmjs.com/package/csrf) | Contains the logic behind CSRF token creation and verification. Use this module to create custom CSRF middleware. |
+| [finalhandler](https://www.npmjs.com/package/finalhandler) | Function to invoke as the final step to respond to HTTP request. |
+| [parseurl](https://www.npmjs.com/package/parseurl) | Parse a URL with caching. |
+| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Turn an Express-style path string such as \`\`/user/:name\` into a regular expression. |
+| [resolve-path](https://www.npmjs.com/package/resolve-path) | Resolves a relative path against a root path with validation. |
+| [router](https://www.npmjs.com/package/router) | Simple middleware-style router. |
+| [send](https://www.npmjs.com/package/send) | Library for streaming files as a HTTP response, with support for partial responses (ranges), conditional-GET negotiation, and granular events. |
+
+For additional low-level HTTP-related modules, see [jshttp](http://jshttp.github.io/).
diff --git a/de/starter/basic-routing.md b/de/starter/basic-routing.md
old mode 100755
new mode 100644
index e59ce41246..eaed71d21a
--- a/de/starter/basic-routing.md
+++ b/de/starter/basic-routing.md
@@ -1,24 +1,24 @@
---
layout: page
title: Basisrouting in Express
+description: Learn the fundamentals of routing in Express.js applications, including how to define routes, handle HTTP methods, and create route handlers for your web server.
menu: starter
-lang: de
+redirect_from: " "
---
# Basisrouting
-Per *Routing* wird bestimmt, wie eine Antwort auf eine Clientanforderung an einem bestimmten Endpunkt antwortet. Dies ist eine URI (oder ein Pfad) und eine bestimmte HTTP-Anforderungsmethode (GET, POST usw.).
+Per _Routing_ wird bestimmt, wie eine Antwort auf eine Clientanforderung an einem bestimmten Endpunkt antwortet. Dies ist eine URI (oder ein Pfad) und eine bestimmte HTTP-Anforderungsmethode (GET, POST usw.).
Jede Weiterleitung (Route) kann eine oder mehrere Handlerfunktionen haben, die ausgeführt werden, wenn die Weiterleitung abgeglichen wird.
Weiterleitungsdefinitionen haben die folgende Struktur:
-
-
+
+```js
app.METHOD(PATH, HANDLER)
-
-
+```
-Bedeutung:
+Where:
- `app` ist eine Instanz von `express`.
- `METHOD` ist eine [HTTP-Anforderungsmethode](http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol).
@@ -33,42 +33,36 @@ Die folgenden Beispiele veranschaulichen das Definieren einfacher Weiterleitunge
Antworten Sie mit `Hello World!` auf der Homepage:
-
-
-app.get('/', function (req, res) {
- res.send('Hello World!');
-});
-
-
+```js
+app.get('/', (req, res) => {
+ res.send('Hello World!')
+})
+```
-Antworten Sie auf POST-Anforderungen auf die Weiterleitung zum Stammverzeichnis (`/`), der Homepage der Anwendung:
+Respond to a POST request on the root route (`/`), the application's home page:
-
-
-app.post('/', function (req, res) {
- res.send('Got a POST request');
-});
-
-
+```js
+app.post('/', (req, res) => {
+ res.send('Got a POST request')
+})
+```
Antworten Sie auf eine PUT-Anforderung zur Weiterleitung `/user`:
-
-
-app.put('/user', function (req, res) {
- res.send('Got a PUT request at /user');
-});
-
-
+```js
+app.put('/user', (req, res) => {
+ res.send('Got a PUT request at /user')
+})
+```
Antworten Sie auf eine DELETE-Anforderung zur Weiterleitung `/user`:
-
-
-app.delete('/user', function (req, res) {
- res.send('Got a DELETE request at /user');
-});
-
-
+```js
+app.delete('/user', (req, res) => {
+ res.send('Got a DELETE request at /user')
+})
+```
Details zum Thema Routing finden Sie in der entsprechenden [Routinganleitung](/{{ page.lang }}/guide/routing.html).
+
+### [Previous: Express application generator ](/{{ page.lang }}/starter/generator.html) [Next: Serving static files in Express ](/{{ page.lang }}/starter/static-files.html)
diff --git a/de/starter/examples.md b/de/starter/examples.md
new file mode 100644
index 0000000000..a03e016318
--- /dev/null
+++ b/de/starter/examples.md
@@ -0,0 +1,21 @@
+---
+layout: page
+title: Express examples
+description: Explore a collection of Express.js application examples covering various use cases, integrations, and advanced configurations to help you learn and build your projects.
+menu: starter
+redirect_from: " "
+---
+
+{% capture examples %}{% include readmes/express-master/examples.md %}{% endcapture %}
+{{ examples | replace: "](.", "](https://github.com/expressjs/express/tree/master/examples" }}
+
+## Additional examples
+
+These are some additional examples with more extensive integrations.
+
+{% include community-caveat.html %}
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Fullstack app with Express and Next.js using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API with Express in TypeScript using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
+
+### [Previous: Static Files ](/{{ page.lang }}/starter/static-files.html) [Next: FAQ ](/{{ page.lang }}/starter/faq.html)
diff --git a/de/starter/faq.md b/de/starter/faq.md
old mode 100755
new mode 100644
index 89ba8e6a52..178246ecea
--- a/de/starter/faq.md
+++ b/de/starter/faq.md
@@ -1,8 +1,9 @@
---
layout: page
title: Häufig gestellte Fragen zu Express
+description: Finden Sie Antworten auf häufig gestellte Fragen zu Express.js, darunter Themen wie Anwendungsstruktur, Models, Authentifizierung, Template-Engines, Fehlerbehandlung und mehr.
menu: starter
-lang: de
+redirect_from: " "
---
# Häufig gestellte Fragen
@@ -13,14 +14,13 @@ Auf diese Frage gibt es keine verbindliche Antwort. Die Antwort hängt vom Umfan
Weiterleitungen und andere anwendungsspezifische Logik können in einer beliebigen Anzahl von Dateien und in jeder von Ihnen bevorzugten Verzeichnisstruktur vorkommen. Die folgenden Beispiele sollen als Entscheidungshilfe dienen:
-
-* [Weiterleitungslisten](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-47)
-* [Weiterleitungszuordnung](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
-* [Controller im MVC-Stil](https://github.com/expressjs/express/tree/master/examples/mvc)
+- [Weiterleitungslisten](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-47)
+- [Weiterleitungszuordnung](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [Controller im MVC-Stil](https://github.com/expressjs/express/tree/master/examples/mvc)
Darüber hinaus gibt es Erweiterungen anderer Anbieter für Express, die zur Vereinfachung einiger dieser Muster beitragen:
-* [Weiterleitung mit "express-resource"](https://github.com/expressjs/express-resource)
+- [Weiterleitung mit "express-resource"](https://github.com/expressjs/express-resource)
## Wie definiere ich Modelle?
@@ -30,40 +30,51 @@ Express hat keine Vorstellungen von einer Datenbank. Dieses Konzept bleibt Node-
## Wie kann ich Benutzer authentifizieren?
-Die Authentifizierung ist ein weiterer meinungsstarker Bereich, in den Express nicht eingreift. Sie können ein Authentifizierungsschema nach Ihren Vorstellungen verwenden. Ein einfaches Benutzername/Kennwort-Schema können Sie in [diesem Beispiel](https://github.com/expressjs/express/tree/master/examples/auth) sehen.
-
+Die Authentifizierung ist ein weiterer meinungsstarker Bereich, in den Express nicht eingreift. Sie können ein Authentifizierungsschema nach Ihren Vorstellungen verwenden.
+Ein einfaches Benutzername/Kennwort-Schema können Sie in [diesem Beispiel](https://github.com/expressjs/express/tree/master/examples/auth) sehen.
## Welche Template-Engines unterstützt Express?
-Express unterstützt jede Template-Engine, die der `(path, locals, callback)`-Signatur entspricht. Informationen zur Normalisierung von Template-Engine-Schnittstellen und -Caching siehe das Projekt [consolidate.js](https://github.com/visionmedia/consolidate.js). Nicht aufgelistete Template-Engines können trotzdem die Express-Signatur unterstützen.
+Express unterstützt jede Template-Engine, die der `(path, locals, callback)`-Signatur entspricht.
+Informationen zur Normalisierung von Template-Engine-Schnittstellen und -Caching siehe das Projekt [consolidate.js](https://github.com/visionmedia/consolidate.js). Nicht aufgelistete Template-Engines können trotzdem die Express-Signatur unterstützen.
+
+For more information, see [Using template engines with Express](/{{page.lang}}/guide/using-template-engines.html).
## Wie handhabe ich 404-Antworten?
In Express sind 404-Antworten nicht das Ergebnis eines Fehlers, sodass diese Antworten von der Fehlerbehandlungsroutine nicht erfasst werden. Dieses Verhalten ist damit zu erklären, dass eine 404-Antwort einfach angibt, dass keine weiteren Arbeiten auszuführen sind. In anderen Worten: Express hat alle Middlewarefunktionen und Weiterleitungen ausgeführt und festgestellt, dass keine Funktion eine Antwort zurückgegeben hat. Sie müssen also bei der Handhabung der 404-Antwort nur eine Middlewarefunktion am Ende des Stacks (unterhalb von allen anderen Funktionen) hinzufügen:
-
-
-app.use(function(req, res, next) {
- res.status(404).send('Sorry cant find that!');
-});
-
-
+```js
+app.use((req, res, next) => {
+ res.status(404).send("Sorry can't find that!")
+})
+```
+
+Add routes dynamically at runtime on an instance of `express.Router()`
+so the routes are not superseded by a middleware function.
## Wie richte ich eine Fehlerbehandlungsroutine ein?
Middleware für die Fehlerbehandlung wird in derselben Weise definiert wie andere Middleware; außer dass sie vier anstatt drei Argumente aufweist. Dies gilt speziell bei der Signatur `(err, req, res, next)`:
-
-
-app.use(function(err, req, res, next) {
- console.error(err.stack);
- res.status(500).send('Something broke!');
-});
-
-
+```js
+app.use((err, req, res, next) => {
+ console.error(err.stack)
+ res.status(500).send('Something broke!')
+})
+```
Weitere Informationen siehe [Fehlerbehandlung](/{{ page.lang }}/guide/error-handling.html).
## Wie gebe ich normales HTML-Format aus?
-Das ist nicht Ihre Aufgabe! Sie müssen kein HTML-Format mit der Funktion `res.render()` ausgeben. Verwenden Sie die Funktion `res.sendFile()`, wenn Sie es mit einer bestimmten Datei zu tun haben. Wenn Sie viele Assets aus einem Verzeichnis bedienen müssen, verwenden Sie die Middlewarefunktion `express.static()`.
+Das ist nicht Ihre Aufgabe! Sie müssen kein HTML-Format mit der Funktion `res.render()` ausgeben.
+Verwenden Sie die Funktion `res.sendFile()`, wenn Sie es mit einer bestimmten Datei zu tun haben.
+Wenn Sie viele Assets aus einem Verzeichnis bedienen müssen, verwenden Sie die Middlewarefunktion `express.static()`.
+
+## Welche Version von Node.js benötigt Express?
+
+- [Express 4.x](/{{ page.lang }}/4x/api.html) requires Node.js 0.10 or higher.
+- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher.
+
+### [Previous: More examples ](/{{ page.lang }}/starter/examples.html)
diff --git a/de/starter/generator.md b/de/starter/generator.md
old mode 100755
new mode 100644
index 11be303f78..f59f6e1d1a
--- a/de/starter/generator.md
+++ b/de/starter/generator.md
@@ -1,29 +1,34 @@
---
layout: page
title: Express-Anwendungsgenerator
+description: Learn how to use the Express application generator tool to quickly create a skeleton for your Express.js applications, streamlining setup and configuration.
menu: starter
-lang: de
+redirect_from: " "
---
# Express-Anwendungsgenerator
Mit dem Application Generator Tool `express` können Sie innerhalb kürzester Zeit ein Anwendungsgerüst erstellen.
-Installieren Sie `express` mit dem folgenden Befehl:
+You can run the application generator with the `npx` command (available in Node.js 8.2.0).
-
-
-$ npm install express-generator -g
-
-
+```bash
+$ npx express-generator
+```
+
+For earlier Node versions, install the application generator as a global npm package and then launch it:
+
+```bash
+$ npm install -g express-generator
+$ express
+```
Zeigen Sie die Befehlsoptionen mit der Option `-h` an:
-
-
+```bash
$ express -h
- Usage: express [options][dir]
+ Usage: express [options] [dir]
Options:
@@ -34,17 +39,15 @@ $ express -h
--pug add pug engine support
-H, --hogan add hogan.js engine support
--no-view generate without view engine
- -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
- -c, --css <engine> add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
+ -v, --view add view support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
+ -c, --css add stylesheet support (less|stylus|compass|sass) (defaults to plain css)
--git add .gitignore
-f, --force force on non-empty directory
-
-
+```
-Im folgenden Beispiel wird eine Express-Anwendung mit dem Namen _myapp_ im aktuellen Arbeitsverzeichnis erstellt:
+Im folgenden Beispiel wird eine Express-Anwendung mit dem Namen _myapp_ im aktuellen Arbeitsverzeichnis erstellt: The app will be created in a folder named _myapp_ in the current working directory and the view engine will be set to Pug:
-
-
+```bash
$ express --view=pug myapp
create : myapp
@@ -64,40 +67,38 @@ $ express --view=pug myapp
create : myapp/views/error.pug
create : myapp/bin
create : myapp/bin/www
-
-
+```
Installieren Sie dann Abhängigkeiten:
-
-
+```bash
$ cd myapp
$ npm install
-
-
+```
-Führen Sie unter MacOS oder Linux die Anwendung mit diesem Befehl aus:
+Verwenden Sie unter Windows diesen Befehl:
-
-
+```bash
$ DEBUG=myapp:* npm start
-
-
+```
-Verwenden Sie unter Windows diesen Befehl:
+Führen Sie unter MacOS oder Linux die Anwendung mit diesem Befehl aus:
-
-
+```bash
> set DEBUG=myapp:* & npm start
-
-
+```
+
+On Windows PowerShell, use this command:
+
+```bash
+PS> $env:DEBUG='myapp:*'; npm start
+```
Laden Sie dann `http://localhost:3000/` in Ihren Browser, um auf die Anwendung zuzugreifen.
Die erstellte Anwendung hat die folgende Verzeichnisstruktur:
-
-
+```bash
.
├── app.js
├── bin
@@ -117,9 +118,10 @@ Die erstellte Anwendung hat die folgende Verzeichnisstruktur:
└── layout.pug
7 directories, 9 files
-
-
+```
Die vom Generator erstellte Anwendungsstruktur ist nur eine der vielen Möglichkeiten, Express-Anwendungen zu strukturieren. Sie können diese Struktur verwenden oder sie an Ihre Anforderungen anpassen.
+
+### [Previous: Hello World ](/{{ page.lang }}/starter/hello-world.html) [Next: Basic routing](/{{ page.lang }}/starter/basic-routing.html)
diff --git a/de/starter/hello-world.md b/de/starter/hello-world.md
old mode 100755
new mode 100644
index 3534baba3b..3fd33c8743
--- a/de/starter/hello-world.md
+++ b/de/starter/hello-world.md
@@ -1,8 +1,9 @@
---
layout: page
title: Beispiel "Hello World" in Express
+description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners.
menu: starter
-lang: de
+redirect_from: " "
---
# Beispiel "Hello World"
@@ -11,12 +12,7 @@ lang: de
Dies ist wohl die einfachste Express-Anwendung, die Sie erstellen können. Es handelt sich um eine Anwendung mit nur einer Datei und — *nicht* das, was Sie mit dem [Express Generator](/{{ page.lang }}/starter/generator.html) erhalten würden. Mit dem Generator würde das Gerüst für eine vollständige Anwendung mit zahlreichen JavaScript-Dateien, Jade-Vorlagen und Unterverzeichnissen für verschiedene Zwecke erstellt werden.
-Erstellen Sie zunächst ein Verzeichnis namens `myapp`, wechseln Sie in das Verzeichnis und führen Sie `npm init` aus. Installieren Sie dann `express` als Abhängigkeit, wie im [Installationshandbuch](/{{ page.lang }}/starter/installing.html) beschrieben.
-
-Erstellen Sie im Verzeichnis `myapp` eine Datei namens `app.js` und fügen Sie den folgenden Code hinzu:
-
-
-
+```js
const express = require('express')
const app = express()
const port = 3000
@@ -26,24 +22,26 @@ app.get('/', (req, res) => {
})
app.listen(port, () => {
- console.log(`Example app listening at http://localhost:${port}`)
+ console.log(`Example app listening on port ${port}`)
})
-
-
+```
-Die Anwendung startet einen Server und ist an Port 3000 empfangsbereit für Verbindungen. Die Anwendung antwortet mit "Hello World!" auf Anforderungen zur Stamm-URL (`/`) oder zu *route*. Bei jedem anderen Pfad lautet die Antwort **404 Not Found**.
+Die Anwendung startet einen Server und ist an Port 3000 empfangsbereit für Verbindungen. Die Anwendung antwortet mit "Hello World!" auf Anforderungen zur Stamm-URL (`/`) oder zu _route_. Bei jedem anderen Pfad lautet die Antwort **404 Not Found**.
-
-`req` (Anforderung) und `res` (Antwort) sind genau dieselben Objekte, die Node bereitstellt. Sie können also `req.pipe()`, `req.on('data', callback)` und alle anderen Tasks, die Sie ausführen wollen, ohne Express ausführen.
-
+### Running Locally
+
+Erstellen Sie zunächst ein Verzeichnis namens `myapp`, wechseln Sie in das Verzeichnis und führen Sie `npm init` aus. Installieren Sie dann `express` als Abhängigkeit, wie im [Installationshandbuch](/{{ page.lang }}/starter/installing.html) beschrieben.
+
+Erstellen Sie im Verzeichnis `myapp` eine Datei namens `app.js` und fügen Sie den folgenden Code hinzu:
+
+`req` (Anforderung) und `res` (Antwort) sind genau dieselben Objekte, die Node bereitstellt. Sie können also `req.pipe()`, `req.on('data', callback)` und alle anderen Tasks, die Sie ausführen wollen, ohne Express ausführen.
Führen Sie die Anwendung mit dem folgenden Befehl aus:
-
-
+```bash
$ node app.js
-
-
+```
Laden Sie dann [http://localhost:3000/](http://localhost:3000/) in einen Browser, um die Ausgabe zu sehen.
+### [Previous: Installing ](/{{ page.lang }}/starter/installing.html) [Next: Express Generator ](/{{ page.lang }}/starter/generator.html)
diff --git a/de/starter/installing.md b/de/starter/installing.md
old mode 100755
new mode 100644
index e47a9c1cb9..e745549656
--- a/de/starter/installing.md
+++ b/de/starter/installing.md
@@ -1,55 +1,53 @@
---
layout: page
title: Express installieren
+description: Erfahren Sie, wie Sie Express.js in Ihrer Node.js-Umgebung installieren, wie Sie Ihr Projektverzeichnis aufsetzen und Abhängigkeiten mit npm verwalten.
menu: starter
-lang: de
+redirect_from: " "
---
# Installation
Angenommen, Sie haben [Node.js](https://nodejs.org/) bereits installiert. Erstellen Sie ein Verzeichnis für Ihre Anwendung und definieren Sie dieses Verzeichnis als Ihr Arbeitsverzeichnis.
-
-
+- [Express 4.x](/{{ page.lang }}/4x/api.html) requires Node.js 0.10 or higher.
+- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher.
+
+```bash
$ mkdir myapp
$ cd myapp
-
-
+```
-Erstellen Sie mit dem Befehl `npm init` eine Datei namens `package.json` für Ihre Anwendung. Weitere Informationen zur Funktionsweise von `package.json` finden Sie in den [Angaben zur Handhabung der npm-Datei package.json](https://docs.npmjs.com/files/package.json).
+Erstellen Sie mit dem Befehl `npm init` eine Datei namens `package.json` für Ihre Anwendung.
+Weitere Informationen zur Funktionsweise von `package.json` finden Sie in den [Angaben zur Handhabung der npm-Datei package.json](https://docs.npmjs.com/files/package.json).
-
-
+```bash
$ npm init
-
-
+```
-Dieser Befehl fordert Sie zur Eingabe verschiedener Angaben wie Name und Version Ihrer Anwendung auf. Für den Moment reicht es, die Eingabetaste zu drücken und die Standardwerte für die meisten Angaben zu akzeptieren. Es gilt jedoch folgende Ausnahme:
+Dieser Befehl fordert Sie zur Eingabe verschiedener Angaben wie Name und Version Ihrer Anwendung auf.
+For now, you can simply hit RETURN to accept the defaults for most of them, with the following exception:
-
-
+```
entry point: (index.js)
-
-
+```
Geben Sie `app.js` oder einen Namen Ihrer Vorstellung als Namen für die Hauptdatei ein. Wenn dieser Name `index.js` lauten soll, drücken Sie die Eingabetaste, um den vorgeschlagenen Standarddateinamen zu akzeptieren.
Installieren Sie jetzt Express im Verzeichnis `myapp` und speichern Sie es in der Abhängigkeitsliste. Beispiel:
-
-
-$ npm install express --save
-
-
+```bash
+$ npm install express
+```
Wenn Sie Express vorübergehend installieren und nicht zur Abhängigkeitsliste hinzufügen wollen, geben Sie die Option `--save` nicht an:
-
-
-$ npm install express
-
-
+```bash
+$ npm install express --no-save
+```
Node-Module, die mit der Option `--save` installiert werden, werden zur `Abhängigkeitsliste` in der Datei `package.json` hinzugefügt. Danach werden bei der Ausführung von `npm install` im Verzeichnis `app` automatisch alle Module in der Abhängigkeitsliste installiert.
+
+### [Next: Hello World ](/{{ page.lang }}/starter/hello-world.html)
\ No newline at end of file
diff --git a/de/starter/static-files.md b/de/starter/static-files.md
old mode 100755
new mode 100644
index 9c6197ee3e..620afe0dc0
--- a/de/starter/static-files.md
+++ b/de/starter/static-files.md
@@ -1,72 +1,79 @@
---
layout: page
title: Statische Dateien in Express bereitstellen
+description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware.
menu: starter
-lang: de
+redirect_from: " "
---
# Statische Dateien in Express bereitstellen
Wenn Sie statische Dateien wie Bilder, CSS-Dateien und JavaScript-Dateien bereitstellen wollen, verwenden Sie die in Express integrierte Middlewarefunktion `express.static`.
-Übergeben Sie den Namen des Verzeichnisses mit den statischen Assets an die Middlewarefunktion `express.static`, um direkt mit dem Bereitstellen der Dateien zu beginnen. Beispiel: Verwenden Sie den folgenden Code, um Bilder, CSS-Dateien und JavaScript-Dateien in einem Verzeichnis namens `public` bereitzustellen:
+The function signature is:
-
-
-app.use(express.static('public'));
-
-
+```js
+express.static(root, [options])
+```
+
+The `root` argument specifies the root directory from which to serve static assets.
+For more information on the `options` argument, see [express.static](/{{page.lang}}/5x/api.html#express.static).
+
+Beispiel: Verwenden Sie den folgenden Code, um Bilder, CSS-Dateien und JavaScript-Dateien in einem Verzeichnis namens `public` bereitzustellen:
+
+```js
+app.use(express.static('public'))
+```
Jetzt können Sie die Dateien laden, die sich im Verzeichnis `public` befinden:
-
-
+```text
http://localhost:3000/images/kitten.jpg
http://localhost:3000/css/style.css
http://localhost:3000/js/app.js
http://localhost:3000/images/bg.png
http://localhost:3000/hello.html
-
-
+```
-
-Express sucht nach den Dateien, die sich auf das Verzeichnis mit den statischen Assets beziehen. Der Name dieses Verzeichnisses ist also nicht Teil der URL.
+Express sucht nach den Dateien, die sich auf das Verzeichnis mit den statischen Assets beziehen. Der Name dieses Verzeichnisses ist also nicht Teil der URL.
Wenn Sie mehrere Verzeichnisse mit statischen Assets verwenden wollen, rufen Sie die Middlewarefunktion `express.static` mehrmals auf:
-
-
-app.use(express.static('public'));
-app.use(express.static('files'));
-
-
+```js
+app.use(express.static('public'))
+app.use(express.static('files'))
+```
Express sucht in der Reihenfolge nach den Dateien, in der sie die Verzeichnisse mit den statischen Assets über die Middlewarefunktion `express.static` festgelegt haben.
-Wenn Sie ein Präfix für einen virtuellen Pfad (in dem der Pfad nicht wirklich im Dateisystem existiert) für Dateien festlegen wollen, die über die Funktion `express.static` bereitgestellt werden, [müssen Sie einen Mountpfad](/{{ page.lang }}/4x/api.html#app.use) für das Verzeichnis mit den statischen Assets wie unten gezeigt angeben:
+{% capture alert_content %}
+For best results, [use a reverse proxy](/{{page.lang}}/advanced/best-practice-performance.html#use-a-reverse-proxy) cache to improve performance of serving static assets.
+{% endcapture %}
+{% include admonitions/note.html content=alert_content %}
-
-
-app.use('/static', express.static('public'));
-
-
+To create a virtual path prefix (where the path does not actually exist in the file system) for files that are served by the `express.static` function, [specify a mount path](/{{ page.lang }}/5x/api.html#app.use) for the static directory, as shown below:
+
+```js
+app.use('/static', express.static('public'))
+```
Jetzt können Sie die Dateien, die sich im Verzeichnis `public` befinden, aus dem Pfadpräfix `/static` laden.
-
-
+```text
http://localhost:3000/static/images/kitten.jpg
http://localhost:3000/static/css/style.css
http://localhost:3000/static/js/app.js
http://localhost:3000/static/images/bg.png
http://localhost:3000/static/hello.html
-
-
+```
Der Pfad, den Sie für die Funktion `express.static` angeben, ist jedoch relativ zum Verzeichnis, aus dem Sie Ihren Prozess `node` starten. Wenn Sie die Express-Anwendung aus einem anderen Verzeichnis ausführen, ist es sicherer, den absoluten Pfad des Verzeichnisses zu verwenden, das Sie bereitstellen wollen:
-
-
-app.use('/static', express.static(__dirname + '/public'));
-
-
+```js
+const path = require('path')
+app.use('/static', express.static(path.join(__dirname, 'public')))
+```
+
+For more details about the `serve-static` function and its options, see [serve-static](/resources/middleware/serve-static.html).
+
+### [Previous: Basic Routing ](/{{ page.lang }}/starter/basic-routing.html) [Next: More examples ](/{{ page.lang }}/starter/examples.html)
diff --git a/de/support/index.md b/de/support/index.md
new file mode 100644
index 0000000000..3b0c7ad325
--- /dev/null
+++ b/de/support/index.md
@@ -0,0 +1,27 @@
+---
+layout: page
+title: Version-Support
+description: Finden Sie Informationen über den Support-Zeitplan für verschiedene Express.js Versionen, einschließlich der aktuellen Versionen und der End-of-Life-Richtlinien.
+menu: support
+---
+
+# Version-Support
+
+Es wird nur die neueste Version einer bestimmten Hauptversionslinie unterstützt.
+
+Versionen, die EOL (End-of-Life) sind, _können_ Updates für kritische Sicherheitslücken erhalten, aber das Express-Team bietet keine Garantie und plant nicht, Fixes für gefundene Fehler zu entwickeln oder zu veröffentlichen.
+
+| Major Version | Minimale Node.js Version | Support Startdatum | Support-Enddatum |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- | ------------------ | ---------------------------------------------------------------- |
+| [**v5.x**{: .supported }](/{{page.lang}}/5x/api.html){: .ignore-underline} | 18 | September 2024 | **läuft derzeit**{: .supported } |
+| [**v4.x**{: .supported }](/{{page.lang}}/4x/api.html){: .ignore-underline} | 0.10.0 | April 2014 | **läuft derzeit**{: .supported } |
+| [**v3.x**{: .eol }](/{{page.lang}}/3x/api.html){: .ignore-underline} | 0.8.0 | Oktober 2012 | Juli 2015 |
+| [**v2.x**{: .eol }](/2x/){: .ignore-underline} | 0.4.1 | März 2011 | Juli 2012 |
+| **v1.x**{: .eol } | 0.2.0 | Dezember 2010 | März 2011 |
+| **v0.14.x**{: .eol } | 0.1.98 | Dezember 2010 | Dezember 2010 |
+
+## Kommerzielle Support Optionen
+
+Wenn Sie nicht auf eine unterstützte Version von Express aktualisieren können, wenden Sie sich bitte an einen unserer Partner, um Sicherheitsaktualisierungen zu erhalten:
+
+- [HeroDevs Never-Ending Support](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/en/3x/api.md b/en/3x/api.md
index 7421a648df..b421e2afe6 100644
--- a/en/3x/api.md
+++ b/en/3x/api.md
@@ -1,24 +1,27 @@
---
-layout: 3x-api
+layout: api
+version: 3x
title: Express 3.x - API Reference
+description: Access the API reference for Express.js version 3.x, noting that this version is end-of-life and no longer maintained - includes details on modules and methods.
menu: api
-lang: en
redirect_from: "/3x/api.html"
---
- **Express 3.x IS NO LONGER MAINTAINED**
+ **Express 3.x IS END-OF-LIFE AND NO LONGER MAINTAINED**
Known and unknown security and performance issues in 3.x have not been addressed since the last update (1 August, 2015). It is highly recommended to use the latest version of Express.
+
+ If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
3.x API
- {% include api/{{ page.lang }}/3x/express.md %}
- {% include api/{{ page.lang }}/3x/app.md %}
- {% include api/{{ page.lang }}/3x/req.md %}
- {% include api/{{ page.lang }}/3x/res.md %}
- {% include api/{{ page.lang }}/3x/middleware.md %}
+ {% include api/en/3x/express.md %}
+ {% include api/en/3x/app.md %}
+ {% include api/en/3x/req.md %}
+ {% include api/en/3x/res.md %}
+ {% include api/en/3x/middleware.md %}
diff --git a/en/4x/api.md b/en/4x/api.md
index 542148ec89..5c45b6f859 100644
--- a/en/4x/api.md
+++ b/en/4x/api.md
@@ -1,18 +1,27 @@
---
-layout: 4x-api
+layout: api
+version: 4x
title: Express 4.x - API Reference
+description: Access the API reference for Express.js 4.x, detailing all modules, methods, and properties for building web applications with this version.
menu: api
-lang: en
redirect_from: "/4x/api.html"
---
4.x API
- {% include api/{{ page.lang }}/4x/express.md %}
- {% include api/{{ page.lang }}/4x/app.md %}
- {% include api/{{ page.lang }}/4x/req.md %}
- {% include api/{{ page.lang }}/4x/res.md %}
- {% include api/{{ page.lang }}/4x/router.md %}
+ {% capture node-version %}
+
+ Express 4.0 requires Node.js 0.10 or higher.
+
+ {% endcapture %}
+
+ {% include admonitions/note.html content=node-version %}
+
+ {% include api/en/4x/express.md %}
+ {% include api/en/4x/app.md %}
+ {% include api/en/4x/req.md %}
+ {% include api/en/4x/res.md %}
+ {% include api/en/4x/router.md %}
diff --git a/en/5x/api.md b/en/5x/api.md
index 252b5cf954..e406b9c925 100644
--- a/en/5x/api.md
+++ b/en/5x/api.md
@@ -1,20 +1,27 @@
---
-layout: 5x-api
+layout: api
+version: 5x
title: Express 5.x - API Reference
+description: Access the API reference for Express.js 5.x, detailing all modules, methods, and properties for building web applications with this latest version.
menu: api
-lang: en
redirect_from: "/5x/api.html"
---
5.x API
- {% include note.html content="This is early alpha documentation that may be incomplete and is still under development." %}
+ {% capture node-version %}
- {% include api/{{ page.lang }}/5x/express.md %}
- {% include api/{{ page.lang }}/5x/app.md %}
- {% include api/{{ page.lang }}/5x/req.md %}
- {% include api/{{ page.lang }}/5x/res.md %}
- {% include api/{{ page.lang }}/5x/router.md %}
+ Express 5.0 requires Node.js 18 or higher.
+
+ {% endcapture %}
+
+ {% include admonitions/note.html content=node-version %}
+
+ {% include api/en/5x/express.md %}
+ {% include api/en/5x/app.md %}
+ {% include api/en/5x/req.md %}
+ {% include api/en/5x/res.md %}
+ {% include api/en/5x/router.md %}
diff --git a/en/advanced/best-practice-performance.md b/en/advanced/best-practice-performance.md
index d0ca92584c..d23e8ee392 100644
--- a/en/advanced/best-practice-performance.md
+++ b/en/advanced/best-practice-performance.md
@@ -1,15 +1,12 @@
---
layout: page
title: Performance Best Practices Using Express in Production
+description: Discover performance and reliability best practices for Express apps in production, covering code optimizations and environment setups for optimal performance.
menu: advanced
-lang: en
redirect_from: "/advanced/best-practice-performance.html"
---
-
# Production best practices: performance and reliability
-## Overview
-
This article discusses performance and reliability best practices for Express applications deployed to production.
This topic clearly falls into the "devops" world, spanning both traditional development and operations. Accordingly, the information is divided into two parts:
@@ -41,9 +38,10 @@ Here are some things you can do in your code to improve your application's perfo
Gzip compressing can greatly decrease the size of the response body and hence increase the speed of a web app. Use the [compression](https://www.npmjs.com/package/compression) middleware for gzip compression in your Express app. For example:
```js
-var compression = require('compression')
-var express = require('express')
-var app = express()
+const compression = require('compression')
+const express = require('express')
+const app = express()
+
app.use(compression())
```
@@ -55,11 +53,11 @@ Synchronous functions and methods tie up the executing process until they return
Although Node and many modules provide synchronous and asynchronous versions of their functions, always use the asynchronous version in production. The only time when a synchronous function can be justified is upon initial startup.
-If you are using Node.js 4.0+ or io.js 2.1.0+, you can use the `--trace-sync-io` command-line flag to print a warning and a stack trace whenever your application uses a synchronous API. Of course, you wouldn't want to use this in production, but rather to ensure that your code is ready for production. See the [node command-line options documentation](https://nodejs.org/api/cli.html#cli_trace_sync_io) for more information.
+You can use the `--trace-sync-io` command-line flag to print a warning and a stack trace whenever your application uses a synchronous API. Of course, you wouldn't want to use this in production, but rather to ensure that your code is ready for production. See the [node command-line options documentation](https://nodejs.org/api/cli.html#cli_trace_sync_io) for more information.
### Do logging correctly
-In general, there are two reasons for logging from your app: For debugging and for logging app activity (essentially, everything else). Using `console.log()` or `console.error()` to print log messages to the terminal is common practice in development. But [these functions are synchronous](https://nodejs.org/api/console.html#console_console_1) when the destination is a terminal or a file, so they are not suitable for production, unless you pipe the output to another program.
+In general, there are two reasons for logging from your app: For debugging and for logging app activity (essentially, everything else). Using `console.log()` or `console.error()` to print log messages to the terminal is common practice in development. But [these functions are synchronous](https://nodejs.org/api/console.html#console) when the destination is a terminal or a file, so they are not suitable for production, unless you pipe the output to another program.
#### For debugging
@@ -67,7 +65,7 @@ If you're logging for purposes of debugging, then instead of using `console.log(
#### For app activity
-If you're logging app activity (for example, tracking traffic or API calls), instead of using `console.log()`, use a logging library like [Winston](https://www.npmjs.com/package/winston) or [Bunyan](https://www.npmjs.com/package/bunyan). For a detailed comparison of these two libraries, see the StrongLoop blog post [Comparing Winston and Bunyan Node.js Logging](https://strongloop.com/strongblog/compare-node-js-logging-winston-bunyan/).
+If you're logging app activity (for example, tracking traffic or API calls), instead of using `console.log()`, use a logging library like [Pino](https://www.npmjs.com/package/pino), which is the fastest and most efficient option available.
### Handle exceptions properly
@@ -82,23 +80,12 @@ Before diving into these topics, you should have a basic understanding of Node/E
For more on the fundamentals of error handling, see:
-* [Error Handling in Node.js](https://www.joyent.com/developers/node/design/errors)
-* [Building Robust Node Applications: Error Handling](https://strongloop.com/strongblog/robust-node-applications-error-handling/) (StrongLoop blog)
-
-#### What not to do
-
-One thing you should _not_ do is to listen for the `uncaughtException` event, emitted when an exception bubbles all the way back to the event loop. Adding an event listener for `uncaughtException` will change the default behavior of the process that is encountering an exception; the process will continue to run despite the exception. This might sound like a good way of preventing your app from crashing, but continuing to run the app after an uncaught exception is a dangerous practice and is not recommended, because the state of the process becomes unreliable and unpredictable.
-
-Additionally, using `uncaughtException` is officially recognized as [crude](https://nodejs.org/api/process.html#process_event_uncaughtexception). So listening for `uncaughtException` is just a bad idea. This is why we recommend things like multiple processes and supervisors: crashing and restarting is often the most reliable way to recover from an error.
-
-We also don't recommend using [domains](https://nodejs.org/api/domain.html). It generally doesn't solve the problem and is a deprecated module.
+* [Error Handling in Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
#### Use try-catch
Try-catch is a JavaScript language construct that you can use to catch exceptions in synchronous code. Use try-catch, for example, to handle JSON parsing errors as shown below.
-Use a tool such as [JSHint](http://jshint.com/) or [JSLint](http://www.jslint.com/) to help you find implicit exceptions like [reference errors on undefined variables](http://www.jshint.com/docs/options/#undef).
-
Here is an example of using try-catch to handle a potential process-crashing exception.
This middleware function accepts a query field parameter named "params" that is a JSON object.
@@ -106,9 +93,9 @@ This middleware function accepts a query field parameter named "params" that is
app.get('/search', (req, res) => {
// Simulating async operation
setImmediate(() => {
- var jsonStr = req.query.params
+ const jsonStr = req.query.params
try {
- var jsonObj = JSON.parse(jsonStr)
+ const jsonObj = JSON.parse(jsonStr)
res.send('Success')
} catch (e) {
res.status(400).send('Invalid JSON string')
@@ -121,44 +108,39 @@ However, try-catch works only for synchronous code. Because the Node platform is
#### Use promises
-Promises will handle any exceptions (both explicit and implicit) in asynchronous code blocks that use `then()`. Just add `.catch(next)` to the end of promise chains. For example:
+When an error is thrown in an `async` function or a rejected promise is awaited inside an `async` function, those errors will be passed to the error handler as if calling `next(err)`
```js
-app.get('/', (req, res, next) => {
- // do some sync stuff
- queryDb()
- .then((data) => makeCsv(data)) // handle data
- .then((csv) => { /* handle csv */ })
- .catch(next)
+app.get('/', async (req, res, next) => {
+ const data = await userData() // If this promise fails, it will automatically call `next(err)` to handle the error.
+
+ res.send(data)
})
app.use((err, req, res, next) => {
- // handle error
+ res.status(err.status ?? 500).send({ error: err.message })
})
```
-Now all errors asynchronous and synchronous get propagated to the error middleware.
-
-However, there are two caveats:
-
-1. All your asynchronous code must return promises (except emitters). If a particular library does not return promises, convert the base object by using a helper function like [Bluebird.promisifyAll()](http://bluebirdjs.com/docs/api/promise.promisifyall.html).
-2. Event emitters (like streams) can still cause uncaught exceptions. So make sure you are handling the error event properly; for example:
+Also, you can use asynchronous functions for your middleware, and the router will handle errors if the promise fails, for example:
```js
-const wrap = fn => (...args) => fn(...args).catch(args[2])
+app.use(async (req, res, next) => {
+ req.locals.user = await getUser(req)
-app.get('/', wrap(async (req, res, next) => {
- const company = await getCompanyById(req.query.id)
- const stream = getLogoStreamById(company.id)
- stream.on('error', next).pipe(res)
-}))
+ next() // This will be called if the promise does not throw an error.
+})
```
-The `wrap()` function is a wrapper that catches rejected promises and calls `next()` with the error as the first argument.
-For details, see [Asynchronous
-Error Handling in Express with Promises, Generators and ES7](https://strongloop.com/strongblog/async-error-handling-expressjs-es7-promises-generators/#cleaner-code-with-generators).
+Best practice is to handle errors as close to the site as possible. So while this is now handled in the router, it’s best to catch the error in the middleware and handle it without relying on separate error-handling middleware.
+
+#### What not to do
+
+One thing you should _not_ do is to listen for the `uncaughtException` event, emitted when an exception bubbles all the way back to the event loop. Adding an event listener for `uncaughtException` will change the default behavior of the process that is encountering an exception; the process will continue to run despite the exception. This might sound like a good way of preventing your app from crashing, but continuing to run the app after an uncaught exception is a dangerous practice and is not recommended, because the state of the process becomes unreliable and unpredictable.
+
+Additionally, using `uncaughtException` is officially recognized as [crude](https://nodejs.org/api/process.html#process_event_uncaughtexception). So listening for `uncaughtException` is just a bad idea. This is why we recommend things like multiple processes and supervisors: crashing and restarting is often the most reliable way to recover from an error.
-For more information about error-handling by using promises, see [Promises in Node.js with Q – An Alternative to Callbacks](https://strongloop.com/strongblog/promises-in-node-js-with-q-an-alternative-to-callbacks/).
+We also don't recommend using [domains](https://nodejs.org/api/domain.html). It generally doesn't solve the problem and is a deprecated module.
## Things to do in your environment / setup {#in-environment}
@@ -173,7 +155,7 @@ Here are some things you can do in your system environment to improve your app's
### Set NODE_ENV to "production"
-The NODE_ENV environment variable specifies the environment in which an application is running (usually, development or production). One of the simplest things you can do to improve performance is to set NODE_ENV to "production."
+The NODE_ENV environment variable specifies the environment in which an application is running (usually, development or production). One of the simplest things you can do to improve performance is to set NODE_ENV to `production`.
Setting NODE_ENV to "production" makes Express:
@@ -181,20 +163,11 @@ Setting NODE_ENV to "production" makes Express:
* Cache CSS files generated from CSS extensions.
* Generate less verbose error messages.
-[Tests indicate](http://apmblog.dynatrace.com/2015/07/22/the-drastic-effects-of-omitting-node_env-in-your-express-js-applications/) that just doing this can improve app performance by a factor of three!
+[Tests indicate](https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/) that just doing this can improve app performance by a factor of three!
If you need to write environment-specific code, you can check the value of NODE_ENV with `process.env.NODE_ENV`. Be aware that checking the value of any environment variable incurs a performance penalty, and so should be done sparingly.
-In development, you typically set environment variables in your interactive shell, for example by using `export` or your `.bash_profile` file. But in general you shouldn't do that on a production server; instead, use your OS's init system (systemd or Upstart). The next section provides more details about using your init system in general, but setting NODE_ENV is so important for performance (and easy to do), that it's highlighted here.
-
-With Upstart, use the `env` keyword in your job file. For example:
-
-```sh
-# /etc/init/env.conf
- env NODE_ENV=production
-```
-
-For more information, see the [Upstart Intro, Cookbook and Best Practices](http://upstart.ubuntu.com/cookbook/#environment-variables).
+In development, you typically set environment variables in your interactive shell, for example by using `export` or your `.bash_profile` file. But in general, you shouldn't do that on a production server; instead, use your OS's init system (systemd). The next section provides more details about using your init system in general, but setting `NODE_ENV` is so important for performance (and easy to do), that it's highlighted here.
With systemd, use the `Environment` directive in your unit file. For example:
@@ -203,7 +176,7 @@ With systemd, use the `Environment` directive in your unit file. For example:
Environment=NODE_ENV=production
```
-For more information, see [Using Environment Variables In systemd Units](https://coreos.com/os/docs/latest/using-environment-variables-in-systemd-units.html).
+For more information, see [Using Environment Variables In systemd Units](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/).
### Ensure your app automatically restarts
@@ -222,32 +195,13 @@ In addition to restarting your app when it crashes, a process manager can enable
* Gain insights into runtime performance and resource consumption.
* Modify settings dynamically to improve performance.
-* Control clustering (StrongLoop PM and pm2).
-
-The most popular process managers for Node are as follows:
-
-* [StrongLoop Process Manager](http://strong-pm.io/)
-* [PM2](https://github.com/Unitech/pm2)
-* [Forever](https://www.npmjs.com/package/forever)
-
-For a feature-by-feature comparison of the three process managers, see [http://strong-pm.io/compare/](http://strong-pm.io/compare/). For a more detailed introduction to all three, see [Process managers for Express apps](/{{ page.lang }}/advanced/pm.html).
-
-Using any of these process managers will suffice to keep your application up, even if it does crash from time to time.
-
-However, StrongLoop PM has lots of features that specifically target production deployment. You can use it and the related StrongLoop tools to:
+* Control clustering (pm2).
-* Build and package your app locally, then deploy it securely to your production system.
-* Automatically restart your app if it crashes for any reason.
-* Manage your clusters remotely.
-* View CPU profiles and heap snapshots to optimize performance and diagnose memory leaks.
-* View performance metrics for your application.
-* Easily scale to multiple hosts with integrated control for Nginx load balancer.
-
-As explained below, when you install StrongLoop PM as an operating system service using your init system, it will automatically restart when the system restarts. Thus, it will keep your application processes and clusters alive forever.
+Historically, it was popular to use a Node.js process manager like [PM2](https://github.com/Unitech/pm2). See their documentation if you wish to do this. However, we recommend using your init system for process management.
#### Use an init system
-The next layer of reliability is to ensure that your app restarts when the server restarts. Systems can still go down for a variety of reasons. To ensure that your app restarts if the server crashes, use the init system built into your OS. The two main init systems in use today are [systemd](https://wiki.debian.org/systemd) and [Upstart](http://upstart.ubuntu.com/).
+The next layer of reliability is to ensure that your app restarts when the server restarts. Systems can still go down for a variety of reasons. To ensure that your app restarts if the server crashes, use the init system built into your OS. The main init system in use today is [systemd](https://wiki.debian.org/systemd).
There are two ways to use init systems with your Express app:
@@ -258,7 +212,7 @@ There are two ways to use init systems with your Express app:
Systemd is a Linux system and service manager. Most major Linux distributions have adopted systemd as their default init system.
-A systemd service configuration file is called a _unit file_, with a filename ending in `.service`. Here's an example unit file to manage a Node app directly. Replace the values enclosed in `` for your system and app:
+A systemd service configuration file is called a _unit file_, with a filename ending in `.service`. Here's an example unit file to manage a Node app directly. Replace the values enclosed in `` for your system and app:
```sh
[Unit]
@@ -289,93 +243,8 @@ Restart=always
[Install]
WantedBy=multi-user.target
```
-For more information on systemd, see the [systemd reference (man page)](http://www.freedesktop.org/software/systemd/man/systemd.unit.html).
-
-##### StrongLoop PM as a systemd service
-You can easily install StrongLoop Process Manager as a systemd service. After you do, when the server restarts, it will automatically restart StrongLoop PM, which will then restart all the apps it is managing.
-
-To install StrongLoop PM as a systemd service:
-
-```sh
-$ sudo sl-pm-install --systemd
-```
-
-Then start the service with:
-
-```sh
-$ sudo /usr/bin/systemctl start strong-pm
-```
-
-For more information, see [Setting up a production host (StrongLoop documentation)](https://docs.strongloop.com/display/SLC/Setting+up+a+production+host#Settingupaproductionhost-RHEL7+,Ubuntu15.04or15.10).
-
-##### Upstart
-
-Upstart is a system tool available on many Linux distributions for starting tasks and services during system startup, stopping them during shutdown, and supervising them. You can configure your Express app or process manager as a service and then Upstart will automatically restart it when it crashes.
-
-An Upstart service is defined in a job configuration file (also called a "job") with filename ending in `.conf`. The following example shows how to create a job called "myapp" for an app named "myapp" with the main file located at `/projects/myapp/index.js`.
-
-Create a file named `myapp.conf` at `/etc/init/` with the following content (replace the bold text with values for your system and app):
-
-```sh
-# When to start the process
-start on runlevel [2345]
-
-# When to stop the process
-stop on runlevel [016]
-
-# Increase file descriptor limit to be able to handle more requests
-limit nofile 50000 50000
-
-# Use production mode
-env NODE_ENV=production
-
-# Run as www-data
-setuid www-data
-setgid www-data
-
-# Run from inside the app dir
-chdir /projects/myapp
-
-# The process to start
-exec /usr/local/bin/node /projects/myapp/index.js
-
-# Restart the process if it is down
-respawn
-
-# Limit restart attempt to 10 times within 10 seconds
-respawn limit 10 10
-```
-
-NOTE: This script requires Upstart 1.4 or newer, supported on Ubuntu 12.04-14.10.
-
-Since the job is configured to run when the system starts, your app will be started along with the operating system, and automatically restarted if the app crashes or the system goes down.
-
-Apart from automatically restarting the app, Upstart enables you to use these commands:
-
-* `start myapp` – Start the app
-* `restart myapp` – Restart the app
-* `stop myapp` – Stop the app.
-
-For more information on Upstart, see [Upstart Intro, Cookbook and Best Practises](http://upstart.ubuntu.com/cookbook).
-
-##### StrongLoop PM as an Upstart service
-
-You can easily install StrongLoop Process Manager as an Upstart service. After you do, when the server restarts, it will automatically restart StrongLoop PM, which will then restart all the apps it is managing.
-
-To install StrongLoop PM as an Upstart 1.4 service:
-
-```sh
-$ sudo sl-pm-install
-```
-
-Then run the service with:
-
-```sh
-$ sudo /sbin/initctl start strong-pm
-```
-
-NOTE: On systems that don't support Upstart 1.4, the commands are slightly different. See [Setting up a production host (StrongLoop documentation)](https://docs.strongloop.com/display/SLC/Setting+up+a+production+host#Settingupaproductionhost-RHELLinux5and6,Ubuntu10.04-.10,11.04-.10) for more information.
+For more information on systemd, see the [systemd reference (man page)](http://www.freedesktop.org/software/systemd/man/systemd.unit.html).
### Run your app in a cluster
@@ -389,31 +258,17 @@ In clustered apps, worker processes can crash individually without affecting the
#### Using Node's cluster module
-Clustering is made possible with Node's [cluster module](https://nodejs.org/dist/latest-v4.x/docs/api/cluster.html). This enables a master process to spawn worker processes and distribute incoming connections among the workers. However, rather than using this module directly, it's far better to use one of the many tools out there that does it for you automatically; for example [node-pm](https://www.npmjs.com/package/node-pm) or [cluster-service](https://www.npmjs.com/package/cluster-service).
-
-#### Using StrongLoop PM
-
-If you deploy your application to StrongLoop Process Manager (PM), then you can take advantage of clustering _without_ modifying your application code.
-
-When StrongLoop Process Manager (PM) runs an application, it automatically runs it in a cluster with a number of workers equal to the number of CPU cores on the system. You can manually change the number of worker processes in the cluster using the slc command line tool without stopping the app.
-
-For example, assuming you've deployed your app to prod.foo.com and StrongLoop PM is listening on port 8701 (the default), then to set the cluster size to eight using slc:
-
-```sh
-$ slc ctl -C http://prod.foo.com:8701 set-size my-app 8
-```
-
-For more information on clustering with StrongLoop PM, see [Clustering](https://docs.strongloop.com/display/SLC/Clustering) in StrongLoop documentation.
+Clustering is made possible with Node's [cluster module](https://nodejs.org/api/cluster.html). This enables a master process to spawn worker processes and distribute incoming connections among the workers.
#### Using PM2
-If you deploy your application with PM2, then you can take advantage of clustering _without_ modifying your application code. You should ensure your [application is stateless](http://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) first, meaning no local data is stored in the process (such as sessions, websocket connections and the like).
+If you deploy your application with PM2, then you can take advantage of clustering _without_ modifying your application code. You should ensure your [application is stateless](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) first, meaning no local data is stored in the process (such as sessions, websocket connections and the like).
When running an application with PM2, you can enable **cluster mode** to run it in a cluster with a number of instances of your choosing, such as the matching the number of available CPUs on the machine. You can manually change the number of processes in the cluster using the `pm2` command line tool without stopping the app.
To enable cluster mode, start your application like so:
-```sh
+```bash
# Start 4 worker processes
$ pm2 start npm --name my-app -i 4 -- start
# Auto-detect number of available CPUs and start that many worker processes
@@ -424,7 +279,7 @@ This can also be configured within a PM2 process file (`ecosystem.config.js` or
Once running, the application can be scaled like so:
-```sh
+```bash
# Add 3 more workers
$ pm2 scale my-app +3
# Scale to a specific number of workers
@@ -437,18 +292,18 @@ For more information on clustering with PM2, see [Cluster Mode](https://pm2.keym
Another strategy to improve the performance in production is to cache the result of requests, so that your app does not repeat the operation to serve the same request repeatedly.
-Use a caching server like [Varnish](https://www.varnish-cache.org/) or [Nginx](https://www.nginx.com/resources/wiki/start/topics/examples/reverseproxycachingexample/) (see also [Nginx Caching](https://serversforhackers.com/nginx-caching/)) to greatly improve the speed and performance of your app.
+Use a caching server like [Varnish](https://www.varnish-cache.org/) or [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) (see also [Nginx Caching](https://serversforhackers.com/nginx-caching/)) to greatly improve the speed and performance of your app.
### Use a load balancer
No matter how optimized an app is, a single instance can handle only a limited amount of load and traffic. One way to scale an app is to run multiple instances of it and distribute the traffic via a load balancer. Setting up a load balancer can improve your app's performance and speed, and enable it to scale more than is possible with a single instance.
-A load balancer is usually a reverse proxy that orchestrates traffic to and from multiple application instances and servers. You can easily set up a load balancer for your app by using [Nginx](http://nginx.org/en/docs/http/load_balancing.html) or [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
+A load balancer is usually a reverse proxy that orchestrates traffic to and from multiple application instances and servers. You can easily set up a load balancer for your app by using [Nginx](https://nginx.org/en/docs/http/load_balancing.html) or [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
-With load balancing, you might have to ensure that requests that are associated with a particular session ID connect to the process that originated them. This is known as _session affinity_, or _sticky sessions_, and may be addressed by the suggestion above to use a data store such as Redis for session data (depending on your application). For a discussion, see [Using multiple nodes](http://socket.io/docs/using-multiple-nodes/).
+With load balancing, you might have to ensure that requests that are associated with a particular session ID connect to the process that originated them. This is known as _session affinity_, or _sticky sessions_, and may be addressed by the suggestion above to use a data store such as Redis for session data (depending on your application). For a discussion, see [Using multiple nodes](https://socket.io/docs/v4/using-multiple-nodes/).
### Use a reverse proxy
A reverse proxy sits in front of a web app and performs supporting operations on the requests, apart from directing requests to the app. It can handle error pages, compression, caching, serving files, and load balancing among other things.
-Handing over tasks that do not require knowledge of application state to a reverse proxy frees up Express to perform specialized application tasks. For this reason, it is recommended to run Express behind a reverse proxy like [Nginx](https://www.nginx.com/) or [HAProxy](http://www.haproxy.org/) in production.
+Handing over tasks that do not require knowledge of application state to a reverse proxy frees up Express to perform specialized application tasks. For this reason, it is recommended to run Express behind a reverse proxy like [Nginx](https://www.nginx.org/) or [HAProxy](https://www.haproxy.org/) in production.
diff --git a/en/advanced/best-practice-security.md b/en/advanced/best-practice-security.md
index ee8fa0d8e4..143cbdddf0 100644
--- a/en/advanced/best-practice-security.md
+++ b/en/advanced/best-practice-security.md
@@ -1,8 +1,8 @@
---
layout: page
title: Security Best Practices for Express in Production
+description: Discover crucial security best practices for Express apps in production, including using TLS, input validation, secure cookies, and preventing vulnerabilities.
menu: advanced
-lang: en
redirect_from: "/advanced/best-practice-security.html"
---
@@ -14,25 +14,36 @@ The term _"production"_ refers to the stage in the software lifecycle when an ap
Development and production environments are usually set up differently and have vastly different requirements. What's fine in development may not be acceptable in production. For example, in a development environment you may want verbose logging of errors for debugging, while the same behavior can become a security concern in a production environment. And in development, you don't need to worry about scalability, reliability, and performance, while those concerns become critical in production.
-{% include note.html content="If you believe you have discovered a security vulnerability in Express, please see
+{% capture security-note %}
+
+If you believe you have discovered a security vulnerability in Express, please see
[Security Policies and Procedures](/en/resources/contributing.html#security-policies-and-procedures).
-" %}
-Security best practices for Express applications in production include:
+{% endcapture %}
-- [Don’t use deprecated or vulnerable versions of Express](#dont-use-deprecated-or-vulnerable-versions-of-express)
-- [Use TLS](#use-tls)
-- [Use Helmet](#use-helmet)
-- [Use cookies securely](#use-cookies-securely)
-- [Prevent brute-force attacks against authorization](#prevent-brute-force-attacks-against-authorization)
-- [Ensure your dependencies are secure](#ensure-your-dependencies-are-secure)
-- [Avoid other known vulnerabilities](#avoid-other-known-vulnerabilities)
-- [Additional considerations](#additional-considerations)
+{% include admonitions/note.html content=security-note %}
+
+Security best practices for Express applications in production include:
+- [Production Best Practices: Security](#production-best-practices-security)
+ - [Overview](#overview)
+ - [Don't use deprecated or vulnerable versions of Express](#dont-use-deprecated-or-vulnerable-versions-of-express)
+ - [Use TLS](#use-tls)
+ - [Do not trust user input](#do-not-trust-user-input)
+ - [Prevent open redirects](#prevent-open-redirects)
+ - [Use Helmet](#use-helmet)
+ - [Reduce fingerprinting](#reduce-fingerprinting)
+ - [Use cookies securely](#use-cookies-securely)
+ - [Don't use the default session cookie name](#dont-use-the-default-session-cookie-name)
+ - [Set cookie security options](#set-cookie-security-options)
+ - [Prevent brute-force attacks against authorization](#prevent-brute-force-attacks-against-authorization)
+ - [Ensure your dependencies are secure](#ensure-your-dependencies-are-secure)
+ - [Avoid other known vulnerabilities](#avoid-other-known-vulnerabilities)
+ - [Additional considerations](#additional-considerations)
## Don't use deprecated or vulnerable versions of Express
-Express 2.x and 3.x are no longer maintained. Security and performance issues in these versions won't be fixed. Do not use them! If you haven't moved to version 4, follow the [migration guide](/{{ page.lang }}/guide/migrating-4.html).
+Express 2.x and 3.x are no longer maintained. Security and performance issues in these versions won't be fixed. Do not use them! If you haven't moved to version 4, follow the [migration guide](/{{ page.lang }}/guide/migrating-4.html) or consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
Also ensure you are not using any of the vulnerable Express versions listed on the [Security updates page](/{{ page.lang }}/advanced/security-updates.html). If you are, update to one of the stable releases, preferably the latest.
@@ -40,29 +51,63 @@ Also ensure you are not using any of the vulnerable Express versions listed on t
If your app deals with or transmits sensitive data, use [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (TLS) to secure the connection and the data. This technology encrypts data before it is sent from the client to the server, thus preventing some common (and easy) hacks. Although Ajax and POST requests might not be visibly obvious and seem "hidden" in browsers, their network traffic is vulnerable to [packet sniffing](https://en.wikipedia.org/wiki/Packet_analyzer) and [man-in-the-middle attacks](https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
-You may be familiar with Secure Socket Layer (SSL) encryption. [TLS is simply the next progression of SSL](https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515(v=vs.85).aspx). In other words, if you were using SSL before, consider upgrading to TLS. In general, we recommend Nginx to handle TLS. For a good reference to configure TLS on Nginx (and other servers), see [Recommended Server Configurations (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
+You may be familiar with Secure Socket Layer (SSL) encryption. [TLS is simply the next progression of SSL](https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515(v=vs.85).aspx). In other words, if you were using SSL before, consider upgrading to TLS. In general, we recommend Nginx to handle TLS. For a good reference to configure TLS on Nginx (and other servers), see [Recommended Server Configurations (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
Also, a handy tool to get a free TLS certificate is [Let's Encrypt](https://letsencrypt.org/about/), a free, automated, and open certificate authority (CA) provided by the [Internet Security Research Group (ISRG)](https://www.abetterinternet.org/).
+## Do not trust user input
+
+For web applications, one of the most critical security requirements is proper user input validation and handling. This comes in many forms and we will not cover all of them here.
+Ultimately, the responsibility for validating and correctly handling the types of user input your application accepts is yours.
+
+### Prevent open redirects
+
+An example of potentially dangerous user input is an _open redirect_, where an application accepts a URL as user input (often in the URL query, for example `?url=https://example.com`) and uses `res.redirect` to set the `location` header and
+return a 3xx status.
+
+An application must validate that it supports redirecting to the incoming URL to avoid sending users to malicious links such as phishing websites, among other risks.
+
+Here is an example of checking URLs before using `res.redirect` or `res.location`:
+
+```js
+app.use((req, res) => {
+ try {
+ if (new Url(req.query.url).host !== 'example.com') {
+ return res.status(400).end(`Unsupported redirect to host: ${req.query.url}`)
+ }
+ } catch (e) {
+ return res.status(400).end(`Invalid url: ${req.query.url}`)
+ }
+ res.redirect(req.query.url)
+})
+```
+
## Use Helmet
-[Helmet](https://www.npmjs.com/package/helmet) can help protect your app from some well-known web vulnerabilities by setting HTTP headers appropriately.
+[Helmet][helmet] can help protect your app from some well-known web vulnerabilities by setting HTTP headers appropriately.
+
+Helmet is a middleware function that sets security-related HTTP response headers. Helmet sets the following headers by default:
-Helmet is actually just a collection of smaller middleware functions that set security-related HTTP response headers:
+- `Content-Security-Policy`: A powerful allow-list of what can happen on your page which mitigates many attacks
+- `Cross-Origin-Opener-Policy`: Helps process-isolate your page
+- `Cross-Origin-Resource-Policy`: Blocks others from loading your resources cross-origin
+- `Origin-Agent-Cluster`: Changes process isolation to be origin-based
+- `Referrer-Policy`: Controls the [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer) header
+- `Strict-Transport-Security`: Tells browsers to prefer HTTPS
+- `X-Content-Type-Options`: Avoids [MIME sniffing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
+- `X-DNS-Prefetch-Control`: Controls DNS prefetching
+- `X-Download-Options`: Forces downloads to be saved (Internet Explorer only)
+- `X-Frame-Options`: Legacy header that mitigates [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking) attacks
+- `X-Permitted-Cross-Domain-Policies`: Controls cross-domain behavior for Adobe products, like Acrobat
+- `X-Powered-By`: Info about the web server. Removed because it could be used in simple attacks
+- `X-XSS-Protection`: Legacy header that tries to mitigate [XSS attacks](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting), but makes things worse, so Helmet disables it
-* [csp](https://github.com/helmetjs/csp) sets the `Content-Security-Policy` header to help prevent cross-site scripting attacks and other cross-site injections.
-* [hidePoweredBy](https://github.com/helmetjs/hide-powered-by) removes the `X-Powered-By` header.
-* [hsts](https://github.com/helmetjs/hsts) sets `Strict-Transport-Security` header that enforces secure (HTTP over SSL/TLS) connections to the server.
-* [ieNoOpen](https://github.com/helmetjs/ienoopen) sets `X-Download-Options` for IE8+.
-* [noCache](https://github.com/helmetjs/nocache) sets `Cache-Control` and Pragma headers to disable client-side caching.
-* [noSniff](https://github.com/helmetjs/dont-sniff-mimetype) sets `X-Content-Type-Options` to prevent browsers from MIME-sniffing a response away from the declared content-type.
-* [frameguard](https://github.com/helmetjs/frameguard) sets the `X-Frame-Options` header to provide [clickjacking](https://www.owasp.org/index.php/Clickjacking) protection.
-* [xssFilter](https://github.com/helmetjs/x-xss-protection) sets `X-XSS-Protection` to disable the buggy Cross-site scripting (XSS) filter in web browsers.
+Each header can be configured or disabled. To read more about it please go to [its documentation website][helmet].
Install Helmet like any other module:
-```sh
-$ npm install --save helmet
+```bash
+$ npm install helmet
```
Then to use it in your code:
@@ -70,28 +115,58 @@ Then to use it in your code:
```js
// ...
-var helmet = require('helmet')
+const helmet = require('helmet')
app.use(helmet())
// ...
```
-### At a minimum, disable X-Powered-By header
+## Reduce fingerprinting
-If you don't want to use Helmet, then at least disable the `X-Powered-By` header. Attackers can use this header (which is enabled by default) to detect apps running Express and then launch specifically-targeted attacks.
+It can help to provide an extra layer of security to reduce the ability of attackers to determine
+the software that a server uses, known as "fingerprinting." Though not a security issue itself,
+reducing the ability to fingerprint an application improves its overall security posture.
+Server software can be fingerprinted by quirks in how it responds to specific requests, for example in
+the HTTP response headers.
-So, best practice is to turn off the header with the `app.disable()` method:
+By default, Express sends the `X-Powered-By` response header that you can
+disable using the `app.disable()` method:
```js
app.disable('x-powered-by')
```
-If you use `helmet.js`, it takes care of this for you.
+{% capture powered-advisory %}
-{% include note.html content="Disabling the `X-Powered-By header` does not prevent
-a sophisticated attacker from determining that an app is running Express. It may
+Disabling the `X-Powered-By header` does not prevent
+a sophisticated attacker from determining that an app is running Express. It may
discourage a casual exploit, but there are other ways to determine an app is running
-Express. "%}
+Express.
+
+{% endcapture %}
+
+{% include admonitions/note.html content=powered-advisory %}
+
+Express also sends its own formatted "404 Not Found" messages and formatter error
+response messages. These can be changed by
+[adding your own not found handler](/en/starter/faq.html#how-do-i-handle-404-responses)
+and
+[writing your own error handler](/en/guide/error-handling.html#writing-error-handlers):
+
+```js
+// last app.use calls right before app.listen():
+
+// custom 404
+app.use((req, res, next) => {
+ res.status(404).send("Sorry can't find that!")
+})
+
+// custom error handler
+app.use((err, req, res, next) => {
+ console.error(err.stack)
+ res.status(500).send('Something broke!')
+})
+```
## Use cookies securely
@@ -102,18 +177,18 @@ There are two main middleware cookie session modules:
* [express-session](https://www.npmjs.com/package/express-session) that replaces `express.session` middleware built-in to Express 3.x.
* [cookie-session](https://www.npmjs.com/package/cookie-session) that replaces `express.cookieSession` middleware built-in to Express 3.x.
-The main difference between these two modules is how they save cookie session data. The [express-session](https://www.npmjs.com/package/express-session) middleware stores session data on the server; it only saves the session ID in the cookie itself, not session data. By default, it uses in-memory storage and is not designed for a production environment. In production, you'll need to set up a scalable session-store; see the list of [compatible session stores](https://github.com/expressjs/session#compatible-session-stores).
+The main difference between these two modules is how they save cookie session data. The [express-session](https://www.npmjs.com/package/express-session) middleware stores session data on the server; it only saves the session ID in the cookie itself, not session data. By default, it uses in-memory storage and is not designed for a production environment. In production, you'll need to set up a scalable session-store; see the list of [compatible session stores](https://github.com/expressjs/session#compatible-session-stores).
-In contrast, [cookie-session](https://www.npmjs.com/package/cookie-session) middleware implements cookie-backed storage: it serializes the entire session to the cookie, rather than just a session key. Only use it when session data is relatively small and easily encoded as primitive values (rather than objects). Although browsers are supposed to support at least 4096 bytes per cookie, to ensure you don't exceed the limit, don't exceed a size of 4093 bytes per domain. Also, be aware that the cookie data will be visible to the client, so if there is any reason to keep it secure or obscure, then express-session may be a better choice.
+In contrast, [cookie-session](https://www.npmjs.com/package/cookie-session) middleware implements cookie-backed storage: it serializes the entire session to the cookie, rather than just a session key. Only use it when session data is relatively small and easily encoded as primitive values (rather than objects). Although browsers are supposed to support at least 4096 bytes per cookie, to ensure you don't exceed the limit, don't exceed a size of 4093 bytes per domain. Also, be aware that the cookie data will be visible to the client, so if there is any reason to keep it secure or obscure, then `express-session` may be a better choice.
### Don't use the default session cookie name
-Using the default session cookie name can open your app to attacks. The security issue posed is similar to `X-Powered-By`: a potential attacker can use it to fingerprint the server and target attacks accordingly.
+Using the default session cookie name can open your app to attacks. The security issue posed is similar to `X-Powered-By`: a potential attacker can use it to fingerprint the server and target attacks accordingly.
To avoid this problem, use generic cookie names; for example using [express-session](https://www.npmjs.com/package/express-session) middleware:
```js
-var session = require('express-session')
+const session = require('express-session')
app.set('trust proxy', 1) // trust first proxy
app.use(session({
secret: 's3Cur3',
@@ -134,11 +209,11 @@ Set the following cookie options to enhance security:
Here is an example using [cookie-session](https://www.npmjs.com/package/cookie-session) middleware:
```js
-var session = require('cookie-session')
-var express = require('express')
-var app = express()
+const session = require('cookie-session')
+const express = require('express')
+const app = express()
-var expiryDate = new Date(Date.now() + 60 * 60 * 1000) // 1 hour
+const expiryDate = new Date(Date.now() + 60 * 60 * 1000) // 1 hour
app.use(session({
name: 'session',
keys: ['key1', 'key2'],
@@ -157,18 +232,18 @@ app.use(session({
Make sure login endpoints are protected to make private data more secure.
A simple and powerful technique is to block authorization attempts using two metrics:
-1. The first is number of consecutive failed attempts by the same user name and IP address.
-1. The second is number of failed attempts from an IP address over some long period of time. For example, block an IP address if it makes 100 failed attempts in one day.
+1. The number of consecutive failed attempts by the same user name and IP address.
+1. The number of failed attempts from an IP address over some long period of time. For example, block an IP address if it makes 100 failed attempts in one day.
-[rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) package provides tools to make this technique easy and fast. You can find [an example of brute-force protection in the documentation](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
+[rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) package provides tools to make this technique easy and fast. You can find [an example of brute-force protection in the documentation](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
## Ensure your dependencies are secure
-Using npm to manage your application's dependencies is powerful and convenient. But the packages that you use may contain critical security vulnerabilities that could also affect your application. The security of your app is only as strong as the "weakest link" in your dependencies.
+Using npm to manage your application's dependencies is powerful and convenient. But the packages that you use may contain critical security vulnerabilities that could also affect your application. The security of your app is only as strong as the "weakest link" in your dependencies.
-Since npm@6, npm automatically reviews every install request. Also you can use 'npm audit' to analyze your dependency tree.
+Since npm@6, npm automatically reviews every install request. Also, you can use `npm audit` to analyze your dependency tree.
-```sh
+```bash
$ npm audit
```
@@ -176,36 +251,31 @@ If you want to stay more secure, consider [Snyk](https://snyk.io/).
Snyk offers both a [command-line tool](https://www.npmjs.com/package/snyk) and a [Github integration](https://snyk.io/docs/github) that checks your application against [Snyk's open source vulnerability database](https://snyk.io/vuln/) for any known vulnerabilities in your dependencies. Install the CLI as follows:
-```sh
+```bash
$ npm install -g snyk
$ cd your-app
```
Use this command to test your application for vulnerabilities:
-```sh
+```bash
$ snyk test
```
-Use this command to open a wizard that walks you through the process of applying updates or patches to fix the vulnerabilities that were found:
-
-```sh
-$ snyk wizard
-```
-
-## Avoid other known vulnerabilities
+### Avoid other known vulnerabilities
-Keep an eye out for [Node Security Project](https://npmjs.com/advisories) or [Snyk](https://snyk.io/vuln/) advisories that may affect Express or other modules that your app uses. In general, these databases are excellent resources for knowledge and tools about Node security.
+Keep an eye out for [Node Security Project](https://npmjs.com/advisories) or [Snyk](https://snyk.io/vuln/) advisories that may affect Express or other modules that your app uses. In general, these databases are excellent resources for knowledge and tools about Node security.
-Finally, Express apps - like any other web apps - can be vulnerable to a variety of web-based attacks. Familiarize yourself with known [web vulnerabilities](https://www.owasp.org/index.php/Top_10-2017_Top_10) and take precautions to avoid them.
+Finally, Express apps—like any other web apps—can be vulnerable to a variety of web-based attacks. Familiarize yourself with known [web vulnerabilities](https://www.owasp.org/www-project-top-ten/) and take precautions to avoid them.
## Additional considerations
-Here are some further recommendations from the excellent [Node.js Security Checklist](https://blog.risingstack.com/node-js-security-checklist/). Refer to that blog post for all the details on these recommendations:
+Here are some further recommendations from the excellent [Node.js Security Checklist](https://blog.risingstack.com/node-js-security-checklist/). Refer to that blog post for all the details on these recommendations:
-* Use [csurf](https://www.npmjs.com/package/csurf) middleware to protect against cross-site request forgery (CSRF).
* Always filter and sanitize user input to protect against cross-site scripting (XSS) and command injection attacks.
* Defend against SQL injection attacks by using parameterized queries or prepared statements.
* Use the open-source [sqlmap](http://sqlmap.org/) tool to detect SQL injection vulnerabilities in your app.
* Use the [nmap](https://nmap.org/) and [sslyze](https://github.com/nabla-c0d3/sslyze) tools to test the configuration of your SSL ciphers, keys, and renegotiation as well as the validity of your certificate.
* Use [safe-regex](https://www.npmjs.com/package/safe-regex) to ensure your regular expressions are not susceptible to [regular expression denial of service](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS) attacks.
+
+[helmet]: https://helmetjs.github.io/
\ No newline at end of file
diff --git a/en/advanced/developing-template-engines.md b/en/advanced/developing-template-engines.md
index 9a8ba5fb40..5e84f2b4e0 100755
--- a/en/advanced/developing-template-engines.md
+++ b/en/advanced/developing-template-engines.md
@@ -1,8 +1,8 @@
---
layout: page
title: Developing template engines for Express
+description: Learn how to develop custom template engines for Express.js using app.engine(), with examples on creating and integrating your own template rendering logic.
menu: advanced
-lang: en
redirect_from: "/advanced/developing-template-engines.html"
---
@@ -13,14 +13,14 @@ Use the `app.engine(ext, callback)` method to create your own template engine. `
The following code is an example of implementing a very simple template engine for rendering `.ntl` files.
```js
-var fs = require('fs') // this engine requires the fs module
-app.engine('ntl', function (filePath, options, callback) { // define the template engine
- fs.readFile(filePath, function (err, content) {
+const fs = require('fs') // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => { // define the template engine
+ fs.readFile(filePath, (err, content) => {
if (err) return callback(err)
// this is an extremely simple template engine
- var rendered = content.toString()
- .replace('#title#', '' + options.title + ' ')
- .replace('#message#', '' + options.message + '
')
+ const rendered = content.toString()
+ .replace('#title#', `${options.title} `)
+ .replace('#message#', `${options.message}
`)
return callback(null, rendered)
})
})
@@ -30,15 +30,15 @@ app.set('view engine', 'ntl') // register the template engine
Your app will now be able to render `.ntl` files. Create a file named `index.ntl` in the `views` directory with the following content.
-```text
+```pug
#title#
#message#
```
Then, create the following route in your app.
```js
-app.get('/', function (req, res) {
+app.get('/', (req, res) => {
res.render('index', { title: 'Hey', message: 'Hello there!' })
})
```
-When you make a request to the home page, `index.ntl` will be rendered as HTML.
+When you make a request to the home page, `index.ntl` will be rendered as HTML.
\ No newline at end of file
diff --git a/en/advanced/healthcheck-graceful-shutdown.md b/en/advanced/healthcheck-graceful-shutdown.md
index ca1eb19d36..4398238fad 100644
--- a/en/advanced/healthcheck-graceful-shutdown.md
+++ b/en/advanced/healthcheck-graceful-shutdown.md
@@ -1,8 +1,8 @@
---
layout: page
title: Health Checks and Graceful Shutdown
+description: Learn how to implement health checks and graceful shutdown in Express apps to enhance reliability, manage deployments, and integrate with load balancers like Kubernetes.
menu: advanced
-lang: en
redirect_from: "/advanced/healthcheck-graceful-shutdown.html"
---
@@ -10,9 +10,10 @@ redirect_from: "/advanced/healthcheck-graceful-shutdown.html"
## Graceful shutdown
-When you deploy a new version of your application, you must replace the previous version. The [process manager](pm.html) you're using will first send a SIGTERM signal to the application to notify it that it will be killed. Once the application gets this signal, it should stop accepting new requests, finish all the ongoing requests, clean up the resources it used, including database connections and file locks then exit.
+When you deploy a new version of your application, you must replace the previous version. The process manager you're using will first send a SIGTERM signal to the application to notify it that it will be killed. Once the application gets this signal, it should stop accepting new requests, finish all the ongoing requests, clean up the resources it used, including database connections and file locks then exit.
+
+### Example
-### Example Graceful Shutdown
```js
const server = app.listen(port)
@@ -29,153 +30,4 @@ process.on('SIGTERM', () => {
A load balancer uses health checks to determine if an application instance is healthy and can accept requests. For example, [Kubernetes has two health checks](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
* `liveness`, that determines when to restart a container.
-* `readiness`, that determines when a container is ready to start accepting traffic. When a pod is not ready, it is removed from the service load balancers.
-
-## Third-party solutions
-
-{% include community-caveat.html %}
-
-### Terminus
-
-[Terminus](https://github.com/godaddy/terminus) is an open-source project that adds health checks and graceful shutdown to your application to eliminate the need to write boilerplate code. You just provide the cleanup logic for graceful shutdowns and the health check logic for health checks, and terminus handles the rest.
-
-Install terminus as follows:
-
-```sh
-npm i @godaddy/terminus --save
-```
-
-Here's a basic template that illustrates using terminus. For more information, see .
-
-```js
-const http = require('http')
-const express = require('express')
-const { createTerminus } = require('@godaddy/terminus')
-
-const app = express()
-
-app.get('/', (req, res) => {
- res.send('ok')
-})
-
-const server = http.createServer(app)
-
-function onSignal () {
- console.log('server is starting cleanup')
- // start cleanup of resource, like databases or file descriptors
-}
-
-async function onHealthCheck () {
- // checks if the system is healthy, like the db connection is live
- // resolves, if health, rejects if not
-}
-
-createTerminus(server, {
- signal: 'SIGINT',
- healthChecks: { '/healthcheck': onHealthCheck },
- onSignal
-})
-
-server.listen(3000)
-```
-
-### Lightship
-
-[Lightship](https://github.com/gajus/lightship) is an open-source project that adds health, readiness and liveness checks to your application. Lightship is a standalone HTTP-service that runs as a separate HTTP service; this allows having health-readiness-liveness HTTP endpoints without exposing them on the public interface.
-
-Install Lightship as follows:
-
-```sh
-npm install lightship
-
-```
-
-Basic template that illustrates using Lightship:
-
-```js
-const http = require('http')
-const express = require('express')
-const {
- createLightship
-} = require('lightship')
-
-// Lightship will start a HTTP service on port 9000.
-const lightship = createLightship()
-
-const app = express()
-
-app.get('/', (req, res) => {
- res.send('ok')
-})
-
-app.listen(3000, () => {
- lightship.signalReady()
-})
-
-// You can signal that the service is not ready using `lightship.signalNotReady()`.
-```
-
-[Lightship documentation](https://github.com/gajus/lightship) provides examples of the corresponding [Kubernetes configuration](https://github.com/gajus/lightship#lightship-usage-kubernetes-container-probe-configuration) and a complete example of integration with [Express.js](https://github.com/gajus/lightship#using-with-expressjs).
-
-### http-terminator
-
-[http-terminator](https://github.com/gajus/http-terminator) implements logic for gracefully terminating an express.js server.
-
-Terminating a HTTP server in Node.js requires keeping track of all open connections and signaling them that the server is shutting down. http-terminator implements the logic for tracking all connections and their termination upon a timeout. http-terminator also ensures graceful communication of the server intention to shutdown to any clients that are currently receiving response from this server.
-
-Install http-terminator as follows:
-
-```sh
-npm install http-terminator
-
-```
-
-Basic template that illustrates using http-terminator:
-
-```js
-const express = require('express')
-const { createHttpTerminator } = require('http-terminator')
-
-const app = express()
-
-const server = app.listen(3000)
-
-const httpTerminator = createHttpTerminator({ server })
-
-app.get('/', (req, res) => {
- res.send('ok')
-})
-
-// A server will terminate after invoking `httpTerminator.terminate()`.
-// Note: Timeout is used for illustration of delayed termination purposes only.
-setTimeout(() => {
- httpTerminator.terminate()
-}, 1000)
-```
-
-[http-terminator documentation](https://github.com/gajus/http-terminator) provides API documentation and comparison to other existing third-party solutions.
-
-### express-actuator
-
-[express-actuator](https://github.com/rcruzper/express-actuator) is a middleware to add endpoints to help you monitor and manage applications.
-
-Install express-actuator as follows:
-
-```sh
-npm install --save express-actuator
-```
-
-Basic template that illustrates using express-actuator:
-
-```js
-const express = require('express')
-const actuator = require('express-actuator')
-
-const app = express()
-
-app.use(actuator())
-
-app.listen(3000)
-```
-
-The [express-actuator documentation](https://github.com/rcruzper/express-actuator) provides different options for customization.
+* `readiness`, that determines when a container is ready to start accepting traffic. When a pod is not ready, it is removed from the service load balancers.
\ No newline at end of file
diff --git a/en/advanced/pm.md b/en/advanced/pm.md
deleted file mode 100755
index 43251d6252..0000000000
--- a/en/advanced/pm.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-layout: page
-title: Process managers for Express apps
-menu: advanced
-lang: en
-redirect_from: "/advanced/pm.html"
----
-
-# Process managers for Express apps
-
-{% include community-caveat.html %}
-
-When you run Express apps for production, it is helpful to use a _process manager_ to:
-
-- Restart the app automatically if it crashes.
-- Gain insights into runtime performance and resource consumption.
-- Modify settings dynamically to improve performance.
-- Control clustering.
-
-A process manager is somewhat like an application server: it's a "container" for applications that facilitates deployment, provides high availability, and enables you to manage the application at runtime.
-
-The most popular process managers for Express and other Node.js applications are:
-
-- **[Forever](https://github.com/foreverjs/forever){: target="_blank"}**: A simple command-line interface tool to ensure that a script runs continuously (forever). Forever's simple interface makes it ideal for running smaller deployments of Node.js apps and scripts.
-- **[PM2](https://github.com/Unitech/pm2){: target="_blank"}**: A production process manager for Node.js applications that has a built-in load balancer. PM2 enables you to keep applications alive forever, reloads them without downtime, helps you to manage application logging, monitoring, and clustering.
-- **[StrongLoop Process Manager (Strong-PM)](http://strong-pm.io/)**: A production process manager for Node.js applications with built-in load balancing, monitoring, and multi-host deployment. Includes a CLI to build, package, and deploy Node.js applications to a local or remote system.
-- **SystemD**: The default process manager on modern Linux distributions, that makes it simple to run a Node application as a service. For more information, see ["Run node.js service with systemd" by Ralph Slooten (@axllent)](https://www.axllent.org/docs/view/nodejs-service-with-systemd/).
diff --git a/en/advanced/security-updates.md b/en/advanced/security-updates.md
index 1846728906..19edff3e21 100755
--- a/en/advanced/security-updates.md
+++ b/en/advanced/security-updates.md
@@ -1,23 +1,42 @@
---
layout: page
title: Express security updates
+description: Review the latest security updates and patches for Express.js, including detailed vulnerability lists for different versions to help maintain a secure application.
menu: advanced
-lang: en
redirect_from: "/advanced/security-updates.html"
---
+
# Security updates
-Node.js vulnerabilities directly affect Express. Therefore [keep a watch on Node.js vulnerabilities](http://blog.nodejs.org/vulnerability/) and make sure you are using the latest stable version of Node.js.
+Node.js vulnerabilities directly affect Express. Therefore, [keep a watch on Node.js vulnerabilities](https://nodejs.org/en/blog/vulnerability/) and make sure you are using the latest stable version of Node.js.
The list below enumerates the Express vulnerabilities that were fixed in the specified version update.
-**NOTE**: If you believe you have discovered a security vulnerability in Express, please see
+
+{% capture security-policy %}
+If you believe you have discovered a security vulnerability in Express, please see
[Security Policies and Procedures](/{{page.lang}}/resources/contributing.html#security-policies-and-procedures).
+{% endcapture %}
-## 4.x
+{% include admonitions/note.html content=security-policy %}
+## 4.x
+ * 4.21.2
+ * The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
+ * 4.21.1
+ * The dependency `cookie` has been updated to address a [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), This may affect your application if you use `res.cookie`.
+ * 4.20.0
+ * Fixed XSS vulnerability in `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
+ * The dependency `serve-static` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p).
+ * The dependency `send` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
+ * The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
+ * The dependency `body-parser` has been updated to addres a [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), This may affect your application if you had url enconding activated.
+ * 4.19.0, 4.19.1
+ * Fixed open redirect vulnerability in `res.location` and `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
+ * 4.17.3
+ * The dependency `qs` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp). This may affect your application if the following APIs are used: `req.query`, `req.body`, `req.param`.
* 4.16.0
* The dependency `forwarded` has been updated to address a [vulnerability](https://npmjs.com/advisories/527). This may affect your application if the following APIs are used: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
* The dependency `mime` has been updated to address a [vulnerability](https://npmjs.com/advisories/535), but this issue does not impact Express.
@@ -44,9 +63,11 @@ The list below enumerates the Express vulnerabilities that were fixed in the spe
## 3.x
- **Express 3.x IS NO LONGER MAINTAINED**
+ **Express 3.x IS END-OF-LIFE AND NO LONGER MAINTAINED**
+
+ Known and unknown security and performance issues in 3.x have not been addressed since the last update (1 August, 2015). It is highly recommended to use the latest version of Express.
- Known and unknown security issues in 3.x have not been addressed since the last update (1 August, 2015). Using the 3.x line should not be considered secure.
+ If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
* 3.19.1
@@ -61,4 +82,4 @@ The list below enumerates the Express vulnerabilities that were fixed in the spe
* Sparse arrays that have extremely high indexes in query string could cause the process to run out of memory and crash the server.
* Extremely nested query string objects could cause the process to block and make the server unresponsive temporarily.
* 3.3.0
- * The 404 response of an unsupported method override attempt was susceptible to cross-site scripting attacks.
+ * The 404 response of an unsupported method override attempt was susceptible to cross-site scripting attacks.
\ No newline at end of file
diff --git a/en/api.md b/en/api.md
index 16227d369e..41382818cc 100644
--- a/en/api.md
+++ b/en/api.md
@@ -1,26 +1,21 @@
---
-layout: 4x-api
-title: Express 4.x - API Reference
-lang: en
+layout: api
+version: 5x
+title: Express 5.x - API Reference
+description: Access the API reference for Express.js detailing all modules, methods, and properties for building web applications with this version.
+menu: api
redirect_from: "/api.html"
---
-
- 4.x API
-
+ 5.x API
- {% include api/{{ page.lang }}/4x/express.md %}
-
+ {% include api/en/5x/express.md %}
- {% include api/{{ page.lang }}/4x/app.md %}
-
+ {% include api/en/5x/app.md %}
- {% include api/{{ page.lang }}/4x/req.md %}
-
+ {% include api/en/5x/req.md %}
- {% include api/{{ page.lang }}/4x/res.md %}
-
+ {% include api/en/5x/res.md %}
- {% include api/{{ page.lang }}/4x/router.md %}
-
+ {% include api/en/5x/router.md %}
diff --git a/en/blog/posts.md b/en/blog/posts.md
new file mode 100644
index 0000000000..b5be34e66c
--- /dev/null
+++ b/en/blog/posts.md
@@ -0,0 +1,28 @@
+---
+layout: post
+title: Express Blog Posts
+description: Explore the latest articles, announcements, and updates from the Express.js team and community on the Express blog.
+menu: blog
+redirect_from: "/blog/posts.html"
+---
+
+Want to write a post? See the submission [guidelines.](/en/blog/write-post.html)
+
+{% if site.posts.size != 0 %}
+
+{% for post in site.posts %}
+
+
+ {{ post.title }}
+
+
+ {% include blog/authors.html authors=post.authors %}
+ {{ post.date | date:"%b %d, %Y" }}
+
+ {{post.excerpt | truncate: 240 | markdownify }}
+
+{% endfor %}
+
+{% else %}
+ There are currently no blog posts.
+{% endif %}
diff --git a/en/blog/write-post.md b/en/blog/write-post.md
new file mode 100644
index 0000000000..21cfc5b4b3
--- /dev/null
+++ b/en/blog/write-post.md
@@ -0,0 +1,51 @@
+---
+layout: post
+title: How to write a blog post
+description: Learn how to propose and write a blog post for the Express.js blog, including submission guidelines and steps to contribute your content.
+menu: blog
+redirect_from: "/blog/write.html"
+---
+
+
+
+If you have an idea for a blog post, follow these steps to propose it and potentially get it published!
+
+1. ### Propose your post
+Before taking the time to write a post, please confirm that we will be able to publish it. We're looking for topics specifically related to Express, and so we want to pre-approve all posts. For the moment, this means we aren't accepting any unsolicited posts. To propose a blog post, [open an issue](https://github.com/expressjs/expressjs.com/issues) entitled `Blog post proposal: `.
+
+
+1. ### Fork the repository
+If the Express TC accepts your proposal, start to write your post by forking the [expressjs.com](https://github.com/expressjs/expressjs.com) repository and cloning it to your local machine. Once you open a pull request, you'll be able to preview your post on GitHub. See step six below.
+
+ Optional: To run the site locally and preview your post before opening a PR, see the [setup instructions in the README](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#expressjscom).
+ {: .doc-box .doc-info}
+
+1. ### Create a new file
+Create a new file in the `_posts` directory named using following the format: `YYYY-MM-DD-title.md`.
+
+1. ### Add the required front matter
+ Copy the following front matter, including the dotted lines, and paste it at the top of file you just created. Replace the placeholder values with as desired.
+
+ ```markdown
+ ---
+ title:
+ sub_title:
+ description:
+ tags:
+ authors:
+ - name:
+ github:
+ ---
+ ```
+
+ The `github` property of an author is optional. Including your username only (not your full profile URL) will ensure that your blog post links out to it.
+
+2. ### Add your content
+ Finally, start writing your content below the front matter. Use standard markdown formatting.
+
+1. ### Open a pull request (PR)
+ Once you open a PR, you will be able to preview your results: There will be a section on the page entitled `Deploy Preview for expressjscom-preview ready!` Click the link to see the site rendered from your fork/branch.
+
+ You can use this feature over multiple commits to refine your post by making a `draft` pull request. Once it's ready for review, switch it to a formal PR.
+
+
\ No newline at end of file
diff --git a/en/changelog/4x.md b/en/changelog/4x.md
deleted file mode 100644
index c30ef0d5ca..0000000000
--- a/en/changelog/4x.md
+++ /dev/null
@@ -1,337 +0,0 @@
----
-layout: page
-title: Express 4.x changelog
-menu: changelog
-lang: en
-redirect_from: "/changelog/4x.html"
----
-
-# Release Change Log
-
-## 4.17.1 - Release date: 2019-05-25
-{: id="4.17.1"}
-
-The 4.17.1 patch release includes one bug fix:
-
-
- -
- The change to the `res.status()` API has been reverted due to causing regressions in existing Express 4 applications.
-
-
-
-For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4171--2019-05-25).
-
-## 4.17.0 - Release date: 2019-05-16
-{: id="4.17.0"}
-
-The 4.17.0 minor release includes bug fixes and some new features, including:
-
-
- -
- The `express.raw()` and `express.text()` middleware have been added to provide request body parsing for more raw request payloads. This uses the [expressjs/body-parser module](https://www.npmjs.com/package/body-parser) module underneath, so apps that are currently requiring the module separately can switch to the built-in parsers.
-
-
- -
- The `res.cookie()` API now supports the `"none"` value for the `sameSite` option.
-
-
- -
- When the `"trust proxy"` setting is enabled, the `req.hostname` now supports multiple `X-Forwarded-For` headers in a request.
-
-
- -
- Starting with this version, Express supports Node.js 10.x and 12.x.
-
-
- -
- The `res.sendFile()` API now provides and more immediate and easier to understand error when a non-string is passed as the `path` argument.
-
-
- -
- The `res.status()` API now provides and more immediate and easier to understand error when `null` or `undefined` is passed as the argument.
-
-
-
-For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4170--2019-05-16).
-
-## 4.16.4 - Release date: 2018-10-10
-{: id="4.16.4"}
-
-The 4.16.4 patch release includes various bug fixes:
-
-
- -
- Fix issue where `"Request aborted"` may be logged in `res.sendfile`.
-
-
-
-For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4164--2018-10-10).
-
-## 4.16.3 - Release date: 2018-03-12
-{: id="4.16.3"}
-
-The 4.16.3 patch release includes various bug fixes:
-
-
- -
- Fix issue where a plain `%` at the end of the url in the `res.location` method or the `res.redirect` method would not get encoded as `%25`.
-
-
- -
- Fix issue where a blank `req.url` value can result in a thrown error within the default 404 handling.
-
-
- -
- Fix the generated HTML document for `express.static` redirect responses to properly include ``.
-
-
-
-For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4163--2018-03-12).
-
-## 4.16.2 - Release date: 2017-10-09
-{: id="4.16.2"}
-
-The 4.16.2 patch release includes a regression bug fix:
-
-
- -
- Fix a `TypeError` that can occur in the `res.send` method when a `Buffer` is passed to `res.send` and the `ETag` header is already set on the response.
-
-
-
-For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4162--2017-10-09).
-
-## 4.16.1 - Release date: 2017-09-29
-{: id="4.16.1"}
-
-The 4.16.1 patch release includes a regression bug fix:
-
-
- -
- Update to [pillarjs/send module](https://www.npmjs.com/package/send) to fix an edge case scenario regression that affected certain users of `express.static`.
-
-
-
-For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4161--2017-09-29).
-
-## 4.16.0 - Release date: 2017-09-28
-{: id="4.16.0"}
-
-The 4.16.0 minor release includes security updates, bug fixes, performance enhancements, and some new features, including:
-
-
- -
- Update to [jshttp/forwarded module](https://www.npmjs.com/package/forwarded) to address a [vulnerability](https://npmjs.com/advisories/527). This may affect your application if the following APIs are used: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
-
-
- -
- Update a dependency of the [pillarjs/send module](https://www.npmjs.com/package/send) to address a [vulnerability](https://npmjs.com/advisories/535) in the `mime` dependency. This may affect your application if untrusted string input is passed to the following APIs: `res.type()`.
-
-
- -
- The [pillarjs/send module](https://www.npmjs.com/package/send) has implemented a protection against the Node.js 8.5.0 [vulnerability](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/). Using any prior version of Express.js with Node.js 8.5.0 (that specific Node.js version) will make the following APIs vulnerable: `express.static`, `res.sendfile`, and `res.sendFile`.
-
-
- -
- Starting with this version, Express supports Node.js 8.x.
-
-
- -
- The new setting `"json escape"` can be enabled to escape characters in `res.json()`, `res.jsonp()` and `res.send()` responses that can trigger clients to sniff the response as HTML instead of honoring the `Content-Type`. This can help protect an Express app from a class of persistent XSS-based attacks.
-
-
- -
- The [`res.download()` method](/{{ page.lang }}/4x/api.html#res.download) now accepts an optional `options` object.
-
-
- -
- The `express.json()` and `express.urlencoded()` middleware have been added to provide request body parsing support out-of-the-box. This uses the [expressjs/body-parser module](https://www.npmjs.com/package/body-parser) module underneath, so apps that are currently requiring the module separately can switch to the built-in parsers.
-
-
- -
- The [`express.static()` middleware](/{{ page.lang }}/4x/api.html#express.static) and [`res.sendFile()` method](/{{ page.lang }}/4x/api.html#res.sendFile) now support setting the `immutable` directive on the `Cache-Control` header. Setting this header with an appropriate `maxAge` will prevent supporting web browsers from sending any request to the server when the file is still in their cache.
-
-
- -
- The [pillarjs/send module](https://www.npmjs.com/package/send) has an updated list of MIME types to better set the `Content-Type` of more files. There are 70 new types for file extensions.
-
-
-
-For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4160--2017-09-28).
-
-## 4.15.5 - Release date: 2017-09-24
-{: id="4.15.5"}
-
-The 4.15.5 patch release includes security updates, some minor performance enhancements, and a bug fix:
-
-
- -
- Update to [debug module](https://www.npmjs.com/package/debug) to address a [vulnerability](https://snyk.io/vuln/npm:debug:20170905), but this issue does not impact Express.
-
-
- -
- Update to [jshttp/fresh module](https://www.npmjs.com/package/fresh) to address a [vulnerability](https://npmjs.com/advisories/526). This will affect your application if the following APIs are used: `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`.
-
-
- -
- Update to [jshttp/fresh module](https://www.npmjs.com/package/fresh) fixes handling of modified headers with invalid dates and makes parsing conditional headers (like `If-None-Match`) faster.
-
-
-
-For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4155--2017-09-24).
-
-## 4.15.4 - Release date: 2017-08-06
-{: id="4.15.4"}
-
-The 4.15.4 patch release includes some minor bug fixes:
-
-
- -
- Fix array being set for `"trust proxy"` value being manipulated in certain conditions.
-
-
-
-For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4154--2017-08-06).
-
-## 4.15.3 - Release date: 2017-05-16
-{: id="4.15.3"}
-
-The 4.15.3 patch release includes a security update and some minor bug fixes:
-
-
- -
- Update a dependency of the [pillarjs/send module](https://www.npmjs.com/package/send) to address a [vulnerability](https://snyk.io/vuln/npm:ms:20170412). This may affect your application if untrusted string input is passed to the `maxAge` option in the following APIs: `express.static`, `res.sendfile`, and `res.sendFile`.
-
-
- -
- Fix error when `res.set` cannot add charset to `Content-Type`.
-
-
- -
- Fix missing `` in HTML document.
-
-
-
-For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4153--2017-05-16).
-
-## 4.15.2 - Release date: 2017-03-06
-{: id="4.15.2"}
-
-The 4.15.2 patch release includes a minor bug fix:
-
-
- -
- Fix regression parsing keys starting with `[` in the extended (default) query parser.
-
-
-
-For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4152--2017-03-06).
-
-## 4.15.1 - Release date: 2017-03-05
-{: id="4.15.1"}
-
-The 4.15.1 patch release includes a minor bug fix:
-
-
- -
- Fix compatibility issue when using the datejs 1.x library where the [`express.static()` middleware](/{{ page.lang }}/4x/api.html#express.static) and [`res.sendFile()` method](/{{ page.lang }}/4x/api.html#res.sendFile) would incorrectly respond with 412 Precondition Failed.
-
-
-
-For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4151--2017-03-05).
-
-## 4.15.0 - Release date: 2017-03-01
-{: id="4.15.0"}
-
-The 4.15.0 minor release includes bug fixes, performance improvements, and other minor feature additions, including:
-
-
- -
- Starting with this version, Express supports Node.js 7.x.
-
-
- -
- The [`express.static()` middleware](/{{ page.lang }}/4x/api.html#express.static) and [`res.sendFile()` method](/{{ page.lang }}/4x/api.html#res.sendFile) now support the `If-Match` and `If-Unmodified-Since` request headers.
-
-
- -
- Update to [jshttp/etag module](https://www.npmjs.com/package/etag) to generate the default ETags for responses which work when Node.js has [FIPS-compliant crypto enabled](https://nodejs.org/dist/latest/docs/api/cli.html#cli_enable_fips).
-
-
- -
- Various auto-generated HTML responses like the default not found and error handlers will respond with complete HTML 5 documents and additional security headers.
-
-
-
-For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4150--2017-03-01).
-
-## 4.14.1 - Release date: 2017-01-28
-{: id="4.14.1"}
-
-The 4.14.1 patch release includes bug fixes and performance improvements, including:
-
-
- -
- Update to [pillarjs/finalhandler module](https://www.npmjs.com/package/finalhandler) fixes an exception when Express handles an `Error` object which has a `headers` property that is not an object.
-
-
-
-For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4141--2017-01-28).
-
-## 4.14.0 - Release date: 2016-06-16
-{: id="4.14.0"}
-
-The 4.14.0 minor release includes bug fixes, security update, performance improvements, and other minor feature additions, including:
-
-
- -
- Starting with this version, Express supports Node.js 6.x.
-
-
- -
- Update to [jshttp/negotiator module](https://www.npmjs.com/package/negotiator) fixes a [regular expression denial of service vulnerability](https://npmjs.com/advisories/106).
-
-
- -
- The [`res.sendFile()` method](/{{ page.lang }}/4x/api.html#res.sendFile) now accepts two new options: `acceptRanges` and `cacheControl`.
-
- - `acceptRanges` (defaut is `true`), enables or disables accepting ranged requests. When disabled, the response does not send the `Accept-Ranges` header and ignores the contents of the `Range` request header.
-
- - `cacheControl`, (default is `true`), enables or disables the `Cache-Control` response header. Disabling it will ignore the `maxAge` option.
-
- - `res.sendFile` has also been updated to handle `Range` header and redirections better.
-
-
- -
- The [`res.location()` method](/{{ page.lang }}/4x/api.html#res.location) and [`res.redirect()` method](/{{ page.lang }}/4x/api.html#res.redirect) will now URL-encode the URL string, if it is not already encoded.
-
-
- -
- The performance of the [`res.json()` method](/{{ page.lang }}/4x/api.html#res.json) and [`res.jsonp()` method](/{{ page.lang }}/4x/api.html#res.jsonp) have been improved in the common cases.
-
-
- -
- The [jshttp/cookie module](https://www.npmjs.com/package/cookie) (in addition to a number of other improvements) has been updated and now the [`res.cookie()` method](/{{ page.lang }}/4x/api.html#res.cookie) supports the `sameSite` option to let you specify the [SameSite cookie attribute](https://tools.ietf.org/html/draft-west-first-party-cookies-07). NOTE: This attribute has not yet been fully standardized, may change in the future, and many clients may ignore it.
-
- The possible value for the `sameSite` option are:
-
- - `true`, which sets the `SameSite` attribute to `Strict` for strict same site enforcement.
- - `false`, which does not set the `SameSite` attribute.
- - `'lax'`, which sets the `SameSite` attribute to `Lax` for lax same site enforcement.
- - `'strict'`, which sets the `SameSite` attribute to `Strict` for strict same site enforcement.
-
-
- -
- Absolute path checking on Windows, which was incorrect for some cases, has been fixed.
-
-
- -
- IP address resolution with proxies has been greatly improved.
-
-
- -
- The [`req.range()` method](/{{ page.lang }}/4x/api.html#req.range) options object now supports a `combine` option (`false` by default), which when `true`, combines overlapping and adjacent ranges and returns them as if they were specified that way in the header.
-
-
-
-For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4140--2016-06-16).
diff --git a/en/changelog/index.md b/en/changelog/index.md
new file mode 100644
index 0000000000..85bebed4fa
--- /dev/null
+++ b/en/changelog/index.md
@@ -0,0 +1,597 @@
+---
+layout: page
+title: Express changelog
+description: Stay updated with the release changelog for Express.js, detailing new features, bug fixes, and important changes across versions.
+sitemap: false
+redirect_from:
+ - "/changelog/4x.html"
+ - "en/changelog/4x.html"
+---
+
+
+
+
+
+# Release changelog
+
+All the latest updates, improvements, and fixes to Express
+
+## Express v5
+{: id="5.x"}
+
+### 5.1.0 - Release date: 2025-03-31
+{: id="5.0.1"}
+
+The 5.1.0 minor release includes some new features and improvements:
+
+* Support for sending responses as Uint8Array
+* Added support for ETag option in `res.sendFile()`
+* Added support for adding multiple links with the same rel with `res.links()`
+* Performance: Use loop for acceptParams
+* [body-parser@2.2.0](https://github.com/expressjs/body-parser/releases/tag/v2.2.0)
+ * Remove legacy node.js support checks for Brotli & `AsyncLocalStorage`
+ * Remove `unpipe` & `destroy`
+* [router@2.2.0](https://github.com/pillarjs/router/releases/tag/v2.2.0)
+ * Restore `debug`. Now with the `router` scope instead of `express`.
+ * Remove legacy node.js support checks for `setImmediate`
+ * Deprecate non-native promise support
+ * Remove `after`, `safe-buffer`, `array-flatten`, `setprotoypeof`, `methods`, `utils-merge`
+* [finalhandler@2.1.0](https://github.com/pillarjs/finalhandler/releases/tag/v2.1.0)
+ * Remove legacy node.js support checks for `headersSent`, `setImmediate`, & http2 support
+ * Remove `unpipe`
+* Transitioned all remaining dependencies to use `^` ranges instead of locked versions
+* Add package.json funding field to highlight our OpenCollective
+* See [Changelog v5.1.0](https://github.com/expressjs/express/releases/tag/v5.1.0)
+### 5.0.1 - Release date: 2024-10-08
+{: id="5.0.1"}
+
+The 5.0.1 patch release includes one security fix:
+
+* Update [jshttps/cookie](https://www.npmjs.com/package/cookie) to address a [vulnerability](https://github.com/advisories/GHSA-pxg6-pf52-xh8x).
+
+### 5.0.0 - Release date: 2024-09-09
+{: id="5.0.0"}
+
+Check the [migration guide](/{{page.lang}}/guide/migrating-5.html) with all the changes in this new version of Express.
+
+## Express v4
+{: id="4.x"}
+
+### 4.21.2 - Release date: 2024-11-06
+{: id="4.21.2"}
+
+The 4.21.2 patch release includes one security fix:
+
+* Update [pillajs/path-to-regexp](https://www.npmjs.com/package/path-to-regexp) to address a [vulnerability](https://github.com/advisories/GHSA-rhx6-c78j-4q9w).
+
+### 4.21.1 - Release date: 2024-10-08
+{: id="4.21.1"}
+
+The 4.21.1 patch release includes one security fix:
+
+* Update [jshttps/cookie](https://www.npmjs.com/package/cookie) to address a [vulnerability](https://github.com/advisories/GHSA-pxg6-pf52-xh8x).
+
+### 4.21.0 - Release date: 2024-09-11
+{: id="4.21.0"}
+
+The 4.21.0 minor release includes one new feature:
+
+* Deprecate `res.location("back")` and `res.redirect("back")` magic string
+
+### 4.20.0 - Release date: 2024-09-10
+{: id="4.20.0"}
+
+The 4.20.0 minor release includes bug fixes and some new features, including:
+
+* The [`res.clearCookie()` method](/{{ page.lang }}/4x/api.html#res.clearCookie) deprecates `options.maxAge` and `options.expires` options.
+* The [`res.redirect()` method](/{{ page.lang }}/4x/api.html#res.redirect) removes HTML link rendering.
+* The [`express.urlencoded()` method](/{{ page.lang }}/4x/api.html#express.urlencoded) method now has a depth level of `32`, whereas it was previously `Infinity`.
+* Adds support for named matching groups in the routes using a regex
+* Removes encoding of `\`, `|`, and `^` to align better with URL spec
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4200--2024-09-10)
+
+### 4.19.2 - Release date: 2024-03-25
+{: id="4.19.2"}
+
+* Improved fix for open redirect allow list bypass
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4192--2024-03-25)
+
+### 4.19.1 - Release date: 2024-03-20
+{: id="4.19.1"}
+
+* Allow passing non-strings to res.location with new encoding handling checks
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4191--2024-03-20)
+
+### 4.19.0 - Release date: 2024-03-20
+{: id="4.19.0"}
+
+* Prevent open redirect allow list bypass due to encodeurl
+* deps: cookie@0.6.0
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4190--2024-03-20)
+
+### 4.18.3 - Release date: 2024-02-29
+{: id="4.18.3"}
+
+The 4.18.3 patch release includes the following bug fix:
+
+
+ -
+ Fix routing requests without method. ([commit](https://github.com/expressjs/express/commit/74beeac0718c928b4ba249aba3652c52fbe32ca8))
+
+
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4183--2024-02-26)
+
+### 4.18.2 - Release date: 2022-10-08
+{: id="4.18.2"}
+
+The 4.18.2 patch release includes the following bug fix:
+
+
+ -
+ Fix regression routing a large stack in a single route. ([commit](https://github.com/expressjs/express/commit/7ec5dd2b3c5e7379f68086dae72859f5573c8b9b))
+
+
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4182--2022-10-08)
+
+### 4.18.1 - Release date: 2022-04-29
+{: id="4.18.1"}
+
+The 4.18.1 patch release includes the following bug fix:
+
+
+ -
+ Fix the condition where if an Express application is created with a very large stack of routes, and all of those routes are sync (call `next()` synchronously), then the request processing may hang.
+
+
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4181--2022-04-29).
+
+### 4.18.0 - Release date: 2022-04-25
+{: id="4.18.0"}
+
+The 4.18.0 minor release includes bug fixes and some new features, including:
+
+
+ -
+ The [`app.get()` method](/{{ page.lang }}/4x/api.html#app.get) and the [`app.set()` method](/{{ page.lang }}/4x/api.html#app.set) now ignores properties directly on `Object.prototype` when getting a setting value.
+
+
+ -
+ The [`res.cookie()` method](/{{ page.lang }}/4x/api.html#res.cookie) now accepts a "priority" option to set the Priority attribute on the Set-Cookie response header.
+
+
+ -
+ The [`res.cookie()` method](/{{ page.lang }}/4x/api.html#res.cookie) now rejects an Invalid Date object provided as the "expires" option.
+
+
+ -
+ The [`res.cookie()` method](/{{ page.lang }}/4x/api.html#res.cookie) now works when `null` or `undefined` is explicitly provided as the "maxAge" argument.
+
+
+ -
+ Starting with this version, Express supports Node.js 18.x.
+
+
+ -
+ The [`res.download()` method](/{{ page.lang }}/4x/api.html#res.download) now accepts a "root" option to match [`res.sendFile()`](/{{ page.lang }}/4x/api.html#res.sendFile).
+
+
+ -
+ The [`res.download()` method](/{{ page.lang }}/4x/api.html#res.download) can be supplied with an `options` object without providing a `filename` argument, simplifying calls when the default `filename` is desired.
+
+
+ -
+ The [`res.format()` method](/{{ page.lang }}/4x/api.html#res.format) now invokes the provided "default" handler with the same arguments as the type handlers (`req`, `res`, and `next`).
+
+
+ -
+ The [`res.send()` method](/{{ page.lang }}/4x/api.html#res.send) will not attempt to send a response body when the response code is set to 205.
+
+
+ -
+ The default error handler will now remove certain response headers that will break the error response rendering, if they were set previously.
+
+
+ -
+ The status code 425 is now represented as the standard "Too Early" instead of "Unordered Collection".
+
+
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4180--2022-04-25).
+
+### 4.17.3 - Release date: 2022-02-16
+{: id="4.17.3"}
+
+The 4.17.3 patch release includes one bug fix:
+
+
+ -
+ Update to [qs module](https://www.npmjs.com/package/qs) for a fix around parsing `__proto__` properties.
+
+
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4173--2022-02-16).
+
+### 4.17.2 - Release date: 2021-12-16
+{: id="4.17.2"}
+
+The 4.17.2 patch release includes the following bug fixes:
+
+
+ -
+ Fix handling of `undefined` in `res.jsonp` when a callback is provided.
+
+
+ -
+ Fix handling of `undefined` in `res.json` and `res.jsonp` when `"json escape"` is enabled.
+
+
+ -
+ Fix handling of invalid values to the `maxAge` option of `res.cookie()`.
+
+
+ -
+ Update to [jshttp/proxy-addr module](https://www.npmjs.com/package/proxy-addr) to use `req.socket` over deprecated `req.connection`.
+
+
+ -
+ Starting with this version, Express supports Node.js 14.x.
+
+
+
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4172--2021-12-16).
+
+### 4.17.1 - Release date: 2019-05-25
+{: id="4.17.1"}
+
+The 4.17.1 patch release includes one bug fix:
+
+
+ -
+ The change to the `res.status()` API has been reverted due to causing regressions in existing Express 4 applications.
+
+
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4171--2019-05-25).
+
+### 4.17.0 - Release date: 2019-05-16
+{: id="4.17.0"}
+
+The 4.17.0 minor release includes bug fixes and some new features, including:
+
+
+ -
+ The `express.raw()` and `express.text()` middleware have been added to provide request body parsing for more raw request payloads. This uses the [expressjs/body-parser module](https://www.npmjs.com/package/body-parser) module underneath, so apps that are currently requiring the module separately can switch to the built-in parsers.
+
+
+ -
+ The `res.cookie()` API now supports the `"none"` value for the `sameSite` option.
+
+
+ -
+ When the `"trust proxy"` setting is enabled, the `req.hostname` now supports multiple `X-Forwarded-For` headers in a request.
+
+
+ -
+ Starting with this version, Express supports Node.js 10.x and 12.x.
+
+
+ -
+ The `res.sendFile()` API now provides and more immediate and easier to understand error when a non-string is passed as the `path` argument.
+
+
+ -
+ The `res.status()` API now provides and more immediate and easier to understand error when `null` or `undefined` is passed as the argument.
+
+
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4170--2019-05-16).
+
+### 4.16.4 - Release date: 2018-10-10
+{: id="4.16.4"}
+
+The 4.16.4 patch release includes various bug fixes:
+
+
+ -
+ Fix issue where `"Request aborted"` may be logged in `res.sendfile`.
+
+
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4164--2018-10-10).
+
+### 4.16.3 - Release date: 2018-03-12
+{: id="4.16.3"}
+
+The 4.16.3 patch release includes various bug fixes:
+
+
+ -
+ Fix issue where a plain `%` at the end of the url in the `res.location` method or the `res.redirect` method would not get encoded as `%25`.
+
+
+ -
+ Fix issue where a blank `req.url` value can result in a thrown error within the default 404 handling.
+
+
+ -
+ Fix the generated HTML document for `express.static` redirect responses to properly include `
-var express = require('express');
-var routes = require('./routes');
-var user = require('./routes/user');
-var http = require('http');
-var path = require('path');
+```js
+var express = require('express')
+var routes = require('./routes')
+var user = require('./routes/user')
+var http = require('http')
+var path = require('path')
-var app = express();
+var app = express()
// all environments
-app.set('port', process.env.PORT || 3000);
-app.set('views', path.join(__dirname, 'views'));
-app.set('view engine', 'pug');
-app.use(express.favicon());
-app.use(express.logger('dev'));
-app.use(express.methodOverride());
-app.use(express.session({ secret: 'your secret here' }));
-app.use(express.bodyParser());
-app.use(app.router);
-app.use(express.static(path.join(__dirname, 'public')));
+app.set('port', process.env.PORT || 3000)
+app.set('views', path.join(__dirname, 'views'))
+app.set('view engine', 'pug')
+app.use(express.favicon())
+app.use(express.logger('dev'))
+app.use(express.methodOverride())
+app.use(express.session({ secret: 'your secret here' }))
+app.use(express.bodyParser())
+app.use(app.router)
+app.use(express.static(path.join(__dirname, 'public')))
// development only
-if ('development' == app.get('env')) {
- app.use(express.errorHandler());
+if (app.get('env') === 'development') {
+ app.use(express.errorHandler())
}
-app.get('/', routes.index);
-app.get('/users', user.list);
+app.get('/', routes.index)
+app.get('/users', user.list)
-http.createServer(app).listen(app.get('port'), function(){
- console.log('Express server listening on port ' + app.get('port'));
-});
-
-package.json
+```json
{
"name": "application-name",
"version": "0.0.1",
@@ -354,8 +351,7 @@ Die zugehörige `package.json`-Datei der Version 3 sieht in etwa wie folgt aus:
"pug": "*"
}
}
-
-
-
+```bash
$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
-
-
+```
Nehmen Sie an `app.js` die folgenden Änderungen vor:
1. Die integrierten Express-Middlewarefunktionen `express.favicon`,
- `express.logger`, `express.methodOverride`,
- `express.session`, `express.bodyParser` und
- `express.errorHandler` sind im Objekt `express` nicht mehr verfügbar. Sie müssen deren Alternativen manuell installieren und in die Anwendung laden.
+ `express.logger`, `express.methodOverride`,
+ `express.session`, `express.bodyParser` und
+ `express.errorHandler` sind im Objekt `express` nicht mehr verfügbar. Sie müssen deren Alternativen manuell installieren und in die Anwendung laden.
-2. Sie müssen die Funktion `app.router` nicht mehr laden. Sie ist kein gültiges Express 4-Anwendungsobjekt. Entfernen Sie also den Code `app.use(app.router);`.
+2. Sie müssen die Funktion `app.router` nicht mehr laden.
+ Sie ist kein gültiges Express 4-Anwendungsobjekt. Entfernen Sie also den Code `app.use(app.router);`.
3. Stellen Sie sicher, dass die Middlewarefunktionen in der richtigen Reihenfolge geladen werden – laden Sie `errorHandler` nach dem Laden der Anwendungsweiterleitungen.
@@ -386,8 +381,7 @@ Nehmen Sie an `app.js` die folgenden Änderungen vor:
Durch Ausführung des Befehls `npm` wird `package.json` wie folgt aktualisiert:
-
-
+```json
{
"name": "application-name",
"version": "0.0.1",
@@ -400,87 +394,84 @@ Durch Ausführung des Befehls `npm` wird `package.json` wie folgt aktualisiert:
"errorhandler": "^1.1.1",
"express": "^4.8.0",
"express-session": "^1.7.2",
- "pug": "^2.0.0-beta6",
+ "pug": "^2.0.0",
"method-override": "^2.1.2",
"morgan": "^1.2.2",
"multer": "^0.1.3",
"serve-favicon": "^2.0.1"
}
}
-
-
+```
app.js
Entfernen Sie dann ungültigen Code, laden Sie die erforderliche Middleware und nehmen Sie andere Änderungen nach Bedarf vor. Die Datei `app.js` sieht dann wie folgt aus:
-
-
-var http = require('http');
-var express = require('express');
-var routes = require('./routes');
-var user = require('./routes/user');
-var path = require('path');
+```js
+var http = require('http')
+var express = require('express')
+var routes = require('./routes')
+var user = require('./routes/user')
+var path = require('path')
-var favicon = require('serve-favicon');
-var logger = require('morgan');
-var methodOverride = require('method-override');
-var session = require('express-session');
-var bodyParser = require('body-parser');
-var multer = require('multer');
-var errorHandler = require('errorhandler');
+var favicon = require('serve-favicon')
+var logger = require('morgan')
+var methodOverride = require('method-override')
+var session = require('express-session')
+var bodyParser = require('body-parser')
+var multer = require('multer')
+var errorHandler = require('errorhandler')
-var app = express();
+var app = express()
// all environments
-app.set('port', process.env.PORT || 3000);
-app.set('views', path.join(__dirname, 'views'));
-app.set('view engine', 'pug');
-app.use(favicon(__dirname + '/public/favicon.ico'));
-app.use(logger('dev'));
-app.use(methodOverride());
-app.use(session({ resave: true,
- saveUninitialized: true,
- secret: 'uwotm8' }));
-app.use(bodyParser.json());
-app.use(bodyParser.urlencoded({ extended: true }));
-app.use(multer());
-app.use(express.static(path.join(__dirname, 'public')));
-
-app.get('/', routes.index);
-app.get('/users', user.list);
+app.set('port', process.env.PORT || 3000)
+app.set('views', path.join(__dirname, 'views'))
+app.set('view engine', 'pug')
+app.use(favicon(path.join(__dirname, '/public/favicon.ico')))
+app.use(logger('dev'))
+app.use(methodOverride())
+app.use(session({
+ resave: true,
+ saveUninitialized: true,
+ secret: 'uwotm8'
+}))
+app.use(bodyParser.json())
+app.use(bodyParser.urlencoded({ extended: true }))
+app.use(multer())
+app.use(express.static(path.join(__dirname, 'public')))
+
+app.get('/', routes.index)
+app.get('/users', user.list)
// error handling middleware should be loaded after the loading the routes
-if ('development' == app.get('env')) {
- app.use(errorHandler());
+if (app.get('env') === 'development') {
+ app.use(errorHandler())
}
-var server = http.createServer(app);
-server.listen(app.get('port'), function(){
- console.log('Express server listening on port ' + app.get('port'));
-});
-
-
-
-
-Wenn Sie nicht direkt mit dem Modul `http` arbeiten müssen (socket.io/SPDY/HTTPS), ist das Laden des Moduls nicht erforderlich. Die Anwendung kann dann einfach wie folgt gestartet werden:
-req.param(name)
res.json(obj, status)
res.jsonp(obj, status)
+ res.redirect('back') and res.location('back')
+ res.redirect(url, status)
res.send(body, status)
res.send(status)
res.sendfile()
+ router.param(fn)
+ express.static.mime
+ express:router debug logs
-**Geändert**
+**Verbesserungen**
-app.listen(app.get('port'), function(){
- console.log('Express server listening on port ' + app.get('port'));
-});
-
-
+var server = http.createServer(app)
+server.listen(app.get('port'), () => {
+ console.log('Express server listening on port ' + app.get('port'))
+})
+```
+
+Wenn Sie nicht direkt mit dem Modul `http` arbeiten müssen (socket.io/SPDY/HTTPS), ist das Laden des Moduls nicht erforderlich. Die Anwendung kann dann einfach wie folgt gestartet werden:
+
+```js
+app.listen(app.get('port'), () => {
+ console.log('Express server listening on port ' + app.get('port'))
+})
+```
+
Anwendung ausführen
Der Migrationsprozess ist abgeschlossen und die Anwendung ist nun eine Express 4-Anwendung. Zum Bestätigen starten Sie die Anwendung mit dem folgenden Befehl: -
-
+```bash
$ node .
-
-
+```
Laden Sie [http://localhost:3000](http://localhost:3000) und sehen Sie, wie die Homepage von Express 4 wiedergegeben wird.
@@ -492,23 +483,20 @@ Das Befehlszeilentool zum Generieren einer Express-Anwendung ist nach wie vor `e
Wenn der Express 3 App Generator bereits auf Ihrem System installiert ist, müssen Sie diesen deinstallieren:
-
-
+```bash
$ npm uninstall -g express
-
-
+```
+
Abhängig davon, wie Ihre Datei- und Verzeichnissberechtigungen konfiguriert sind, müssen Sie diesen Befehl möglicherweise mit `sudo` ausführen.
+
Installieren Sie nun den neuen Generator:
-
-
+```bash
$ npm install -g express-generator
-
-
+```
Abhängig davon, wie Ihre Datei- und Verzeichnissberechtigungen konfiguriert sind, müssen Sie diesen Befehl möglicherweise mit `sudo` ausführen.
-
Nun wird der Befehl `express` auf Ihrem System auf den Express 4 App Generator aktualisiert.
Änderungen am App Generator
@@ -516,19 +504,18 @@ Nun wird der Befehl `express` auf Ihrem System auf den Express 4 App Generator a Befehlsoptionen und -nutzung bleiben größtenteils unverändert. Es gelten jedoch folgende Ausnahmen: {: .doclist } -* Option `--sessions` wurde entfernt. -* Option `--jshtml` wurde entfernt. -* Option `--hogan` wurde hinzugefügt, um [Hogan.js](http://twitter.github.io/hogan.js/) zu unterstützen. + +- Option `--sessions` wurde entfernt. +- Option `--jshtml` wurde entfernt. +- Option `--hogan` wurde hinzugefügt, um [Hogan.js](http://twitter.github.io/hogan.js/) zu unterstützen.Beispiel
Führen Sie den folgenden Befehl aus, um eine Express 4-Anwendung zu erstellen: -
-
+```bash
$ express app4
-
-
+```
Wenn Sie sich den Inhalt der Datei `app4/app.js` ansehen, werden Sie feststellen, dass alle Middlewarefunktionen (außer `express.static`), die für die Anwendung erforderlich sind, als unabhängige Module geladen werden und die Middleware `router` nicht mehr explizit in die Anwendung geladen wird.
@@ -536,11 +523,9 @@ Sie werden auch feststellen, dass die Datei `app.js` nun ein Node.js-Modul ist
Starten Sie nach der Installation der Abhängigkeiten die Anwendung mit dem folgenden Befehl:
-
-
+```bash
$ npm start
-
-
+```
Wenn Sie sich das npm-Startscript in der Datei `package.json` näher ansehen, werden Sie feststellen, dass der eigentliche Befehl, der die Anwendung startet, `node ./bin/www` heißt. Dieser Befehl lautete in Express 3 `node app.js`.
@@ -550,23 +535,19 @@ Weder das Verzeichnis `bin` noch die erweiterungslose Datei `www` ist für das E
Um das Verzeichnis `www` zu löschen und alles im "Express 3-Stil" zu belassen, löschen Sie die Zeile mit dem Eintrag `module.exports = app;` am Ende der Datei `app.js`. Fügen Sie dann stattdessen den folgenden Code an derselben Position ein:
-
-
-app.set('port', process.env.PORT || 3000);
+```js
+app.set('port', process.env.PORT || 3000)
-var server = app.listen(app.get('port'), function() {
- debug('Express server listening on port ' + server.address().port);
-});
-
-
+var server = app.listen(app.get('port'), () => {
+ debug('Express server listening on port ' + server.address().port)
+})
+```
Stellen Sie sicher, dass Sie das Modul `debug` am Anfang der Datei `app.js` laden. Verwenden Sie dazu den folgenden Code:
-
-
-var debug = require('debug')('app4');
-
-
+```js
+var debug = require('debug')('app4')
+```
Ändern Sie als Nächstes `"start": "node ./bin/www"` in der Datei `package.json` in `"start": "node app.js"`.
diff --git a/de/guide/migrating-5.md b/de/guide/migrating-5.md
old mode 100755
new mode 100644
index 837fdea897..af9d495fd5
--- a/de/guide/migrating-5.md
+++ b/de/guide/migrating-5.md
@@ -1,31 +1,44 @@
---
layout: page
title: Migration auf Express 5
+description: A comprehensive guide to migrating your Express.js applications from version 4 to 5, detailing breaking changes, deprecated methods, and new improvements.
menu: guide
-lang: de
+redirect_from: " "
---
# Wechsel zu Express 5
Überblick
-Express 5.0 befindet sich noch in der Alpha-Release-Phase. Hier finden Sie jedoch bereits eine Vorschau zu den Änderungen in diesem Release und zur Migration Ihrer Express 4-Anwendung auf Express 5. +Express 5.0 befindet sich noch in der Beta-Release-Phase. Hier finden Sie jedoch bereits eine Vorschau zu den Änderungen in diesem Release und zur Migration Ihrer Express 4-Anwendung auf Express 5. -Express 5 unterscheidet sich nicht allzu sehr von Express 4: Die Änderungen an der API sind nicht so signifikant wie von 3.0 zu 4.0. Auch wenn die Basis-API unverändert bleibt, wird es doch einige grundlegende Veränderungen geben. In anderen Worten: Ein vorhandenes Express 4-Programm funktioniert möglicherweise nicht mehr, wenn Sie es für Express 5 aktualisieren. +To install this version, you need to have a Node.js version 18 or higher. Then, execute the following command in your application directory: -Zum Installieren der aktuellen Alpha-Version und zur Vorschau von Express 5 geben Sie den folgenden Befehl im Stammverzeichnis Ihrer Anwendung ein: - -
-
-$ npm install express@5.0.0-alpha.2 --save
-
-
+```sh
+npm install "express@5"
+```
Sie können Ihre automatisierten Tests ausführen, um zu sehen, was fehlschlägt, und Probleme gemäß den folgenden Updates beheben. Nachdem Sie alle Testfehler behoben haben, führen Sie Ihre Anwendung aus, um zu sehen, welche Fehler noch auftreten. Sie werden sofort feststellen, ob die Anwendung Methoden oder Eigenschaften verwendet, die nicht unterstützt werden.
-Änderungen in Express 5
+## Express 5 Codemods + +To help you migrate your express server, we have created a set of codemods that will help you automatically update your code to the latest version of Express. + +Run the following command for run all the codemods available: + +```sh +npx @expressjs/codemod upgrade +``` + +If you want to run a specific codemod, you can run the following command: + +```sh +npx @expressjs/codemod name-of-the-codemod +``` + +You can find the list of available codemods [here](https://github.com/expressjs/codemod?tab=readme-ov-file#available-codemods). -Nachfolgend finden Sie eine Liste mit Änderungen (Stand: Alpha-2-Release), die sich auf Sie als Express-Benutzer auswirken werden. Siehe hierzu auch die [Pull-Anforderung](https://github.com/expressjs/express/pull/2237) mit einer Liste aller geplanten Features und Funktionen. +Änderungen in Express 5
**Entfernte Methoden und Eigenschaften** @@ -37,95 +50,497 @@ Nachfolgend finden Sie eine Liste mit Änderungen (Stand: Alpha-2-Release), die-
+
- Path route matching syntax +
- Rejected promises handled from middleware and handlers +
- express.urlencoded +
- express.static dotfiles +
- app.listen
- app.router +
- req.body
- req.host
- req.query +
- res.clearCookie +
- res.status +
- res.vary
Entfernte Methoden und Eigenschaften
+## Entfernte Methoden und Eigenschaften Wenn Sie eine dieser Methoden oder Eigenschaften in Ihrer Anwendung verwenden, stürzt die Anwendung ab. Sie müssen also Ihre Anwendung ändern, wenn Sie auf Version 5 umgestellt haben. -app.del()
+app.del()
Express 5 unterstützt die Funktion `app.del()` nicht mehr. Wenn Sie diese Funktion verwenden, wird ein Fehler ausgelöst. Für die Registrierung von HTTP DELETE-Weiterleitungen verwenden Sie stattdessen die Funktion `app.delete()`. -Anfänglich wurde `del` statt `delete` verwendet, weil `delete` in JavaScript ein reserviertes Schlüsselwort ist. Ab ECMAScript 6 jedoch können `delete` und andere reservierte Schlüsselwörter legal als Eigenschaftsnamen verwendet werden. Lesen hier auch die Diskussion, die zur Einstellung der Unterstützung der Funktion `app.del` geführt hat. +Anfänglich wurde `del` statt `delete` verwendet, weil `delete` in JavaScript ein reserviertes Schlüsselwort ist. Ab ECMAScript 6 jedoch können `delete` und andere reservierte Schlüsselwörter legal als Eigenschaftsnamen verwendet werden. + +{% capture codemod-deprecated-signatures %} +You can replace the deprecated signatures with the following command: + +```plain-text +npx @expressjs/codemod v4-deprecated-signatures +``` + +{% endcapture %} -app.param(fn)
+{% include admonitions/note.html content=codemod-deprecated-signatures %} -Die Signatur `app.param(fn)` wurde für die Änderung der Verhaltensweise der Funktion `app.param(name, fn)` verwendet. Seit v4.11.0 wurde sie nicht mehr verwendet. In Express 5 wird sie überhaupt nicht mehr unterstützt. +```js +// v4 +app.del('/user/:id', (req, res) => { + res.send(`DELETE /user/${req.params.id}`) +}) -Pluralisierte Methodennamen
+// v5 +app.delete('/user/:id', (req, res) => { + res.send(`DELETE /user/${req.params.id}`) +}) +``` + +app.param(fn)
+ +Die Signatur `app.param(fn)` wurde für die Änderung der Verhaltensweise der Funktion `app.param(name, fn)` verwendet. Seit v4.11.0 wurde sie nicht mehr verwendet. In Express 5 wird sie überhaupt nicht mehr unterstützt. + +Pluralisierte Methodennamen
Die folgenden Methodennamen wurden pluralisiert. In Express 4 wurde bei Verwendung der alten Methoden eine Warnung zur Einstellung der Unterstützung ausgegeben. Express 5 unterstützt diese Methoden nicht mehr. +`req.acceptsLanguage()` wird durch `req.acceptsLanguages()` ersetzt. + `req.acceptsCharset()` wird durch `req.acceptsCharsets()` ersetzt. `req.acceptsEncoding()` wird durch `req.acceptsEncodings()` ersetzt. -`req.acceptsLanguage()` wird durch `req.acceptsLanguages()` ersetzt. +{% capture codemod-pluralized-methods %} +You can replace the deprecated signatures with the following command: + +```plain-text +npx @expressjs/codemod pluralized-methods +``` + +{% endcapture %} -Führender Doppelpunkt (:) im Namen für app.param(name, fn)
+{% include admonitions/note.html content=codemod-pluralized-methods %} + +```js +// v4 +app.all('/', (req, res) => { + req.acceptsCharset('utf-8') + req.acceptsEncoding('br') + req.acceptsLanguage('en') + + // ... +}) + +// v5 +app.all('/', (req, res) => { + req.acceptsCharsets('utf-8') + req.acceptsEncodings('br') + req.acceptsLanguages('en') + + // ... +}) +``` + +Führender Doppelpunkt (:) im Namen für app.param(name, fn)
Ein führendes Doppelpunktzeichen (:) im Namen für die Funktion `app.param(name, fn)` ist ein Überbleibsel aus Express 3. Aus Gründen der Abwärtskompatibilität wurde dieser Name in Express 4 mit einem Hinweis zu veralteten Versionen weiter unterstützt. In Express 5 wird dieser Name stillschwiegend ignoriert und der Namensparameter ohne einen vorangestellten Doppelpunkt verwendet. Dies dürfte keine Auswirkungen auf Ihren Code haben, wenn Sie die Express 4-Dokumentation zu [app.param](/{{ page.lang }}/4x/api.html#app.param) befolgen, da dort der führende Doppelpunkt nicht erwähnt wird. -req.param(name)
+req.param(name)
Dieses potenziell verwirrende und durchaus riskante Verfahren des Abrufens von Formulardaten wurde entfernt. Sie müssen nun ganz speziell nach dem übergebenen Parameternamen im Objekt `req.params`, `req.body` oder `req.query` suchen. -res.json(obj, status)
+{% capture codemod-req-param %} +You can replace the deprecated signatures with the following command: + +```plain-text +npx @expressjs/codemod req-param +``` + +{% endcapture %} + +{% include admonitions/note.html content=codemod-req-param %} + +```js +// v4 +app.post('/user', (req, res) => { + const id = req.param('id') + const body = req.param('body') + const query = req.param('query') + + // ... +}) + +// v5 +app.post('/user', (req, res) => { + const id = req.params.id + const body = req.body + const query = req.query + + // ... +}) +``` + +res.json(obj, status)
Express 5 unterstützt die Signatur `res.json(obj, status)` nicht mehr. Stattdessen müssen Sie den Status festlegen und diesen dann mit `res.json()`-Methoden wie dieser verketten: `res.status(status).json(obj)`. -res.jsonp(obj, status)
+{% include admonitions/note.html content=codemod-deprecated-signatures %} + +```js +// v4 +app.post('/user', (req, res) => { + res.json({ name: 'Ruben' }, 201) +}) + +// v5 +app.post('/user', (req, res) => { + res.status(201).json({ name: 'Ruben' }) +}) +``` + +res.jsonp(obj, status)
Express 5 unterstützt die Signatur `res.jsonp(obj, status)` nicht mehr. Stattdessen müssen Sie den Status festlegen und diesen dann mit `res.jsonp()`-Methoden wie dieser verketten: `res.status(status).jsonp(obj)`. -res.send(body, status)
+{% include admonitions/note.html content=codemod-deprecated-signatures %} + +```js +// v4 +app.post('/user', (req, res) => { + res.jsonp({ name: 'Ruben' }, 201) +}) + +// v5 +app.post('/user', (req, res) => { + res.status(201).jsonp({ name: 'Ruben' }) +}) +``` + +res.redirect(url, status)
Express 5 unterstützt die Signatur `res.send(obj, status)` nicht mehr. Stattdessen müssen Sie den Status festlegen und diesen dann mit `res.send()`-Methoden wie dieser verketten: `res.status(status).send(obj)`. -res.send(status)
+{% include admonitions/note.html content=codemod-deprecated-signatures %} + +```js +// v4 +app.get('/user', (req, res) => { + res.redirect('/users', 301) +}) + +// v5 +app.get('/user', (req, res) => { + res.redirect(301, '/users') +}) +``` + +res.redirect('back') and res.location('back')
+ +Express 5 no longer supports the magic string `back` in the `res.redirect()` and `res.location()` methods. Instead, use the `req.get('Referrer') || '/'` value to redirect back to the previous page. In Express 4, the res.`redirect('back')` and `res.location('back')` methods were deprecated. + +{% capture codemod-magic-redirect %} +You can replace the deprecated signatures with the following command: + +```plain-text +npx @expressjs/codemod magic-redirect +``` + +{% endcapture %} + +{% include admonitions/note.html content=codemod-magic-redirect %} + +```js +// v4 +app.get('/user', (req, res) => { + res.redirect('back') +}) + +// v5 +app.get('/user', (req, res) => { + res.redirect(req.get('Referrer') || '/') +}) +``` + +res.send(body, status)
+ +Express 5 no longer supports the signature `res.send(obj, status)`. Instead, set the status and then chain it to the `res.send()` method like this: `res.status(status).send(obj)`. + +{% include admonitions/note.html content=codemod-deprecated-signatures %} + +```js +// v4 +app.get('/user', (req, res) => { + res.send({ name: 'Ruben' }, 200) +}) + +// v5 +app.get('/user', (req, res) => { + res.status(200).send({ name: 'Ruben' }) +}) +``` + +res.send(status)
+ +Express 5 unterstützt die Signaturres.send(status), nicht mehr, wobei _`status`_ für eine Zahl steht. Verwenden Sie stattdessen die Funktion `res.sendStatus(statusCode)`, mit der der Statuscode für den HTTP-Antwort-Header festgelegt und die Textversion des Codes gesendet wird: "Not Found" (Nicht gefunden), "Internal Server Error" (Interner Serverfehler) usw.
+Wenn Sie eine Zahl senden und hierfür die Funktion `res.send()` verwenden müssen, müssen Sie die Zahl in Anführungszeichen setzen, um diese in eine Zeichenfolge zu konvertieren. Dadurch interpretiert Express diese Zahl nicht als Versuch, die nicht mehr unterstützte alte Signatur zu verwenden.
+
+{% include admonitions/note.html content=codemod-deprecated-signatures %}
-Express 5 unterstützt die Signatur res.send(status), nicht mehr, wobei *`status`* für eine Zahl steht. Verwenden Sie stattdessen die Funktion `res.sendStatus(statusCode)`, mit der der Statuscode für den HTTP-Antwort-Header festgelegt und die Textversion des Codes gesendet wird: "Not Found" (Nicht gefunden), "Internal Server Error" (Interner Serverfehler) usw. Wenn Sie eine Zahl senden und hierfür die Funktion `res.send()` verwenden müssen, müssen Sie die Zahl in Anführungszeichen setzen, um diese in eine Zeichenfolge zu konvertieren. Dadurch interpretiert Express diese Zahl nicht als Versuch, die nicht mehr unterstützte alte Signatur zu verwenden.
+```js
+// v4
+app.get('/user', (req, res) => {
+ res.send(200)
+})
-res.sendfile()
+// v5 +app.get('/user', (req, res) => { + res.sendStatus(200) +}) +``` + +res.sendfile()
Die Funktion `res.sendfile()` wurde durch eine Version in Camel-Schreibweise von `res.sendFile()` in Express 5 ersetzt. -Geändert
+**Note:** In Express 5, `res.sendFile()` uses the `mime-types` package for MIME type detection, which returns different Content-Type values than Express 4 for several common file types: + +- JavaScript files (.js): now "text/javascript" instead of "application/javascript" +- JSON files (.json): now "application/json" instead of "text/json" +- CSS files (.css): now "text/css" instead of "text/plain" +- XML files (.xml): now "application/xml" instead of "text/xml" +- Font files (.woff): now "font/woff" instead of "application/font-woff" +- SVG files (.svg): now "image/svg+xml" instead of "application/svg+xml" + +{% include admonitions/note.html content=codemod-deprecated-signatures %} + +```js +// v4 +app.get('/user', (req, res) => { + res.sendfile('/path/to/file') +}) + +// v5 +app.get('/user', (req, res) => { + res.sendFile('/path/to/file') +}) +``` + +router.param(fn)
+ +The `router.param(fn)` signature was used for modifying the behavior of the `router.param(name, fn)` function. Seit v4.11.0 wurde sie nicht mehr verwendet. In Express 5 wird sie überhaupt nicht mehr unterstützt. + +express.static.mime
+ +In Express 5, `mime` is no longer an exported property of the `static` field. +Use the [`mime-types` package](https://github.com/jshttp/mime-types) to work with MIME type values. + +**Important:** This change affects not only direct usage of `express.static.mime` but also other Express methods that rely on MIME type detection, such as `res.sendFile()`. The following MIME types have changed from Express 4: + +- JavaScript files (.js): now served as "text/javascript" instead of "application/javascript" +- JSON files (.json): now served as "application/json" instead of "text/json" +- CSS files (.css): now served as "text/css" instead of "text/plain" +- HTML files (.html): now served as "text/html; charset=utf-8" instead of just "text/html" +- XML files (.xml): now served as "application/xml" instead of "text/xml" +- Font files (.woff): now served as "font/woff" instead of "application/font-woff" + +```js +// v4 +express.static.mime.lookup('json') + +// v5 +const mime = require('mime-types') +mime.lookup('json') +``` + +express:router debug logs
+ +In Express 5, router handling logic is performed by a dependency. Therefore, the +debug logs for the router are no longer available under the `express:` namespace. +In v4, the logs were available under the namespaces `express:router`, `express:router:layer`, +and `express:router:route`. All of these were included under the namespace `express:*`. +In v5.1+, the logs are available under the namespaces `router`, `router:layer`, and `router:route`. +The logs from `router:layer` and `router:route` are included in the namespace `router:*`. +To achieve the same detail of debug logging when using `express:*` in v4, use a conjunction of +`express:*`, `router`, and `router:*`. + +```sh +# v4 +DEBUG=express:* node index.js + +# v5 +DEBUG=express:*,router,router:* node index.js +``` + +## Geändert + +Path route matching syntax
+ +Path route matching syntax is when a string is supplied as the first parameter to the `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()`, and `router.use()` APIs. The following changes have been made to how the path string is matched to an incoming request: + +- The wildcard `*` must have a name, matching the behavior of parameters `:`, use `/*splat` instead of `/*` + +```js +// v4 +app.get('/*', async (req, res) => { + res.send('ok') +}) + +// v5 +app.get('/*splat', async (req, res) => { + res.send('ok') +}) +``` + +{% capture note_wildcard %} +`*splat` matches any path without the root path. If you need to match the root path as well `/`, you can use `/{*splat}`, wrapping the wildcard in braces. + +```js +// v5 +app.get('/{*splat}', async (req, res) => { + res.send('ok') +}) +``` + +{% endcapture %} +{% include admonitions/note.html content=note_wildcard %} + +- The optional character `?` is no longer supported, use braces instead. + +```js +// v4 +app.get('/:file.:ext?', async (req, res) => { + res.send('ok') +}) + +// v5 +app.get('/:file{.:ext}', async (req, res) => { + res.send('ok') +}) +``` + +- Regexp characters are not supported. Beispiel: -app.router
+```js +app.get('/[discussion|page]/:slug', async (req, res) => { + res.status(200).send('ok') +}) +``` + +should be changed to: + +```js +app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => { + res.status(200).send('ok') +}) +``` + +- Some characters have been reserved to avoid confusion during upgrade (`()[]?+!`), use `\` to escape them. +- Parameter names now support valid JavaScript identifiers, or quoted like `:"this"`. + +Rejected promises handled from middleware and handlers
+ +Request middleware and handlers that return rejected promises are now handled by forwarding the rejected value as an `Error` to the error handling middleware. This means that using `async` functions as middleware and handlers are easier than ever. When an error is thrown in an `async` function or a rejected promise is `await`ed inside an async function, those errors will be passed to the error handler as if calling `next(err)`. + +Details of how Express handles errors is covered in the [error handling documentation](/en/guide/error-handling.html). + +express.urlencoded
+ +The `express.urlencoded` method makes the `extended` option `false` by default. + +express.static dotfiles
+ +In Express 5, the `express.static` middleware's `dotfiles` option now defaults to `"ignore"`. This is a change from Express 4, where dotfiles were served by default. As a result, files inside a directory that starts with a dot (`.`), such as `.well-known`, will no longer be accessible and will return a **404 Not Found** error. This can break functionality that depends on serving dot-directories, such as Android App Links, and Apple Universal Links. + +Example of breaking code: + +```js +// v4 +app.use(express.static('public')) +``` + +After migrating to Express 5, a request to `/.well-known/assetlinks.json` will result in a **404 Not Found**. + +To fix this, serve specific dot-directories explicitly using the `dotfiles: "allow"` option: + +```js +// v5 +app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' })) +app.use(express.static('public')) +``` + +This approach allows you to safely serve only the intended dot-directories while keeping the default secure behavior for other dotfiles, which remain inaccessible. + +app.listen
+ +In Express 5, the `app.listen` method will invoke the user-provided callback function (if provided) when the server receives an error event. In Express 4, such errors would be thrown. This change shifts error-handling responsibility to the callback function in Express 5. If there is an error, it will be passed to the callback as an argument. +Beispiel: + +```js +const server = app.listen(8080, '0.0.0.0', (error) => { + if (error) { + throw error // e.g. EADDRINUSE + } + console.log(`Listening on ${JSON.stringify(server.address())}`) +}) +``` + +app.router
Das Objekt `app.router`, das in Express 4 entfernt wurde, ist in Express 5 wieder verfügbar. In der neuen Version fungiert dieses Objekt nur als Referenz zum Express-Basisrouter – im Gegensatz zu Express 3, wo die Anwendung dieses Objekt explizit laden musste. -req.host
+req.body
+ +The `req.body` property returns `undefined` when the body has not been parsed. In Express 4, it returns `{}` by default. + +req.host
In Express 4 übergab die Funktion `req.host` nicht ordnungsgemäß eine eventuell vorhandene Portnummer. In Express 5 wird die Portnummer beibehalten. -req.query
+req.query
+ +The `req.query` property is no longer a writable property and is instead a getter. The default query parser has been changed from "extended" to "simple". -In Express 4.7 und ab Express 5 kann die Abfrageparser-Option `false` akzeptieren, um das Parsing von Abfragezeichenfolgen zu deaktivieren, wenn Sie Ihre eigene Funktion für die Parsinglogik bei Abfragezeichenfolgen verwenden wollen. +res.clearCookie
-Verbesserungen
+The `res.clearCookie` method ignores the `maxAge` and `expires` options provided by the user. -res.render()
+res.status
+ +The `res.status` method only accepts integers in the range of `100` to `999`, following the behavior defined by Node.js, and it returns an error when the status code is not an integer. + +res.vary
+ +The `res.vary` throws an error when the `field` argument is missing. In Express 4, if the argument was omitted, it gave a warning in the console + +## Verbesserungen + +res.render()
Diese Methode erzwingt nun asynchrones Verhalten für alle View-Engines, sodass durch View-Engines mit synchroner Implementierung verursachte Fehler vermieden werden, durch die die empfohlene Schnittstelle nicht verwendet werden konnte. + +Brotli encoding support
+ +Express 5 supports Brotli encoding for requests received from clients that support it. diff --git a/de/guide/overriding-express-api.md b/de/guide/overriding-express-api.md new file mode 100644 index 0000000000..032e3dd625 --- /dev/null +++ b/de/guide/overriding-express-api.md @@ -0,0 +1,72 @@ +--- +layout: page +title: Overriding the Express API +description: Discover how to customize and extend the Express.js API by overriding methods and properties on the request and response objects using prototypes. +menu: guide +--- + +# Overriding the Express API + +The Express API consists of various methods and properties on the request and response objects. These are inherited by prototype. There are two extension points for the Express API: + +1. The global prototypes at `express.request` and `express.response`. +2. App-specific prototypes at `app.request` and `app.response`. + +Altering the global prototypes will affect all loaded Express apps in the same process. If desired, alterations can be made app-specific by only altering the app-specific prototypes after creating a new app. + +## Methods + +You can override the signature and behavior of existing methods with your own, by assigning a custom function. + +Following is an example of overriding the behavior of [res.sendStatus](/4x/api.html#res.sendStatus). + +```js +app.response.sendStatus = function (statusCode, type, message) { + // code is intentionally kept simple for demonstration purpose + return this.contentType(type) + .status(statusCode) + .send(message) +} +``` + +The above implementation completely changes the original signature of `res.sendStatus`. It now accepts a status code, encoding type, and the message to be sent to the client. + +The overridden method may now be used this way: + +```js +res.sendStatus(404, 'application/json', '{"error":"resource not found"}') +``` + +## Properties + +Properties in the Express API are either: + +1. Assigned properties (ex: `req.baseUrl`, `req.originalUrl`) +2. Defined as getters (ex: `req.secure`, `req.ip`) + +Since properties under category 1 are dynamically assigned on the `request` and `response` objects in the context of the current request-response cycle, their behavior cannot be overridden. + +Properties under category 2 can be overwritten using the Express API extensions API. + +The following code rewrites how the value of `req.ip` is to be derived. Now, it simply returns the value of the `Client-IP` request header. + +```js +Object.defineProperty(app.request, 'ip', { + configurable: true, + enumerable: true, + get () { return this.get('Client-IP') } +}) +``` + +## Prototype + +In order to provide the Express API, the request/response objects passed to Express (via `app(req, res)`, for example) need to inherit from the same prototype chain. By default, this is `http.IncomingRequest.prototype` for the request and `http.ServerResponse.prototype` for the response. + +Unless necessary, it is recommended that this be done only at the application level, rather than globally. Also, take care that the prototype that is being used matches the functionality as closely as possible to the default prototypes. + +```js +// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse +// for the given app reference +Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype) +Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype) +``` diff --git a/de/guide/routing.md b/de/guide/routing.md old mode 100755 new mode 100644 index 42c4a90989..29fdb6431c --- a/de/guide/routing.md +++ b/de/guide/routing.md @@ -1,27 +1,38 @@ --- layout: page title: Weiterleitung in Express +description: Learn how to define and use routes in Express.js applications, including route methods, route paths, parameters, and using Router for modular routing. menu: guide -lang: de +redirect_from: " " --- # Weiterleitung (Routing) -Der Begriff *Weiterleitung* (Routing) bezieht sich auf die Definition von Anwendungsendpunkten (URIs) und deren Antworten auf Clientanforderungen. Eine Einführung in dieses Routing siehe [Basisrouting](/{{ page.lang }}/starter/basic-routing.html). +Der Begriff _Weiterleitung_ (Routing) bezieht sich auf die Definition von Anwendungsendpunkten (URIs) und deren Antworten auf Clientanforderungen. +Eine Einführung in dieses Routing siehe [Basisrouting](/{{ page.lang }}/starter/basic-routing.html). + +You define routing using methods of the Express `app` object that correspond to HTTP methods; +for example, `app.get()` to handle GET requests and `app.post` to handle POST requests. For a full list, +see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD). You can also use [app.all()](/{{ page.lang }}/5x/api.html#app.all) to handle all HTTP methods and [app.use()](/{{ page.lang }}/5x/api.html#app.use) to +specify middleware as the callback function (See [Using middleware](/{{ page.lang }}/guide/using-middleware.html) for details). + +These routing methods specify a callback function (sometimes called "handler functions") called when the application receives a request to the specified route (endpoint) and HTTP method. In other words, the application "listens" for requests that match the specified route(s) and method(s), and when it detects a match, it calls the specified callback function. + +In fact, the routing methods can have more than one callback function as arguments. +With multiple callback functions, it is important to provide `next` as an argument to the callback function and then call `next()` within the body of the function to hand off control +to the next callback. Der folgende Code ist ein Beispiel für ein sehr einfaches Basisrouting. -
-
-var express = require('express');
-var app = express();
+```js
+const express = require('express')
+const app = express()
// respond with "hello world" when a GET request is made to the homepage
-app.get('/', function(req, res) {
- res.send('hello world');
-});
-
-
+app.get('/', (req, res) => {
+ res.send('hello world')
+})
+```
Weiterleitungsmethoden
@@ -29,150 +40,205 @@ Eine Weiterleitungsmethode wird von einer HTTP-Methode abgeleitet und an eine In Der folgende Code ist ein Beispiel für Weiterleitungen, die für die Methoden GET und POST zum Stamm (Root) der Anwendung definiert werden. -
-
+```js
// GET method route
-app.get('/', function (req, res) {
- res.send('GET request to the homepage');
-});
+app.get('/', (req, res) => {
+ res.send('GET request to the homepage')
+})
// POST method route
-app.post('/', function (req, res) {
- res.send('POST request to the homepage');
-});
-
-
-
-Express unterstützt die folgenden Weiterleitungsmethoden, die den HTTP-Methoden entsprechen: `get`, `post`, `put`, `head`, `delete`, `options`, `trace`, `copy`, `lock`, `mkcol`, `move`, `purge`, `propfind`, `proppatch`, `unlock`, `report`, `mkactivity`, `checkout`, `merge`, `m-search`, `notify`, `subscribe`, `unsubscribe`, `patch`, `search` und `connect`.
+app.post('/', (req, res) => {
+ res.send('POST request to the homepage')
+})
+```
-
-Verwenden Sie zum Weiterleiten von Methoden, die zu den JavaScript-Variablennamen führen, die Notation "Eckige Klammer". Beispiel: `app['m-search']('/', function ...`
-
-
-Es gibt eine spezielle Weiterleitungsmethode, `app.all()`, die nicht von einer HTTP-Methode abgeleitet wird. Diese Methode wird zum Laden von Middlewarefunktionen bei einem Pfad für alle Anforderungsmethoden verwendet.
+Express supports methods that correspond to all HTTP request methods: `get`, `post`, and so on.
+For a full list, see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD).
-Im folgenden Beispiel wird der Handler für Anforderungen zur Weiterleitung "/secret" ausgeführt, um herauszufinden, ob Sie GET-, POST-, PUT-, DELETE- oder andere HTTP-Anforderungsmethoden verwenden, die im [HTTP-Modul](https://nodejs.org/api/http.html#http_http_methods) unterstützt werden.
+Es gibt eine spezielle Weiterleitungsmethode, `app.all()`, die nicht von einer HTTP-Methode abgeleitet wird. Diese Methode wird zum Laden von Middlewarefunktionen bei einem Pfad für alle Anforderungsmethoden verwendet. Im folgenden Beispiel wird der Handler für Anforderungen zur Weiterleitung "/secret" ausgeführt, um herauszufinden, ob Sie GET-, POST-, PUT-, DELETE- oder andere HTTP-Anforderungsmethoden verwenden, die im [HTTP-Modul](https://nodejs.org/api/http.html#http_http_methods) unterstützt werden.
-
-
-app.all('/secret', function (req, res, next) {
- console.log('Accessing the secret section ...');
- next(); // pass control to the next handler
-});
-
-
+```js
+app.all('/secret', (req, res, next) => {
+ console.log('Accessing the secret section ...')
+ next() // pass control to the next handler
+})
+```
Weiterleitungspfade
Über Weiterleitungspfade werden in Kombination mit einer Anforderungsmethode die Endpunkte definiert, bei denen Anforderungen erfolgen können. Weiterleitungspfade können Zeichenfolgen, Zeichenfolgemuster oder reguläre Ausdrücke sein. -
-Express verwendet für den Abgleich der Weiterleitungspfade [path-to-regexp](https://www.npmjs.com/package/path-to-regexp). In der Dokumentation zu "path-to-regexp" finden Sie alle Möglichkeiten zum Definieren von Weiterleitungspfaden. [Express Route Tester](http://forbeslindesay.github.io/express-route-tester/) ist ein handliches Tool zum Testen von Express-Basisweiterleitungen, auch wenn dieses Tool keine Musterabgleiche unterstützt.
-
+{% capture caution-character %} In express 5, the characters `?`, `+`, `*`, `[]`, and `()` are handled differently than in version 4, please review the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-Abfragezeichenfolgen sind nicht Teil des Weiterleitungspfads.
-
+{% include admonitions/caution.html content=caution-character %}
-Dies sind einige Beispiele für Weiterleitungspfade auf Basis von Zeichenfolgen.
+{% capture note-dollar-character %}In express 4, regular expression characters such as `$` need to be escaped with a `\`.
+{% endcapture %}
+
+{% include admonitions/caution.html content=note-dollar-character %}
+
+{% capture note-path-to-regexp %}
+
+Express uses [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) for matching the route paths; see the path-to-regexp documentation for all the possibilities in defining route paths. [Express Route Tester](http://forbeslindesay.github.io/express-route-tester/) ist ein handliches Tool zum Testen von Express-Basisweiterleitungen, auch wenn dieses Tool keine Musterabgleiche unterstützt.
+
+{% endcapture %}
+
+{% include admonitions/note.html content=note-path-to-regexp %}
+
+{% capture query-string-note %}
+
+Query strings are not part of the route path.
+
+{% endcapture %}
+
+{% include admonitions/warning.html content=query-string-note %}
+
+### Route paths based on strings
Dieser Weiterleitungspfad gleicht Weiterleitungsanforderungen zum Stammverzeichnis (`/`) ab.
-
-
-app.get('/', function (req, res) {
- res.send('root');
-});
-
-
+```js
+app.get('/', (req, res) => {
+ res.send('root')
+})
+```
Dieser Weiterleitungspfad gleicht Anforderungen mit `/about` ab.
-
-
-app.get('/about', function (req, res) {
- res.send('about');
-});
-
-
+```js
+app.get('/about', (req, res) => {
+ res.send('about')
+})
+```
Dieser Weiterleitungspfad gleicht Anforderungen mit `/random.text` ab.
-
-
-app.get('/random.text', function (req, res) {
- res.send('random.text');
-});
-
-
+```js
+app.get('/random.text', (req, res) => {
+ res.send('random.text')
+})
+```
-Dies sind einige Beispiele für Weiterleitungspfade auf Basis von Zeichenfolgemustern.
+### Route paths based on string patterns
+
+{% capture caution-string-patterns %} The string patterns in Express 5 no longer work. Please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
+
+{% include admonitions/caution.html content=caution-string-patterns %}
Dieser Weiterleitungspfad gleicht `acd` und `abcd` ab.
-
-
-app.get('/ab?cd', function(req, res) {
- res.send('ab?cd');
-});
-
-
-
-Dieser Weiterleitungspfad gleicht `abcd`, `abbcd`, `abbbcd` usw. ab.
-
-
-
-app.get('/ab+cd', function(req, res) {
- res.send('ab+cd');
-});
-
-
-
-Dieser Weiterleitungspfad gleicht `abcd`, `abxcd`, `abRABDOMcd`, `ab123cd` usw. ab.
-
-
-
-app.get('/ab*cd', function(req, res) {
- res.send('ab*cd');
-});
-
-
+```js
+app.get('/ab?cd', (req, res) => {
+ res.send('ab?cd')
+})
+```
+
+Dies sind einige Beispiele für Weiterleitungspfade auf Basis von Zeichenfolgemustern.
+
+```js
+app.get('/ab+cd', (req, res) => {
+ res.send('ab+cd')
+})
+```
+
+Dies sind einige Beispiele für Weiterleitungspfade auf Basis von Zeichenfolgen.
+
+```js
+app.get('/ab*cd', (req, res) => {
+ res.send('ab*cd')
+})
+```
Dieser Weiterleitungspfad gleicht `/abe` und `/abcde` ab.
-
-
-app.get('/ab(cd)?e', function(req, res) {
- res.send('ab(cd)?e');
-});
-
-
+```js
+app.get('/ab(cd)?e', (req, res) => {
+ res.send('ab(cd)?e')
+})
+```
+
+### Route paths based on regular expressions
-
-Die Zeichen ?, +, * und () sind Subsets ihrer Entsprechungen in regulären Ausdrücken. Der Bindestrich (-) und der Punkt (.) werden von zeichenfolgebasierten Pfaden förmlich interpretiert.
+Dieser Weiterleitungspfad gleicht alle Weiterleitungsnamen ab, die den Buchstaben "a" enthalten.
+
+```js
+app.get(/a/, (req, res) => {
+ res.send('/a/')
+})
+```
+
+Dieser Weiterleitungspfad gleicht `butterfly` und `dragonfly`, jedoch nicht `butterflyman`, `dragonfly man` usw.
+
+```js
+app.get(/.*fly$/, (req, res) => {
+ res.send('/.*fly$/')
+})
+```
+
+
Route parameters
+ +Route parameters are named URL segments that are used to capture the values specified at their position in the URL. The captured values are populated in the `req.params` object, with the name of the route parameter specified in the path as their respective keys. + +``` +Route path: /users/:userId/books/:bookId +Request URL: http://localhost:3000/users/34/books/8989 +req.params: { "userId": "34", "bookId": "8989" } +``` + +To define routes with route parameters, simply specify the route parameters in the path of the route as shown below. + +```js +app.get('/users/:userId/books/:bookId', (req, res) => { + res.send(req.params) +}) +``` + +
+The name of route parameters must be made up of "word characters" ([A-Za-z0-9_]).
-Beispiele für Weiterleitungspfade auf Basis regulärer Ausdrücke:
+Since the hyphen (`-`) and the dot (`.`) are interpreted literally, they can be used along with route parameters for useful purposes.
-Dieser Weiterleitungspfad gleicht alle Weiterleitungsnamen ab, die den Buchstaben "a" enthalten.
+```
+Route path: /flights/:from-:to
+Request URL: http://localhost:3000/flights/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+Route path: /plantae/:genus.:species
+Request URL: http://localhost:3000/plantae/Prunus.persica
+req.params: { "genus": "Prunus", "species": "persica" }
+```
+
+{% capture warning-regexp %}
+In express 5, Regexp characters are not supported in route paths, for more information please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax).{% endcapture %}
+
+{% include admonitions/caution.html content=warning-regexp %}
-
-
-app.get(/a/, function(req, res) {
- res.send('/a/');
-});
-
-
+To have more control over the exact string that can be matched by a route parameter, you can append a regular expression in parentheses (`()`):
-Dieser Weiterleitungspfad gleicht `butterfly` und `dragonfly`, jedoch nicht `butterflyman`, `dragonfly man` usw. ab.
+```
+Route path: /user/:userId(\d+)
+Request URL: http://localhost:3000/user/42
+req.params: {"userId": "42"}
+```
-
-
-app.get(/.*fly$/, function(req, res) {
- res.send('/.*fly$/');
-});
-
-
+{% capture escape-advisory %}
+
+Because the regular expression is usually part of a literal string, be sure to escape any `\` characters with an additional backslash, for example `\\d+`.
+
+{% endcapture %}
+
+{% include admonitions/warning.html content=escape-advisory %}
+
+{% capture warning-version %}
+
+In Express 4.x, the `*` character in regular expressions is not interpreted in the usual way. As a workaround, use `{0,}` instead of `*`. This will likely be fixed in Express 5.
+
+{% endcapture %}
+
+{% include admonitions/warning.html content=warning-version %}
Routenhandler (Weiterleitungsroutinen)
@@ -182,108 +248,99 @@ Routenhandler können eine Funktion und/oder ein Funktionsarray sein, wie in den Eine einzelne Callback-Funktion kann eine Weiterleitung verarbeiten. Beispiel: -
-
-app.get('/example/a', function (req, res) {
- res.send('Hello from A!');
-});
-
-
+```js
+app.get('/example/a', (req, res) => {
+ res.send('Hello from A!')
+})
+```
Mehrere Callback-Funktionen können eine Weiterleitung verarbeiten (achten Sie darauf, dass Sie das Objekt `next` angeben). Beispiel:
-
-
-app.get('/example/b', function (req, res, next) {
- console.log('the response will be sent by the next function ...');
- next();
-}, function (req, res) {
- res.send('Hello from B!');
-});
-
-
+```js
+app.get('/example/b', (req, res, next) => {
+ console.log('the response will be sent by the next function ...')
+ next()
+}, (req, res) => {
+ res.send('Hello from B!')
+})
+```
Ein Array von Callback-Funktionen kann eine Weiterleitung verarbeiten. Beispiel:
-
-
-var cb0 = function (req, res, next) {
- console.log('CB0');
- next();
+```js
+const cb0 = function (req, res, next) {
+ console.log('CB0')
+ next()
}
-var cb1 = function (req, res, next) {
- console.log('CB1');
- next();
+const cb1 = function (req, res, next) {
+ console.log('CB1')
+ next()
}
-var cb2 = function (req, res) {
- res.send('Hello from C!');
+const cb2 = function (req, res) {
+ res.send('Hello from C!')
}
-app.get('/example/c', [cb0, cb1, cb2]);
-
-
+app.get('/example/c', [cb0, cb1, cb2])
+```
Eine Kombination aus unabhängigen Funktionen und Funktionsarrays kann eine Weiterleitung verarbeiten. Beispiel:
-
-
-var cb0 = function (req, res, next) {
- console.log('CB0');
- next();
+```js
+const cb0 = function (req, res, next) {
+ console.log('CB0')
+ next()
}
-var cb1 = function (req, res, next) {
- console.log('CB1');
- next();
+const cb1 = function (req, res, next) {
+ console.log('CB1')
+ next()
}
-app.get('/example/d', [cb0, cb1], function (req, res, next) {
- console.log('the response will be sent by the next function ...');
- next();
-}, function (req, res) {
- res.send('Hello from D!');
-});
-
-
+app.get('/example/d', [cb0, cb1], (req, res, next) => {
+ console.log('the response will be sent by the next function ...')
+ next()
+}, (req, res) => {
+ res.send('Hello from D!')
+})
+```
Antwortmethoden
Über die Methoden für das Antwortobjekt (`res`) in der folgenden Tabelle kann eine Antwort an den Client gesendet und der Anforderung/Antwort-Zyklus beendet werden. Wenn keine dieser Methoden über einen Routenhandler aufgerufen wird, bleibt die Clientanforderung im Status "blockiert". -| Methode | Beschreibung -|----------------------|-------------------------------------- -| [res.download()](/{{ page.lang }}/4x/api.html#res.download) | Gibt eine Eingabeaufforderung zum Herunterladen einer Datei aus. -| [res.end()](/{{ page.lang }}/4x/api.html#res.end) | Beendet den Prozess "Antwort". -| [res.json()](/{{ page.lang }}/4x/api.html#res.json) | Sendet eine JSON-Antwort. -| [res.jsonp()](/{{ page.lang }}/4x/api.html#res.jsonp) | Sendet eine JSON-Antwort mit JSONP-Unterstützung. -| [res.redirect()](/{{ page.lang }}/4x/api.html#res.redirect) | Leitet eine Anforderung um. -| [res.render()](/{{ page.lang }}/4x/api.html#res.render) | Gibt eine Anzeigevorlage aus. -| [res.send()](/{{ page.lang }}/4x/api.html#res.send) | Sendet eine Antwort mit unterschiedlichen Typen. -| [res.sendFile](/{{ page.lang }}/4x/api.html#res.sendFile) | Sendet eine Datei als Oktett-Stream. -| [res.sendStatus()](/{{ page.lang }}/4x/api.html#res.sendStatus) | Legt den Antwortstatuscode fest und sendet dessen Zeichenfolgedarstellung als Antworthauptteil. +| Methode | Beschreibung | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | +| [res.download()](/{{ page.lang }}/4x/api.html#res.download) | Gibt eine Eingabeaufforderung zum Herunterladen einer Datei aus. | +| [res.end()](/{{ page.lang }}/4x/api.html#res.end) | End the response process. | +| [res.json()](/{{ page.lang }}/4x/api.html#res.json) | Sendet eine JSON-Antwort. | +| [res.jsonp()](/{{ page.lang }}/4x/api.html#res.jsonp) | Sendet eine JSON-Antwort mit JSONP-Unterstützung. | +| [res.redirect()](/{{ page.lang }}/4x/api.html#res.redirect) | Leitet eine Anforderung um. | +| [res.render()](/{{ page.lang }}/4x/api.html#res.render) | Render a view template. | +| [res.send()](/{{ page.lang }}/4x/api.html#res.send) | Sendet eine Antwort mit unterschiedlichen Typen. | +| [res.sendFile](/{{ page.lang }}/4x/api.html#res.sendFile) | Sendet eine Datei als Oktett-Stream. | +| [res.sendStatus()](/{{ page.lang }}/4x/api.html#res.sendStatus) | Legt den Antwortstatuscode fest und sendet dessen Zeichenfolgedarstellung als Antworthauptteil. |app.route()
-Sie können mithilfe von `app.route()` verkettbare Routenhandler für einen Weiterleitungspfad erstellen. Da der Pfad an einer einzelnen Position angegeben wird, ist das Erstellen modularer Weiterleitungen hilfreich, da Redundanzen und Schreibfehler reduziert werden. Weitere Informationen zu Weiterleitungen finden Sie in der Dokumentation zu [Router()](/{{ page.lang }}/4x/api.html#router). +Sie können mithilfe von `app.route()` verkettbare Routenhandler für einen Weiterleitungspfad erstellen. +Da der Pfad an einer einzelnen Position angegeben wird, ist das Erstellen modularer Weiterleitungen hilfreich, da Redundanzen und Schreibfehler reduziert werden. Weitere Informationen zu Weiterleitungen finden Sie in der Dokumentation zu [Router()](/{{ page.lang }}/4x/api.html#router). Dies ist ein Beispiel für verkettete Routenhandler, die mit der Funktion `app.route()` definiert werden. -
-
+```js
app.route('/book')
- .get(function(req, res) {
- res.send('Get a random book');
+ .get((req, res) => {
+ res.send('Get a random book')
})
- .post(function(req, res) {
- res.send('Add a book');
+ .post((req, res) => {
+ res.send('Add a book')
})
- .put(function(req, res) {
- res.send('Update the book');
- });
-
-
+ .put((req, res) => {
+ res.send('Update the book')
+ })
+```
express.Router
@@ -293,37 +350,43 @@ Im folgenden Beispiel wird ein Router als Modul erstellt, eine Middlewarefunktio Erstellen Sie eine Routerdatei namens `birds.js` mit dem folgenden Inhalt im Anwendungsverzeichnis: -
-
-var express = require('express');
-var router = express.Router();
+```js
+const express = require('express')
+const router = express.Router()
// middleware that is specific to this router
-router.use(function timeLog(req, res, next) {
- console.log('Time: ', Date.now());
- next();
-});
+const timeLog = (req, res, next) => {
+ console.log('Time: ', Date.now())
+ next()
+}
+router.use(timeLog)
+
// define the home page route
-router.get('/', function(req, res) {
- res.send('Birds home page');
-});
+router.get('/', (req, res) => {
+ res.send('Birds home page')
+})
// define the about route
-router.get('/about', function(req, res) {
- res.send('About birds');
-});
+router.get('/about', (req, res) => {
+ res.send('About birds')
+})
-module.exports = router;
-
-
+module.exports = router
+```
Laden Sie dann das Routermodul in die Anwendung:
-
-
-var birds = require('./birds');
-...
-app.use('/birds', birds);
-
-
+```js
+const birds = require('./birds')
+
+// ...
+
+app.use('/birds', birds)
+```
Die Anwendung kann nun Anforderungen an die Pfade `/birds` und `/birds/about` bearbeiten und ruft die Middlewarefunktion `timeLog` auf, die speziell für diese Weiterleitung bestimmt ist.
+
+But if the parent route `/birds` has path parameters, it will not be accessible by default from the sub-routes. To make it accessible, you will need to pass the `mergeParams` option to the Router constructor [reference](/{{ page.lang }}/5x/api.html#app.use).
+
+```js
+const router = express.Router({ mergeParams: true })
+```
diff --git a/de/guide/using-middleware.md b/de/guide/using-middleware.md
old mode 100755
new mode 100644
index a1eddb6b0a..0d1baea51c
--- a/de/guide/using-middleware.md
+++ b/de/guide/using-middleware.md
@@ -1,183 +1,229 @@
---
layout: page
title: Express-Middleware verwenden
+description: Learn how to use middleware in Express.js applications, including application-level and router-level middleware, error handling, and integrating third-party middleware.
menu: guide
-lang: de
+redirect_from: " "
---
# Middleware verwenden
Express ist ein Weiterleitungs- und Middleware-Web-Framework, das selbst nur minimale Funktionalität aufweist: Eine Express-Anwendung besteht im Wesentlichen aus einer Reihe von Middlewarefunktionsaufrufen.
-*Middlewarefunktionen* sind Funktionen, die Zugriff auf das [Anforderungsobjekt](/{{ page.lang }}/4x/api.html#req) (`req`), das [Antwortobjekt](/{{ page.lang }}/4x/api.html#res) (`res`) und die nächste Middlewarefunktion im Anforderung/Antwort-Zyklus der Anwendung haben. Die nächste Middlewarefunktion wird im Allgemeinen durch die Variable `next` bezeichnet.
+_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the next middleware function in the application's request-response cycle. Die nächste Middlewarefunktion wird im Allgemeinen durch die Variable `next` bezeichnet.
Über Middlewarefunktionen lassen sich die folgenden Tasks ausführen:
-* Ausführen von Code
-* Vornehmen von Änderungen an der Anforderung und an Antwortobjekten
-* Beenden des Anforderung/Antwort-Zyklus
-* Aufrufen der nächsten Middlewarefunktion im Stack
+- Ausführen von Code
+- Vornehmen von Änderungen an der Anforderung und an Antwortobjekten
+- End the request-response cycle.
+- Aufrufen der nächsten Middlewarefunktion im Stack
Wenn über die aktuelle Middlewarefunktion der Anforderung/Antwort-Zyklus nicht beendet werden kann, muss `next()` aufgerufen werden, um die Steuerung an die nächste Middlewarefunktion zu übergeben. Andernfalls geht die Anforderung in den Status "Blockiert" über.
Eine Express-Anwendung kann die folgenden Middlewaretypen verwenden:
- - [Middleware auf Anwendungsebene](#middleware.application)
- - [Middleware auf Routerebene](#middleware.router)
- - [Middleware für die Fehlerbehandlung](#middleware.error-handling)
- - [Integrierte Middleware](#middleware.built-in)
- - [Middleware anderer Anbieter](#middleware.third-party)
+- [Middleware auf Anwendungsebene](#middleware.application)
+- [Middleware auf Routerebene](#middleware.router)
+- [Middleware für die Fehlerbehandlung](#middleware.error-handling)
+- [Integrierte Middleware](#middleware.built-in)
+- [Middleware anderer Anbieter](#middleware.third-party)
-Sie können Middleware auf Anwendungsebene und Routerebene mit einem optionalen Mountpfad laden. Sie können auch eine Reihe von Middlewarefunktionen zusammen laden. Dadurch wird ein Sub-Stack des Middlewaresystems am Mountpunkt erstellt.
+Sie können Middleware auf Anwendungsebene und Routerebene mit einem optionalen Mountpfad laden.
+Sie können auch eine Reihe von Middlewarefunktionen zusammen laden. Dadurch wird ein Sub-Stack des Middlewaresystems am Mountpunkt erstellt.
Middleware auf Anwendungsebene
-Binden Sie Middleware auf Anwendungsebene zu einer Instanz des [Anwendungsobjekts](/{{ page.lang }}/4x/api.html#app), indem Sie die Funktionen `app.use()` und `app.METHOD()` verwenden. `METHOD` ist dabei die HTTP-Methode der Anforderung, die die Middlewarefunktion in Kleinschreibung verarbeitet (wie GET, PU oder POST). +Bind application-level middleware to an instance of the [app object](/{{ page.lang }}/5x/api.html#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase. Dieses Beispiel zeigt eine Middlewarefunktion ohne Mountpfad. Die Funktion wird immer dann ausgeführt, wenn die Anwendung eine Anforderung erhält. -
-
-var app = express();
+```js
+const express = require('express')
+const app = express()
-app.use(function (req, res, next) {
- console.log('Time:', Date.now());
- next();
-});
-
-
+app.use((req, res, next) => {
+ console.log('Time:', Date.now())
+ next()
+})
+```
Dieses Beispiel zeigt eine Middlewarefunktion mit dem Mountpfad `/user/:id`. Die Funktion wird für jede Art von HTTP-Anforderung auf dem Pfad `/user/:id` ausgeführt.
-
-
-app.use('/user/:id', function (req, res, next) {
- console.log('Request Type:', req.method);
- next();
-});
-
-
+```js
+app.use('/user/:id', (req, res, next) => {
+ console.log('Request Type:', req.method)
+ next()
+})
+```
Dieses Beispiel zeigt eine Weiterleitung und deren Handlerfunktion (Middlewaresystem). Die Funktion verarbeitet GET-Anforderungen zum Pfad `/user/:id`.
-
-
-app.get('/user/:id', function (req, res, next) {
- res.send('USER');
-});
-
-
-
-Dies ist ein Beispiel zum Laden einer Reihe von Middlewarefunktionen an einem Mountpunkt mit einem Mountpfad. Das Beispiel veranschaulicht einen Middleware-Stack, über den Anforderungsinformationen zu einer HTTP-Anforderung zum Pfad `/user/:id` ausgegeben werden.
-
-
-
-app.use('/user/:id', function(req, res, next) {
- console.log('Request URL:', req.originalUrl);
- next();
-}, function (req, res, next) {
- console.log('Request Type:', req.method);
- next();
-});
-
-
+```js
+app.get('/user/:id', (req, res, next) => {
+ res.send('USER')
+})
+```
+
+Dies ist ein Beispiel zum Laden einer Reihe von Middlewarefunktionen an einem Mountpunkt mit einem Mountpfad.
+Das Beispiel veranschaulicht einen Middleware-Stack, über den Anforderungsinformationen zu einer HTTP-Anforderung zum Pfad `/user/:id` ausgegeben werden.
+
+```js
+app.use('/user/:id', (req, res, next) => {
+ console.log('Request URL:', req.originalUrl)
+ next()
+}, (req, res, next) => {
+ console.log('Request Type:', req.method)
+ next()
+})
+```
Mit einem Routenhandler können Sie mehrere Weiterleitungen für einen Pfad definieren. Im folgenden Beispiel werden zwei Weiterleitungen für GET-Anforderungen zum Pfad `/user/:id` definiert. Die zweite Weiterleitung verursacht zwar keine Probleme, wird jedoch nie aufgerufen, da durch die erste Weiterleitung der Anforderung/Antwort-Zyklus beendet wird.
Dieses Beispiel zeigt einen Middleware-Sub-Stack, über den GET-Anforderungen zum Pfad `/user/:id` verarbeitet werden.
-
-
-app.get('/user/:id', function (req, res, next) {
- console.log('ID:', req.params.id);
- next();
-}, function (req, res, next) {
- res.send('User Info');
-});
+```js
+app.get('/user/:id', (req, res, next) => {
+ console.log('ID:', req.params.id)
+ next()
+}, (req, res, next) => {
+ res.send('User Info')
+})
// handler for the /user/:id path, which prints the user ID
-app.get('/user/:id', function (req, res, next) {
- res.end(req.params.id);
-});
-
-
+app.get('/user/:id', (req, res, next) => {
+ res.send(req.params.id)
+})
+```
-Wenn Sie den Rest der Middlewarefunktionen eines Weiterleitungs-Middleware-Stack überspringen wollen, rufen Sie `next('route')` auf, um die Steuerung an die nächste Weiterleitung zu übergeben. **HINWEIS**: `next('route')` funktioniert nur in Middlewarefunktionen, die über die Funktionen `app.METHOD()` oder `router.METHOD()` geladen wurden.
+Wenn Sie den Rest der Middlewarefunktionen eines Weiterleitungs-Middleware-Stack überspringen wollen, rufen Sie `next('route')` auf, um die Steuerung an die nächste Weiterleitung zu übergeben.
+
+{% capture next-function %}
+
+`next('route')` will work only in middleware functions that were loaded by using the `app.METHOD()` or `router.METHOD()` functions.
+
+{% endcapture %}
+
+{% include admonitions/note.html content=next-function %}
Dieses Beispiel zeigt einen Middleware-Sub-Stack, über den GET-Anforderungen zum Pfad `/user/:id` verarbeitet werden.
-
-
-app.get('/user/:id', function (req, res, next) {
+```js
+app.get('/user/:id', (req, res, next) => {
// if the user ID is 0, skip to the next route
- if (req.params.id == 0) next('route');
+ if (req.params.id === '0') next('route')
// otherwise pass the control to the next middleware function in this stack
- else next(); //
-}, function (req, res, next) {
- // render a regular page
- res.render('regular');
-});
+ else next()
+}, (req, res, next) => {
+ // send a regular response
+ res.send('regular')
+})
-// handler for the /user/:id path, which renders a special page
-app.get('/user/:id', function (req, res, next) {
- res.render('special');
-});
-
-
+// handler for the /user/:id path, which sends a special response
+app.get('/user/:id', (req, res, next) => {
+ res.send('special')
+})
+```
+
+Middleware can also be declared in an array for reusability.
+
+Dies ist ein Beispiel zur Verwendung der Middlewarefunktion `express.static` mit einem ausführlich dargestellten Optionsobjekt:
+
+```js
+function logOriginalUrl (req, res, next) {
+ console.log('Request URL:', req.originalUrl)
+ next()
+}
+
+function logMethod (req, res, next) {
+ console.log('Request Type:', req.method)
+ next()
+}
+
+const logStuff = [logOriginalUrl, logMethod]
+app.get('/user/:id', logStuff, (req, res, next) => {
+ res.send('User Info')
+})
+```
Middleware auf Routerebene
Middleware auf Routerebene funktioniert in der gleichen Weise wie Middleware auf Anwendungsebene, mit dem einzigen Unterschied, dass sie an eine Instanz von `express.Router()` gebunden ist. -
-
-var router = express.Router();
-
-
+```js
+const router = express.Router()
+```
+
Laden Sie Middleware auf Routerebene über die Funktionen `router.use()` und `router.METHOD()`.
+
Der folgende Beispielcode repliziert das Middlewaresystem, das oben für die Middleware auf Anwendungsebene gezeigt wird, durch Verwendung von Middleware auf Routerebene.
-
-
-var app = express();
-var router = express.Router();
+```js
+const express = require('express')
+const app = express()
+const router = express.Router()
// a middleware function with no mount path. This code is executed for every request to the router
-router.use(function (req, res, next) {
- console.log('Time:', Date.now());
- next();
-});
+router.use((req, res, next) => {
+ console.log('Time:', Date.now())
+ next()
+})
// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
-router.use('/user/:id', function(req, res, next) {
- console.log('Request URL:', req.originalUrl);
- next();
-}, function (req, res, next) {
- console.log('Request Type:', req.method);
- next();
-});
+router.use('/user/:id', (req, res, next) => {
+ console.log('Request URL:', req.originalUrl)
+ next()
+}, (req, res, next) => {
+ console.log('Request Type:', req.method)
+ next()
+})
// a middleware sub-stack that handles GET requests to the /user/:id path
-router.get('/user/:id', function (req, res, next) {
+router.get('/user/:id', (req, res, next) => {
// if the user ID is 0, skip to the next router
- if (req.params.id == 0) next('route');
+ if (req.params.id === '0') next('route')
// otherwise pass control to the next middleware function in this stack
- else next(); //
-}, function (req, res, next) {
+ else next()
+}, (req, res, next) => {
// render a regular page
- res.render('regular');
-});
+ res.render('regular')
+})
// handler for the /user/:id path, which renders a special page
-router.get('/user/:id', function (req, res, next) {
- console.log(req.params.id);
- res.render('special');
-});
+router.get('/user/:id', (req, res, next) => {
+ console.log(req.params.id)
+ res.render('special')
+})
// mount the router on the app
-app.use('/', router);
-
-
+app.use('/', router)
+```
+
+To skip the rest of the router's middleware functions, call `next('router')`
+to pass control back out of the router instance.
+
+Dieses Beispiel zeigt einen Middleware-Sub-Stack, über den GET-Anforderungen zum Pfad `/user/:id` verarbeitet werden.
+
+```js
+const express = require('express')
+const app = express()
+const router = express.Router()
+
+// predicate the router with a check and bail out when needed
+router.use((req, res, next) => {
+ if (!req.headers['x-auth']) return next('router')
+ next()
+})
+
+router.get('/user/:id', (req, res) => {
+ res.send('hello, user!')
+})
+
+// use the router and 401 anything falling through
+app.use('/admin', router, (req, res) => {
+ res.sendStatus(401)
+})
+```
Middleware für die Fehlerbehandlung
@@ -187,14 +233,12 @@ Middleware für die Fehlerbehandlung benötigt immer *vier* Argumente. Sie müss Middlewarefunktionen für die Fehlerbehandlung werden in derselben Weise definiert wie andere Middlewarefunktionen, außer dass Fehlerbehandlungsfunktionen speziell bei Signaturen vier anstatt drei Argumente aufweisen `(err, req, res, next)`: -
-
-app.use(function(err, req, res, next) {
- console.error(err.stack);
- res.status(500).send('Something broke!');
-});
-
-
+```js
+app.use((err, req, res, next) => {
+ console.error(err.stack)
+ res.status(500).send('Something broke!')
+})
+```
Details zu Middleware für die Fehlerbehandlung siehe [Fehlerbehandlung](/{{ page.lang }}/guide/error-handling.html).
@@ -202,56 +246,11 @@ Details zu Middleware für die Fehlerbehandlung siehe [Fehlerbehandlung](/{{ pag
Seit Version 4.x bestehen bei Express keine Abhängigkeiten zu [Connect](https://github.com/senchalabs/connect) mehr. Mit Ausnahme von `express.static` befinden sich nun alle Middlewarefunktionen, die bisher in Express enthalten waren, in separaten Modulen. Sehen Sie sich hierzu auch die [Liste der Middlewarefunktionen](https://github.com/senchalabs/connect#middleware) an.
-express.static(root, [options])
- -Die einzige integrierte Middlewarefunktion in Express ist `express.static`. Diese Funktion basiert auf [serve-static](https://github.com/expressjs/serve-static) und ist zuständig für die statischen Assets einer Express-Anwendung. - -Das Argument `root` gibt das Stammverzeichnis an, von dem aus statische Assets bedient werden. - -Das optionale Objekt `options` kann folgende Eigenschaften aufweisen: - -| Eigenschaft | Beschreibung | Typ | Standard | -|---------------|-----------------------------------------------------------------------|-------------|-----------------| -| `dotfiles` | Option für Dateien mit Punkterweiterung (dotfiles). Mögliche Werte sind "allow", "deny" und "ignore" | Zeichenfolge | "ignore" | -| `etag` | Aktiviert oder inaktiviert die etag-Generierung. | Boolesch | `true` | -| `extensions` | Legt Dateierweiterungs-Fallbacks fest. | Bereich | `[]` | -| `index` | Sendet die verzeichnissspezifische indexierte Datei. Bei `false` wird die Verzeichnisindexierung inaktiviert. | Gemischt | "index.html" | - `lastModified` | Legt den Header `Last-Modified` auf das Datum der letzten Änderung der Datei im Betriebssystem fest. Mögliche Werte sind`true` und `false`. | Boolesch | `true` | -| `maxAge` | Legt die Eigenschaft "max-age" des Headers "Cache-Control" in Millisekunden oder als Zeichenfolge im [ms-Format](https://www.npmjs.org/package/ms) fest. | Zahl | 0 | -| `redirect` | Umleitung zu einem abschließenden "/", wenn der Pfadname ein Verzeichnis ist. | Boolesch | `true` | -| `setHeaders` | Funktion zum Festlegen von HTTP-Headern für die Datei. | Funktion | | - -Dies ist ein Beispiel zur Verwendung der Middlewarefunktion `express.static` mit einem ausführlich dargestellten Optionsobjekt: - -
-
-var options = {
- dotfiles: 'ignore',
- etag: false,
- extensions: ['htm', 'html'],
- index: false,
- maxAge: '1d',
- redirect: false,
- setHeaders: function (res, path, stat) {
- res.set('x-timestamp', Date.now());
- }
-}
-
-app.use(express.static('public', options));
-
-
-
-Es sind mehrere statische Verzeichnisse pro Anwendung möglich:
-
-
-
-app.use(express.static('public'));
-app.use(express.static('uploads'));
-app.use(express.static('files'));
-
-
+Die einzige integrierte Middlewarefunktion in Express ist `express.static`.
-Details zur Funktion `serve-static` und deren Optionen finden Sie in der Dokumentation zu [serve-static](https://github.com/expressjs/serve-static).
+- [express.static](/en/5x/api.html#express.static) serves static assets such as HTML files, images, and so on.
+- [express.json](/en/5x/api.html#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
+- [express.urlencoded](/en/5x/api.html#express.urlencoded) parses incoming requests with URL-encoded payloads. **NOTE: Available with Express 4.16.0+**
Middleware anderer Anbieter
@@ -261,21 +260,17 @@ Installieren Sie das Modul Node.js für die erforderliche Funktionalität. Laden Das folgende Beispiel veranschaulicht das Installieren und Laden der Middlewarefunktion `cookie-parser` für das Cookie-Parsing. -
-
+```bash
$ npm install cookie-parser
-
-
+```
-
-
-var express = require('express');
-var app = express();
-var cookieParser = require('cookie-parser');
+```js
+const express = require('express')
+const app = express()
+const cookieParser = require('cookie-parser')
// load the cookie-parsing middleware
-app.use(cookieParser());
-
-
+app.use(cookieParser())
+```
Eine nicht vollständige Liste zu den Middlewarefunktionen anderer Anbieter, die im Allgemeinen mit Express verwendet werden, finden Sie unter [Middleware anderer Anbieter](../resources/middleware.html).
diff --git a/de/guide/using-template-engines.md b/de/guide/using-template-engines.md
old mode 100755
new mode 100644
index 5850860b81..abce1f7ffd
--- a/de/guide/using-template-engines.md
+++ b/de/guide/using-template-engines.md
@@ -1,59 +1,61 @@
---
layout: page
title: Template-Engines in Express verwenden
+description: Discover how to integrate and use template engines like Pug, Handlebars, and EJS with Express.js to render dynamic HTML pages efficiently.
menu: guide
-lang: de
+redirect_from: " "
---
# Template-Engines in Express verwenden
-Bevor über Express Vorlagendateien ausgegeben werden können, müssen die folgenden Anwendungseinstellungen festgelegt werden:
+A _template engine_ enables you to use static template files in your application. At runtime, the template engine replaces
+variables in a template file with actual values, and transforms the template into an HTML file sent to the client.
+This approach makes it easier to design an HTML page.
-* `views`, das Verzeichnis, in dem sich die Vorlagendateien befinden. Beispiel: `app.set('views', './views')`
-* `view engine`, die zu verwendende Template-Engine. Beispiel: `app.set('view engine', 'pug')`
+The [Express application generator](/{{ page.lang }}/starter/generator.html) uses [Pug](https://pugjs.org/api/getting-started.html) as its default, but it also supports [Handlebars](https://www.npmjs.com/package/handlebars), and [EJS](https://www.npmjs.com/package/ejs), among others.
+
+To render template files, set the following [application setting properties](/{{ page.lang }}/4x/api.html#app.set), in the default `app.js` created by the generator:
+
+- `views`, das Verzeichnis, in dem sich die Vorlagendateien befinden. Beispiel: `app.set('views', './views')`
+ This defaults to the `views` directory in the application root directory.
+- `view engine`, die zu verwendende Template-Engine. Beispiel: `app.set('view engine', 'pug')`
Installieren Sie dann das entsprechende npm-Paket für die Template-Engine:
-
-
+```bash
$ npm install pug --save
-
-
+```
+
+Express-konforme Template-Engines wie Pug exportieren eine Funktion namens `__express(filePath, options, callback)`, die über die Funktion `res.render()` aufgerufen wird, um den Vorlagencode ausgeben zu können.
+
+Einige Template-Engines folgen dieser Konvention nicht. Die Bibliothek [Consolidate.js](https://www.npmjs.org/package/consolidate) folgt dieser Konvention, indem alle gängigen Node.js-Template-Engines zugeordnet werden. Daher ist eine reibungslose Funktion in Express gewährleistet.
-
-
-Express-konforme Template-Engines wie Pug exportieren eine Funktion namens `__express(filePath, options, callback)`, die über die Funktion `res.render()` aufgerufen wird, um den Vorlagencode ausgeben zu können. Einige Template-Engines folgen dieser Konvention nicht. Die Bibliothek [Consolidate.js](https://www.npmjs.org/package/consolidate) folgt dieser Konvention, indem alle gängigen Node.js-Template-Engines zugeordnet werden. Daher ist eine reibungslose Funktion in Express gewährleistet.
Nach der Festlegung der View-Engine muss die Engine nicht angegeben oder das Template-Engine-Modul nicht in Ihre Anwendung geladen werden. Express lädt das Modul intern (wie unten für das obige Beispiel gezeigt).
-
-
-app.set('view engine', 'pug');
-
-
+```js
+app.set('view engine', 'pug')
+```
Erstellen Sie eine Pug-Vorlagendatei namens `index.pug` im Verzeichnis `views` mit dem folgenden Inhalt:
-
-
+```pug
html
head
title= title
body
h1= message
-
-
+```
Dann erstellen Sie eine Weiterleitung, um die Datei `index.pug` auszugeben. Wenn die Eigenschaft `view engine` nicht festgelegt wurde, müssen Sie die Erweiterung der Datei `view` angeben. Andernfalls müssen Sie diese Erweiterung nicht angeben.
-
-
-app.get('/', function (req, res) {
- res.render('index', { title: 'Hey', message: 'Hello there!'});
-});
-
-
+```js
+app.get('/', (req, res) => {
+ res.render('index', { title: 'Hey', message: 'Hello there!' })
+})
+```
Wenn Sie eine Anforderung zur Homepage ausführen, wird die Datei `index.pug` im HTML-Format ausgegeben.
-Weitere Informationen zur Funktionsweise von Template-Engines in Express siehe ["Template-Engines für Express entwickeln"](/{{ page.lang }}/advanced/developing-template-engines.html).
+The view engine cache does not cache the contents of the template's output, only the underlying template itself. The view is still re-rendered with every request even when the cache is on.
diff --git a/de/guide/writing-middleware.md b/de/guide/writing-middleware.md
old mode 100755
new mode 100644
index 283fbeaac8..c4d5653244
--- a/de/guide/writing-middleware.md
+++ b/de/guide/writing-middleware.md
@@ -1,33 +1,35 @@
---
layout: page
title: Middleware für die Verwendung in Express-Anwendungen schreiben
+description: Learn how to write custom middleware functions for Express.js applications, including examples and best practices for enhancing request and response handling.
menu: guide
-lang: de
+redirect_from: " "
---
# Middleware für die Verwendung in Express-Anwendungen schreiben
Überblick
-*Middlewarefunktionen* sind Funktionen, die Zugriff auf das [Anforderungsobjekt](/{{ page.lang }}/4x/api.html#req) (`req`), das [Antwortobjekt](/{{ page.lang }}/4x/api.html#res) (`res`) und die nächste Middlewarefunktion im Anforderung/Antwort-Zyklus der Anwendung haben. Die nächste Middlewarefunktion wird im Allgemeinen durch die Variable `next` bezeichnet. +_Middlewarefunktionen_ sind Funktionen, die Zugriff auf das [Anforderungsobjekt](/{{ page.lang }}/4x/api.html#req) (`req`), das [Antwortobjekt](/{{ page.lang }}/4x/api.html#res) (`res`) und die nächste Middlewarefunktion im Anforderung/Antwort-Zyklus der Anwendung haben. Die nächste Middlewarefunktion wird im Allgemeinen durch die Variable `next` bezeichnet. Über Middlewarefunktionen lassen sich die folgenden Tasks ausführen: -* Ausführen von Code -* Vornehmen von Änderungen an der Anforderung und an Antwortobjekten -* Beenden des Anforderung/Antwort-Zyklus -* Aufrufen der nächsten Middleware im Stack +- Ausführen von Code +- Vornehmen von Änderungen an der Anforderung und an Antwortobjekten +- End the request-response cycle. +- Aufrufen der nächsten Middleware im Stack Wenn über die aktuelle Middlewarefunktion der Anforderung/Antwort-Zyklus nicht beendet werden kann, muss `next()` aufgerufen werden, um die Steuerung an die nächste Middlewarefunktion zu übergeben. Andernfalls geht die Anforderung in den Status "Blockiert" über. Das folgende Beispiel zeigt die Elemente eines Middlewarefunktionsaufrufs: -|
-
+
+
+
+Starting with Express 5, middleware functions that return a Promise will call `next(value)` when they reject or throw an error. `next` will be called with either the rejected value or the thrown Error.
-Dies ist ein Beispiel einer einfachen Express-Anwendung namens "Hello World", für die Sie zwei Middlewarefunktionen definieren:
+
Beispiel-Entwicklung+app.listen(3000) +``` +Dies ist ein Beispiel einer einfachen Express-Anwendung namens "Hello World", für die Sie zwei Middlewarefunktionen definieren:Dies ist ein einfaches Beispiel einer Middlewarefunktion namens "myLogger". Diese Funktion gibt lediglich "LOGGED" aus, wenn eine Anforderung zur Anwendung über diese Funktion läuft. Die Middlewarefunktion ist der Variablen `myLogger` zugeordnet. -
-
+```js
+const myLogger = function (req, res, next) {
+ console.log('LOGGED')
+ next()
+}
+```
-Beachten Sie den Aufruf oben zu `next()`. Durch den Aufruf dieser Funktion wird die nächste Middlewarefunktion in der Anwendung aufgerufen. Die Funktion `next()` ist nicht Teil der Node.js- oder Express-API, sondern das dritte Argument, das an die Middlewarefunktion übergeben wird. Die Funktion `next()` kann jeden beliebigen Namen haben, per Konvention erhält sie jedoch immer den Namen "next". Um Unklarheiten zu vermeiden, sollten Sie immer diese Konvention verwenden.
+Beachten Sie den Aufruf oben zu `next()`. Durch den Aufruf dieser Funktion wird die nächste Middlewarefunktion in der Anwendung aufgerufen.
+Die Funktion `next()` ist nicht Teil der Node.js- oder Express-API, sondern das dritte Argument, das an die Middlewarefunktion übergeben wird. Die Funktion `next()` kann jeden beliebigen Namen haben, per Konvention erhält sie jedoch immer den Namen "next".
+Um Unklarheiten zu vermeiden, sollten Sie immer diese Konvention verwenden.
+Zum Laden der Middlewarefunktion rufen Sie `app.use()` auf und geben die Middlewarefunktion an.
+Beispiel: Durch den folgenden Code wird die Middlewarefunktion `myLogger` vor der Weiterleitung zum Stammverzeichnispfad (/) geladen.
-Zum Laden der Middlewarefunktion rufen Sie `app.use()` auf und geben die Middlewarefunktion an. Beispiel: Durch den folgenden Code wird die Middlewarefunktion `myLogger` vor der Weiterleitung zum Stammverzeichnispfad (/) geladen.
+```js
+const express = require('express')
+const app = express()
-
-
+app.listen(3000)
+```
Sobald die Anwendung eine Anforderung erhält, gibt sie die Nachricht "LOGGED" an das Terminal aus.
@@ -102,43 +109,112 @@ Wenn `myLogger` nach der Weiterleitung zum Stammverzeichnispfad geladen wird, er
Die Middlewarefunktion `myLogger` gibt einfach eine Nachricht aus und übergibt dann die Anforderung zur nächsten Middlewarefunktion im Stack durch Aufruf der Funktion `next()`.
+Middleware function requestTime+ Im nächsten Beispiel wird die Eigenschaft `requestTime` zum Anforderungsobjekt hinzugefügt. Diese Middlewarefunktion erhält den Namen "requestTime". -
-
+```js
+const requestTime = function (req, res, next) {
+ req.requestTime = Date.now()
+ next()
+}
+```
Die Anwendung verwendet nun die Middlewarefunktion `requestTime`. Außerdem verwendet die Callback-Funktion der Weiterleitung zum Stammverzeichnispfad die Eigenschaft, die die Middlewarefunktion zu `req` (dem Anforderungsobjekt) hinzufügt.
-
-
+app.listen(3000)
+```
Wenn Sie eine Anforderung zum Stammverzeichnis der Anwendung einleiten, zeigt die Anwendung nun die Zeitmarke Ihrer Anforderung im Browser an.
+Middleware function validateCookies+ +Finally, we'll create a middleware function that validates incoming cookies and sends a 400 response if cookies are invalid. + +Here's an example function that validates cookies with an external async service. + +```js +async function cookieValidator (cookies) { + try { + await externallyValidateCookie(cookies.testCookie) + } catch { + throw new Error('Invalid cookies') + } +} +``` + +Here, we use the [`cookie-parser`](/resources/middleware/cookie-parser.html) middleware to parse incoming cookies off the `req` object and pass them to our `cookieValidator` function. The `validateCookies` middleware returns a Promise that upon rejection will automatically trigger our error handler. + +```js +const express = require('express') +const cookieParser = require('cookie-parser') +const cookieValidator = require('./cookieValidator') + +const app = express() + +async function validateCookies (req, res, next) { + await cookieValidator(req.cookies) + next() +} + +app.use(cookieParser()) + +app.use(validateCookies) + +// error handler +app.use((err, req, res, next) => { + res.status(400).send(err.message) +}) + +app.listen(3000) +``` + +
+Note how `next()` is called after `await cookieValidator(req.cookies)`. This ensures that if `cookieValidator` resolves, the next middleware in the stack will get called. If you pass anything to the `next()` function (except the string `'route'` or `'router'`), Express regards the current request as being an error and will skip any remaining non-error handling routing and middleware functions.
+
+
Da Sie Zugriff auf das Anforderungsobjekt, das Antwortobjekt, die nächste Middlewarefunktion im Stack und die gesamte Node.js-API haben, sind die Möglichkeiten, die Sie mit Middlewarefunktionen haben, nahezu unendlich.
Weitere Informationen zur Verwendung von Middleware in Express siehe [ Express-Middleware verwenden](/{{ page.lang }}/guide/using-middleware.html).
+
+Configurable middleware+ +If you need your middleware to be configurable, export a function which accepts an options object or other parameters, which, then returns the middleware implementation based on the input parameters. + +File: `my-middleware.js` + +```js +module.exports = function (options) { + return function (req, res, next) { + // Implement the middleware function based on the options object + next() + } +} +``` + +The middleware can now be used as shown below. + +```js +const mw = require('./my-middleware.js') + +app.use(mw({ option1: '1', option2: '2' })) +``` + +Refer to [cookie-session](https://github.com/expressjs/cookie-session) and [compression](https://github.com/expressjs/compression) for examples of configurable middleware. diff --git a/de/index.md b/de/index.md index a52f08bb5b..ffacc291f9 100644 --- a/de/index.md +++ b/de/index.md @@ -1,50 +1,61 @@ --- layout: home -title: Express - Node.js-Framework von Webanwendungen +title: Express - Node.js Web Application Framework +description: "Express is a fast, unopinionated, minimalist web framework for Node.js, providing a robust set of features for web and mobile applications." menu: home -lang: de +redirect_from: " " --- +
+ Fast, unopinionated, minimalist web framework for Node.js$ npm install express --save
-
-
+
-
-
+
-
-
-
-
-
- WebanwendungenExpress ist ein einfaches und flexibles Node.js-Framework von Webanwendungen, das zahlreiche leistungsfähige Features und Funktionen für Webanwendungen und mobile Anwendungen bereitstellt. -
-
+app.get('/', (req, res) => {
+ res.send('Hello World!')
+})
- APIsMithilfe unzähliger HTTP-Dienstprogrammmethoden und Middlewarefunktionen gestaltet sich das Erstellen einer leistungsfähigen API schnell und einfach.
-
+app.listen(port, () => {
+ console.log(`Example app listening on port ${port}`)
+})
+```
-
LeistungExpress bietet eine Thin-Layer-Ebene mit grundlegenden Webanwendungsfunktionen, ohne die bekannten Node.js-Features zu überlagern.
+
+
+
-Erstellen Sie zunächst ein Verzeichnis namens `myapp`, wechseln Sie in das Verzeichnis und führen Sie `npm init` aus. Installieren Sie dann `express` als Abhängigkeit, wie im [Installationshandbuch](/{{ page.lang }}/starter/installing.html) beschrieben.
-
-Erstellen Sie im Verzeichnis `myapp` eine Datei namens `app.js` und fügen Sie den folgenden Code hinzu:
-
-
+
\ No newline at end of file
diff --git a/de/resources/contributing.md b/de/resources/contributing.md
new file mode 100644
index 0000000000..e37cee3122
--- /dev/null
+++ b/de/resources/contributing.md
@@ -0,0 +1,466 @@
+---
+layout: page
+title: Contributing to Express
+description: Find out how to contribute to Express.js, including guidelines for reporting issues, submitting pull requests, becoming a collaborator, and understanding security policies.
+menu: resources
+redirect_from: " "
+---
+
+# Contributing to Express
+
+### Looking to contribute to Expressjs.com? Click [here](#expressjs-website-contributing).
+
+Express and the other projects in the [expressjs organization on GitHub](https://github.com/expressjs) are projects of the [OpenJs Foundation](https://openjsf.org/).
+These projects are governed under the general policies and guidelines of the Node.js Foundation along with the additional guidelines below.
+
+- [Technical committee](#technical-committee)
+- [Community contributing guide](#community-contributing-guide)
+- [Collaborator's guide](#collaborators-guide)
+- [Security policies and procedures](#security-policies-and-procedures)
+
+## Technical committee
+
+The Express technical committee consists of active project members, and guides development and maintenance of the Express project. For more information, see [Express Community - Technical committee](community.html#technical-committee).
+
+## Community contributing guide
+
+
+
+The goal of this document is to create a contribution process that:
+
+- Encourages new contributions.
+- Encourages contributors to remain involved.
+- Avoids unnecessary processes and bureaucracy whenever possible.
+- Creates a transparent decision making process that makes it clear how
+ contributors can be involved in decision making.
+
+### Vocabulary
+
+- A **Contributor** is any individual creating or commenting on an issue or pull request.
+- A **Committer** is a subset of contributors who have been given write access to the repository.
+- A **Project Captain** is the lead maintainer of a repository.
+- A **TC (Technical Committee)** is a group of committers representing the required technical
+ expertise to resolve rare disputes.
+- A **Triager** is a subset of contributors who have been given triage access to the repository.
+
+### Logging Issues
+
+Log an issue for any question or problem you might have. When in doubt, log an issue, and
+any additional policies about what to include will be provided in the responses. The only
+exception is security disclosures which should be sent privately.
+
+Committers may direct you to another repository, ask for additional clarifications, and
+add appropriate metadata before the issue is addressed.
+
+Please be courteous and respectful. Every participant is expected to follow the
+project's Code of Conduct.
+
+### Contributions
+
+Any change to resources in this repository must be through pull requests. This applies to all changes
+to documentation, code, binary files, etc. Even long term committers and TC members must use
+pull requests.
+
+No pull request can be merged without being reviewed.
+
+For non-trivial contributions, pull requests should sit for at least 36 hours to ensure that
+contributors in other timezones have time to review. Consideration should also be given to
+weekends and other holiday periods to ensure active committers all have reasonable time to
+become involved in the discussion and review process if they wish.
+
+The default for each contribution is that it is accepted once no committer has an objection.
+During a review, committers may also request that a specific contributor who is most versed in a
+particular area gives a "LGTM" before the PR can be merged. There is no additional "sign off"
+process for contributions to land. Once all issues brought by committers are addressed it can
+be landed by any committer.
+
+In the case of an objection being raised in a pull request by another committer, all involved
+committers should seek to arrive at a consensus by way of addressing concerns being expressed
+by discussion, compromise on the proposed change, or withdrawal of the proposed change.
+
+If a contribution is controversial and committers cannot agree about how to get it to land
+or if it should land then it should be escalated to the TC. TC members should regularly
+discuss pending contributions in order to find a resolution. It is expected that only a
+small minority of issues be brought to the TC for resolution and that discussion and
+compromise among committers be the default resolution mechanism.
+
+### Becoming a Triager
+
+Anyone can become a triager! Read more about the process of being a triager in
+[the triage process document](https://github.com/expressjs/discussions/blob/master/docs/contributing/triager-guide.md).
+
+Currently, any existing [organization member](https://github.com/orgs/expressjs/people) can nominate
+a new triager. If you are interested in becoming a triager, our best advice is to actively participate
+in the community by helping triaging issues and pull requests. As well we recommend
+to engage in other community activities like attending the TC meetings, and participating in the Slack
+discussions. If you feel ready and have been helping triage some issues, reach out to an active member of the organization to ask if they'd
+be willing to support you. If they agree, they can create a pull request to formalize your nomination. In the case of an objection to the nomination, the triage team is responsible for working with the individuals involved and finding a resolution.
+
+You can also reach out to any of the [organization members](https://github.com/orgs/expressjs/people)
+if you have questions or need guidance.
+
+### Becoming a Committer
+
+All contributors who have landed significant and valuable contributions should be onboarded in a timely manner,
+and added as a committer, and be given write access to the repository.
+
+Committers are expected to follow this policy and continue to send pull requests, go through
+proper review, and have other committers merge their pull requests.
+
+### TC Process
+
+The TC uses a "consensus seeking" process for issues that are escalated to the TC.
+The group tries to find a resolution that has no open objections among TC members.
+If a consensus cannot be reached that has no objections then a majority wins vote
+is called. It is also expected that the majority of decisions made by the TC are via
+a consensus seeking process and that voting is only used as a last-resort.
+
+Resolution may involve returning the issue to project captains with suggestions on
+how to move forward towards a consensus. It is not expected that a meeting of the TC
+will resolve all issues on its agenda during that meeting and may prefer to continue
+the discussion happening among the project captains.
+
+Members can be added to the TC at any time. Any TC member can nominate another committer
+to the TC and the TC uses its standard consensus seeking process to evaluate whether or
+not to add this new member. The TC will consist of a minimum of 3 active members and a
+maximum of 10. If the TC should drop below 5 members the active TC members should nominate
+someone new. If a TC member is stepping down, they are encouraged (but not required) to
+nominate someone to take their place.
+
+TC members will be added as admin's on the Github orgs, npm orgs, and other resources as
+necessary to be effective in the role.
+
+To remain "active" a TC member should have participation within the last 12 months and miss
+no more than six consecutive TC meetings. Our goal is to increase participation, not punish
+people for any lack of participation, this guideline should be only be used as such
+(replace an inactive member with a new active one, for example). Members who do not meet this
+are expected to step down. If A TC member does not step down, an issue can be opened in the
+discussions repo to move them to inactive status. TC members who step down or are removed due
+to inactivity will be moved into inactive status.
+
+Inactive status members can become active members by self nomination if the TC is not already
+larger than the maximum of 10. They will also be given preference if, while at max size, an
+active member steps down.
+
+### Project Captains
+
+The Express TC can designate captains for individual projects/repos in the
+organizations. These captains are responsible for being the primary
+day-to-day maintainers of the repo on a technical and community front.
+Repo captains are empowered with repo ownership and package publication rights.
+When there are conflicts, especially on topics that effect the Express project
+at large, captains are responsible to raise it up to the TC and drive
+those conflicts to resolution. Captains are also responsible for making sure
+community members follow the community guidelines, maintaining the repo
+and the published package, as well as in providing user support.
+
+Like TC members, Repo captains are a subset of committers.
+
+To become a captain for a project the candidate is expected to participate in that
+project for at least 6 months as a committer prior to the request. They should have
+helped with code contributions as well as triaging issues. They are also required to
+have 2FA enabled on both their GitHub and npm accounts.
+
+Any TC member or an existing captain on the **same** repo can nominate another committer
+to the captain role. To do so, they should submit a PR to this document, updating the
+**Active Project Captains** section (while maintaining the sort order) with the project
+name, the nominee's GitHub handle, and their npm username (if different).
+
+- Repos can have as many captains as make sense for the scope of work.
+- A TC member or an existing repo captain **on the same project** can nominate a new captain.
+ Repo captains from other projects should not nominate captains for a different project.
+
+The PR will require at least 2 approvals from TC members and 2 weeks hold time to allow
+for comment and/or dissent. When the PR is merged, a TC member will add them to the
+proper GitHub/npm groups.
+
+#### Active Projects and Captains
+
+The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members)
+
+#### Current Initiative Captains
+
+The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains)
+
+### Developer's Certificate of Origin 1.1
+
+```text
+By making a contribution to this project, I certify that:
+
+ (a) The contribution was created in whole or in part by me and I
+ have the right to submit it under the open source license
+ indicated in the file; or
+
+ (b) The contribution is based upon previous work that, to the best
+ of my knowledge, is covered under an appropriate open source
+ license and I have the right under that license to submit that
+ work with modifications, whether created in whole or in part
+ by me, under the same open source license (unless I am
+ permitted to submit under a different license), as indicated
+ in the file; or
+
+ (c) The contribution was provided directly to me by some other
+ person who certified (a), (b) or (c) and I have not modified
+ it.
+
+ (d) I understand and agree that this project and the contribution
+ are public and that a record of the contribution (including all
+ personal information I submit with it, including my sign-off) is
+ maintained indefinitely and may be redistributed consistent with
+ this project or the open source license(s) involved.
+```
+
+## Collaborator's guide
+
+
+
+### Website Issues
+
+Open issues for the expressjs.com website in https://github.com/expressjs/expressjs.com.
+
+For issues in other Express managed repos (everything in `expressjs`, `pillarjs` or `jshttp` other than `expressjs/express`), be sure to check their contributing guide and open issues and PRs in the appropriate repository.
+
+### PRs and Code contributions
+
+- Tests must pass.
+- Follow the [JavaScript Standard Style](https://standardjs.com/) and `npm run lint`.
+- If you fix a bug, add a test.
+
+### Branches
+
+Use the `master` branch for bug fixes or minor work that is intended for the
+current release stream.
+
+Use the correspondingly named branch, e.g. `6.x`, for anything intended for
+a future release of Express.
+
+### Steps for contributing
+
+1. Create an issue for the
+ bug you want to fix or the feature that you want to add.
+2. Create your own fork on GitHub, then
+ checkout your fork.
+3. Write your code in your local copy. It's good practice to create a branch for
+ each new issue you work on, although not compulsory.
+4. To run the test suite, first install the dependencies by running `npm install`,
+ then run `npm test`.
+5. Ensure your code is linted by running `npm run lint` -- fix any issue you
+ see listed.
+6. If the tests pass, you can commit your changes to your fork and then create
+ a pull request from there. Make sure to reference your issue from the pull
+ request comments by including the issue number e.g. `#123`.
+
+### Issues which are questions
+
+We will typically close any vague issues or questions that are specific to some
+app you are writing. Please double check the docs and other references before
+being trigger happy with posting a question issue.
+
+Things that will help get your question issue looked at:
+
+- Full and runnable JS code.
+- Clear description of the problem or unexpected behavior.
+- Clear description of the expected result.
+- Steps you have taken to debug it yourself.
+
+If you post a question and do not outline the above items or make it easy for
+us to understand and reproduce your issue, it will be closed.
+
+If your question meets all of the above requirements but you do not believe it needs to be looked at
+by the maintainers
+(for example, if you are just looking for community input) please open it as a discussion topic instead
+of an issue. If you
+are unsure and open an issue, we may move it to discussions if we triage them and decide they do
+not need high
+visibility or maintainer input.
+
+## Security Policies and Procedures
+
+
+
+This document outlines security procedures and general policies for the Express
+project.
+
+- [Reporting a Bug](#reporting-a-bug)
+- [Disclosure Policy](#disclosure-policy)
+- [Comments on this Policy](#comments-on-this-policy)
+
+### Reporting a Bug
+
+The Express team and community take all security bugs in Express seriously.
+Thank you for improving the security of Express. We appreciate your efforts and
+responsible disclosure and will make every effort to acknowledge your
+contributions.
+
+Report security bugs by emailing `express-security@lists.openjsf.org`.
+
+To ensure the timely response to your report, please ensure that the entirety
+of the report is contained within the email body and not solely behind a web
+link or an attachment.
+
+The lead maintainer will acknowledge your email within 48 hours, and will send a
+more detailed response within 48 hours indicating the next steps in handling
+your report. After the initial reply to your report, the security team will
+endeavor to keep you informed of the progress towards a fix and full
+announcement, and may ask for additional information or guidance.
+
+Report security bugs in third-party modules to the person or team maintaining
+the module.
+
+### Pre-release Versions
+
+Alpha and Beta releases are unstable and **not suitable for production use**.
+Vulnerabilities found in pre-releases should be reported according to the [Reporting a Bug](#reporting-a-bug) section.
+Due to the unstable nature of the branch it is not guaranteed that any fixes will be released in the next pre-release.
+
+### Disclosure Policy
+
+When the security team receives a security bug report, they will assign it to a
+primary handler. This person will coordinate the fix and release process,
+involving the following steps:
+
+- Confirm the problem and determine the affected versions.
+- Audit code to find any potential similar problems.
+- Prepare fixes for all releases still under maintenance. These fixes will be
+ released as fast as possible to npm.
+
+### The Express Threat Model
+
+We are currently working on a new version of the security model, the most updated version can be found [here](https://github.com/expressjs/security-wg/blob/main/docs/ThreatModel.md)
+
+### Comments on this Policy
+
+If you have suggestions on how this process could be improved please submit a
+pull request.
+
+----
+
+# Contributing to Expressjs.com {#expressjs-website-contributing}
+
+
+
+### The Official Documentation of the Express JS Framework
+
+This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
+
+#### Need some ideas? These are some typical issues.
+
+1. **Website issues**: If you see anything on the site that could use a tune-up, think about how to fix it.
+ - Display or screen sizing problems
+ - Mobile responsiveness issues
+ - Missing or broken accessibility features
+ - Website outages
+ - Broken links
+ - Page structure or user interface enhancements
+
+2. **Content Issues**: Fix anything related to site content or typos.
+ - Spelling errors
+ - Incorrect/outdated Express JS documentation
+ - Missing content
+
+3. **Translation Issues**: Fix any translation errors or contribute new content.
+ - Fix spelling errors
+ - Fix incorrect/poorly translated words
+ - Check out the [Contributing translations](#contributing-translations) section below for a contributing guide.
+
+#### Want to work on a backlog issue?
+
+We often have bugs or enhancements that need work. You can find these under our repo's [Issues tab](https://github.com/expressjs/expressjs.com/issues). Check out the tags to find something that's a good match for you.
+
+#### Have an idea? Found a bug?
+
+If you've found a bug or a typo, or if you have an idea for an enhancement, you can:
+
+- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
+
+- Make a [Github pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work and it's ready to go, feel free to send it our way.
+
+## Getting Started
+
+The steps below will guide you through the Expressjs.com contribution process.
+
+#### Step 1: (OPTIONAL) Open a New Issue
+
+So you've found a problem that you want to fix, or have a site enhancement you want to make.
+
+1. If you want to get feedback or discuss, open a discussion [issue](https://github.com/expressjs/expressjs.com/issues/new/choose) prior to starting work. This is not required, but encouraged for larger proposals.
+ - While we highly encourage this step, it is only for submissions proposing significant change. It helps us to clarify and focus the work, and ensure it aligns with overall project priorities.
+ - For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
+ - When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
+
+2. After receiving your issue the Express JS documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
+ - For submissions proposing significant change, we encourage you to follow the review process before starting work.
+
+#### Step 2: Get the Application Code Base
+
+Clone the repo and get the code:
+
+```sh
+git clone https://github.com/expressjs/expressjs.com.git
+```
+
+After you've got the code you're ready to start making your changes!
+
+But just in case you need a little extra explanation, this section below outlines the main sections of the code base, where most changes are likely to be made.
+
+**Markdown Page Files**:
+
+- These files render to html and make up the individual pages of the site. Most of the site's documentation text content is written in `md` files.
+- Change these to make changes to individual pages' content/text or markup.
+- Each language has its own complete set of pages, located under their respective language directories - all the Spanish markdown content is found in the `es` directory, for example.
+
+**Includes Partials and Layout Templates**
+
+- `_includes` are partials that are imported and reused across multiple pages.
+ - These are used to import text content for reuse across pages, such as the API documentation, e.g., `_includes > api > en > 5x`, which is included in every language.
+ - These are used to include the page components that make up site-wide user interface and periphery structure, e.g., Header, Footer, etc.
+- `_layouts` are the templates used to wrap the site's individual pages.
+ - These are used to display the structure of the site's periphery, such as the header and footer, and for injecting and displaying individual markdown pages inside the `content` tag.
+
+**Blog Markdown Files**
+
+- These files make up the individual blog posts. If you want to contribute a blog post please
+ follow the specific instructions for [How to write a blog post.](https://expressjs.com/en/blog/write-post.html)
+- Located under the `_posts` directory.
+
+**CSS or Javascript**
+
+- All css and js files are kept in `css` and `js` folders on the project root.
+
+The Express JS website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [Github Pages](https://pages.github.com/).
+
+#### Step 3: Running the Application
+
+Now you'll need a way to see your changes, which means you'll need a running version of the application. You have two options.
+
+1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
+ - This is the recommended option for moderate to complex work.
+
+2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/site-deploys/deploy-previews/).
+ 1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
+ 2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
+ 3. After you are completely done your work and it's ready for review, remove the draft status on your pull request and submit your work.
+
+## Contributing translations
+
+We use Crowdin to manage our translations in multiple languages and achieve automatic translation with artificial intelligence. Since these translations can be inefficient in some cases, we need help from the community to provide accurate and helpful translations.
+
+The documentation is translated into these languages:
+
+- Chinese Simplified (`zh-cn`)
+- Chinese Traditional (`zh-tw`)
+- English (`en`)
+- French (`fr`)
+- German (`de`)
+- Italian (`it`)
+- Japanese (`ja`)
+- Korean (`ko`)
+- Brazilian Portuguese (`pt-br`)
+- Spanish (`es`)
+
+### How to translate
+
+1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
+2. [Select the language you want to translate](https://support.crowdin.com/joining-translation-project/#starting-translation)
+3. [Start translating](https://support.crowdin.com/online-editor/)
+
diff --git a/de/resources/glossary.md b/de/resources/glossary.md
old mode 100755
new mode 100644
index 71f78f6ef1..991a7a584a
--- a/de/resources/glossary.md
+++ b/de/resources/glossary.md
@@ -1,23 +1,16 @@
---
layout: page
title: Express-Glossar
+description: A comprehensive glossary of terms related to Express.js, Node.js, middleware, routing, and other key concepts to help you understand and use Express effectively.
menu: resources
-lang: de
+redirect_from: " "
---
# Glossar
-### Anforderung
-
-Eine HTTP-Anforderung. Ein Client übergibt eine HTTP-Anforderungsnachricht an einen Server, der wiederum eine Antwort zurückgibt. Bei der Anforderung muss eine der [Anforderungsmethoden](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) wie GET, POST usw. verwendet werden.
-
-### Antwort
-
-Eine HTTP-Antwort. Ein Server gibt eine HTTP-Antwortnachricht an den Client zurück. Die Antwort enthält Informationen zum Beendigungsstatus in Bezug auf die Anforderung und kann im Nachrichtenhauptteil auch angeforderten Inhalt enthalten.
-
### Anwendung
-Im Allgemeinen besteht eine Anwendung aus einem oder mehreren Programmen, über die Operationen für bestimmte Zwecke ausgeführt werden. Im Zusammenhang mit Express ist eine Anwendung ein Programm, das die auf der Node.js-Plattform laufende Express-API nutzt. Wird auch als [Anwendungsobjekt](/{{ page.lang }}/api.html#express) bezeichnet.
+Im Allgemeinen besteht eine Anwendung aus einem oder mehreren Programmen, über die Operationen für bestimmte Zwecke ausgeführt werden. Im Zusammenhang mit Express ist eine Anwendung ein Programm, das die auf der Node.js-Plattform laufende Express-API nutzt. Wird auch als [Anwendungsobjekt](/{{ page.lang }}/api.html#express) bezeichnet.
### API
@@ -31,26 +24,42 @@ Schnelles, offenes, unkompliziertes Web-Framework für Node.js-Anwendungen. Im A
Eine plattformübergreifende Unterstützungsbibliothek, bei der die asynchrone Ein-/Ausgabe im Mittelpunkt steht. Sie wurde in erster Linie für die Verwendung in Node.js entwickelt.
-### Middleware
+### middleware
Eine Funktion, die über die Weiterleitungsebene in Express vor dem letzten Anforderungshandler aufgerufen wird. Deshalb befindet sich diese Funktion in der Mitte zwischen einer unformatierten Anforderung und der endgültigen beabsichtigten Weiterleitung. Nachfolgend finden Sie einige Details zur Middlewareterminologie:
- * `var foo = require('middleware')` bedeutet, dass ein Node.js-Modul *benötigt* oder *verwendet* wird. Dann gibt die Anweisung `var mw = foo()` in der Regel die Middleware zurück.
- * `app.use(mw)` bedeutet, dass die *Middleware dem globalen Verarbeitungsstack hinzugefügt wird*.
- * `app.get('/foo', mw, function (req, res) { ... })` bedeutet, dass die *Middleware dem "GET /foo"-Verarbeitungsstack hinzugefügt wird*.
+- `var foo = require('middleware')` bedeutet, dass ein Node.js-Modul _benötigt_ oder _verwendet_ wird. Dann gibt die Anweisung `var mw = foo()` in der Regel die Middleware zurück.
+- `app.use(mw)` bedeutet, dass die _Middleware dem globalen Verarbeitungsstack hinzugefügt wird_.
+- `app.get('/foo', mw, function (req, res) { ... })` bedeutet, dass die _Middleware dem "GET /foo"-Verarbeitungsstack hinzugefügt wird_.
### Node.js
-Eine Softwareplattform, die für die Erstellung skalierbarer Netzanwendungen verwendet wird. Node.js verwendet JavaScript als Scripting-Sprache und erzielt den hohen Durchsatz durch nicht blockierende Ein-/Ausgabe und eine Ereignisschleife mit einem Thread. Siehe auch [nodejs.org](http://nodejs.org/). **Hinweis**: Der ursprüngliche Name lautet "Node.js". Mittlerweile ist die Bezeichnung "Node" geläufig.
+Eine Softwareplattform, die für die Erstellung skalierbarer Netzanwendungen verwendet wird. Node.js verwendet JavaScript als Scripting-Sprache und erzielt den hohen Durchsatz durch nicht blockierende Ein-/Ausgabe und eine Ereignisschleife mit einem Thread. Siehe auch [nodejs.org](http://nodejs.org/). **Hinweis**: Der ursprüngliche Name lautet "Node.js".
### Open-Source
Bei Verwendung als Adjektiv muss dieser Begriff mit Bindestrichen gekoppelt werden: Beispiel: "Dies ist eine Open-Source-Software." Siehe auch [Open-Source-Software in Wikipedia](http://en.wikipedia.org/wiki/Open-source_software).
-### Router
+{% capture english-rules %}
-Siehe [Router](/{{ page.lang }}/4x/api.html#router) in der API-Referenz.
+Although it is common not to hyphenate this term, we are using the standard English rules for hyphenating a compound adjective.
+
+{% endcapture %}
+
+{% include admonitions/note.html content=english-rules %}
+
+### Anforderung
+
+Eine HTTP-Antwort. Ein Server gibt eine HTTP-Antwortnachricht an den Client zurück. Die Antwort enthält Informationen zum Beendigungsstatus in Bezug auf die Anforderung und kann im Nachrichtenhauptteil auch angeforderten Inhalt enthalten.
+
+### Antwort
+
+Eine HTTP-Anforderung. Ein Client übergibt eine HTTP-Anforderungsnachricht an einen Server, der wiederum eine Antwort zurückgibt. The response contains completion status information about the request and might also contain requested content in its message body.
### Weiterleitung (Route)
Teil einer URL, die eine Ressource angibt. Beispiel: In `http://foo.com/products/id` ist "/products/id" die Weiterleitung.
+
+### Router
+
+Siehe [Router](/{{ page.lang }}/4x/api.html#router) in der API-Referenz.
diff --git a/de/resources/learning.md b/de/resources/learning.md
deleted file mode 100755
index 5529984543..0000000000
--- a/de/resources/learning.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-layout: page
-title: Zusätzliches Lernen
-menu: resources
-lang: de
----
-
-# Zusätzliches Lernen
-
-Disclaimer: Unendorsed community content.
-
-## Books
-
-Here are a few of the many books on Express:
-
- - **[Getting MEAN with Mongo, Express, Angular, and Node](http://www.manning.com/sholmes/)**,
-Manning Publications, early 2015.
- - **[Express.js in Action](http://www.manning.com/hahn/)**,
-Manning Publications, early 2015.
- - **[Mastering Web Application Development with Express](https://www.packtpub.com/web-development/mastering-web-application-development-express-raw)**,
-Packt Publishing, September 2014.
- - **[Web Development with Node and Express](http://shop.oreilly.com/product/0636920032977.do)**,
-O'Reilly Media, July 2014.
- - **[Node.js in Action](http://www.manning.com/cantelon/)**,
-Manning Publications, October 2013.
- - **[Express Web Application Development](https://www.packtpub.com/web-development/express-web-application-development)**,
-Packt Publishing, June 2013.
-- **[express - Middleware für node.js](http://www.amazon.de/express-Middleware-node-js-J%C3%B6rg-Krause/dp/1517281342/ref=sr_1_1?ie=UTF8&qid=1442001556&sr=8-1&keywords=1517281342)**,
-texxtoor, September 2015. In deutscher Sprache / in German language
-- **[JADE - die Template Engine für node.js](http://www.amazon.de/JADE-Die-Template-Engine-node-js/dp/1517282098/ref=sr_1_1?ie=UTF8&qid=1442001592&sr=8-1&keywords=1517282098)**,
-texxtoor, September 2015. In deutscher Sprache / in German language
-- **[Node Web Development, 2nd edition](https://www.packtpub.com/web-development/node-web-development-second-edition)**, Packt Publishing, August 2013
-
-### Add your book here!
-
-[Edit the Markdown file](https://github.com/expressjs/expressjs.com/blob/gh-pages/{{ page.lang }}/resources/learning.md) and add a link to your book, then submit a pull request (GitHub login required). Follow the format of the above listings.
-
-## Blogs
-
-- [StrongLoop Blog: Express category](http://strongloop.com/strongblog/category/express/)
-- [Hage Yaapa's Blog: Express category](http://www.hacksparrow.com/category/express-js)
-- [Codeforgeek Blog: Express category](http://codeforgeek.com/code/nodejs/express/)
-
-### Add your blog here!
-
-[Edit the Markdown file](https://github.com/expressjs/expressjs.com/blob/gh-pages/{{ page.lang }}/resources/learning.md) and add a link to your blog, then submit a pull request (GitHub login required). Follow the format of the above listings.
diff --git a/de/resources/middleware.md b/de/resources/middleware.md
old mode 100755
new mode 100644
index a000551777..6342018377
--- a/de/resources/middleware.md
+++ b/de/resources/middleware.md
@@ -1,64 +1,43 @@
---
-layout: page
+layout: middleware
title: Express-Middleware
+description: Explore a list of Express.js middleware modules maintained by the Express team and the community, including built-in middleware and popular third-party modules.
menu: resources
-lang: de
+redirect_from: " "
+module: mw-home
---
-# Middleware anderer Anbieter
+## Express-Middleware
Nachfolgend sind einige Express-Middlewaremodule aufgeführt:
- - [body-parser](https://github.com/expressjs/body-parser): Bisher: `express.bodyParser`, `json` und `urlencoded`.
- Siehe auch:
- - [body](https://github.com/raynos/body)
- - [co-body](https://github.com/visionmedia/co-body)
- - [raw-body](https://github.com/stream-utils/raw-body)
- - [compression](https://github.com/expressjs/compression): Bisher `express.compress`
- - [connect-image-optimus](https://github.com/msemenistyi/connect-image-optimus): Connect/Express-Middlewaremodule für optimales Image-Serving. Wechselt Images (wenn möglich) zu `.webp` oder `.jxr`.
- - [connect-timeout](https://github.com/expressjs/timeout): Bisher: `express.timeout`
- - [cookie-parser](https://github.com/expressjs/cookie-parser): Bisher: `express.cookieParser`
- - [cookie-session](https://github.com/expressjs/cookie-session): Bisher: `express.cookieSession`
- - [csurf](https://github.com/expressjs/csurf): Bisher: `express.csrf`
- - [errorhandler](https://github.com/expressjs/errorhandler): Bisher: `express.errorHandler`
- - [express-debug](https://github.com/devoidfury/express-debug): Entwicklungstool, mit dem eine Registerkarte mit Informationen zu Vorlagenvariablen (lokalen Variablen), zur aktuellen Sitzung, zu hilfreichen Anforderungsdaten usw. Ihrer Anwendung hinzugefügt werden können.
- - [express-partial-response](https://github.com/nemtsov/express-partial-response): Express-Middlewaremodul für die Filterung von Teilen von JSON-Antworten auf Basis der Abfragezeichenfolge `fields` durch Verwendung der Google-API Partial Response.
- - [express-session](https://github.com/expressjs/session): Bisher: `express.session`
- - [express-simple-cdn](https://github.com/jamiesteven/express-simple-cdn): Express-Middlewaremodul für die Verwendung eines CDN (Content Delivery Network) für statische Assets mit Unterstützung mehrerer Hosts (Beispiel: cdn1.host.com, cdn2.host.com).
- - [express-slash](https://github.com/ericf/express-slash): Express-Middlewaremodul für Benutzer, die hohen Wert auf abschließende Schrägstriche legen.
- - [express-stormpath](https://github.com/stormpath/stormpath-express): Express-Middlewaremodul für Benutzerspeicher, Authentifizierung, Autorisierung, SSO und Datensicherheit.
- - [express-uncapitalize](https://github.com/jamiesteven/express-uncapitalize): Middlewaremodul für die Umleitung von HTTP-Anforderungen mit Großbuchstaben in eine kanonische Form mit Kleinbuchstaben.
- - [helmet](https://github.com/helmetjs/helmet): Modul zur Sicherung Ihrer Anwendungen durch Festlegung verschiedener HTTP-Header.
- - [join-io](https://github.com/coderaiser/join-io "join-io"): Modul für die Verknüpfung von Dateien während der Verarbeitung, um die Anzahl der Anforderungen zu reduzieren.
- - [method-override](https://github.com/expressjs/method-override): Bisher: `express.methodOverride`
- - [morgan](https://github.com/expressjs/morgan): Bisher: `logger`
- - [passport](https://github.com/jaredhanson/passport): Express-Middlewaremodul für die Authentifizierung.
- - [response-time](https://github.com/expressjs/response-time): Bisher: `express.responseTime`
- - [serve-favicon](https://github.com/expressjs/serve-favicon): Bisher: `express.favicon`
- - [serve-index](https://github.com/expressjs/serve-index): Bisher: `express.directory`
- - [serve-static](https://github.com/expressjs/serve-static): Modul für statischen Inhalt.
- - [static-expiry](https://github.com/paulwalker/connect-static-expiry): URLs mit elektronischem Fingerabdruck oder Caching-Headern für statische Assets einschließlich Unterstützung für eine oder mehrere externe Domänen.
- - [vhost](https://github.com/expressjs/vhost): Bisher: `express.vhost`
- - [view-helpers](https://github.com/madhums/node-view-helpers): Express-Middlewaremodul, das allgemeine Helper-Methoden für Ansichten bereitstellt.
- - [sriracha-admin](https://github.com/hdngr/siracha): Express-Middlewaremodul, das eine Administratorsite für Mongoose dynamisch generiert.
+| [express-slash](https://github.com/ericf/express-slash): Express-Middlewaremodul für Benutzer, die hohen Wert auf abschließende Schrägstriche legen. | Beschreibung |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------- |
+| [body-parser](/{{page.lang}}/resources/middleware/body-parser.html) | Parse HTTP request body. |
+| [compression](/{{page.lang}}/resources/middleware/compression.html) | Compress HTTP responses. |
+| [connect-rid](/{{page.lang}}/resources/middleware/connect-rid.html) | Generate unique request ID. |
+| [cookie-parser](/{{page.lang}}/resources/middleware/cookie-parser.html) | Parse cookie header and populate `req.cookies`. See also [cookies](https://github.com/jed/cookies). |
+| [cookie-session](/{{page.lang}}/resources/middleware/cookie-session.html) | Establish cookie-based sessions. |
+| [cors](/{{page.lang}}/resources/middleware/cors.html) | Enable cross-origin resource sharing (CORS) with various options. |
+| [errorhandler](/{{page.lang}}/resources/middleware/errorhandler.html) | Development error-handling/debugging. |
+| [method-override](/{{page.lang}}/resources/middleware/method-override.html) | Override HTTP methods using header. |
+| [morgan](/{{page.lang}}/resources/middleware/morgan.html) | HTTP request logger. |
+| [multer](/{{page.lang}}/resources/middleware/multer.html) | Handle multi-part form data. |
+| [response-time](/{{page.lang}}/resources/middleware/response-time.html) | Record HTTP response time. |
+| [serve-favicon](/{{page.lang}}/resources/middleware/serve-favicon.html) | Serve a favicon. |
+| [serve-index](/{{page.lang}}/resources/middleware/serve-index.html) | Serve directory listing for a given path. |
+| [serve-static](/{{page.lang}}/resources/middleware/serve-static.html) | Serve static files. |
+| [session](/{{page.lang}}/resources/middleware/session.html) | Establish server-based sessions (development only). |
+| [timeout](/{{page.lang}}/resources/middleware/timeout.html) | Set a timeout perioHTTP request processing. |
+| [vhost](/{{page.lang}}/resources/middleware/vhost.html) | Create virtual domains. |
-Einige Middlewaremodule, die bisher zu Connect gehörten, werden vom Connect/Express-Team nicht mehr unterstützt. Diese Module werden durch ein alternatives oder besseres Modul ersetzt. Verwenden Sie eine der folgenden Alternativen:
+## Informationen zu weiteren Middlewaremodulen siehe:
- - express.cookieParser
- - [cookies](https://github.com/jed/cookies) und [keygrip](https://github.com/jed/keygrip)
- - express.limit
- - [raw-body](https://github.com/stream-utils/raw-body)
- - express.multipart
- - [connect-busboy](https://github.com/mscdex/connect-busboy)
- - [multer](https://github.com/expressjs/multer)
- - [connect-multiparty](https://github.com/superjoe30/connect-multiparty)
- - express.query
- - [qs](https://github.com/visionmedia/node-querystring)
- - express.staticCache
- - [st](https://github.com/isaacs/st)
- - [connect-static](https://github.com/andrewrk/connect-static)
+These are some additional popular middleware modules.
-Informationen zu weiteren Middlewaremodulen siehe:
+{% include community-caveat.html %}
- - [http-framework](https://github.com/Raynos/http-framework/wiki/Modules)
- - [expressjs](https://github.com/expressjs)
+| [express-slash](https://github.com/ericf/express-slash): Express-Middlewaremodul für Benutzer, die hohen Wert auf abschließende Schrägstriche legen. | Beschreibung |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [helmet](https://github.com/helmetjs/helmet): Modul zur Sicherung Ihrer Anwendungen durch Festlegung verschiedener HTTP-Header. | Helps secure your apps by setting various HTTP headers. |
+| [passport](https://github.com/jaredhanson/passport): Express-Middlewaremodul für die Authentifizierung. | Authentication using "strategies" such as OAuth, OpenID and many others. See [passportjs.org](https://passportjs.org/) for more information. |
diff --git a/de/resources/middleware/body-parser.md b/de/resources/middleware/body-parser.md
new file mode 100644
index 0000000000..9c3e7e0276
--- /dev/null
+++ b/de/resources/middleware/body-parser.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express body-parser middleware
+menu: resources
+redirect_from: ' '
+module: body-parser
+---
diff --git a/de/resources/middleware/compression.md b/de/resources/middleware/compression.md
new file mode 100644
index 0000000000..d288542a65
--- /dev/null
+++ b/de/resources/middleware/compression.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express compression middleware
+menu: resources
+redirect_from: ' '
+module: compression
+---
diff --git a/de/resources/middleware/connect-rid.md b/de/resources/middleware/connect-rid.md
new file mode 100644
index 0000000000..95b2689265
--- /dev/null
+++ b/de/resources/middleware/connect-rid.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express connect-rid middleware
+menu: resources
+redirect_from: ' '
+module: connect-rid
+---
diff --git a/de/resources/middleware/cookie-parser.md b/de/resources/middleware/cookie-parser.md
new file mode 100644
index 0000000000..55100372e3
--- /dev/null
+++ b/de/resources/middleware/cookie-parser.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express cookie-parser middleware
+menu: resources
+redirect_from: ' '
+module: cookie-parser
+---
diff --git a/de/resources/middleware/cookie-session.md b/de/resources/middleware/cookie-session.md
new file mode 100644
index 0000000000..c6308fa81c
--- /dev/null
+++ b/de/resources/middleware/cookie-session.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express cookie-session middleware
+menu: resources
+redirect_from: ' '
+module: cookie-session
+---
diff --git a/de/resources/middleware/cors.md b/de/resources/middleware/cors.md
new file mode 100644
index 0000000000..4692141929
--- /dev/null
+++ b/de/resources/middleware/cors.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express cors middleware
+menu: resources
+redirect_from: ' '
+module: cors
+---
diff --git a/de/resources/middleware/errorhandler.md b/de/resources/middleware/errorhandler.md
new file mode 100644
index 0000000000..3b11a1208e
--- /dev/null
+++ b/de/resources/middleware/errorhandler.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express errorhandler middleware
+menu: resources
+redirect_from: ' '
+module: errorhandler
+---
diff --git a/de/resources/middleware/method-override.md b/de/resources/middleware/method-override.md
new file mode 100644
index 0000000000..8dff029cd4
--- /dev/null
+++ b/de/resources/middleware/method-override.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express method-override middleware
+menu: resources
+redirect_from: ' '
+module: method-override
+---
diff --git a/de/resources/middleware/morgan.md b/de/resources/middleware/morgan.md
new file mode 100644
index 0000000000..99c4c80fa9
--- /dev/null
+++ b/de/resources/middleware/morgan.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express morgan middleware
+menu: resources
+redirect_from: ' '
+module: morgan
+---
diff --git a/de/resources/middleware/multer.md b/de/resources/middleware/multer.md
new file mode 100644
index 0000000000..2fffab3b73
--- /dev/null
+++ b/de/resources/middleware/multer.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express multer middleware
+menu: resources
+redirect_from: ' '
+module: multer
+---
diff --git a/de/resources/middleware/response-time.md b/de/resources/middleware/response-time.md
new file mode 100644
index 0000000000..78ee67cd32
--- /dev/null
+++ b/de/resources/middleware/response-time.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express response-time middleware
+menu: resources
+redirect_from: ' '
+module: response-time
+---
diff --git a/de/resources/middleware/serve-favicon.md b/de/resources/middleware/serve-favicon.md
new file mode 100644
index 0000000000..7a1c8e6f5c
--- /dev/null
+++ b/de/resources/middleware/serve-favicon.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express serve-favicon middleware
+menu: resources
+redirect_from: ' '
+module: serve-favicon
+---
diff --git a/de/resources/middleware/serve-index.md b/de/resources/middleware/serve-index.md
new file mode 100644
index 0000000000..deeb963c8f
--- /dev/null
+++ b/de/resources/middleware/serve-index.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express serve-index middleware
+menu: resources
+redirect_from: ' '
+module: serve-index
+---
diff --git a/de/resources/middleware/serve-static.md b/de/resources/middleware/serve-static.md
new file mode 100644
index 0000000000..ff9bcc313e
--- /dev/null
+++ b/de/resources/middleware/serve-static.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express serve-static middleware
+menu: resources
+redirect_from: ' '
+module: serve-static
+---
diff --git a/de/resources/middleware/session.md b/de/resources/middleware/session.md
new file mode 100644
index 0000000000..22cf354ae7
--- /dev/null
+++ b/de/resources/middleware/session.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express session middleware
+menu: resources
+redirect_from: ' '
+module: session
+---
diff --git a/de/resources/middleware/timeout.md b/de/resources/middleware/timeout.md
new file mode 100644
index 0000000000..1afa2c5dd3
--- /dev/null
+++ b/de/resources/middleware/timeout.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express timeout middleware
+menu: resources
+redirect_from: ' '
+module: timeout
+---
diff --git a/de/resources/middleware/vhost.md b/de/resources/middleware/vhost.md
new file mode 100644
index 0000000000..2bad4c964f
--- /dev/null
+++ b/de/resources/middleware/vhost.md
@@ -0,0 +1,7 @@
+---
+layout: middleware
+title: Express vhost middleware
+menu: resources
+redirect_from: ' '
+module: vhost
+---
diff --git a/de/resources/utils.md b/de/resources/utils.md
new file mode 100644
index 0000000000..0fd21eea69
--- /dev/null
+++ b/de/resources/utils.md
@@ -0,0 +1,25 @@
+---
+layout: page
+title: Express utilities
+description: Discover utility modules related to Express.js and Node.js, including tools for cookies, CSRF protection, URL parsing, routing, and more to enhance your applications.
+menu: resources
+redirect_from: " "
+---
+
+## Express utility functions
+
+The [pillarjs](https://github.com/pillarjs) GitHub organization contains a number of modules
+for utility functions that may be generally useful.
+
+| Utility modules | Beschreibung |
+| -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [cookies](https://www.npmjs.com/package/cookies) | Get and set HTTP(S) cookies that can be signed to prevent tampering, using Keygrip. Can be used with the Node.js HTTP library or as Express middleware. |
+| [csrf](https://www.npmjs.com/package/csrf) | Contains the logic behind CSRF token creation and verification. Use this module to create custom CSRF middleware. |
+| [finalhandler](https://www.npmjs.com/package/finalhandler) | Function to invoke as the final step to respond to HTTP request. |
+| [parseurl](https://www.npmjs.com/package/parseurl) | Parse a URL with caching. |
+| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Turn an Express-style path string such as \`\`/user/:name\` into a regular expression. |
+| [resolve-path](https://www.npmjs.com/package/resolve-path) | Resolves a relative path against a root path with validation. |
+| [router](https://www.npmjs.com/package/router) | Simple middleware-style router. |
+| [send](https://www.npmjs.com/package/send) | Library for streaming files as a HTTP response, with support for partial responses (ranges), conditional-GET negotiation, and granular events. |
+
+For additional low-level HTTP-related modules, see [jshttp](http://jshttp.github.io/).
diff --git a/de/starter/basic-routing.md b/de/starter/basic-routing.md
old mode 100755
new mode 100644
index e59ce41246..eaed71d21a
--- a/de/starter/basic-routing.md
+++ b/de/starter/basic-routing.md
@@ -1,24 +1,24 @@
---
layout: page
title: Basisrouting in Express
+description: Learn the fundamentals of routing in Express.js applications, including how to define routes, handle HTTP methods, and create route handlers for your web server.
menu: starter
-lang: de
+redirect_from: " "
---
# Basisrouting
-Per *Routing* wird bestimmt, wie eine Antwort auf eine Clientanforderung an einem bestimmten Endpunkt antwortet. Dies ist eine URI (oder ein Pfad) und eine bestimmte HTTP-Anforderungsmethode (GET, POST usw.).
+Per _Routing_ wird bestimmt, wie eine Antwort auf eine Clientanforderung an einem bestimmten Endpunkt antwortet. Dies ist eine URI (oder ein Pfad) und eine bestimmte HTTP-Anforderungsmethode (GET, POST usw.).
Jede Weiterleitung (Route) kann eine oder mehrere Handlerfunktionen haben, die ausgeführt werden, wenn die Weiterleitung abgeglichen wird.
Weiterleitungsdefinitionen haben die folgende Struktur:
-
-
+```
-Bedeutung:
+Where:
- `app` ist eine Instanz von `express`.
- `METHOD` ist eine [HTTP-Anforderungsmethode](http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol).
@@ -33,42 +33,36 @@ Die folgenden Beispiele veranschaulichen das Definieren einfacher Weiterleitunge
Antworten Sie mit `Hello World!` auf der Homepage:
-
-
+```js
+app.get('/', (req, res) => {
+ res.send('Hello World!')
+})
+```
-Antworten Sie auf POST-Anforderungen auf die Weiterleitung zum Stammverzeichnis (`/`), der Homepage der Anwendung:
+Respond to a POST request on the root route (`/`), the application's home page:
-
-
+```js
+app.post('/', (req, res) => {
+ res.send('Got a POST request')
+})
+```
Antworten Sie auf eine PUT-Anforderung zur Weiterleitung `/user`:
-
-
+```js
+app.put('/user', (req, res) => {
+ res.send('Got a PUT request at /user')
+})
+```
Antworten Sie auf eine DELETE-Anforderung zur Weiterleitung `/user`:
-
-
+```js
+app.delete('/user', (req, res) => {
+ res.send('Got a DELETE request at /user')
+})
+```
Details zum Thema Routing finden Sie in der entsprechenden [Routinganleitung](/{{ page.lang }}/guide/routing.html).
+
+### [Previous: Express application generator ](/{{ page.lang }}/starter/generator.html) [Next: Serving static files in Express ](/{{ page.lang }}/starter/static-files.html)
diff --git a/de/starter/examples.md b/de/starter/examples.md
new file mode 100644
index 0000000000..a03e016318
--- /dev/null
+++ b/de/starter/examples.md
@@ -0,0 +1,21 @@
+---
+layout: page
+title: Express examples
+description: Explore a collection of Express.js application examples covering various use cases, integrations, and advanced configurations to help you learn and build your projects.
+menu: starter
+redirect_from: " "
+---
+
+{% capture examples %}{% include readmes/express-master/examples.md %}{% endcapture %}
+{{ examples | replace: "](.", "](https://github.com/expressjs/express/tree/master/examples" }}
+
+## Additional examples
+
+These are some additional examples with more extensive integrations.
+
+{% include community-caveat.html %}
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Fullstack app with Express and Next.js using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API with Express in TypeScript using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
+
+### [Previous: Static Files ](/{{ page.lang }}/starter/static-files.html) [Next: FAQ ](/{{ page.lang }}/starter/faq.html)
diff --git a/de/starter/faq.md b/de/starter/faq.md
old mode 100755
new mode 100644
index 89ba8e6a52..178246ecea
--- a/de/starter/faq.md
+++ b/de/starter/faq.md
@@ -1,8 +1,9 @@
---
layout: page
title: Häufig gestellte Fragen zu Express
+description: Finden Sie Antworten auf häufig gestellte Fragen zu Express.js, darunter Themen wie Anwendungsstruktur, Models, Authentifizierung, Template-Engines, Fehlerbehandlung und mehr.
menu: starter
-lang: de
+redirect_from: " "
---
# Häufig gestellte Fragen
@@ -13,14 +14,13 @@ Auf diese Frage gibt es keine verbindliche Antwort. Die Antwort hängt vom Umfan
Weiterleitungen und andere anwendungsspezifische Logik können in einer beliebigen Anzahl von Dateien und in jeder von Ihnen bevorzugten Verzeichnisstruktur vorkommen. Die folgenden Beispiele sollen als Entscheidungshilfe dienen:
-
-* [Weiterleitungslisten](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-47)
-* [Weiterleitungszuordnung](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
-* [Controller im MVC-Stil](https://github.com/expressjs/express/tree/master/examples/mvc)
+- [Weiterleitungslisten](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-47)
+- [Weiterleitungszuordnung](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [Controller im MVC-Stil](https://github.com/expressjs/express/tree/master/examples/mvc)
Darüber hinaus gibt es Erweiterungen anderer Anbieter für Express, die zur Vereinfachung einiger dieser Muster beitragen:
-* [Weiterleitung mit "express-resource"](https://github.com/expressjs/express-resource)
+- [Weiterleitung mit "express-resource"](https://github.com/expressjs/express-resource)
## Wie definiere ich Modelle?
@@ -30,40 +30,51 @@ Express hat keine Vorstellungen von einer Datenbank. Dieses Konzept bleibt Node-
## Wie kann ich Benutzer authentifizieren?
-Die Authentifizierung ist ein weiterer meinungsstarker Bereich, in den Express nicht eingreift. Sie können ein Authentifizierungsschema nach Ihren Vorstellungen verwenden. Ein einfaches Benutzername/Kennwort-Schema können Sie in [diesem Beispiel](https://github.com/expressjs/express/tree/master/examples/auth) sehen.
-
+Die Authentifizierung ist ein weiterer meinungsstarker Bereich, in den Express nicht eingreift. Sie können ein Authentifizierungsschema nach Ihren Vorstellungen verwenden.
+Ein einfaches Benutzername/Kennwort-Schema können Sie in [diesem Beispiel](https://github.com/expressjs/express/tree/master/examples/auth) sehen.
## Welche Template-Engines unterstützt Express?
-Express unterstützt jede Template-Engine, die der `(path, locals, callback)`-Signatur entspricht. Informationen zur Normalisierung von Template-Engine-Schnittstellen und -Caching siehe das Projekt [consolidate.js](https://github.com/visionmedia/consolidate.js). Nicht aufgelistete Template-Engines können trotzdem die Express-Signatur unterstützen.
+Express unterstützt jede Template-Engine, die der `(path, locals, callback)`-Signatur entspricht.
+Informationen zur Normalisierung von Template-Engine-Schnittstellen und -Caching siehe das Projekt [consolidate.js](https://github.com/visionmedia/consolidate.js). Nicht aufgelistete Template-Engines können trotzdem die Express-Signatur unterstützen.
+
+For more information, see [Using template engines with Express](/{{page.lang}}/guide/using-template-engines.html).
## Wie handhabe ich 404-Antworten?
In Express sind 404-Antworten nicht das Ergebnis eines Fehlers, sodass diese Antworten von der Fehlerbehandlungsroutine nicht erfasst werden. Dieses Verhalten ist damit zu erklären, dass eine 404-Antwort einfach angibt, dass keine weiteren Arbeiten auszuführen sind. In anderen Worten: Express hat alle Middlewarefunktionen und Weiterleitungen ausgeführt und festgestellt, dass keine Funktion eine Antwort zurückgegeben hat. Sie müssen also bei der Handhabung der 404-Antwort nur eine Middlewarefunktion am Ende des Stacks (unterhalb von allen anderen Funktionen) hinzufügen:
-
-
+```js
+app.use((req, res, next) => {
+ res.status(404).send("Sorry can't find that!")
+})
+```
+
+Add routes dynamically at runtime on an instance of `express.Router()`
+so the routes are not superseded by a middleware function.
## Wie richte ich eine Fehlerbehandlungsroutine ein?
Middleware für die Fehlerbehandlung wird in derselben Weise definiert wie andere Middleware; außer dass sie vier anstatt drei Argumente aufweist. Dies gilt speziell bei der Signatur `(err, req, res, next)`:
-
-
+```js
+app.use((err, req, res, next) => {
+ console.error(err.stack)
+ res.status(500).send('Something broke!')
+})
+```
Weitere Informationen siehe [Fehlerbehandlung](/{{ page.lang }}/guide/error-handling.html).
## Wie gebe ich normales HTML-Format aus?
-Das ist nicht Ihre Aufgabe! Sie müssen kein HTML-Format mit der Funktion `res.render()` ausgeben. Verwenden Sie die Funktion `res.sendFile()`, wenn Sie es mit einer bestimmten Datei zu tun haben. Wenn Sie viele Assets aus einem Verzeichnis bedienen müssen, verwenden Sie die Middlewarefunktion `express.static()`.
+Das ist nicht Ihre Aufgabe! Sie müssen kein HTML-Format mit der Funktion `res.render()` ausgeben.
+Verwenden Sie die Funktion `res.sendFile()`, wenn Sie es mit einer bestimmten Datei zu tun haben.
+Wenn Sie viele Assets aus einem Verzeichnis bedienen müssen, verwenden Sie die Middlewarefunktion `express.static()`.
+
+## Welche Version von Node.js benötigt Express?
+
+- [Express 4.x](/{{ page.lang }}/4x/api.html) requires Node.js 0.10 or higher.
+- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher.
+
+### [Previous: More examples ](/{{ page.lang }}/starter/examples.html)
diff --git a/de/starter/generator.md b/de/starter/generator.md
old mode 100755
new mode 100644
index 11be303f78..f59f6e1d1a
--- a/de/starter/generator.md
+++ b/de/starter/generator.md
@@ -1,29 +1,34 @@
---
layout: page
title: Express-Anwendungsgenerator
+description: Learn how to use the Express application generator tool to quickly create a skeleton for your Express.js applications, streamlining setup and configuration.
menu: starter
-lang: de
+redirect_from: " "
---
# Express-Anwendungsgenerator
Mit dem Application Generator Tool `express` können Sie innerhalb kürzester Zeit ein Anwendungsgerüst erstellen.
-Installieren Sie `express` mit dem folgenden Befehl:
+You can run the application generator with the `npx` command (available in Node.js 8.2.0).
-
-
+```bash
+$ npx express-generator
+```
+
+For earlier Node versions, install the application generator as a global npm package and then launch it:
+
+```bash
+$ npm install -g express-generator
+$ express
+```
Zeigen Sie die Befehlsoptionen mit der Option `-h` an:
-
-
+```
-Im folgenden Beispiel wird eine Express-Anwendung mit dem Namen _myapp_ im aktuellen Arbeitsverzeichnis erstellt:
+Im folgenden Beispiel wird eine Express-Anwendung mit dem Namen _myapp_ im aktuellen Arbeitsverzeichnis erstellt: The app will be created in a folder named _myapp_ in the current working directory and the view engine will be set to Pug:
-
-
+```
Installieren Sie dann Abhängigkeiten:
-
-
+```
-Führen Sie unter MacOS oder Linux die Anwendung mit diesem Befehl aus:
+Verwenden Sie unter Windows diesen Befehl:
-
-
+```
-Verwenden Sie unter Windows diesen Befehl:
+Führen Sie unter MacOS oder Linux die Anwendung mit diesem Befehl aus:
-
-
+```
+
+On Windows PowerShell, use this command:
+
+```bash
+PS> $env:DEBUG='myapp:*'; npm start
+```
Laden Sie dann `http://localhost:3000/` in Ihren Browser, um auf die Anwendung zuzugreifen.
Die erstellte Anwendung hat die folgende Verzeichnisstruktur:
-
-
+```
Die vom Generator erstellte Anwendungsstruktur ist nur eine der vielen Möglichkeiten, Express-Anwendungen zu strukturieren. Sie können diese Struktur verwenden oder sie an Ihre Anforderungen anpassen.
+
+### [Previous: Hello World ](/{{ page.lang }}/starter/hello-world.html) [Next: Basic routing](/{{ page.lang }}/starter/basic-routing.html)
diff --git a/de/starter/hello-world.md b/de/starter/hello-world.md
old mode 100755
new mode 100644
index 3534baba3b..3fd33c8743
--- a/de/starter/hello-world.md
+++ b/de/starter/hello-world.md
@@ -1,8 +1,9 @@
---
layout: page
title: Beispiel "Hello World" in Express
+description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners.
menu: starter
-lang: de
+redirect_from: " "
---
# Beispiel "Hello World"
@@ -11,12 +12,7 @@ lang: de
Dies ist wohl die einfachste Express-Anwendung, die Sie erstellen können. Es handelt sich um eine Anwendung mit nur einer Datei und — *nicht* das, was Sie mit dem [Express Generator](/{{ page.lang }}/starter/generator.html) erhalten würden. Mit dem Generator würde das Gerüst für eine vollständige Anwendung mit zahlreichen JavaScript-Dateien, Jade-Vorlagen und Unterverzeichnissen für verschiedene Zwecke erstellt werden.
-
+```
-Die Anwendung startet einen Server und ist an Port 3000 empfangsbereit für Verbindungen. Die Anwendung antwortet mit "Hello World!" auf Anforderungen zur Stamm-URL (`/`) oder zu *route*. Bei jedem anderen Pfad lautet die Antwort **404 Not Found**.
+Die Anwendung startet einen Server und ist an Port 3000 empfangsbereit für Verbindungen. Die Anwendung antwortet mit "Hello World!" auf Anforderungen zur Stamm-URL (`/`) oder zu _route_. Bei jedem anderen Pfad lautet die Antwort **404 Not Found**.
-
-`req` (Anforderung) und `res` (Antwort) sind genau dieselben Objekte, die Node bereitstellt. Sie können also `req.pipe()`, `req.on('data', callback)` und alle anderen Tasks, die Sie ausführen wollen, ohne Express ausführen.
-
+### Running Locally
+
+Erstellen Sie zunächst ein Verzeichnis namens `myapp`, wechseln Sie in das Verzeichnis und führen Sie `npm init` aus. Installieren Sie dann `express` als Abhängigkeit, wie im [Installationshandbuch](/{{ page.lang }}/starter/installing.html) beschrieben.
+
+Erstellen Sie im Verzeichnis `myapp` eine Datei namens `app.js` und fügen Sie den folgenden Code hinzu:
+
+`req` (Anforderung) und `res` (Antwort) sind genau dieselben Objekte, die Node bereitstellt. Sie können also `req.pipe()`, `req.on('data', callback)` und alle anderen Tasks, die Sie ausführen wollen, ohne Express ausführen.
Führen Sie die Anwendung mit dem folgenden Befehl aus:
-
-
+```
Laden Sie dann [http://localhost:3000/](http://localhost:3000/) in einen Browser, um die Ausgabe zu sehen.
+### [Previous: Installing ](/{{ page.lang }}/starter/installing.html) [Next: Express Generator ](/{{ page.lang }}/starter/generator.html)
diff --git a/de/starter/installing.md b/de/starter/installing.md
old mode 100755
new mode 100644
index e47a9c1cb9..e745549656
--- a/de/starter/installing.md
+++ b/de/starter/installing.md
@@ -1,55 +1,53 @@
---
layout: page
title: Express installieren
+description: Erfahren Sie, wie Sie Express.js in Ihrer Node.js-Umgebung installieren, wie Sie Ihr Projektverzeichnis aufsetzen und Abhängigkeiten mit npm verwalten.
menu: starter
-lang: de
+redirect_from: " "
---
# Installation
Angenommen, Sie haben [Node.js](https://nodejs.org/) bereits installiert. Erstellen Sie ein Verzeichnis für Ihre Anwendung und definieren Sie dieses Verzeichnis als Ihr Arbeitsverzeichnis.
-
-
+```
-Erstellen Sie mit dem Befehl `npm init` eine Datei namens `package.json` für Ihre Anwendung. Weitere Informationen zur Funktionsweise von `package.json` finden Sie in den [Angaben zur Handhabung der npm-Datei package.json](https://docs.npmjs.com/files/package.json).
+Erstellen Sie mit dem Befehl `npm init` eine Datei namens `package.json` für Ihre Anwendung.
+Weitere Informationen zur Funktionsweise von `package.json` finden Sie in den [Angaben zur Handhabung der npm-Datei package.json](https://docs.npmjs.com/files/package.json).
-
-
+```
-Dieser Befehl fordert Sie zur Eingabe verschiedener Angaben wie Name und Version Ihrer Anwendung auf. Für den Moment reicht es, die Eingabetaste zu drücken und die Standardwerte für die meisten Angaben zu akzeptieren. Es gilt jedoch folgende Ausnahme:
+Dieser Befehl fordert Sie zur Eingabe verschiedener Angaben wie Name und Version Ihrer Anwendung auf.
+For now, you can simply hit RETURN to accept the defaults for most of them, with the following exception:
-
-
+```
Geben Sie `app.js` oder einen Namen Ihrer Vorstellung als Namen für die Hauptdatei ein. Wenn dieser Name `index.js` lauten soll, drücken Sie die Eingabetaste, um den vorgeschlagenen Standarddateinamen zu akzeptieren.
Installieren Sie jetzt Express im Verzeichnis `myapp` und speichern Sie es in der Abhängigkeitsliste. Beispiel:
-
-
+```bash
+$ npm install express
+```
Wenn Sie Express vorübergehend installieren und nicht zur Abhängigkeitsliste hinzufügen wollen, geben Sie die Option `--save` nicht an:
-
-
+```bash
+$ npm install express --no-save
+```
Node-Module, die mit der Option `--save` installiert werden, werden zur `Abhängigkeitsliste` in der Datei `package.json` hinzugefügt. Danach werden bei der Ausführung von `npm install` im Verzeichnis `app` automatisch alle Module in der Abhängigkeitsliste installiert.
+
+### [Next: Hello World ](/{{ page.lang }}/starter/hello-world.html)
\ No newline at end of file
diff --git a/de/starter/static-files.md b/de/starter/static-files.md
old mode 100755
new mode 100644
index 9c6197ee3e..620afe0dc0
--- a/de/starter/static-files.md
+++ b/de/starter/static-files.md
@@ -1,72 +1,79 @@
---
layout: page
title: Statische Dateien in Express bereitstellen
+description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware.
menu: starter
-lang: de
+redirect_from: " "
---
# Statische Dateien in Express bereitstellen
Wenn Sie statische Dateien wie Bilder, CSS-Dateien und JavaScript-Dateien bereitstellen wollen, verwenden Sie die in Express integrierte Middlewarefunktion `express.static`.
-Übergeben Sie den Namen des Verzeichnisses mit den statischen Assets an die Middlewarefunktion `express.static`, um direkt mit dem Bereitstellen der Dateien zu beginnen. Beispiel: Verwenden Sie den folgenden Code, um Bilder, CSS-Dateien und JavaScript-Dateien in einem Verzeichnis namens `public` bereitzustellen:
+The function signature is:
-
-
+```js
+express.static(root, [options])
+```
+
+The `root` argument specifies the root directory from which to serve static assets.
+For more information on the `options` argument, see [express.static](/{{page.lang}}/5x/api.html#express.static).
+
+Beispiel: Verwenden Sie den folgenden Code, um Bilder, CSS-Dateien und JavaScript-Dateien in einem Verzeichnis namens `public` bereitzustellen:
+
+```js
+app.use(express.static('public'))
+```
Jetzt können Sie die Dateien laden, die sich im Verzeichnis `public` befinden:
-
-
+```
-
-Express sucht nach den Dateien, die sich auf das Verzeichnis mit den statischen Assets beziehen. Der Name dieses Verzeichnisses ist also nicht Teil der URL.
+Express sucht nach den Dateien, die sich auf das Verzeichnis mit den statischen Assets beziehen. Der Name dieses Verzeichnisses ist also nicht Teil der URL.
Wenn Sie mehrere Verzeichnisse mit statischen Assets verwenden wollen, rufen Sie die Middlewarefunktion `express.static` mehrmals auf:
-
-
+```js
+app.use(express.static('public'))
+app.use(express.static('files'))
+```
Express sucht in der Reihenfolge nach den Dateien, in der sie die Verzeichnisse mit den statischen Assets über die Middlewarefunktion `express.static` festgelegt haben.
-Wenn Sie ein Präfix für einen virtuellen Pfad (in dem der Pfad nicht wirklich im Dateisystem existiert) für Dateien festlegen wollen, die über die Funktion `express.static` bereitgestellt werden, [müssen Sie einen Mountpfad](/{{ page.lang }}/4x/api.html#app.use) für das Verzeichnis mit den statischen Assets wie unten gezeigt angeben:
+{% capture alert_content %}
+For best results, [use a reverse proxy](/{{page.lang}}/advanced/best-practice-performance.html#use-a-reverse-proxy) cache to improve performance of serving static assets.
+{% endcapture %}
+{% include admonitions/note.html content=alert_content %}
-
-
+To create a virtual path prefix (where the path does not actually exist in the file system) for files that are served by the `express.static` function, [specify a mount path](/{{ page.lang }}/5x/api.html#app.use) for the static directory, as shown below:
+
+```js
+app.use('/static', express.static('public'))
+```
Jetzt können Sie die Dateien, die sich im Verzeichnis `public` befinden, aus dem Pfadpräfix `/static` laden.
-
-
+```
Der Pfad, den Sie für die Funktion `express.static` angeben, ist jedoch relativ zum Verzeichnis, aus dem Sie Ihren Prozess `node` starten. Wenn Sie die Express-Anwendung aus einem anderen Verzeichnis ausführen, ist es sicherer, den absoluten Pfad des Verzeichnisses zu verwenden, das Sie bereitstellen wollen:
-
-
+```js
+const path = require('path')
+app.use('/static', express.static(path.join(__dirname, 'public')))
+```
+
+For more details about the `serve-static` function and its options, see [serve-static](/resources/middleware/serve-static.html).
+
+### [Previous: Basic Routing ](/{{ page.lang }}/starter/basic-routing.html) [Next: More examples ](/{{ page.lang }}/starter/examples.html)
diff --git a/de/support/index.md b/de/support/index.md
new file mode 100644
index 0000000000..3b0c7ad325
--- /dev/null
+++ b/de/support/index.md
@@ -0,0 +1,27 @@
+---
+layout: page
+title: Version-Support
+description: Finden Sie Informationen über den Support-Zeitplan für verschiedene Express.js Versionen, einschließlich der aktuellen Versionen und der End-of-Life-Richtlinien.
+menu: support
+---
+
+# Version-Support
+
+Es wird nur die neueste Version einer bestimmten Hauptversionslinie unterstützt.
+
+Versionen, die EOL (End-of-Life) sind, _können_ Updates für kritische Sicherheitslücken erhalten, aber das Express-Team bietet keine Garantie und plant nicht, Fixes für gefundene Fehler zu entwickeln oder zu veröffentlichen.
+
+| Major Version | Minimale Node.js Version | Support Startdatum | Support-Enddatum |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- | ------------------ | ---------------------------------------------------------------- |
+| [**v5.x**{: .supported }](/{{page.lang}}/5x/api.html){: .ignore-underline} | 18 | September 2024 | **läuft derzeit**{: .supported } |
+| [**v4.x**{: .supported }](/{{page.lang}}/4x/api.html){: .ignore-underline} | 0.10.0 | April 2014 | **läuft derzeit**{: .supported } |
+| [**v3.x**{: .eol }](/{{page.lang}}/3x/api.html){: .ignore-underline} | 0.8.0 | Oktober 2012 | Juli 2015 |
+| [**v2.x**{: .eol }](/2x/){: .ignore-underline} | 0.4.1 | März 2011 | Juli 2012 |
+| **v1.x**{: .eol } | 0.2.0 | Dezember 2010 | März 2011 |
+| **v0.14.x**{: .eol } | 0.1.98 | Dezember 2010 | Dezember 2010 |
+
+## Kommerzielle Support Optionen
+
+Wenn Sie nicht auf eine unterstützte Version von Express aktualisieren können, wenden Sie sich bitte an einen unserer Partner, um Sicherheitsaktualisierungen zu erhalten:
+
+- [HeroDevs Never-Ending Support](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/en/3x/api.md b/en/3x/api.md
index 7421a648df..b421e2afe6 100644
--- a/en/3x/api.md
+++ b/en/3x/api.md
@@ -1,24 +1,27 @@
---
-layout: 3x-api
+layout: api
+version: 3x
title: Express 3.x - API Reference
+description: Access the API reference for Express.js version 3.x, noting that this version is end-of-life and no longer maintained - includes details on modules and methods.
menu: api
-lang: en
redirect_from: "/3x/api.html"
---
- **Express 3.x IS NO LONGER MAINTAINED**
+ **Express 3.x IS END-OF-LIFE AND NO LONGER MAINTAINED**
Known and unknown security and performance issues in 3.x have not been addressed since the last update (1 August, 2015). It is highly recommended to use the latest version of Express.
+
+ If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
3.x API- {% include api/{{ page.lang }}/3x/express.md %} - {% include api/{{ page.lang }}/3x/app.md %} - {% include api/{{ page.lang }}/3x/req.md %} - {% include api/{{ page.lang }}/3x/res.md %} - {% include api/{{ page.lang }}/3x/middleware.md %} + {% include api/en/3x/express.md %} + {% include api/en/3x/app.md %} + {% include api/en/3x/req.md %} + {% include api/en/3x/res.md %} + {% include api/en/3x/middleware.md %}4.x API- {% include api/{{ page.lang }}/4x/express.md %} - {% include api/{{ page.lang }}/4x/app.md %} - {% include api/{{ page.lang }}/4x/req.md %} - {% include api/{{ page.lang }}/4x/res.md %} - {% include api/{{ page.lang }}/4x/router.md %} + {% capture node-version %} + + Express 4.0 requires Node.js 0.10 or higher. + + {% endcapture %} + + {% include admonitions/note.html content=node-version %} + + {% include api/en/4x/express.md %} + {% include api/en/4x/app.md %} + {% include api/en/4x/req.md %} + {% include api/en/4x/res.md %} + {% include api/en/4x/router.md %}5.x API- {% include note.html content="This is early alpha documentation that may be incomplete and is still under development." %} + {% capture node-version %} - {% include api/{{ page.lang }}/5x/express.md %} - {% include api/{{ page.lang }}/5x/app.md %} - {% include api/{{ page.lang }}/5x/req.md %} - {% include api/{{ page.lang }}/5x/res.md %} - {% include api/{{ page.lang }}/5x/router.md %} + Express 5.0 requires Node.js 18 or higher. + + {% endcapture %} + + {% include admonitions/note.html content=node-version %} + + {% include api/en/5x/express.md %} + {% include api/en/5x/app.md %} + {% include api/en/5x/req.md %} + {% include api/en/5x/res.md %} + {% include api/en/5x/router.md %}' + options.message + '') + const rendered = content.toString() + .replace('#title#', `${options.message}`) return callback(null, rendered) }) }) @@ -30,15 +30,15 @@ app.set('view engine', 'ntl') // register the template engine Your app will now be able to render `.ntl` files. Create a file named `index.ntl` in the `views` directory with the following content. -```text +```pug #title# #message# ``` Then, create the following route in your app. ```js -app.get('/', function (req, res) { +app.get('/', (req, res) => { res.render('index', { title: 'Hey', message: 'Hello there!' }) }) ``` -When you make a request to the home page, `index.ntl` will be rendered as HTML. +When you make a request to the home page, `index.ntl` will be rendered as HTML. \ No newline at end of file diff --git a/en/advanced/healthcheck-graceful-shutdown.md b/en/advanced/healthcheck-graceful-shutdown.md index ca1eb19d36..4398238fad 100644 --- a/en/advanced/healthcheck-graceful-shutdown.md +++ b/en/advanced/healthcheck-graceful-shutdown.md @@ -1,8 +1,8 @@ --- layout: page title: Health Checks and Graceful Shutdown +description: Learn how to implement health checks and graceful shutdown in Express apps to enhance reliability, manage deployments, and integrate with load balancers like Kubernetes. menu: advanced -lang: en redirect_from: "/advanced/healthcheck-graceful-shutdown.html" --- @@ -10,9 +10,10 @@ redirect_from: "/advanced/healthcheck-graceful-shutdown.html" ## Graceful shutdown -When you deploy a new version of your application, you must replace the previous version. The [process manager](pm.html) you're using will first send a SIGTERM signal to the application to notify it that it will be killed. Once the application gets this signal, it should stop accepting new requests, finish all the ongoing requests, clean up the resources it used, including database connections and file locks then exit. +When you deploy a new version of your application, you must replace the previous version. The process manager you're using will first send a SIGTERM signal to the application to notify it that it will be killed. Once the application gets this signal, it should stop accepting new requests, finish all the ongoing requests, clean up the resources it used, including database connections and file locks then exit. + +### Example -### Example Graceful Shutdown ```js const server = app.listen(port) @@ -29,153 +30,4 @@ process.on('SIGTERM', () => { A load balancer uses health checks to determine if an application instance is healthy and can accept requests. For example, [Kubernetes has two health checks](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/): * `liveness`, that determines when to restart a container. -* `readiness`, that determines when a container is ready to start accepting traffic. When a pod is not ready, it is removed from the service load balancers. - -## Third-party solutions - -{% include community-caveat.html %} - -### Terminus - -[Terminus](https://github.com/godaddy/terminus) is an open-source project that adds health checks and graceful shutdown to your application to eliminate the need to write boilerplate code. You just provide the cleanup logic for graceful shutdowns and the health check logic for health checks, and terminus handles the rest. - -Install terminus as follows: - -```sh -npm i @godaddy/terminus --save -``` - -Here's a basic template that illustrates using terminus. For more information, see
-Node.js vulnerabilities directly affect Express. Therefore [keep a watch on Node.js vulnerabilities](http://blog.nodejs.org/vulnerability/) and make sure you are using the latest stable version of Node.js.
+Node.js vulnerabilities directly affect Express. Therefore, [keep a watch on Node.js vulnerabilities](https://nodejs.org/en/blog/vulnerability/) and make sure you are using the latest stable version of Node.js.
The list below enumerates the Express vulnerabilities that were fixed in the specified version update.
-**NOTE**: If you believe you have discovered a security vulnerability in Express, please see
+
+{% capture security-policy %}
+If you believe you have discovered a security vulnerability in Express, please see
[Security Policies and Procedures](/{{page.lang}}/resources/contributing.html#security-policies-and-procedures).
+{% endcapture %}
-## 4.x
+{% include admonitions/note.html content=security-policy %}
+## 4.x
+ * 4.21.2
+ * The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
+ * 4.21.1
+ * The dependency `cookie` has been updated to address a [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), This may affect your application if you use `res.cookie`.
+ * 4.20.0
+ * Fixed XSS vulnerability in `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
+ * The dependency `serve-static` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p).
+ * The dependency `send` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
+ * The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
+ * The dependency `body-parser` has been updated to addres a [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), This may affect your application if you had url enconding activated.
+ * 4.19.0, 4.19.1
+ * Fixed open redirect vulnerability in `res.location` and `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
+ * 4.17.3
+ * The dependency `qs` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp). This may affect your application if the following APIs are used: `req.query`, `req.body`, `req.param`.
* 4.16.0
* The dependency `forwarded` has been updated to address a [vulnerability](https://npmjs.com/advisories/527). This may affect your application if the following APIs are used: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
* The dependency `mime` has been updated to address a [vulnerability](https://npmjs.com/advisories/535), but this issue does not impact Express.
@@ -44,9 +63,11 @@ The list below enumerates the Express vulnerabilities that were fixed in the spe
## 3.x
- **Express 3.x IS NO LONGER MAINTAINED**
+ **Express 3.x IS END-OF-LIFE AND NO LONGER MAINTAINED**
+
+ Known and unknown security and performance issues in 3.x have not been addressed since the last update (1 August, 2015). It is highly recommended to use the latest version of Express.
- Known and unknown security issues in 3.x have not been addressed since the last update (1 August, 2015). Using the 3.x line should not be considered secure.
+ If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
* 3.19.1
@@ -61,4 +82,4 @@ The list below enumerates the Express vulnerabilities that were fixed in the spe
* Sparse arrays that have extremely high indexes in query string could cause the process to run out of memory and crash the server.
* Extremely nested query string objects could cause the process to block and make the server unresponsive temporarily.
* 3.3.0
- * The 404 response of an unsupported method override attempt was susceptible to cross-site scripting attacks.
+ * The 404 response of an unsupported method override attempt was susceptible to cross-site scripting attacks.
\ No newline at end of file
diff --git a/en/api.md b/en/api.md
index 16227d369e..41382818cc 100644
--- a/en/api.md
+++ b/en/api.md
@@ -1,26 +1,21 @@
---
-layout: 4x-api
-title: Express 4.x - API Reference
-lang: en
+layout: api
+version: 5x
+title: Express 5.x - API Reference
+description: Access the API reference for Express.js detailing all modules, methods, and properties for building web applications with this version.
+menu: api
redirect_from: "/api.html"
---
-
-
diff --git a/en/blog/posts.md b/en/blog/posts.md
new file mode 100644
index 0000000000..b5be34e66c
--- /dev/null
+++ b/en/blog/posts.md
@@ -0,0 +1,28 @@
+---
+layout: post
+title: Express Blog Posts
+description: Explore the latest articles, announcements, and updates from the Express.js team and community on the Express blog.
+menu: blog
+redirect_from: "/blog/posts.html"
+---
+
+Want to write a post? See the submission [guidelines.](/en/blog/write-post.html)
+
+{% if site.posts.size != 0 %}
+4.x API- +5.x API- {% include api/{{ page.lang }}/4x/express.md %} - + {% include api/en/5x/express.md %} - {% include api/{{ page.lang }}/4x/app.md %} - + {% include api/en/5x/app.md %} - {% include api/{{ page.lang }}/4x/req.md %} - + {% include api/en/5x/req.md %} - {% include api/{{ page.lang }}/4x/res.md %} - + {% include api/en/5x/res.md %} - {% include api/{{ page.lang }}/4x/router.md %} - + {% include api/en/5x/router.md %}
+{% for post in site.posts %}
+
+{% else %}
+ There are currently no blog posts.
+{% endif %}
diff --git a/en/blog/write-post.md b/en/blog/write-post.md
new file mode 100644
index 0000000000..21cfc5b4b3
--- /dev/null
+++ b/en/blog/write-post.md
@@ -0,0 +1,51 @@
+---
+layout: post
+title: How to write a blog post
+description: Learn how to propose and write a blog post for the Express.js blog, including submission guidelines and steps to contribute your content.
+menu: blog
+redirect_from: "/blog/write.html"
+---
+
+
+
+If you have an idea for a blog post, follow these steps to propose it and potentially get it published!
+
+1. ### Propose your post
+Before taking the time to write a post, please confirm that we will be able to publish it. We're looking for topics specifically related to Express, and so we want to pre-approve all posts. For the moment, this means we aren't accepting any unsolicited posts. To propose a blog post, [open an issue](https://github.com/expressjs/expressjs.com/issues) entitled `Blog post proposal:
+
+{% endfor %}
+
+ {{ post.title }}
+
+
+ {% include blog/authors.html authors=post.authors %}
+
+ {{ post.date | date:"%b %d, %Y" }}
+ {{post.excerpt | truncate: 240 | markdownify }}
+
+
+# Release changelog
+
+All the latest updates, improvements, and fixes to Express
+
+## Express v5
+{: id="5.x"}
+
+### 5.1.0 - Release date: 2025-03-31
+{: id="5.0.1"}
+
+The 5.1.0 minor release includes some new features and improvements:
+
+* Support for sending responses as Uint8Array
+* Added support for ETag option in `res.sendFile()`
+* Added support for adding multiple links with the same rel with `res.links()`
+* Performance: Use loop for acceptParams
+* [body-parser@2.2.0](https://github.com/expressjs/body-parser/releases/tag/v2.2.0)
+ * Remove legacy node.js support checks for Brotli & `AsyncLocalStorage`
+ * Remove `unpipe` & `destroy`
+* [router@2.2.0](https://github.com/pillarjs/router/releases/tag/v2.2.0)
+ * Restore `debug`. Now with the `router` scope instead of `express`.
+ * Remove legacy node.js support checks for `setImmediate`
+ * Deprecate non-native promise support
+ * Remove `after`, `safe-buffer`, `array-flatten`, `setprotoypeof`, `methods`, `utils-merge`
+* [finalhandler@2.1.0](https://github.com/pillarjs/finalhandler/releases/tag/v2.1.0)
+ * Remove legacy node.js support checks for `headersSent`, `setImmediate`, & http2 support
+ * Remove `unpipe`
+* Transitioned all remaining dependencies to use `^` ranges instead of locked versions
+* Add package.json funding field to highlight our OpenCollective
+* See [Changelog v5.1.0](https://github.com/expressjs/express/releases/tag/v5.1.0)
+### 5.0.1 - Release date: 2024-10-08
+{: id="5.0.1"}
+
+The 5.0.1 patch release includes one security fix:
+
+* Update [jshttps/cookie](https://www.npmjs.com/package/cookie) to address a [vulnerability](https://github.com/advisories/GHSA-pxg6-pf52-xh8x).
+
+### 5.0.0 - Release date: 2024-09-09
+{: id="5.0.0"}
+
+Check the [migration guide](/{{page.lang}}/guide/migrating-5.html) with all the changes in this new version of Express.
+
+## Express v4
+{: id="4.x"}
+
+### 4.21.2 - Release date: 2024-11-06
+{: id="4.21.2"}
+
+The 4.21.2 patch release includes one security fix:
+
+* Update [pillajs/path-to-regexp](https://www.npmjs.com/package/path-to-regexp) to address a [vulnerability](https://github.com/advisories/GHSA-rhx6-c78j-4q9w).
+
+### 4.21.1 - Release date: 2024-10-08
+{: id="4.21.1"}
+
+The 4.21.1 patch release includes one security fix:
+
+* Update [jshttps/cookie](https://www.npmjs.com/package/cookie) to address a [vulnerability](https://github.com/advisories/GHSA-pxg6-pf52-xh8x).
+
+### 4.21.0 - Release date: 2024-09-11
+{: id="4.21.0"}
+
+The 4.21.0 minor release includes one new feature:
+
+* Deprecate `res.location("back")` and `res.redirect("back")` magic string
+
+### 4.20.0 - Release date: 2024-09-10
+{: id="4.20.0"}
+
+The 4.20.0 minor release includes bug fixes and some new features, including:
+
+* The [`res.clearCookie()` method](/{{ page.lang }}/4x/api.html#res.clearCookie) deprecates `options.maxAge` and `options.expires` options.
+* The [`res.redirect()` method](/{{ page.lang }}/4x/api.html#res.redirect) removes HTML link rendering.
+* The [`express.urlencoded()` method](/{{ page.lang }}/4x/api.html#express.urlencoded) method now has a depth level of `32`, whereas it was previously `Infinity`.
+* Adds support for named matching groups in the routes using a regex
+* Removes encoding of `\`, `|`, and `^` to align better with URL spec
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4200--2024-09-10)
+
+### 4.19.2 - Release date: 2024-03-25
+{: id="4.19.2"}
+
+* Improved fix for open redirect allow list bypass
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4192--2024-03-25)
+
+### 4.19.1 - Release date: 2024-03-20
+{: id="4.19.1"}
+
+* Allow passing non-strings to res.location with new encoding handling checks
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4191--2024-03-20)
+
+### 4.19.0 - Release date: 2024-03-20
+{: id="4.19.0"}
+
+* Prevent open redirect allow list bypass due to encodeurl
+* deps: cookie@0.6.0
+
+For a complete list of changes in this release, see [History.md](https://github.com/expressjs/express/blob/master/History.md#4190--2024-03-20)
+
+### 4.18.3 - Release date: 2024-02-29
+{: id="4.18.3"}
+
+The 4.18.3 patch release includes the following bug fix:
+
+
|
+ 
+ 
+ 
+