From f0ed36227a730e4ba1da6d1a9193b42739a50d1c Mon Sep 17 00:00:00 2001 From: Crowdin Bot Date: Mon, 17 Nov 2025 08:07:00 +0000 Subject: [PATCH] New Crowdin translations by GitHub Action --- _data/ko/menu.yml | 4 +- _data/pt-br/general.yml | 16 ++-- _data/pt-br/menu.yml | 14 ++-- de/advanced/best-practice-performance.md | 1 + de/advanced/best-practice-security.md | 1 + de/advanced/developing-template-engines.md | 1 + de/advanced/healthcheck-graceful-shutdown.md | 1 + de/advanced/security-updates.md | 1 + de/guide/behind-proxies.md | 1 + de/guide/database-integration.md | 1 + de/guide/debugging.md | 1 + de/guide/error-handling.md | 1 + de/guide/migrating-4.md | 9 ++- de/guide/migrating-5.md | 3 +- de/guide/overriding-express-api.md | 1 + de/guide/routing.md | 1 + de/guide/using-middleware.md | 1 + de/guide/using-template-engines.md | 1 + de/guide/writing-middleware.md | 1 + de/resources/community.md | 1 + de/resources/contributing.md | 77 ++++++++++++------- de/resources/glossary.md | 1 + de/resources/middleware.md | 1 + de/resources/utils.md | 1 + de/starter/basic-routing.md | 4 +- de/starter/examples.md | 6 +- de/starter/faq.md | 5 +- de/starter/generator.md | 5 +- de/starter/hello-world.md | 5 +- de/starter/installing.md | 5 +- de/starter/static-files.md | 5 +- es/advanced/best-practice-performance.md | 1 + es/advanced/best-practice-security.md | 1 + es/advanced/developing-template-engines.md | 1 + es/advanced/healthcheck-graceful-shutdown.md | 1 + es/advanced/security-updates.md | 1 + es/guide/behind-proxies.md | 1 + es/guide/database-integration.md | 1 + es/guide/debugging.md | 1 + es/guide/error-handling.md | 1 + es/guide/migrating-4.md | 9 ++- es/guide/migrating-5.md | 3 +- es/guide/overriding-express-api.md | 1 + es/guide/routing.md | 1 + es/guide/using-middleware.md | 1 + es/guide/using-template-engines.md | 1 + es/guide/writing-middleware.md | 1 + es/resources/community.md | 5 +- es/resources/contributing.md | 77 ++++++++++++------- es/resources/glossary.md | 1 + es/resources/middleware.md | 1 + es/resources/utils.md | 1 + es/starter/basic-routing.md | 4 +- es/starter/examples.md | 6 +- es/starter/faq.md | 5 +- es/starter/generator.md | 5 +- es/starter/hello-world.md | 5 +- es/starter/installing.md | 5 +- es/starter/static-files.md | 5 +- fr/advanced/best-practice-performance.md | 1 + fr/advanced/best-practice-security.md | 1 + fr/advanced/developing-template-engines.md | 1 + fr/advanced/healthcheck-graceful-shutdown.md | 1 + fr/advanced/security-updates.md | 1 + fr/guide/behind-proxies.md | 1 + fr/guide/database-integration.md | 1 + fr/guide/debugging.md | 1 + fr/guide/error-handling.md | 1 + fr/guide/migrating-4.md | 15 ++-- fr/guide/migrating-5.md | 3 +- fr/guide/overriding-express-api.md | 1 + fr/guide/routing.md | 1 + fr/guide/using-middleware.md | 1 + fr/guide/using-template-engines.md | 1 + fr/guide/writing-middleware.md | 1 + fr/resources/community.md | 1 + fr/resources/contributing.md | 77 ++++++++++++------- fr/resources/glossary.md | 1 + fr/resources/middleware.md | 1 + fr/resources/utils.md | 1 + fr/starter/basic-routing.md | 4 +- fr/starter/examples.md | 6 +- fr/starter/faq.md | 5 +- fr/starter/generator.md | 5 +- fr/starter/hello-world.md | 5 +- fr/starter/installing.md | 5 +- fr/starter/static-files.md | 5 +- it/advanced/best-practice-performance.md | 1 + it/advanced/best-practice-security.md | 1 + it/advanced/developing-template-engines.md | 1 + it/advanced/healthcheck-graceful-shutdown.md | 1 + it/advanced/security-updates.md | 1 + it/guide/behind-proxies.md | 1 + it/guide/database-integration.md | 1 + it/guide/debugging.md | 1 + it/guide/error-handling.md | 1 + it/guide/migrating-4.md | 15 ++-- it/guide/migrating-5.md | 3 +- it/guide/overriding-express-api.md | 1 + it/guide/routing.md | 1 + it/guide/using-middleware.md | 1 + it/guide/using-template-engines.md | 1 + it/guide/writing-middleware.md | 1 + it/resources/community.md | 1 + it/resources/contributing.md | 77 ++++++++++++------- it/resources/glossary.md | 1 + it/resources/middleware.md | 1 + it/resources/utils.md | 1 + it/starter/basic-routing.md | 4 +- it/starter/examples.md | 6 +- it/starter/faq.md | 5 +- it/starter/generator.md | 5 +- it/starter/hello-world.md | 5 +- it/starter/installing.md | 5 +- it/starter/static-files.md | 5 +- ja/advanced/best-practice-performance.md | 1 + ja/advanced/best-practice-security.md | 1 + ja/advanced/developing-template-engines.md | 1 + ja/advanced/healthcheck-graceful-shutdown.md | 1 + ja/advanced/security-updates.md | 1 + ja/guide/behind-proxies.md | 1 + ja/guide/database-integration.md | 1 + ja/guide/debugging.md | 1 + ja/guide/error-handling.md | 1 + ja/guide/migrating-4.md | 5 +- ja/guide/migrating-5.md | 3 +- ja/guide/overriding-express-api.md | 1 + ja/guide/routing.md | 1 + ja/guide/using-middleware.md | 1 + ja/guide/using-template-engines.md | 1 + ja/guide/writing-middleware.md | 1 + ja/resources/community.md | 1 + ja/resources/contributing.md | 77 ++++++++++++------- ja/resources/glossary.md | 1 + ja/resources/middleware.md | 1 + ja/resources/utils.md | 1 + ja/starter/basic-routing.md | 4 +- ja/starter/examples.md | 6 +- ja/starter/faq.md | 5 +- ja/starter/generator.md | 5 +- ja/starter/hello-world.md | 5 +- ja/starter/installing.md | 5 +- ja/starter/static-files.md | 5 +- ko/advanced/best-practice-performance.md | 1 + ko/advanced/best-practice-security.md | 7 +- ko/advanced/developing-template-engines.md | 1 + ko/advanced/healthcheck-graceful-shutdown.md | 1 + ko/advanced/security-updates.md | 1 + ko/guide/behind-proxies.md | 1 + ko/guide/database-integration.md | 1 + ko/guide/debugging.md | 1 + ko/guide/error-handling.md | 1 + ko/guide/migrating-4.md | 15 ++-- ko/guide/migrating-5.md | 3 +- ko/guide/overriding-express-api.md | 1 + ko/guide/routing.md | 1 + ko/guide/using-middleware.md | 1 + ko/guide/using-template-engines.md | 1 + ko/guide/writing-middleware.md | 1 + ko/resources/community.md | 1 + ko/resources/contributing.md | 77 ++++++++++++------- ko/resources/glossary.md | 1 + ko/resources/middleware.md | 1 + ko/resources/utils.md | 1 + ko/starter/basic-routing.md | 4 +- ko/starter/examples.md | 6 +- ko/starter/faq.md | 5 +- ko/starter/generator.md | 5 +- ko/starter/hello-world.md | 5 +- ko/starter/installing.md | 5 +- ko/starter/static-files.md | 5 +- pt-br/3x/api.md | 6 +- pt-br/4x/api.md | 4 +- pt-br/5x/api.md | 4 +- pt-br/advanced/best-practice-performance.md | 30 +++++--- pt-br/advanced/best-practice-security.md | 1 + pt-br/advanced/developing-template-engines.md | 1 + .../advanced/healthcheck-graceful-shutdown.md | 1 + pt-br/advanced/security-updates.md | 3 +- pt-br/api.md | 2 +- pt-br/changelog/index.md | 4 +- pt-br/guide/behind-proxies.md | 1 + pt-br/guide/database-integration.md | 12 +-- pt-br/guide/debugging.md | 3 +- pt-br/guide/error-handling.md | 1 + pt-br/guide/migrating-4.md | 15 ++-- pt-br/guide/migrating-5.md | 7 +- pt-br/guide/overriding-express-api.md | 1 + pt-br/guide/routing.md | 1 + pt-br/guide/using-middleware.md | 1 + pt-br/guide/using-template-engines.md | 1 + pt-br/guide/writing-middleware.md | 1 + pt-br/index.md | 19 +++-- pt-br/resources/community.md | 17 ++-- pt-br/resources/contributing.md | 77 ++++++++++++------- pt-br/resources/glossary.md | 3 +- pt-br/resources/middleware.md | 49 ++++++------ pt-br/resources/utils.md | 1 + pt-br/starter/basic-routing.md | 4 +- pt-br/starter/examples.md | 5 +- pt-br/starter/faq.md | 5 +- pt-br/starter/generator.md | 5 +- pt-br/starter/hello-world.md | 5 +- pt-br/starter/installing.md | 5 +- pt-br/starter/static-files.md | 5 +- pt-br/support/index.md | 24 +++--- zh-cn/advanced/best-practice-performance.md | 1 + zh-cn/advanced/best-practice-security.md | 1 + zh-cn/advanced/developing-template-engines.md | 1 + .../advanced/healthcheck-graceful-shutdown.md | 1 + zh-cn/advanced/security-updates.md | 1 + zh-cn/guide/behind-proxies.md | 1 + zh-cn/guide/database-integration.md | 1 + zh-cn/guide/debugging.md | 1 + zh-cn/guide/error-handling.md | 1 + zh-cn/guide/migrating-4.md | 5 +- zh-cn/guide/migrating-5.md | 3 +- zh-cn/guide/overriding-express-api.md | 1 + zh-cn/guide/routing.md | 5 +- zh-cn/guide/using-middleware.md | 1 + zh-cn/guide/using-template-engines.md | 1 + zh-cn/guide/writing-middleware.md | 1 + zh-cn/resources/community.md | 1 + zh-cn/resources/contributing.md | 77 ++++++++++++------- zh-cn/resources/glossary.md | 1 + zh-cn/resources/middleware.md | 1 + zh-cn/resources/utils.md | 1 + zh-cn/starter/basic-routing.md | 4 +- zh-cn/starter/examples.md | 6 +- zh-cn/starter/faq.md | 5 +- zh-cn/starter/generator.md | 5 +- zh-cn/starter/hello-world.md | 5 +- zh-cn/starter/installing.md | 5 +- zh-cn/starter/static-files.md | 5 +- zh-tw/advanced/best-practice-performance.md | 1 + zh-tw/advanced/best-practice-security.md | 1 + zh-tw/advanced/developing-template-engines.md | 1 + .../advanced/healthcheck-graceful-shutdown.md | 1 + zh-tw/advanced/security-updates.md | 1 + zh-tw/guide/behind-proxies.md | 1 + zh-tw/guide/database-integration.md | 1 + zh-tw/guide/debugging.md | 1 + zh-tw/guide/error-handling.md | 1 + zh-tw/guide/migrating-4.md | 7 +- zh-tw/guide/migrating-5.md | 3 +- zh-tw/guide/overriding-express-api.md | 1 + zh-tw/guide/routing.md | 1 + zh-tw/guide/using-middleware.md | 1 + zh-tw/guide/using-template-engines.md | 1 + zh-tw/guide/writing-middleware.md | 1 + zh-tw/resources/community.md | 1 + zh-tw/resources/contributing.md | 77 ++++++++++++------- zh-tw/resources/glossary.md | 1 + zh-tw/resources/middleware.md | 1 + zh-tw/resources/utils.md | 1 + zh-tw/starter/basic-routing.md | 4 +- zh-tw/starter/examples.md | 6 +- zh-tw/starter/faq.md | 5 +- zh-tw/starter/generator.md | 5 +- zh-tw/starter/hello-world.md | 5 +- zh-tw/starter/installing.md | 5 +- zh-tw/starter/static-files.md | 5 +- 262 files changed, 922 insertions(+), 594 deletions(-) diff --git a/_data/ko/menu.yml b/_data/ko/menu.yml index 7cbe974ce9..c5469f8c10 100644 --- a/_data/ko/menu.yml +++ b/_data/ko/menu.yml @@ -8,7 +8,7 @@ static_files: 정적 파일 examples: 더 많은 예시 faq: 자주 묻는 질문(FAQ) # Guide -guide: Gu안내서ide +guide: 안내서 routing: 라우팅 writing_middleware: 미들웨어 작성 using_middleware: 미들웨어 사용 @@ -44,7 +44,7 @@ changelog: 릴리즈 변경 로그 # Support support: 지원 # Blog -blog: Blog +blog: 블로그 latest_post: 최신 게시물 all_posts: 모든 게시물 write_post: 게시물 작성 diff --git a/_data/pt-br/general.yml b/_data/pt-br/general.yml index e6327e6214..3544c6811b 100644 --- a/_data/pt-br/general.yml +++ b/_data/pt-br/general.yml @@ -1,8 +1,8 @@ -title_announcement: "Express@5.1.0: Now the Default on npm with LTS Timeline" -body_announcement: "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. Check out our latest blog for more information." -community-caveat-alert: "This information refers to third-party sites, products, or modules that are not maintained by the Expressjs team. Listing here does not constitute an endorsement or recommendation from the Expressjs project team." -warning: 'Warning' -note: 'Note' -caution: 'Caution' -i18n_notice: "This document might be outdated relative to the documentation in English. For the latest updates, please refer to the" -i18n_notice_link_text: "documentation in english" +title_announcement: "Express@5.1.0: Agora o Padrão no npm com LTS Timeline" +body_announcement: "Expresse 5.1.0 agora é o padrão do npm, e estamos introduzindo um cronograma oficial de LTS para as linhas de lançamento v4 e v5. Confira nosso último blog para obter mais informações." +community-caveat-alert: "Esta informação refere-se a sites de terceiros, produtos ou módulos que não são mantidos pela equipe do Expressjs. A listagem aqui não constitui um endosso ou recomendação da equipe de projeto Expressjs." +warning: 'Atenção' +note: 'Observação' +caution: 'Atenção' +i18n_notice: "Este documento pode estar desatualizado em relação à documentação em inglês. Para as últimas atualizações, por favor consulte o" +i18n_notice_link_text: "documentação em inglês" diff --git a/_data/pt-br/menu.yml b/_data/pt-br/menu.yml index d65c2ca623..bc96d7b422 100644 --- a/_data/pt-br/menu.yml +++ b/_data/pt-br/menu.yml @@ -1,18 +1,18 @@ # Getting started getting_started: Introdução installing: Instalação -hello_world: Hello world +hello_world: Olá mundo generator: Gerador do Express basic_routing: Roteamento Básico static_files: Arquivos Estáticos examples: Perguntas mais frequentes faq: Perguntas mais frequentes # Guide -guide: Guide +guide: Guia routing: Roteamento writing_middleware: Escrevendo o middleware using_middleware: Usando o middleware -overriding_express_api: Overriding the Express API +overriding_express_api: Sobrescrevendo a API Express using_template_engines: Usando o mecanismo de modelo error_handling: Manipulação de erros debugging: Depuração @@ -32,15 +32,15 @@ developing_template_engines: Mecanismos de modelo security_updates: Atualizações de segurança best_practice_security: Melhores práticas de segurança best_practice_performance: Melhores práticas de desempenho -healthcheck_graceful_shutdown: Health checks & shutdown +healthcheck_graceful_shutdown: Verificações de saúde e desligamento # Resources resources: Recursos glossary: Glossário middleware: Middleware community: Comunidade -utils: Utility modules -contributing: Contributing to Express -changelog: Release Change Log +utils: Módulos utilitários +contributing: Contribuindo para o Express +changelog: Registros de alterações # Support support: Suporte # Blog diff --git a/de/advanced/best-practice-performance.md b/de/advanced/best-practice-performance.md index c66899b35d..9ea397be26 100644 --- a/de/advanced/best-practice-performance.md +++ b/de/advanced/best-practice-performance.md @@ -3,6 +3,7 @@ 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 +order: 4 redirect_from: " " --- diff --git a/de/advanced/best-practice-security.md b/de/advanced/best-practice-security.md index 8f4f23219d..75d473657d 100644 --- a/de/advanced/best-practice-security.md +++ b/de/advanced/best-practice-security.md @@ -3,6 +3,7 @@ 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 +order: 3 redirect_from: " " --- diff --git a/de/advanced/developing-template-engines.md b/de/advanced/developing-template-engines.md index 5832050244..82f5e3b8ed 100644 --- a/de/advanced/developing-template-engines.md +++ b/de/advanced/developing-template-engines.md @@ -3,6 +3,7 @@ layout: page title: Template-Engines für Express entwickeln 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 +order: 1 redirect_from: " " --- diff --git a/de/advanced/healthcheck-graceful-shutdown.md b/de/advanced/healthcheck-graceful-shutdown.md index c1da62bfca..0f508986cc 100644 --- a/de/advanced/healthcheck-graceful-shutdown.md +++ b/de/advanced/healthcheck-graceful-shutdown.md @@ -3,6 +3,7 @@ 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 +order: 5 redirect_from: " " --- diff --git a/de/advanced/security-updates.md b/de/advanced/security-updates.md index e882a9af54..eb001048c0 100644 --- a/de/advanced/security-updates.md +++ b/de/advanced/security-updates.md @@ -3,6 +3,7 @@ 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 +order: 2 redirect_from: " " --- diff --git a/de/guide/behind-proxies.md b/de/guide/behind-proxies.md index 6dab4f9521..3bf62362de 100644 --- a/de/guide/behind-proxies.md +++ b/de/guide/behind-proxies.md @@ -3,6 +3,7 @@ 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 +order: 8 redirect_from: " " --- diff --git a/de/guide/database-integration.md b/de/guide/database-integration.md index 3b20abc348..0a39aab7ea 100644 --- a/de/guide/database-integration.md +++ b/de/guide/database-integration.md @@ -3,6 +3,7 @@ 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 +order: 11 redirect_from: " " --- diff --git a/de/guide/debugging.md b/de/guide/debugging.md index 0661aaf8b3..570e26d6d7 100644 --- a/de/guide/debugging.md +++ b/de/guide/debugging.md @@ -3,6 +3,7 @@ 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 +order: 7 redirect_from: " " --- diff --git a/de/guide/error-handling.md b/de/guide/error-handling.md index 1ffb0f9738..54c252ea71 100644 --- a/de/guide/error-handling.md +++ b/de/guide/error-handling.md @@ -3,6 +3,7 @@ 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 +order: 6 redirect_from: " " --- diff --git a/de/guide/migrating-4.md b/de/guide/migrating-4.md index ddfe05f09a..2292800f1a 100644 --- a/de/guide/migrating-4.md +++ b/de/guide/migrating-4.md @@ -3,6 +3,7 @@ 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 +order: 9 redirect_from: " " --- @@ -366,12 +367,12 @@ $ npm install serve-favicon morgan method-override express-session body-parser m 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);`. + 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. diff --git a/de/guide/migrating-5.md b/de/guide/migrating-5.md index af9d495fd5..c4c8c97b08 100644 --- a/de/guide/migrating-5.md +++ b/de/guide/migrating-5.md @@ -3,6 +3,7 @@ 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 +order: 10 redirect_from: " " --- @@ -259,7 +260,7 @@ app.get('/user', (req, res) => {

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. +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: diff --git a/de/guide/overriding-express-api.md b/de/guide/overriding-express-api.md index 032e3dd625..5210622ff2 100644 --- a/de/guide/overriding-express-api.md +++ b/de/guide/overriding-express-api.md @@ -3,6 +3,7 @@ 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 +order: 4 --- # Overriding the Express API diff --git a/de/guide/routing.md b/de/guide/routing.md index 29fdb6431c..7baf1ad12c 100644 --- a/de/guide/routing.md +++ b/de/guide/routing.md @@ -3,6 +3,7 @@ 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 +order: 1 redirect_from: " " --- diff --git a/de/guide/using-middleware.md b/de/guide/using-middleware.md index 0d1baea51c..4e67b123c3 100644 --- a/de/guide/using-middleware.md +++ b/de/guide/using-middleware.md @@ -3,6 +3,7 @@ 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 +order: 3 redirect_from: " " --- diff --git a/de/guide/using-template-engines.md b/de/guide/using-template-engines.md index abce1f7ffd..7dd34574e1 100644 --- a/de/guide/using-template-engines.md +++ b/de/guide/using-template-engines.md @@ -3,6 +3,7 @@ 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 +order: 5 redirect_from: " " --- diff --git a/de/guide/writing-middleware.md b/de/guide/writing-middleware.md index c4d5653244..d36e06e9f1 100644 --- a/de/guide/writing-middleware.md +++ b/de/guide/writing-middleware.md @@ -3,6 +3,7 @@ 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 +order: 2 redirect_from: " " --- diff --git a/de/resources/community.md b/de/resources/community.md index 1fe956ad5c..1fc9cecffd 100644 --- a/de/resources/community.md +++ b/de/resources/community.md @@ -3,6 +3,7 @@ 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 +order: 1 redirect_from: " " --- diff --git a/de/resources/contributing.md b/de/resources/contributing.md index e37cee3122..b0944346a1 100644 --- a/de/resources/contributing.md +++ b/de/resources/contributing.md @@ -3,6 +3,7 @@ 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 +order: 5 redirect_from: " " --- @@ -87,7 +88,7 @@ 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). +[the triage process document](https://github.com/expressjs/discussions/blob/master/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 @@ -182,6 +183,26 @@ The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/doc 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) +### Inactivity and Emeritus Policy for Any Role + +To support the health and continuity of the project, all individuals holding a role within the community (such as Triager, Committer, WG member, Project Captain, or TC member) are encouraged to maintain active participation. + +Inactivity is defined as the absence of meaningful involvement in the project—such as contributions, code reviews, triage, meeting attendance, or discussion participation—for a continuous period of 6 months. + +#### Exceptions + +Anyone may request a temporary leave from active participation due to personal or professional reasons. In such cases, the individual should inform the relevant team or the Technical Committee (TC). During this time, the inactivity policy is paused, and the individual will not be flagged as inactive. + +#### Inactivity Process + +- If someone is deemed inactive, the individual may be transitioned to an emeritus role that reflects their past contributions. A best effort will be made to inform them that this has occurred. They may request to be reinstated when they are ready to be active again. +- The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time. + +#### Accountability + +- The Technical Committee (TC) and the respective captains of each package/team are responsible for assessing activity levels and enacting this policy fairly and transparently, in coordination with other relevant teams. +- In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team. + ### Developer's Certificate of Origin 1.1 ```text @@ -237,18 +258,18 @@ 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. + bug you want to fix or the feature that you want to add. 2. Create your own fork on GitHub, then - checkout your fork. + 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. + 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`. + then run `npm test`. 5. Ensure your code is linted by running `npm run lint` -- fix any issue you - see listed. + 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`. + 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 @@ -346,22 +367,22 @@ This is the contribution documentation for the [expressjs.com](https://github.co #### 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 + - 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 + - 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. + - 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? @@ -384,12 +405,12 @@ The steps below will guide you through the Expressjs.com contribution process. 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. + - 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. + - For submissions proposing significant change, we encourage you to follow the review process before starting work. #### Step 2: Get the Application Code Base @@ -434,12 +455,12 @@ The Express JS website is built using [Jekyll](https://jekyllrb.com/) and is hos 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. + - 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. + 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 diff --git a/de/resources/glossary.md b/de/resources/glossary.md index 991a7a584a..bbbd9f6eca 100644 --- a/de/resources/glossary.md +++ b/de/resources/glossary.md @@ -3,6 +3,7 @@ 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 +order: 2 redirect_from: " " --- diff --git a/de/resources/middleware.md b/de/resources/middleware.md index 6342018377..3657f5b2ba 100644 --- a/de/resources/middleware.md +++ b/de/resources/middleware.md @@ -3,6 +3,7 @@ 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 +order: 3 redirect_from: " " module: mw-home --- diff --git a/de/resources/utils.md b/de/resources/utils.md index 0fd21eea69..f5ba489b99 100644 --- a/de/resources/utils.md +++ b/de/resources/utils.md @@ -3,6 +3,7 @@ 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 +order: 4 redirect_from: " " --- diff --git a/de/starter/basic-routing.md b/de/starter/basic-routing.md index eaed71d21a..e264e27975 100644 --- a/de/starter/basic-routing.md +++ b/de/starter/basic-routing.md @@ -3,6 +3,7 @@ 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 +order: 4 redirect_from: " " --- @@ -21,7 +22,7 @@ app.METHOD(PATH, HANDLER) Where: - `app` ist eine Instanz von `express`. -- `METHOD` ist eine [HTTP-Anforderungsmethode](http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol). +- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase. - `PATH` ist ein Pfad auf dem Server. - `HANDLER` ist die Funktion, die ausgeführt wird, wenn die Weiterleitung abgeglichen wird. @@ -65,4 +66,3 @@ app.delete('/user', (req, res) => { 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 index 56da2d1a3c..86700f94c3 100644 --- a/de/starter/examples.md +++ b/de/starter/examples.md @@ -3,6 +3,7 @@ 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 +order: 6 redirect_from: " " --- @@ -15,6 +16,5 @@ These are some additional examples with more extensive integrations. {% include community-caveat.html %} -- [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) +- [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 \ No newline at end of file diff --git a/de/starter/faq.md b/de/starter/faq.md index 178246ecea..3769257e13 100644 --- a/de/starter/faq.md +++ b/de/starter/faq.md @@ -3,6 +3,7 @@ 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 +order: 7 redirect_from: " " --- @@ -75,6 +76,4 @@ Wenn Sie viele Assets aus einem Verzeichnis bedienen müssen, verwenden Sie die ## 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) +- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher. \ No newline at end of file diff --git a/de/starter/generator.md b/de/starter/generator.md index f59f6e1d1a..e0c0a551ac 100644 --- a/de/starter/generator.md +++ b/de/starter/generator.md @@ -3,6 +3,7 @@ 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 +order: 3 redirect_from: " " --- @@ -122,6 +123,4 @@ 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) + \ No newline at end of file diff --git a/de/starter/hello-world.md b/de/starter/hello-world.md index 3fd33c8743..ea21ea36ff 100644 --- a/de/starter/hello-world.md +++ b/de/starter/hello-world.md @@ -3,6 +3,7 @@ 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 +order: 2 redirect_from: " " --- @@ -42,6 +43,4 @@ Führen Sie die Anwendung mit dem folgenden Befehl aus: $ 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) +Laden Sie dann [http://localhost:3000/](http://localhost:3000/) in einen Browser, um die Ausgabe zu sehen. \ No newline at end of file diff --git a/de/starter/installing.md b/de/starter/installing.md index e745549656..7e2b55fc4b 100644 --- a/de/starter/installing.md +++ b/de/starter/installing.md @@ -3,6 +3,7 @@ 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 +order: 1 redirect_from: " " --- @@ -48,6 +49,4 @@ $ 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 + \ No newline at end of file diff --git a/de/starter/static-files.md b/de/starter/static-files.md index 620afe0dc0..79258d1360 100644 --- a/de/starter/static-files.md +++ b/de/starter/static-files.md @@ -3,6 +3,7 @@ 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 +order: 5 redirect_from: " " --- @@ -74,6 +75,4 @@ 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) +For more details about the `serve-static` function and its options, see [serve-static](/resources/middleware/serve-static.html). \ No newline at end of file diff --git a/es/advanced/best-practice-performance.md b/es/advanced/best-practice-performance.md index 2d04813695..817f934314 100644 --- a/es/advanced/best-practice-performance.md +++ b/es/advanced/best-practice-performance.md @@ -3,6 +3,7 @@ layout: page title: Mejores prácticas de rendimiento cuando se utiliza Express en producción description: Discover performance and reliability best practices for Express apps in production, covering code optimizations and environment setups for optimal performance. menu: advanced +order: 4 redirect_from: " " --- diff --git a/es/advanced/best-practice-security.md b/es/advanced/best-practice-security.md index 7aaf8bb415..3aec0f1197 100644 --- a/es/advanced/best-practice-security.md +++ b/es/advanced/best-practice-security.md @@ -3,6 +3,7 @@ layout: page title: Mejores prácticas de seguridad para Express en producción description: Discover crucial security best practices for Express apps in production, including using TLS, input validation, secure cookies, and preventing vulnerabilities. menu: advanced +order: 3 redirect_from: " " --- diff --git a/es/advanced/developing-template-engines.md b/es/advanced/developing-template-engines.md index f10cda9ac9..eb8f2ee917 100644 --- a/es/advanced/developing-template-engines.md +++ b/es/advanced/developing-template-engines.md @@ -3,6 +3,7 @@ layout: page title: Desarrollo de motores de plantilla para 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 +order: 1 redirect_from: " " --- diff --git a/es/advanced/healthcheck-graceful-shutdown.md b/es/advanced/healthcheck-graceful-shutdown.md index 20069a8903..a91cddada0 100644 --- a/es/advanced/healthcheck-graceful-shutdown.md +++ b/es/advanced/healthcheck-graceful-shutdown.md @@ -3,6 +3,7 @@ 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 +order: 5 redirect_from: " " --- diff --git a/es/advanced/security-updates.md b/es/advanced/security-updates.md index 2762211374..5674fb92f6 100644 --- a/es/advanced/security-updates.md +++ b/es/advanced/security-updates.md @@ -3,6 +3,7 @@ layout: page title: Actualizaciones de seguridad de Express 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 +order: 2 redirect_from: " " --- diff --git a/es/guide/behind-proxies.md b/es/guide/behind-proxies.md index 038e1ed139..365fdee6ee 100644 --- a/es/guide/behind-proxies.md +++ b/es/guide/behind-proxies.md @@ -3,6 +3,7 @@ layout: page title: Express detrás de proxies 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 +order: 8 redirect_from: " " --- diff --git a/es/guide/database-integration.md b/es/guide/database-integration.md index af5f568f39..ece4daf098 100644 --- a/es/guide/database-integration.md +++ b/es/guide/database-integration.md @@ -3,6 +3,7 @@ layout: page title: Integración de la base de datos de Express description: Discover how to integrate various databases with Express.js applications, including setup examples for MongoDB, MySQL, PostgreSQL, and more. menu: guide +order: 11 redirect_from: " " --- diff --git a/es/guide/debugging.md b/es/guide/debugging.md index 8011fc0c68..3e67e963e9 100644 --- a/es/guide/debugging.md +++ b/es/guide/debugging.md @@ -3,6 +3,7 @@ layout: page title: Depuración de 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 +order: 7 redirect_from: " " --- diff --git a/es/guide/error-handling.md b/es/guide/error-handling.md index 1d5c7e72e2..df2451a690 100644 --- a/es/guide/error-handling.md +++ b/es/guide/error-handling.md @@ -3,6 +3,7 @@ layout: page title: Manejo de errores de 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 +order: 6 redirect_from: " " --- diff --git a/es/guide/migrating-4.md b/es/guide/migrating-4.md index 437e9c7af8..da2d060819 100644 --- a/es/guide/migrating-4.md +++ b/es/guide/migrating-4.md @@ -3,6 +3,7 @@ layout: page title: Migración a 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 +order: 9 redirect_from: " " --- @@ -370,12 +371,12 @@ $ npm install serve-favicon morgan method-override express-session body-parser m Realice los cambios siguientes en `app.js`: 1. Las funciones de middleware de Express incorporadas `express.favicon`, - `express.logger`, `express.methodOverride`, - `express.session`, `express.bodyParser` y - `express.errorHandler` ya no están disponibles en el objeto `express`. Debe instalar sus alternativas manualmente y cargarlas en la aplicación. + `express.logger`, `express.methodOverride`, + `express.session`, `express.bodyParser` y + `express.errorHandler` ya no están disponibles en el objeto `express`. Debe instalar sus alternativas manualmente y cargarlas en la aplicación. 2. Ya no es necesario cargar la función `app.router`. - No es un objeto de aplicación Express 4 válido, por lo que debe eliminar el código `app.use(app.router);`. + No es un objeto de aplicación Express 4 válido, por lo que debe eliminar el código `app.use(app.router);`. 3. Asegúrese de que las funciones de middleware se cargan en el orden correcto: cargue `errorHandler` después de cargar las rutas de aplicación. diff --git a/es/guide/migrating-5.md b/es/guide/migrating-5.md index 570714ec58..d6bf808073 100644 --- a/es/guide/migrating-5.md +++ b/es/guide/migrating-5.md @@ -3,6 +3,7 @@ layout: page title: Migración a 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 +order: 10 redirect_from: " " --- @@ -259,7 +260,7 @@ app.get('/user', (req, res) => {

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. +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: diff --git a/es/guide/overriding-express-api.md b/es/guide/overriding-express-api.md index 032e3dd625..5210622ff2 100644 --- a/es/guide/overriding-express-api.md +++ b/es/guide/overriding-express-api.md @@ -3,6 +3,7 @@ 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 +order: 4 --- # Overriding the Express API diff --git a/es/guide/routing.md b/es/guide/routing.md index 2b476f03e4..8e722ffdc2 100644 --- a/es/guide/routing.md +++ b/es/guide/routing.md @@ -3,6 +3,7 @@ layout: page title: Direccionamiento de 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 +order: 1 redirect_from: " " --- diff --git a/es/guide/using-middleware.md b/es/guide/using-middleware.md index dda450f2c6..f4fcc65c67 100644 --- a/es/guide/using-middleware.md +++ b/es/guide/using-middleware.md @@ -3,6 +3,7 @@ layout: page title: Utilización del middleware de Express 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 +order: 3 redirect_from: " " --- diff --git a/es/guide/using-template-engines.md b/es/guide/using-template-engines.md index 795f89fa08..c88b786ff6 100644 --- a/es/guide/using-template-engines.md +++ b/es/guide/using-template-engines.md @@ -3,6 +3,7 @@ layout: page title: Utilización de motores de plantilla con Express 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 +order: 5 redirect_from: " " --- diff --git a/es/guide/writing-middleware.md b/es/guide/writing-middleware.md index 2c5a6aa1af..94e730314b 100644 --- a/es/guide/writing-middleware.md +++ b/es/guide/writing-middleware.md @@ -3,6 +3,7 @@ layout: page title: Escritura de middleware para su uso en aplicaciones Express 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 +order: 2 redirect_from: " " --- diff --git a/es/resources/community.md b/es/resources/community.md index 523a119f38..8e753b8c70 100644 --- a/es/resources/community.md +++ b/es/resources/community.md @@ -3,6 +3,7 @@ layout: page title: Comunidad de Express 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 +order: 1 redirect_from: " " --- @@ -41,8 +42,8 @@ Nuestra vibrante comunidad ha creado una larga variedad de extensiones, [módulo Además, la comunidad de Express mantiene módulos en estas dos organizaciones de GitHub: -- [jshttp](https://github.com/jshttp): módulos que proporcionan funciones utilitarias útiles; consulte [Módulos de utilidad](/{{ page.lang }}/resources/utils.html). -- [pillarjs](https://github.com/pillarjs): módulos de bajo nivel que Express utiliza internamente. +- [jshttp](https://github.com/jshttp) modules providing useful utility functions; see [Utility modules](/{{ page.lang }}/resources/utils.html). +- [pillarjs](https://github.com/pillarjs): low-level modules that Express uses internally. Para mantenerse al tanto de lo que está sucediendo en toda la comunidad, consulte [ExpressJS StatusBoard](https://expressjs.github.io/statusboard/). diff --git a/es/resources/contributing.md b/es/resources/contributing.md index f0e9f55836..613e30a73c 100644 --- a/es/resources/contributing.md +++ b/es/resources/contributing.md @@ -3,6 +3,7 @@ layout: page title: Contribuir a 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 +order: 5 redirect_from: " " --- @@ -87,7 +88,7 @@ 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). +[the triage process document](https://github.com/expressjs/discussions/blob/master/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 @@ -182,6 +183,26 @@ The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/doc 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) +### Inactivity and Emeritus Policy for Any Role + +To support the health and continuity of the project, all individuals holding a role within the community (such as Triager, Committer, WG member, Project Captain, or TC member) are encouraged to maintain active participation. + +Inactivity is defined as the absence of meaningful involvement in the project—such as contributions, code reviews, triage, meeting attendance, or discussion participation—for a continuous period of 6 months. + +#### Exceptions + +Anyone may request a temporary leave from active participation due to personal or professional reasons. In such cases, the individual should inform the relevant team or the Technical Committee (TC). During this time, the inactivity policy is paused, and the individual will not be flagged as inactive. + +#### Inactivity Process + +- If someone is deemed inactive, the individual may be transitioned to an emeritus role that reflects their past contributions. A best effort will be made to inform them that this has occurred. They may request to be reinstated when they are ready to be active again. +- The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time. + +#### Accountability + +- The Technical Committee (TC) and the respective captains of each package/team are responsible for assessing activity levels and enacting this policy fairly and transparently, in coordination with other relevant teams. +- In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team. + ### Developer's Certificate of Origin 1.1 ```text @@ -237,18 +258,18 @@ 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. + bug you want to fix or the feature that you want to add. 2. Create your own fork on GitHub, then - checkout your fork. + 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. + 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`. + then run `npm test`. 5. Ensure your code is linted by running `npm run lint` -- fix any issue you - see listed. + 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`. + 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 @@ -346,22 +367,22 @@ This is the contribution documentation for the [expressjs.com](https://github.co #### 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 + - 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 + - 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. + - 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? @@ -384,12 +405,12 @@ The steps below will guide you through the Expressjs.com contribution process. 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. + - 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. + - For submissions proposing significant change, we encourage you to follow the review process before starting work. #### Step 2: Get the Application Code Base @@ -434,12 +455,12 @@ The Express JS website is built using [Jekyll](https://jekyllrb.com/) and is hos 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. + - 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. + 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 diff --git a/es/resources/glossary.md b/es/resources/glossary.md index 28a33ad4a9..ece172a295 100644 --- a/es/resources/glossary.md +++ b/es/resources/glossary.md @@ -3,6 +3,7 @@ layout: page title: Glosario de Express 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 +order: 2 redirect_from: " " --- diff --git a/es/resources/middleware.md b/es/resources/middleware.md index 7a3516311b..19e5e2be88 100644 --- a/es/resources/middleware.md +++ b/es/resources/middleware.md @@ -3,6 +3,7 @@ layout: middleware title: Middleware de Express 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 +order: 3 redirect_from: " " module: mw-home --- diff --git a/es/resources/utils.md b/es/resources/utils.md index f58beb26e1..4c1a17b886 100644 --- a/es/resources/utils.md +++ b/es/resources/utils.md @@ -3,6 +3,7 @@ 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 +order: 4 redirect_from: " " --- diff --git a/es/starter/basic-routing.md b/es/starter/basic-routing.md index 121a304189..e28526867d 100644 --- a/es/starter/basic-routing.md +++ b/es/starter/basic-routing.md @@ -3,6 +3,7 @@ layout: page title: Direccionamiento básico de 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 +order: 4 redirect_from: " " --- @@ -21,7 +22,7 @@ app.METHOD(PATH, HANDLER) Where: - `app` is an instance of `express`. -- `METHOD` es un [método de solicitud HTTP](http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol). +- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase. - `PATH` es una vía de acceso en el servidor. - `HANDLER` es la función que se ejecuta cuando se correlaciona la ruta. @@ -65,4 +66,3 @@ app.delete('/user', (req, res) => { Para obtener más detalles sobre el direccionamiento, consulte la [guía de direccionamiento](/{{ 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/es/starter/examples.md b/es/starter/examples.md index 56da2d1a3c..86700f94c3 100644 --- a/es/starter/examples.md +++ b/es/starter/examples.md @@ -3,6 +3,7 @@ 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 +order: 6 redirect_from: " " --- @@ -15,6 +16,5 @@ These are some additional examples with more extensive integrations. {% include community-caveat.html %} -- [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) +- [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 \ No newline at end of file diff --git a/es/starter/faq.md b/es/starter/faq.md index 2bfbfc4b40..c89471f4b2 100644 --- a/es/starter/faq.md +++ b/es/starter/faq.md @@ -3,6 +3,7 @@ layout: page title: Preguntas más frecuentes sobre Express description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more. menu: starter +order: 7 redirect_from: " " --- @@ -75,6 +76,4 @@ Para el servicio de muchos activos desde un directorio, utilice la función de m ## What version of Node.js does Express require? - [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) +- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher. \ No newline at end of file diff --git a/es/starter/generator.md b/es/starter/generator.md index 51f17576ca..b33f2ae808 100644 --- a/es/starter/generator.md +++ b/es/starter/generator.md @@ -3,6 +3,7 @@ layout: page title: Generador de aplicaciones Express 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 +order: 3 redirect_from: " " --- @@ -122,6 +123,4 @@ The generated app has the following directory structure:
La estructura de la aplicación creada por el generador es sólo una de las muchas formas de estructurar las aplicaciones Express. Puede utilizar esta estructura o modificarla según sus necesidades. -
- -### [Previous: Hello World ](/{{ page.lang }}/starter/hello-world.html)    [Next: Basic routing](/{{ page.lang }}/starter/basic-routing.html) + \ No newline at end of file diff --git a/es/starter/hello-world.md b/es/starter/hello-world.md index 0e4959c30e..053cd78b5b 100644 --- a/es/starter/hello-world.md +++ b/es/starter/hello-world.md @@ -3,6 +3,7 @@ layout: page title: Ejemplo "Hello World" de 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 +order: 2 redirect_from: " " --- @@ -44,6 +45,4 @@ Ejecute la aplicación con el siguiente mandato: $ node app.js ``` -A continuación, cargue [http://localhost:3000/](http://localhost:3000/) en un navegador para ver la salida. - -### [Previous: Installing ](/{{ page.lang }}/starter/installing.html)    [Next: Express Generator ](/{{ page.lang }}/starter/generator.html) +A continuación, cargue [http://localhost:3000/](http://localhost:3000/) en un navegador para ver la salida. \ No newline at end of file diff --git a/es/starter/installing.md b/es/starter/installing.md index bdb23dcd26..e4b98996d6 100644 --- a/es/starter/installing.md +++ b/es/starter/installing.md @@ -3,6 +3,7 @@ layout: page title: Instalación de Express description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm. menu: starter +order: 1 redirect_from: " " --- @@ -48,6 +49,4 @@ $ npm install express --no-save
Los módulos de Node que se instalan con la opción `--save` se añaden a la lista `dependencies` en el archivo `package.json`. Posteriormente, si ejecuta `npm install` en el directorio `app`, los módulos se instalarán automáticamente en la lista de dependencias. -
- -### [Next: Hello World ](/{{ page.lang }}/starter/hello-world.html) \ No newline at end of file + \ No newline at end of file diff --git a/es/starter/static-files.md b/es/starter/static-files.md index 52274ad4a9..e138455a67 100644 --- a/es/starter/static-files.md +++ b/es/starter/static-files.md @@ -3,6 +3,7 @@ layout: page title: Servicio de archivos estáticos en Express description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware. menu: starter +order: 5 redirect_from: " " --- @@ -76,6 +77,4 @@ 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) +For more details about the `serve-static` function and its options, see [serve-static](/resources/middleware/serve-static.html). \ No newline at end of file diff --git a/fr/advanced/best-practice-performance.md b/fr/advanced/best-practice-performance.md index c02e5c9a73..bc82d29503 100644 --- a/fr/advanced/best-practice-performance.md +++ b/fr/advanced/best-practice-performance.md @@ -3,6 +3,7 @@ layout: page title: Meilleures pratiques en termes de performances pour l'utilisation d'Express en production description: Discover performance and reliability best practices for Express apps in production, covering code optimizations and environment setups for optimal performance. menu: advanced +order: 4 redirect_from: " " --- diff --git a/fr/advanced/best-practice-security.md b/fr/advanced/best-practice-security.md index 5be8ad6105..c079c3aca9 100644 --- a/fr/advanced/best-practice-security.md +++ b/fr/advanced/best-practice-security.md @@ -3,6 +3,7 @@ layout: page title: Meilleures pratiques de sécurité pour Express en production description: Discover crucial security best practices for Express apps in production, including using TLS, input validation, secure cookies, and preventing vulnerabilities. menu: advanced +order: 3 redirect_from: " " --- diff --git a/fr/advanced/developing-template-engines.md b/fr/advanced/developing-template-engines.md index 531bc250f8..133037ad85 100644 --- a/fr/advanced/developing-template-engines.md +++ b/fr/advanced/developing-template-engines.md @@ -3,6 +3,7 @@ layout: page title: Développement de moteurs de modèles pour 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 +order: 1 redirect_from: " " --- diff --git a/fr/advanced/healthcheck-graceful-shutdown.md b/fr/advanced/healthcheck-graceful-shutdown.md index fe41569237..53dd47edba 100644 --- a/fr/advanced/healthcheck-graceful-shutdown.md +++ b/fr/advanced/healthcheck-graceful-shutdown.md @@ -3,6 +3,7 @@ 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 +order: 5 redirect_from: " " --- diff --git a/fr/advanced/security-updates.md b/fr/advanced/security-updates.md index 251d8092a6..d7c02f1492 100644 --- a/fr/advanced/security-updates.md +++ b/fr/advanced/security-updates.md @@ -3,6 +3,7 @@ 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 +order: 2 redirect_from: " " --- diff --git a/fr/guide/behind-proxies.md b/fr/guide/behind-proxies.md index 914fd6ebbf..9bb9cf59fa 100644 --- a/fr/guide/behind-proxies.md +++ b/fr/guide/behind-proxies.md @@ -3,6 +3,7 @@ layout: page title: Serveurs proxy derrière Express 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 +order: 8 redirect_from: " " --- diff --git a/fr/guide/database-integration.md b/fr/guide/database-integration.md index ffd2a8bcbb..4118af91ee 100644 --- a/fr/guide/database-integration.md +++ b/fr/guide/database-integration.md @@ -3,6 +3,7 @@ layout: page title: Express database integration description: Discover how to integrate various databases with Express.js applications, including setup examples for MongoDB, MySQL, PostgreSQL, and more. menu: guide +order: 11 redirect_from: " " --- diff --git a/fr/guide/debugging.md b/fr/guide/debugging.md index 1053f85bf1..4ae539dfab 100644 --- a/fr/guide/debugging.md +++ b/fr/guide/debugging.md @@ -3,6 +3,7 @@ layout: page title: Débogage d'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 +order: 7 redirect_from: " " --- diff --git a/fr/guide/error-handling.md b/fr/guide/error-handling.md index 41a4381130..30cf7dc093 100644 --- a/fr/guide/error-handling.md +++ b/fr/guide/error-handling.md @@ -3,6 +3,7 @@ layout: page title: Traitement d'erreurs 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 +order: 6 redirect_from: " " --- diff --git a/fr/guide/migrating-4.md b/fr/guide/migrating-4.md index 025f22c378..ce9d27085a 100644 --- a/fr/guide/migrating-4.md +++ b/fr/guide/migrating-4.md @@ -3,6 +3,7 @@ layout: page title: Migration vers 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 +order: 9 redirect_from: " " --- @@ -383,15 +384,15 @@ $ npm install serve-favicon morgan method-override express-session body-parser m Apportez les modifications suivantes à `app.js` : 1. Les fonctions Express Middleware intégrées `express.favicon`, - `express.logger`, `express.methodOverride`, - `express.session`, `express.bodyParser` et - `express.errorHandler` ne sont plus disponibles sur l'objet - `express`. Vous devez installer leurs fonctions alternatives - manuellement et les charger dans l'application. + `express.logger`, `express.methodOverride`, + `express.session`, `express.bodyParser` et + `express.errorHandler` ne sont plus disponibles sur l'objet + `express`. Vous devez installer leurs fonctions alternatives + manuellement et les charger dans l'application. 2. Vous ne devez plus charger la fonction `app.router`. - Il ne s'agit pas d'un objet d'application Express 4 valide. Supprimez le code - `app.use(app.router);`. + Il ne s'agit pas d'un objet d'application Express 4 valide. Supprimez le code + `app.use(app.router);`. 3. Assurez-vous que les fonctions middleware sont chargées dans l'ordre correct - chargez `errorHandler` après avoir chargé les routes d'application. diff --git a/fr/guide/migrating-5.md b/fr/guide/migrating-5.md index 656f91e3ef..77339128d3 100644 --- a/fr/guide/migrating-5.md +++ b/fr/guide/migrating-5.md @@ -3,6 +3,7 @@ layout: page title: Migration vers 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 +order: 10 redirect_from: " " --- @@ -304,7 +305,7 @@ app.get('/user', (req, res) => {

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. +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: diff --git a/fr/guide/overriding-express-api.md b/fr/guide/overriding-express-api.md index 032e3dd625..5210622ff2 100644 --- a/fr/guide/overriding-express-api.md +++ b/fr/guide/overriding-express-api.md @@ -3,6 +3,7 @@ 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 +order: 4 --- # Overriding the Express API diff --git a/fr/guide/routing.md b/fr/guide/routing.md index 2f1a47bdff..8f82e6f497 100644 --- a/fr/guide/routing.md +++ b/fr/guide/routing.md @@ -3,6 +3,7 @@ layout: page title: Routage 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 +order: 1 redirect_from: " " --- diff --git a/fr/guide/using-middleware.md b/fr/guide/using-middleware.md index f752e5ddda..8695b3f1e3 100644 --- a/fr/guide/using-middleware.md +++ b/fr/guide/using-middleware.md @@ -3,6 +3,7 @@ layout: page title: Utilisation de middleware Express 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 +order: 3 redirect_from: " " --- diff --git a/fr/guide/using-template-engines.md b/fr/guide/using-template-engines.md index 7213af9e5e..80dbe62570 100644 --- a/fr/guide/using-template-engines.md +++ b/fr/guide/using-template-engines.md @@ -3,6 +3,7 @@ layout: page title: Utilisation de moteurs de modèles avec Express 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 +order: 5 redirect_from: " " --- diff --git a/fr/guide/writing-middleware.md b/fr/guide/writing-middleware.md index 9c64f8f560..b5f00af863 100644 --- a/fr/guide/writing-middleware.md +++ b/fr/guide/writing-middleware.md @@ -3,6 +3,7 @@ layout: page title: Ecriture de middleware utilisable dans les applications Express 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 +order: 2 redirect_from: " " --- diff --git a/fr/resources/community.md b/fr/resources/community.md index 727876dc3a..12904a9584 100644 --- a/fr/resources/community.md +++ b/fr/resources/community.md @@ -3,6 +3,7 @@ layout: page title: Communauté Express 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 +order: 1 redirect_from: " " --- diff --git a/fr/resources/contributing.md b/fr/resources/contributing.md index e37cee3122..b0944346a1 100644 --- a/fr/resources/contributing.md +++ b/fr/resources/contributing.md @@ -3,6 +3,7 @@ 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 +order: 5 redirect_from: " " --- @@ -87,7 +88,7 @@ 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). +[the triage process document](https://github.com/expressjs/discussions/blob/master/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 @@ -182,6 +183,26 @@ The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/doc 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) +### Inactivity and Emeritus Policy for Any Role + +To support the health and continuity of the project, all individuals holding a role within the community (such as Triager, Committer, WG member, Project Captain, or TC member) are encouraged to maintain active participation. + +Inactivity is defined as the absence of meaningful involvement in the project—such as contributions, code reviews, triage, meeting attendance, or discussion participation—for a continuous period of 6 months. + +#### Exceptions + +Anyone may request a temporary leave from active participation due to personal or professional reasons. In such cases, the individual should inform the relevant team or the Technical Committee (TC). During this time, the inactivity policy is paused, and the individual will not be flagged as inactive. + +#### Inactivity Process + +- If someone is deemed inactive, the individual may be transitioned to an emeritus role that reflects their past contributions. A best effort will be made to inform them that this has occurred. They may request to be reinstated when they are ready to be active again. +- The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time. + +#### Accountability + +- The Technical Committee (TC) and the respective captains of each package/team are responsible for assessing activity levels and enacting this policy fairly and transparently, in coordination with other relevant teams. +- In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team. + ### Developer's Certificate of Origin 1.1 ```text @@ -237,18 +258,18 @@ 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. + bug you want to fix or the feature that you want to add. 2. Create your own fork on GitHub, then - checkout your fork. + 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. + 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`. + then run `npm test`. 5. Ensure your code is linted by running `npm run lint` -- fix any issue you - see listed. + 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`. + 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 @@ -346,22 +367,22 @@ This is the contribution documentation for the [expressjs.com](https://github.co #### 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 + - 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 + - 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. + - 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? @@ -384,12 +405,12 @@ The steps below will guide you through the Expressjs.com contribution process. 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. + - 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. + - For submissions proposing significant change, we encourage you to follow the review process before starting work. #### Step 2: Get the Application Code Base @@ -434,12 +455,12 @@ The Express JS website is built using [Jekyll](https://jekyllrb.com/) and is hos 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. + - 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. + 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 diff --git a/fr/resources/glossary.md b/fr/resources/glossary.md index f2774da7d6..e8379279bc 100644 --- a/fr/resources/glossary.md +++ b/fr/resources/glossary.md @@ -3,6 +3,7 @@ layout: page title: Glossaire Express 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 +order: 2 redirect_from: " " --- diff --git a/fr/resources/middleware.md b/fr/resources/middleware.md index 2d624487d9..4be979f928 100644 --- a/fr/resources/middleware.md +++ b/fr/resources/middleware.md @@ -3,6 +3,7 @@ layout: middleware title: Middleware Express 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 +order: 3 redirect_from: " " module: mw-home --- diff --git a/fr/resources/utils.md b/fr/resources/utils.md index f58beb26e1..4c1a17b886 100644 --- a/fr/resources/utils.md +++ b/fr/resources/utils.md @@ -3,6 +3,7 @@ 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 +order: 4 redirect_from: " " --- diff --git a/fr/starter/basic-routing.md b/fr/starter/basic-routing.md index 95e496820e..4c1404c08d 100644 --- a/fr/starter/basic-routing.md +++ b/fr/starter/basic-routing.md @@ -3,6 +3,7 @@ layout: page title: Routage de base 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 +order: 4 redirect_from: " " --- @@ -22,7 +23,7 @@ app.METHOD(PATH, HANDLER) Où : - `app` est une instance d'`express`. -- `METHOD` est une [méthode de demande HTTP](http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol). +- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase. - `PATH` est un chemin sur le serveur. - `HANDLER` est la fonction exécutée lorsque la route est mise en correspondance. @@ -66,4 +67,3 @@ app.delete('/user', (req, res) => { Pour plus de détails sur le routage, reportez-vous au [guide de routage](/{{ 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/fr/starter/examples.md b/fr/starter/examples.md index 56da2d1a3c..86700f94c3 100644 --- a/fr/starter/examples.md +++ b/fr/starter/examples.md @@ -3,6 +3,7 @@ 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 +order: 6 redirect_from: " " --- @@ -15,6 +16,5 @@ These are some additional examples with more extensive integrations. {% include community-caveat.html %} -- [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) +- [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 \ No newline at end of file diff --git a/fr/starter/faq.md b/fr/starter/faq.md index d4fed31dfc..d234897893 100644 --- a/fr/starter/faq.md +++ b/fr/starter/faq.md @@ -3,6 +3,7 @@ layout: page title: FAQ Express description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more. menu: starter +order: 7 redirect_from: " " --- @@ -90,6 +91,4 @@ Si vous utilisez plusieurs actifs d'un répertoire, utilisez la fonction middlew ## What version of Node.js does Express require? - [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) +- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher. \ No newline at end of file diff --git a/fr/starter/generator.md b/fr/starter/generator.md index fdf13765b7..36ed111830 100644 --- a/fr/starter/generator.md +++ b/fr/starter/generator.md @@ -3,6 +3,7 @@ layout: page title: Générateur d'applications Express 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 +order: 3 redirect_from: " " --- @@ -122,6 +123,4 @@ L'application générée possède la structure de répertoire suivante :
La structure d'application créée par le générateur est l'une des nombreuses manières possibles de structurer les applications Express. Vous avez toute latitude pour l'utiliser ou la modifier en fonction de vos besoins. -
- -### [Previous: Hello World ](/{{ page.lang }}/starter/hello-world.html)    [Next: Basic routing](/{{ page.lang }}/starter/basic-routing.html) + \ No newline at end of file diff --git a/fr/starter/hello-world.md b/fr/starter/hello-world.md index c33abf6c0a..9dbd498fe4 100644 --- a/fr/starter/hello-world.md +++ b/fr/starter/hello-world.md @@ -3,6 +3,7 @@ layout: page title: Exemple "Hello world" 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 +order: 2 redirect_from: " " --- @@ -47,6 +48,4 @@ Exécutez l'application avec la commande suivante : $ node app.js ``` -Puis chargez [http://localhost:3000/](http://localhost:3000/) dans un navigateur pour consulter le résultat. - -### [Previous: Installing ](/{{ page.lang }}/starter/installing.html)    [Next: Express Generator ](/{{ page.lang }}/starter/generator.html) +Puis chargez [http://localhost:3000/](http://localhost:3000/) dans un navigateur pour consulter le résultat. \ No newline at end of file diff --git a/fr/starter/installing.md b/fr/starter/installing.md index 2c49018236..b893475347 100644 --- a/fr/starter/installing.md +++ b/fr/starter/installing.md @@ -3,6 +3,7 @@ layout: page title: Installation d'Express description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm. menu: starter +order: 1 redirect_from: " " --- @@ -48,6 +49,4 @@ $ npm install express --no-save
` ajoute automatiquement le module Node.js à la liste des dépendances. Par la suite, l'exécution de `npm install` dans le répertoire de l'application installera automatiquement les modules présents dans la liste des dépendances. -
- -### [Next: Hello World ](/{{ page.lang }}/starter/hello-world.html) \ No newline at end of file + \ No newline at end of file diff --git a/fr/starter/static-files.md b/fr/starter/static-files.md index 0a2bc4e33d..b964295b11 100644 --- a/fr/starter/static-files.md +++ b/fr/starter/static-files.md @@ -3,6 +3,7 @@ layout: page title: Servir des fichiers statiques dans Express description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware. menu: starter +order: 5 redirect_from: " " --- @@ -92,6 +93,4 @@ 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) +For more details about the `serve-static` function and its options, see [serve-static](/resources/middleware/serve-static.html). \ No newline at end of file diff --git a/it/advanced/best-practice-performance.md b/it/advanced/best-practice-performance.md index d2a429a77c..41c9b9c5ee 100644 --- a/it/advanced/best-practice-performance.md +++ b/it/advanced/best-practice-performance.md @@ -3,6 +3,7 @@ layout: page title: Best Practice sulle prestazioni utilizzando Express in fase di produzione description: Discover performance and reliability best practices for Express apps in production, covering code optimizations and environment setups for optimal performance. menu: advanced +order: 4 redirect_from: " " --- diff --git a/it/advanced/best-practice-security.md b/it/advanced/best-practice-security.md index d7c9ecba1e..f2164c2f9c 100644 --- a/it/advanced/best-practice-security.md +++ b/it/advanced/best-practice-security.md @@ -3,6 +3,7 @@ layout: page title: Best Practice sulla sicurezza per Express in fase di produzione description: Discover crucial security best practices for Express apps in production, including using TLS, input validation, secure cookies, and preventing vulnerabilities. menu: advanced +order: 3 redirect_from: " " --- diff --git a/it/advanced/developing-template-engines.md b/it/advanced/developing-template-engines.md index 6430a99ad4..2741f5eaae 100644 --- a/it/advanced/developing-template-engines.md +++ b/it/advanced/developing-template-engines.md @@ -3,6 +3,7 @@ layout: page title: Sviluppo dei motori di template per 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 +order: 1 redirect_from: " " --- diff --git a/it/advanced/healthcheck-graceful-shutdown.md b/it/advanced/healthcheck-graceful-shutdown.md index 60ee5f59d9..3afe11f7ce 100644 --- a/it/advanced/healthcheck-graceful-shutdown.md +++ b/it/advanced/healthcheck-graceful-shutdown.md @@ -3,6 +3,7 @@ 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 +order: 5 redirect_from: " " --- diff --git a/it/advanced/security-updates.md b/it/advanced/security-updates.md index a46ba4c164..244ad588c6 100644 --- a/it/advanced/security-updates.md +++ b/it/advanced/security-updates.md @@ -3,6 +3,7 @@ layout: page title: Aggiornamenti sulla sicurezza Express 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 +order: 2 redirect_from: " " --- diff --git a/it/guide/behind-proxies.md b/it/guide/behind-proxies.md index 87864eb5b0..9b50e2e10d 100644 --- a/it/guide/behind-proxies.md +++ b/it/guide/behind-proxies.md @@ -3,6 +3,7 @@ layout: page title: Express con i proxy 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 +order: 8 redirect_from: " " --- diff --git a/it/guide/database-integration.md b/it/guide/database-integration.md index 942d1912b4..52599c4861 100644 --- a/it/guide/database-integration.md +++ b/it/guide/database-integration.md @@ -3,6 +3,7 @@ layout: page title: Integrazione database Express description: Discover how to integrate various databases with Express.js applications, including setup examples for MongoDB, MySQL, PostgreSQL, and more. menu: guide +order: 11 redirect_from: " " --- diff --git a/it/guide/debugging.md b/it/guide/debugging.md index 9e4be0bf88..903a7e19b8 100644 --- a/it/guide/debugging.md +++ b/it/guide/debugging.md @@ -3,6 +3,7 @@ layout: page title: Debug di 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 +order: 7 redirect_from: " " --- diff --git a/it/guide/error-handling.md b/it/guide/error-handling.md index 84dfe10f72..3bb34d7a7a 100644 --- a/it/guide/error-handling.md +++ b/it/guide/error-handling.md @@ -3,6 +3,7 @@ layout: page title: Gestione degli errori di 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 +order: 6 redirect_from: " " --- diff --git a/it/guide/migrating-4.md b/it/guide/migrating-4.md index 61967ece95..459f6a2229 100644 --- a/it/guide/migrating-4.md +++ b/it/guide/migrating-4.md @@ -3,6 +3,7 @@ layout: page title: Migrazione a 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 +order: 9 redirect_from: " " --- @@ -392,15 +393,15 @@ $ npm install serve-favicon morgan method-override express-session body-parser m Apportare le seguenti modifiche a `app.js`: 1. Le funzioni middleware di Express integrate `express.favicon`, - `express.logger`, `express.methodOverride`, - `express.session`, `express.bodyParser` e - `express.errorHandler` non sono più disponibili nell'oggetto - `express`. È necessario installare le funzioni alternative - manualmente e caricarle sull'applicazione. + `express.logger`, `express.methodOverride`, + `express.session`, `express.bodyParser` e + `express.errorHandler` non sono più disponibili nell'oggetto + `express`. È necessario installare le funzioni alternative + manualmente e caricarle sull'applicazione. 2. Non è più necessario caricare la funzione `app.router`. - Non è un oggetto applicazione Express 4 valido, pertanto rimuovere il codice - `app.use(app.router);`. + Non è un oggetto applicazione Express 4 valido, pertanto rimuovere il codice + `app.use(app.router);`. 3. Assicurarsi che le funzioni middleware siano state caricate nell'ordine corretto - caricare `errorHandler` dopo aver caricato le route dell'applicazione. diff --git a/it/guide/migrating-5.md b/it/guide/migrating-5.md index 00522c1c33..20e7f258c9 100644 --- a/it/guide/migrating-5.md +++ b/it/guide/migrating-5.md @@ -3,6 +3,7 @@ layout: page title: Migrazione a 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 +order: 10 redirect_from: " " --- @@ -259,7 +260,7 @@ app.get('/user', (req, res) => {

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. +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: diff --git a/it/guide/overriding-express-api.md b/it/guide/overriding-express-api.md index 032e3dd625..5210622ff2 100644 --- a/it/guide/overriding-express-api.md +++ b/it/guide/overriding-express-api.md @@ -3,6 +3,7 @@ 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 +order: 4 --- # Overriding the Express API diff --git a/it/guide/routing.md b/it/guide/routing.md index 04f96716d1..0e1ff4566a 100644 --- a/it/guide/routing.md +++ b/it/guide/routing.md @@ -3,6 +3,7 @@ layout: page title: Routing 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 +order: 1 redirect_from: " " --- diff --git a/it/guide/using-middleware.md b/it/guide/using-middleware.md index 2084fbf27b..f2630df172 100644 --- a/it/guide/using-middleware.md +++ b/it/guide/using-middleware.md @@ -3,6 +3,7 @@ layout: page title: Utilizzo del middleware Express 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 +order: 3 redirect_from: " " --- diff --git a/it/guide/using-template-engines.md b/it/guide/using-template-engines.md index 6bd6bee198..68b0825ef6 100644 --- a/it/guide/using-template-engines.md +++ b/it/guide/using-template-engines.md @@ -3,6 +3,7 @@ layout: page title: Utilizzo di motori di template con Express 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 +order: 5 redirect_from: " " --- diff --git a/it/guide/writing-middleware.md b/it/guide/writing-middleware.md index d2d105f878..c535af88e8 100644 --- a/it/guide/writing-middleware.md +++ b/it/guide/writing-middleware.md @@ -3,6 +3,7 @@ layout: page title: Compilazione del middleware per l'utilizzo nelle applicazioni Express 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 +order: 2 redirect_from: " " --- diff --git a/it/resources/community.md b/it/resources/community.md index 04c983ca3c..8fd396e306 100644 --- a/it/resources/community.md +++ b/it/resources/community.md @@ -3,6 +3,7 @@ layout: page title: Community di Express 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 +order: 1 redirect_from: " " --- diff --git a/it/resources/contributing.md b/it/resources/contributing.md index e37cee3122..b0944346a1 100644 --- a/it/resources/contributing.md +++ b/it/resources/contributing.md @@ -3,6 +3,7 @@ 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 +order: 5 redirect_from: " " --- @@ -87,7 +88,7 @@ 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). +[the triage process document](https://github.com/expressjs/discussions/blob/master/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 @@ -182,6 +183,26 @@ The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/doc 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) +### Inactivity and Emeritus Policy for Any Role + +To support the health and continuity of the project, all individuals holding a role within the community (such as Triager, Committer, WG member, Project Captain, or TC member) are encouraged to maintain active participation. + +Inactivity is defined as the absence of meaningful involvement in the project—such as contributions, code reviews, triage, meeting attendance, or discussion participation—for a continuous period of 6 months. + +#### Exceptions + +Anyone may request a temporary leave from active participation due to personal or professional reasons. In such cases, the individual should inform the relevant team or the Technical Committee (TC). During this time, the inactivity policy is paused, and the individual will not be flagged as inactive. + +#### Inactivity Process + +- If someone is deemed inactive, the individual may be transitioned to an emeritus role that reflects their past contributions. A best effort will be made to inform them that this has occurred. They may request to be reinstated when they are ready to be active again. +- The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time. + +#### Accountability + +- The Technical Committee (TC) and the respective captains of each package/team are responsible for assessing activity levels and enacting this policy fairly and transparently, in coordination with other relevant teams. +- In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team. + ### Developer's Certificate of Origin 1.1 ```text @@ -237,18 +258,18 @@ 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. + bug you want to fix or the feature that you want to add. 2. Create your own fork on GitHub, then - checkout your fork. + 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. + 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`. + then run `npm test`. 5. Ensure your code is linted by running `npm run lint` -- fix any issue you - see listed. + 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`. + 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 @@ -346,22 +367,22 @@ This is the contribution documentation for the [expressjs.com](https://github.co #### 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 + - 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 + - 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. + - 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? @@ -384,12 +405,12 @@ The steps below will guide you through the Expressjs.com contribution process. 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. + - 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. + - For submissions proposing significant change, we encourage you to follow the review process before starting work. #### Step 2: Get the Application Code Base @@ -434,12 +455,12 @@ The Express JS website is built using [Jekyll](https://jekyllrb.com/) and is hos 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. + - 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. + 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 diff --git a/it/resources/glossary.md b/it/resources/glossary.md index ab17ddf990..a02d3b3811 100644 --- a/it/resources/glossary.md +++ b/it/resources/glossary.md @@ -3,6 +3,7 @@ layout: page title: Glossario di Express 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 +order: 2 redirect_from: " " --- diff --git a/it/resources/middleware.md b/it/resources/middleware.md index 08437e4b22..723da0f4eb 100644 --- a/it/resources/middleware.md +++ b/it/resources/middleware.md @@ -3,6 +3,7 @@ layout: middleware title: Middleware Express 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 +order: 3 redirect_from: " " module: mw-home --- diff --git a/it/resources/utils.md b/it/resources/utils.md index 5fc784092d..168c494d51 100644 --- a/it/resources/utils.md +++ b/it/resources/utils.md @@ -3,6 +3,7 @@ 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 +order: 4 redirect_from: " " --- diff --git a/it/starter/basic-routing.md b/it/starter/basic-routing.md index b42b7cacea..87eaadaa72 100644 --- a/it/starter/basic-routing.md +++ b/it/starter/basic-routing.md @@ -3,6 +3,7 @@ layout: page title: Routing di base 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 +order: 4 redirect_from: " " --- @@ -21,7 +22,7 @@ app.METHOD(PATH, HANDLER) Dove: - `app` è un'istanza di `express`. -- `METHOD` è un [metodo di richiesta HTTP](http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol). +- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase. - `PATH` è un percorso sul server. - `HANDLER` è la funzione eseguita quando si trova una corrispondenza per la route. @@ -65,4 +66,3 @@ app.delete('/user', (req, res) => { Per ulteriori dettagli sul routing, consultare il [Manuale routing](/{{ 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/it/starter/examples.md b/it/starter/examples.md index 56da2d1a3c..86700f94c3 100644 --- a/it/starter/examples.md +++ b/it/starter/examples.md @@ -3,6 +3,7 @@ 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 +order: 6 redirect_from: " " --- @@ -15,6 +16,5 @@ These are some additional examples with more extensive integrations. {% include community-caveat.html %} -- [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) +- [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 \ No newline at end of file diff --git a/it/starter/faq.md b/it/starter/faq.md index 2ce2ea1384..f617055c42 100644 --- a/it/starter/faq.md +++ b/it/starter/faq.md @@ -3,6 +3,7 @@ layout: page title: FAQ di Express description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more. menu: starter +order: 7 redirect_from: " " --- @@ -92,6 +93,4 @@ Se si stanno gestendo molti asset da una directory, utilizzare la funzione middl ## What version of Node.js does Express require? - [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) +- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher. \ No newline at end of file diff --git a/it/starter/generator.md b/it/starter/generator.md index c2e8bec343..4465619aea 100644 --- a/it/starter/generator.md +++ b/it/starter/generator.md @@ -3,6 +3,7 @@ layout: page title: Programma di creazione applicazione Express 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 +order: 3 redirect_from: " " --- @@ -122,6 +123,4 @@ L'applicazione creata dispone della seguente struttura per la directory:
La struttura dell'applicazione creata dal programma di creazione è solo uno dei tanti modi disponibili per creare la struttura delle applicazioni Express. È possibile utilizzare questa struttura o modificarla a seconda delle proprie necessità. -
- -### [Previous: Hello World ](/{{ page.lang }}/starter/hello-world.html)    [Next: Basic routing](/{{ page.lang }}/starter/basic-routing.html) + \ No newline at end of file diff --git a/it/starter/hello-world.md b/it/starter/hello-world.md index e11217a50f..f7cf1edc38 100644 --- a/it/starter/hello-world.md +++ b/it/starter/hello-world.md @@ -3,6 +3,7 @@ layout: page title: Esempio di "Hello World" di 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 +order: 2 redirect_from: " " --- @@ -46,6 +47,4 @@ Eseguire l'applicazione con il seguente comando: $ node app.js ``` -Successivamente, caricare [http://localhost:3000/](http://localhost:3000/) su un browser per visualizzare l'output. - -### [Previous: Installing ](/{{ page.lang }}/starter/installing.html)    [Next: Express Generator ](/{{ page.lang }}/starter/generator.html) +Successivamente, caricare [http://localhost:3000/](http://localhost:3000/) su un browser per visualizzare l'output. \ No newline at end of file diff --git a/it/starter/installing.md b/it/starter/installing.md index 5834f3fc87..23b60b8465 100644 --- a/it/starter/installing.md +++ b/it/starter/installing.md @@ -3,6 +3,7 @@ layout: page title: Installazione di Express description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm. menu: starter +order: 1 redirect_from: " " --- @@ -48,6 +49,4 @@ $ npm install express --no-save
I moduli Node installati con l'opzione `--save` vengono aggiunti all'elenco `dependencies` nel file `package.json`. Successivamente, l'esecuzione di `npm install` nella directory `app` installerà automaticamente i moduli nell'elenco di dipendenze. -
- -### [Next: Hello World ](/{{ page.lang }}/starter/hello-world.html) \ No newline at end of file + \ No newline at end of file diff --git a/it/starter/static-files.md b/it/starter/static-files.md index c06a0b09b1..76a34532e7 100644 --- a/it/starter/static-files.md +++ b/it/starter/static-files.md @@ -3,6 +3,7 @@ layout: page title: Gestione dei file statici in Express description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware. menu: starter +order: 5 redirect_from: " " --- @@ -76,6 +77,4 @@ 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) +For more details about the `serve-static` function and its options, see [serve-static](/resources/middleware/serve-static.html). \ No newline at end of file diff --git a/ja/advanced/best-practice-performance.md b/ja/advanced/best-practice-performance.md index 3de26f0e60..e4ce2161c0 100644 --- a/ja/advanced/best-practice-performance.md +++ b/ja/advanced/best-practice-performance.md @@ -3,6 +3,7 @@ layout: page title: 実稼働環境における Express の使用におけるパフォーマンスに関するベスト・プラクティス description: Discover performance and reliability best practices for Express apps in production, covering code optimizations and environment setups for optimal performance. menu: advanced +order: 4 redirect_from: " " --- diff --git a/ja/advanced/best-practice-security.md b/ja/advanced/best-practice-security.md index 37739aa555..9aeb18cea5 100644 --- a/ja/advanced/best-practice-security.md +++ b/ja/advanced/best-practice-security.md @@ -3,6 +3,7 @@ layout: page title: 実稼働環境における Express のセキュリティーに関するベスト・プラクティス description: Discover crucial security best practices for Express apps in production, including using TLS, input validation, secure cookies, and preventing vulnerabilities. menu: advanced +order: 3 redirect_from: " " --- diff --git a/ja/advanced/developing-template-engines.md b/ja/advanced/developing-template-engines.md index 41cc517423..bcc9a3a6e1 100644 --- a/ja/advanced/developing-template-engines.md +++ b/ja/advanced/developing-template-engines.md @@ -3,6 +3,7 @@ layout: page title: 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 +order: 1 redirect_from: " " --- diff --git a/ja/advanced/healthcheck-graceful-shutdown.md b/ja/advanced/healthcheck-graceful-shutdown.md index e5c452cad7..efe4202588 100644 --- a/ja/advanced/healthcheck-graceful-shutdown.md +++ b/ja/advanced/healthcheck-graceful-shutdown.md @@ -3,6 +3,7 @@ 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 +order: 5 redirect_from: " " --- diff --git a/ja/advanced/security-updates.md b/ja/advanced/security-updates.md index d791a746e4..0bf3801f87 100644 --- a/ja/advanced/security-updates.md +++ b/ja/advanced/security-updates.md @@ -3,6 +3,7 @@ layout: page title: Express のセキュリティー更新 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 +order: 2 redirect_from: " " --- diff --git a/ja/guide/behind-proxies.md b/ja/guide/behind-proxies.md index c8309ce094..dbedb2ed79 100644 --- a/ja/guide/behind-proxies.md +++ b/ja/guide/behind-proxies.md @@ -3,6 +3,7 @@ layout: page title: プロキシーの背後の Express 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 +order: 8 redirect_from: " " --- diff --git a/ja/guide/database-integration.md b/ja/guide/database-integration.md index e5f3885f00..336e9ba204 100644 --- a/ja/guide/database-integration.md +++ b/ja/guide/database-integration.md @@ -3,6 +3,7 @@ layout: page title: Express でのデータベースの統合 description: Discover how to integrate various databases with Express.js applications, including setup examples for MongoDB, MySQL, PostgreSQL, and more. menu: guide +order: 11 redirect_from: " " --- diff --git a/ja/guide/debugging.md b/ja/guide/debugging.md index ba20a68f26..df0da33bba 100644 --- a/ja/guide/debugging.md +++ b/ja/guide/debugging.md @@ -3,6 +3,7 @@ layout: page title: 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 +order: 7 redirect_from: " " --- diff --git a/ja/guide/error-handling.md b/ja/guide/error-handling.md index af90350530..17e4949ad6 100644 --- a/ja/guide/error-handling.md +++ b/ja/guide/error-handling.md @@ -3,6 +3,7 @@ layout: page title: 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 +order: 6 redirect_from: " " --- diff --git a/ja/guide/migrating-4.md b/ja/guide/migrating-4.md index f6221a168e..7caa5dc571 100644 --- a/ja/guide/migrating-4.md +++ b/ja/guide/migrating-4.md @@ -3,6 +3,7 @@ layout: page title: 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 +order: 9 redirect_from: " " --- @@ -380,10 +381,10 @@ $ npm install serve-favicon morgan method-override express-session body-parser m `app.js` に以下の変更を加えます。 1. 標準装備の Express ミドルウェア関数 `express.favicon`、`express.logger`、`express.methodOverride`、`express.session`、`express.bodyParser`、および `express.errorHandler` は `express` オブジェクトで使用できなくなりました。代わりの関数を手動でインストールして、アプリケーションにロードする必要があります。 You must install their alternatives - manually and load them in the app. + manually and load them in the app. 2. You no longer need to load the `app.router` function. - `app.router` 関数をロードする必要がなくなりました。この関数は有効な Express 4 アプリケーション・オブジェクトではないため、`app.use(app.router);` コードを削除してください。 + `app.router` 関数をロードする必要がなくなりました。この関数は有効な Express 4 アプリケーション・オブジェクトではないため、`app.use(app.router);` コードを削除してください。 3. ミドルウェア関数が正しい順序でロードされていることを確認してください。つまり、アプリケーション・ルートをロードした後で `errorHandler` をロードしてください。 diff --git a/ja/guide/migrating-5.md b/ja/guide/migrating-5.md index c6eb92faa0..c9f0b5b7c8 100644 --- a/ja/guide/migrating-5.md +++ b/ja/guide/migrating-5.md @@ -3,6 +3,7 @@ layout: page title: 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 +order: 10 redirect_from: " " --- @@ -259,7 +260,7 @@ app.get('/user', (req, res) => {

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. +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: diff --git a/ja/guide/overriding-express-api.md b/ja/guide/overriding-express-api.md index 032e3dd625..5210622ff2 100644 --- a/ja/guide/overriding-express-api.md +++ b/ja/guide/overriding-express-api.md @@ -3,6 +3,7 @@ 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 +order: 4 --- # Overriding the Express API diff --git a/ja/guide/routing.md b/ja/guide/routing.md index 1a175cbbd5..4cd98b610b 100644 --- a/ja/guide/routing.md +++ b/ja/guide/routing.md @@ -3,6 +3,7 @@ layout: page title: 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 +order: 1 redirect_from: " " --- diff --git a/ja/guide/using-middleware.md b/ja/guide/using-middleware.md index 1210706ee1..7bfca3a572 100644 --- a/ja/guide/using-middleware.md +++ b/ja/guide/using-middleware.md @@ -3,6 +3,7 @@ layout: page title: Express ミドルウェアの使用 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 +order: 3 redirect_from: " " --- diff --git a/ja/guide/using-template-engines.md b/ja/guide/using-template-engines.md index d02b0c6410..8942cffe7c 100644 --- a/ja/guide/using-template-engines.md +++ b/ja/guide/using-template-engines.md @@ -3,6 +3,7 @@ layout: page title: Express でのテンプレート・エンジンの使用 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 +order: 5 redirect_from: " " --- diff --git a/ja/guide/writing-middleware.md b/ja/guide/writing-middleware.md index 265b6b9c52..3be4e0a4ae 100644 --- a/ja/guide/writing-middleware.md +++ b/ja/guide/writing-middleware.md @@ -3,6 +3,7 @@ layout: page title: Express アプリケーションで使用するミドルウェアの作成 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 +order: 2 redirect_from: " " --- diff --git a/ja/resources/community.md b/ja/resources/community.md index 77ea8471e1..2fb3f05c7e 100644 --- a/ja/resources/community.md +++ b/ja/resources/community.md @@ -3,6 +3,7 @@ layout: page title: Express のコミュニティー 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 +order: 1 redirect_from: " " --- diff --git a/ja/resources/contributing.md b/ja/resources/contributing.md index e37cee3122..b0944346a1 100644 --- a/ja/resources/contributing.md +++ b/ja/resources/contributing.md @@ -3,6 +3,7 @@ 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 +order: 5 redirect_from: " " --- @@ -87,7 +88,7 @@ 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). +[the triage process document](https://github.com/expressjs/discussions/blob/master/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 @@ -182,6 +183,26 @@ The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/doc 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) +### Inactivity and Emeritus Policy for Any Role + +To support the health and continuity of the project, all individuals holding a role within the community (such as Triager, Committer, WG member, Project Captain, or TC member) are encouraged to maintain active participation. + +Inactivity is defined as the absence of meaningful involvement in the project—such as contributions, code reviews, triage, meeting attendance, or discussion participation—for a continuous period of 6 months. + +#### Exceptions + +Anyone may request a temporary leave from active participation due to personal or professional reasons. In such cases, the individual should inform the relevant team or the Technical Committee (TC). During this time, the inactivity policy is paused, and the individual will not be flagged as inactive. + +#### Inactivity Process + +- If someone is deemed inactive, the individual may be transitioned to an emeritus role that reflects their past contributions. A best effort will be made to inform them that this has occurred. They may request to be reinstated when they are ready to be active again. +- The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time. + +#### Accountability + +- The Technical Committee (TC) and the respective captains of each package/team are responsible for assessing activity levels and enacting this policy fairly and transparently, in coordination with other relevant teams. +- In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team. + ### Developer's Certificate of Origin 1.1 ```text @@ -237,18 +258,18 @@ 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. + bug you want to fix or the feature that you want to add. 2. Create your own fork on GitHub, then - checkout your fork. + 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. + 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`. + then run `npm test`. 5. Ensure your code is linted by running `npm run lint` -- fix any issue you - see listed. + 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`. + 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 @@ -346,22 +367,22 @@ This is the contribution documentation for the [expressjs.com](https://github.co #### 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 + - 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 + - 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. + - 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? @@ -384,12 +405,12 @@ The steps below will guide you through the Expressjs.com contribution process. 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. + - 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. + - For submissions proposing significant change, we encourage you to follow the review process before starting work. #### Step 2: Get the Application Code Base @@ -434,12 +455,12 @@ The Express JS website is built using [Jekyll](https://jekyllrb.com/) and is hos 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. + - 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. + 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 diff --git a/ja/resources/glossary.md b/ja/resources/glossary.md index b305a8b759..b5f4b3e80a 100644 --- a/ja/resources/glossary.md +++ b/ja/resources/glossary.md @@ -3,6 +3,7 @@ layout: page title: Express の用語集 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 +order: 2 redirect_from: " " --- diff --git a/ja/resources/middleware.md b/ja/resources/middleware.md index f6e625cbb8..7eab9e8256 100644 --- a/ja/resources/middleware.md +++ b/ja/resources/middleware.md @@ -3,6 +3,7 @@ layout: middleware title: Express のミドルウェア 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 +order: 3 redirect_from: " " module: mw-home --- diff --git a/ja/resources/utils.md b/ja/resources/utils.md index b4e0712dff..9d2947a542 100644 --- a/ja/resources/utils.md +++ b/ja/resources/utils.md @@ -3,6 +3,7 @@ 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 +order: 4 redirect_from: " " --- diff --git a/ja/starter/basic-routing.md b/ja/starter/basic-routing.md index 6acae388a9..bc3035c519 100644 --- a/ja/starter/basic-routing.md +++ b/ja/starter/basic-routing.md @@ -3,6 +3,7 @@ layout: page title: 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 +order: 4 redirect_from: " " --- @@ -21,7 +22,7 @@ app.METHOD(PATH, HANDLER) Where: - `app` は、`express` のインスタンスです。 -- `METHOD` は、[HTTP 要求メソッド](http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) です。 +- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase. - `PATH` は、サーバー上のパスです。 - `HANDLER` は、ルートが一致したときに実行される関数です。 @@ -67,4 +68,3 @@ app.delete('/user', (req, res) => { ルーティングについて詳しくは、[ルーティング・ガイド](/{{ 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/ja/starter/examples.md b/ja/starter/examples.md index 56da2d1a3c..86700f94c3 100644 --- a/ja/starter/examples.md +++ b/ja/starter/examples.md @@ -3,6 +3,7 @@ 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 +order: 6 redirect_from: " " --- @@ -15,6 +16,5 @@ These are some additional examples with more extensive integrations. {% include community-caveat.html %} -- [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) +- [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 \ No newline at end of file diff --git a/ja/starter/faq.md b/ja/starter/faq.md index fd51f13b05..e21a5f4af4 100644 --- a/ja/starter/faq.md +++ b/ja/starter/faq.md @@ -3,6 +3,7 @@ layout: page title: Express に関する FAQ description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more. menu: starter +order: 7 redirect_from: " " --- @@ -93,6 +94,4 @@ middleware function. ## What version of Node.js does Express require? - [Express 4.x](/{{ page.lang }}/4x/api.html) には Node.js 0.10 以上が必要です。 -- [Express 5.x](/{{ page.lang }}/5x/api.html) には Node.js 18 以上が必要です。 - -### [Previous: More examples ](/{{ page.lang }}/starter/examples.html) +- [Express 5.x](/{{ page.lang }}/5x/api.html) には Node.js 18 以上が必要です。 \ No newline at end of file diff --git a/ja/starter/generator.md b/ja/starter/generator.md index ff4c74552c..28e96c5540 100644 --- a/ja/starter/generator.md +++ b/ja/starter/generator.md @@ -3,6 +3,7 @@ layout: page title: Express のアプリケーション生成プログラム 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 +order: 3 redirect_from: " " --- @@ -122,6 +123,4 @@ PS> $env:DEBUG='myapp:*'; npm start
The app structure created by the generator is just one of many ways to structure Express apps. Feel free to use this structure or modify it to best suit your needs. -
- -### [Previous: Hello World ](/{{ page.lang }}/starter/hello-world.html)    [Next: Basic routing](/{{ page.lang }}/starter/basic-routing.html) + \ No newline at end of file diff --git a/ja/starter/hello-world.md b/ja/starter/hello-world.md index c572898b06..1aad108c63 100644 --- a/ja/starter/hello-world.md +++ b/ja/starter/hello-world.md @@ -3,6 +3,7 @@ layout: page title: Express の「Hello World」の例 description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners. menu: starter +order: 2 redirect_from: " " --- @@ -44,6 +45,4 @@ This app starts a server and listens on port 3000 for connections. アプリケ $ node app.js ``` -次に、ブラウザーに [http://localhost:3000/](http://localhost:3000/) をロードして、出力を確認します。 - -### ここで紹介するのは基本的に、作成できる最も単純な Express アプリケーションです。このアプリケーションは単一ファイル・アプリケーションであり、[Express ジェネレーター](/{{ page.lang }}/starter/generator.html) を使用して得られるものでは _ありません_ 。このジェネレーターは、さまざまな目的で多数の JavaScript ファイル、Jade テンプレート、サブディレクトリーを使用する完全なアプリケーション用のスキャフォールディングを作成します。 +次に、ブラウザーに [http://localhost:3000/](http://localhost:3000/) をロードして、出力を確認します。 \ No newline at end of file diff --git a/ja/starter/installing.md b/ja/starter/installing.md index 6814a7e858..290c2931f8 100644 --- a/ja/starter/installing.md +++ b/ja/starter/installing.md @@ -3,6 +3,7 @@ layout: page title: Express のインストール description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm. menu: starter +order: 1 redirect_from: " " --- @@ -51,6 +52,4 @@ $ npm install express --no-save npm 5.0 以降のデフォルトでは、npm install はモジュールを `package.json` ファイルの `dependencies` リストに追加します。以前のバージョンの npm では、`--save` オプションを明示的に指定しなければなりません。その後、app ディレクトリで `npm install` を実行すると、依存関係リストにモジュールが自動的にインストールされます。 Then, afterwards, running `npm install` in the app directory will automatically install modules in the dependencies list. - - -### [Next: Hello World ](/{{ page.lang }}/starter/hello-world.html) \ No newline at end of file + \ No newline at end of file diff --git a/ja/starter/static-files.md b/ja/starter/static-files.md index 204e330e6f..01482e914c 100644 --- a/ja/starter/static-files.md +++ b/ja/starter/static-files.md @@ -3,6 +3,7 @@ layout: page title: Express での静的ファイルの提供 description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware. menu: starter +order: 5 redirect_from: " " --- @@ -76,6 +77,4 @@ 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) +For more details about the `serve-static` function and its options, see [serve-static](/resources/middleware/serve-static.html). \ No newline at end of file diff --git a/ko/advanced/best-practice-performance.md b/ko/advanced/best-practice-performance.md index 373816c548..32baab92a2 100644 --- a/ko/advanced/best-practice-performance.md +++ b/ko/advanced/best-practice-performance.md @@ -3,6 +3,7 @@ layout: page title: 프로덕션 환경에서의 Express 사용을 위한 성능 우수 사례 description: Express 애플리케이션의 프로덕션 환경에서 성능과 안정성을 최적화하기 위한 모범 사례를 알아봅니다. 여기에는 코드 최적화와 최적의 성능을 위한 환경 설정이 포함됩니다. menu: advanced +order: 4 redirect_from: " " --- diff --git a/ko/advanced/best-practice-security.md b/ko/advanced/best-practice-security.md index 43155eb952..f15744a61c 100644 --- a/ko/advanced/best-practice-security.md +++ b/ko/advanced/best-practice-security.md @@ -3,6 +3,7 @@ layout: page title: 프로덕션 환경의 Express를 위한 보안 우수 사례 description: Express 애플리케이션을 프로덕션 환경에서 운영할 때 반드시 지켜야 할 중요한 보안 모범 사례를 알아봅니다. 여기에는 TLS 사용, 입력값 검증, 보안 쿠키 설정, 그리고 다양한 취약점 예방 방법이 포함됩니다. menu: advanced +order: 3 redirect_from: " " --- @@ -61,7 +62,7 @@ Express 2.x 및 3.x에 대한 유지보수는 더 이상 이루어지지 않습 ### 오픈 리다이렉트 방지 -잠재적으로 위험한 사용자 입력의 예로 오픈 리다이렉트가 있습니다. 이는 애플리케이션이 URL을 사용자 입력으로 받아들여 (예: `?url=https://example.com` 쿼리 문자열)\ +잠재적으로 위험한 사용자 입력의 예로 오픈 리다이렉트가 있습니다. 이는 애플리케이션이 URL을 사용자 입력으로 받아들여 (예: `?url=https://example.com` 쿼리 문자열) `res.redirect`를 사용해 `location` 헤더를 설정하고 3xx 상태 코드를 반환하는 경우입니다. 애플리케이션은 악성 링크(예: 피싱 사이트) 로 사용자를 유도하는 위험을 방지하기 위해, 들어오는 URL에 대해 리다이렉트를 허용하는지 반드시 검증해야 합니다. @@ -139,8 +140,8 @@ app.disable('x-powered-by') {% include admonitions/note.html content=powered-advisory %} -Express는 자체 포맷의 "404 Not Found" 메시지와 포맷터 오류 응답 메시지도 전송합니다. 이러한 응답은\ -[사용자 정의 404 핸들러 추가](/en/starter/faq.html#how-do-i-handle-404-responses) 및\ +Express는 자체 포맷의 "404 Not Found" 메시지와 포맷터 오류 응답 메시지도 전송합니다. 이러한 응답은 +[사용자 정의 404 핸들러 추가](/en/starter/faq.html#how-do-i-handle-404-responses) 및 [사용자 정의 에러 핸들러 작성](/en/guide/error-handling.html#writing-error-handlers)을 통해 변경할 수 있습니다. ```js diff --git a/ko/advanced/developing-template-engines.md b/ko/advanced/developing-template-engines.md index 6926558ac1..a55dcfa916 100644 --- a/ko/advanced/developing-template-engines.md +++ b/ko/advanced/developing-template-engines.md @@ -3,6 +3,7 @@ layout: page title: Express용 템플릿 엔진 개발 description: App.engine()을 사용하여 Express.js에서 사용자 정의 템플릿 엔진을 개발하는 방법을 학습합니다. 직접 템플릿 렌더링 로직을 생성하고 통합하는 예제를 함께 제공합니다. menu: advanced +order: 1 redirect_from: " " --- diff --git a/ko/advanced/healthcheck-graceful-shutdown.md b/ko/advanced/healthcheck-graceful-shutdown.md index b57db7d289..42045b8e09 100644 --- a/ko/advanced/healthcheck-graceful-shutdown.md +++ b/ko/advanced/healthcheck-graceful-shutdown.md @@ -3,6 +3,7 @@ layout: page title: 상태 검사와 우아한 종료 description: Express 애플리케이션에서 헬스 체크와 그레이스풀 셧다운(Graceful Shutdown)을 구현하는 방법을 학습합니다. 이 기능은 애플리케이션의 신뢰성을 향상시키고, 배포를 원활하게 관리하며, Kubernetes와 같은 로드 밸런서와의 통합을 지원합니다. menu: advanced +order: 5 redirect_from: " " --- diff --git a/ko/advanced/security-updates.md b/ko/advanced/security-updates.md index 27d5094aa5..a5ca08ba4e 100644 --- a/ko/advanced/security-updates.md +++ b/ko/advanced/security-updates.md @@ -5,6 +5,7 @@ description: |- Express.js의 최신 보안 업데이트와 패치 사항을 확인합니다. 각 버전에 대한 상세한 취약점 목록을 포함하여, 애플리케이션의 보안을 유지하는 데 도움이 됩니다. menu: advanced +order: 2 redirect_from: " " --- diff --git a/ko/guide/behind-proxies.md b/ko/guide/behind-proxies.md index baa77d017b..872b248f1a 100644 --- a/ko/guide/behind-proxies.md +++ b/ko/guide/behind-proxies.md @@ -3,6 +3,7 @@ layout: page title: 프록시 환경에서 Express 사용 description: Express.js 애플리케이션을 리버스 프록시 뒤에서 올바르게 작동하도록 설정하는 방법을 알아보십시오. 클라이언트 IP 주소를 처리하기 위해 `trust proxy` 설정을 사용하는 것을 포함합니다. menu: guide +order: 8 redirect_from: " " --- diff --git a/ko/guide/database-integration.md b/ko/guide/database-integration.md index f7f488fd1b..4f0d3c34c2 100644 --- a/ko/guide/database-integration.md +++ b/ko/guide/database-integration.md @@ -3,6 +3,7 @@ layout: page title: Express 데이터베이스 통합 description: Discover how to integrate various databases with Express.js applications, including setup examples for MongoDB, MySQL, PostgreSQL, and more. menu: guide +order: 11 redirect_from: " " --- diff --git a/ko/guide/debugging.md b/ko/guide/debugging.md index 81a5fee4d8..4d258d491f 100644 --- a/ko/guide/debugging.md +++ b/ko/guide/debugging.md @@ -3,6 +3,7 @@ layout: page title: 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 +order: 7 redirect_from: " " --- diff --git a/ko/guide/error-handling.md b/ko/guide/error-handling.md index 1af96b5f13..8b88692df5 100644 --- a/ko/guide/error-handling.md +++ b/ko/guide/error-handling.md @@ -3,6 +3,7 @@ layout: page title: Express 오류 처리 description: Express.js가 동기 및 비동기 코드에서 오류를 처리하는 방식을 이해하고, 애플리케이션에 맞는 사용자 정의 오류 처리 미들웨어를 구현하는 방법을 알아보세요. menu: guide +order: 6 redirect_from: " " --- diff --git a/ko/guide/migrating-4.md b/ko/guide/migrating-4.md index b95dd4a24b..ecd5a86b2f 100644 --- a/ko/guide/migrating-4.md +++ b/ko/guide/migrating-4.md @@ -3,6 +3,7 @@ layout: page title: 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 +order: 9 redirect_from: " " --- @@ -393,15 +394,15 @@ $ npm install serve-favicon morgan method-override express-session body-parser m `app.js`를 다음과 같이 변경하십시오. 1. 기본 제공 Express 미들웨어 함수인 `express.favicon`, - `express.logger`, `express.methodOverride`, - `express.session`, `express.bodyParser` 및 - `express.errorHandler`는 더 이상 `express` - 오브젝트에 사용할 수 없습니다. 이들 함수의 대체 함수를 수동으로 - 설치한 후 앱에서 로드해야 합니다. + `express.logger`, `express.methodOverride`, + `express.session`, `express.bodyParser` 및 + `express.errorHandler`는 더 이상 `express` + 오브젝트에 사용할 수 없습니다. 이들 함수의 대체 함수를 수동으로 + 설치한 후 앱에서 로드해야 합니다. 2. `app.router` 함수는 이제 로드할 필요가 없습니다. - 이 함수는 유효한 Express 4 앱 오브젝트가 아니므로 - `app.use(app.router);` 코드를 제거하십시오. + 이 함수는 유효한 Express 4 앱 오브젝트가 아니므로 + `app.use(app.router);` 코드를 제거하십시오. 3. 미들웨어 함수들이 올바른 순서로 로드되는지 확인하십시오(앱 라우트를 로드한 후 `errorHandler`를 로드). diff --git a/ko/guide/migrating-5.md b/ko/guide/migrating-5.md index 199b1ce2a4..e06b94bc6b 100644 --- a/ko/guide/migrating-5.md +++ b/ko/guide/migrating-5.md @@ -3,6 +3,7 @@ layout: page title: 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 +order: 10 redirect_from: " " --- @@ -259,7 +260,7 @@ app.get('/user', (req, res) => {

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. +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: diff --git a/ko/guide/overriding-express-api.md b/ko/guide/overriding-express-api.md index bd55ab9b24..e70530488f 100644 --- a/ko/guide/overriding-express-api.md +++ b/ko/guide/overriding-express-api.md @@ -3,6 +3,7 @@ layout: page title: Overriding the Express API description: 프로토타입을 사용해 request와 response 객체의 메서드와 속성을 오버라이드하여 Express.js API를 커스터마이즈하고 확장하는 방법을 알아보세요. menu: guide +order: 4 --- # Overriding the Express API diff --git a/ko/guide/routing.md b/ko/guide/routing.md index 5f69c5fe50..c083dbe7e9 100644 --- a/ko/guide/routing.md +++ b/ko/guide/routing.md @@ -3,6 +3,7 @@ layout: page title: 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 +order: 1 redirect_from: " " --- diff --git a/ko/guide/using-middleware.md b/ko/guide/using-middleware.md index 6f65293a64..d80032ca83 100644 --- a/ko/guide/using-middleware.md +++ b/ko/guide/using-middleware.md @@ -3,6 +3,7 @@ layout: page title: Express 미들웨어 사용 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 +order: 3 redirect_from: " " --- diff --git a/ko/guide/using-template-engines.md b/ko/guide/using-template-engines.md index b881be8fda..a3e2cc5cb7 100644 --- a/ko/guide/using-template-engines.md +++ b/ko/guide/using-template-engines.md @@ -3,6 +3,7 @@ layout: page title: Express와 함께 템플리트 엔진 사용 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 +order: 5 redirect_from: " " --- diff --git a/ko/guide/writing-middleware.md b/ko/guide/writing-middleware.md index b6ab5ed606..61b877300c 100644 --- a/ko/guide/writing-middleware.md +++ b/ko/guide/writing-middleware.md @@ -3,6 +3,7 @@ layout: page title: Express 앱에서 사용하기 위한 미들웨어 작성 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 +order: 2 redirect_from: " " --- diff --git a/ko/resources/community.md b/ko/resources/community.md index 04445acf5b..91788e786c 100644 --- a/ko/resources/community.md +++ b/ko/resources/community.md @@ -3,6 +3,7 @@ layout: page title: Express 커뮤니티 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 +order: 1 redirect_from: " " --- diff --git a/ko/resources/contributing.md b/ko/resources/contributing.md index e37cee3122..b0944346a1 100644 --- a/ko/resources/contributing.md +++ b/ko/resources/contributing.md @@ -3,6 +3,7 @@ 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 +order: 5 redirect_from: " " --- @@ -87,7 +88,7 @@ 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). +[the triage process document](https://github.com/expressjs/discussions/blob/master/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 @@ -182,6 +183,26 @@ The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/doc 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) +### Inactivity and Emeritus Policy for Any Role + +To support the health and continuity of the project, all individuals holding a role within the community (such as Triager, Committer, WG member, Project Captain, or TC member) are encouraged to maintain active participation. + +Inactivity is defined as the absence of meaningful involvement in the project—such as contributions, code reviews, triage, meeting attendance, or discussion participation—for a continuous period of 6 months. + +#### Exceptions + +Anyone may request a temporary leave from active participation due to personal or professional reasons. In such cases, the individual should inform the relevant team or the Technical Committee (TC). During this time, the inactivity policy is paused, and the individual will not be flagged as inactive. + +#### Inactivity Process + +- If someone is deemed inactive, the individual may be transitioned to an emeritus role that reflects their past contributions. A best effort will be made to inform them that this has occurred. They may request to be reinstated when they are ready to be active again. +- The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time. + +#### Accountability + +- The Technical Committee (TC) and the respective captains of each package/team are responsible for assessing activity levels and enacting this policy fairly and transparently, in coordination with other relevant teams. +- In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team. + ### Developer's Certificate of Origin 1.1 ```text @@ -237,18 +258,18 @@ 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. + bug you want to fix or the feature that you want to add. 2. Create your own fork on GitHub, then - checkout your fork. + 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. + 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`. + then run `npm test`. 5. Ensure your code is linted by running `npm run lint` -- fix any issue you - see listed. + 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`. + 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 @@ -346,22 +367,22 @@ This is the contribution documentation for the [expressjs.com](https://github.co #### 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 + - 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 + - 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. + - 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? @@ -384,12 +405,12 @@ The steps below will guide you through the Expressjs.com contribution process. 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. + - 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. + - For submissions proposing significant change, we encourage you to follow the review process before starting work. #### Step 2: Get the Application Code Base @@ -434,12 +455,12 @@ The Express JS website is built using [Jekyll](https://jekyllrb.com/) and is hos 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. + - 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. + 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 diff --git a/ko/resources/glossary.md b/ko/resources/glossary.md index 0c81a97d1b..1e1f7b4a04 100644 --- a/ko/resources/glossary.md +++ b/ko/resources/glossary.md @@ -3,6 +3,7 @@ layout: page title: Express 용어집 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 +order: 2 redirect_from: " " --- diff --git a/ko/resources/middleware.md b/ko/resources/middleware.md index b079e6264a..24e25e3986 100644 --- a/ko/resources/middleware.md +++ b/ko/resources/middleware.md @@ -3,6 +3,7 @@ layout: middleware title: Express 미들웨어 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 +order: 3 redirect_from: " " module: mw-home --- diff --git a/ko/resources/utils.md b/ko/resources/utils.md index 424448498b..fe36da50f2 100644 --- a/ko/resources/utils.md +++ b/ko/resources/utils.md @@ -3,6 +3,7 @@ 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 +order: 4 redirect_from: " " --- diff --git a/ko/starter/basic-routing.md b/ko/starter/basic-routing.md index abeb759f89..d428de6877 100644 --- a/ko/starter/basic-routing.md +++ b/ko/starter/basic-routing.md @@ -3,6 +3,7 @@ layout: page title: 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 +order: 4 redirect_from: " " --- @@ -21,7 +22,7 @@ app.METHOD(PATH, HANDLER) 여기서, - `app`은 `express`의 인스턴스입니다. -- `METHOD`는 [HTTP 요청 메소드](http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol)입니다. +- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase. - `PATH`는 서버에서의 경로입니다. - `HANDLER`는 라우트가 일치할 때 실행되는 함수입니다. @@ -65,4 +66,3 @@ app.delete('/user', (req, res) => { 라우팅에 대한 자세한 내용을 확인하려면 [라우팅 안내서](/{{ 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/ko/starter/examples.md b/ko/starter/examples.md index 56da2d1a3c..86700f94c3 100644 --- a/ko/starter/examples.md +++ b/ko/starter/examples.md @@ -3,6 +3,7 @@ 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 +order: 6 redirect_from: " " --- @@ -15,6 +16,5 @@ These are some additional examples with more extensive integrations. {% include community-caveat.html %} -- [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) +- [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 \ No newline at end of file diff --git a/ko/starter/faq.md b/ko/starter/faq.md index b7c54f7172..eb2d3c48a8 100644 --- a/ko/starter/faq.md +++ b/ko/starter/faq.md @@ -3,6 +3,7 @@ layout: page title: Express 자주 묻는 질문(FAQ) description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more. menu: starter +order: 7 redirect_from: " " --- @@ -92,6 +93,4 @@ app.use((err, req, res, next) => { ## What version of Node.js does Express require? - [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) +- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher. \ No newline at end of file diff --git a/ko/starter/generator.md b/ko/starter/generator.md index 1961b4da57..adbf59aa75 100644 --- a/ko/starter/generator.md +++ b/ko/starter/generator.md @@ -3,6 +3,7 @@ layout: page title: Express 애플리케이션 생성기 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 +order: 3 redirect_from: " " --- @@ -122,6 +123,4 @@ PS> $env:DEBUG='myapp:*'; npm start
생성기에 의해 작성된 앱 구조는 Express 앱을 구조화하는 여러 방법 중 하나에 불과합니다. 이러한 구조를 사용하거나 사용자의 요구사항에 가장 적합하도록 구조를 수정하십시오. -
- -### [Previous: Hello World ](/{{ page.lang }}/starter/hello-world.html)    [Next: Basic routing](/{{ page.lang }}/starter/basic-routing.html) + \ No newline at end of file diff --git a/ko/starter/hello-world.md b/ko/starter/hello-world.md index c66293ba50..95616e7ea5 100644 --- a/ko/starter/hello-world.md +++ b/ko/starter/hello-world.md @@ -3,6 +3,7 @@ layout: page title: Express "Hello World" 예제 description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners. menu: starter +order: 2 redirect_from: " " --- @@ -46,6 +47,4 @@ app.listen(port, () => { $ node app.js ``` -이후 브라우저에서 [http://localhost:3000/](http://localhost:3000/)을 로드하여 결과물을 확인하십시오. - -### [Previous: Installing ](/{{ page.lang }}/starter/installing.html)    [Next: Express Generator ](/{{ page.lang }}/starter/generator.html) +이후 브라우저에서 [http://localhost:3000/](http://localhost:3000/)을 로드하여 결과물을 확인하십시오. \ No newline at end of file diff --git a/ko/starter/installing.md b/ko/starter/installing.md index 792b530ddd..d25acf062c 100644 --- a/ko/starter/installing.md +++ b/ko/starter/installing.md @@ -3,6 +3,7 @@ layout: page title: Express 설치 description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm. menu: starter +order: 1 redirect_from: " " --- @@ -48,6 +49,4 @@ $ npm install express --no-save
`--save` 옵션을 통해 설치된 Node 모듈은 `package.json` 파일 내의 `dependencies` 목록에 추가됩니다. 이후 `app` 디렉토리에서 `npm install`을 실행하면 종속 항목 목록 내의 모듈이 자동으로 설치됩니다. -
- -### [Next: Hello World ](/{{ page.lang }}/starter/hello-world.html) \ No newline at end of file + \ No newline at end of file diff --git a/ko/starter/static-files.md b/ko/starter/static-files.md index dc872597e8..847de1f3e7 100644 --- a/ko/starter/static-files.md +++ b/ko/starter/static-files.md @@ -3,6 +3,7 @@ layout: page title: Express에서 정적 파일 제공 description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware. menu: starter +order: 5 redirect_from: " " --- @@ -76,6 +77,4 @@ 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) +For more details about the `serve-static` function and its options, see [serve-static](/resources/middleware/serve-static.html). \ No newline at end of file diff --git a/pt-br/3x/api.md b/pt-br/3x/api.md index e7d0273c41..51e2c55373 100644 --- a/pt-br/3x/api.md +++ b/pt-br/3x/api.md @@ -1,8 +1,8 @@ --- 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. +title: Express 3.x - Referência de API +description: Acesso à referência da API do Express.js versão 3.x, observando que esta versão é final de vida e não mais mantida - inclui detalhes sobre módulos e métodos. menu: api redirect_from: " " --- @@ -14,7 +14,7 @@ redirect_from: " " This series will continue to receive only security updates and bug fixes until July 2015. It is highly recommended to upgrade to Express 4.x. -If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options). +Se você não puder atualizar as últimas 3.x, por favor considere as [Opções de Suporte Comercial](/{{ page.lang }}/support#comercial-support-options). diff --git a/pt-br/4x/api.md b/pt-br/4x/api.md index 7adeb1cdf1..ad55afc5ca 100644 --- a/pt-br/4x/api.md +++ b/pt-br/4x/api.md @@ -2,7 +2,7 @@ layout: api version: 4x title: Express 4.x - Referência de API -description: Access the API reference for Express.js 4.x, detailing all modules, methods, and properties for building web applications with this version. +description: Acesse a referência da API para Express.js 4.x, detalhando todos os módulos, métodos e propriedades para construir aplicações web com esta versão. menu: api redirect_from: " " --- @@ -13,7 +13,7 @@ redirect_from: " " {% capture node-version %} -Express 4.0 requires Node.js 0.10 or higher. +Express 4.0 requer Node.js 0.10 ou superior. {% endcapture %} diff --git a/pt-br/5x/api.md b/pt-br/5x/api.md index bcb1fdb6b0..4007e8d792 100644 --- a/pt-br/5x/api.md +++ b/pt-br/5x/api.md @@ -2,7 +2,7 @@ layout: api version: 5x title: Express 5.x - Referência da API -description: Access the API reference for Express.js 5.x, detailing all modules, methods, and properties for building web applications with this latest version. +description: Acesse a referência da API para Express.js 5.x, detalhando todos os módulos, métodos e propriedades para construir aplicações web com esta versão mais recente. menu: api redirect_from: " " --- @@ -13,7 +13,7 @@ redirect_from: " " {% capture node-version %} -Express 5.0 requires Node.js 18 or higher. +Express 5.0 requer Node.js 18 ou superior. {% endcapture %} diff --git a/pt-br/advanced/best-practice-performance.md b/pt-br/advanced/best-practice-performance.md index e4aae98528..c4dbf9574a 100644 --- a/pt-br/advanced/best-practice-performance.md +++ b/pt-br/advanced/best-practice-performance.md @@ -1,8 +1,9 @@ --- layout: page title: Melhores Práticas de Desempenho Usando o Express em Produção -description: Discover performance and reliability best practices for Express apps in production, covering code optimizations and environment setups for optimal performance. +description: Descubra desempenho e confiabilidade melhores práticas para aplicativos Express na produção, cobrindo otimizações de código e configurações de ambiente para um desempenho ideal. menu: advanced +order: 4 redirect_from: " " --- @@ -17,7 +18,7 @@ Este tópico se enquadra claramente no mundo de "devops", abordando o desenvolvi - Use a compactação gzip - Não use funções síncronas - Faça o registro de logs corretamente - - [Handle exceptions properly](#handle-exceptions-properly) + - [Tratar exceções corretamente](#handle-exceptions-properly) - [Itens a fazer no seu ambiente / configuração](#env) (a parte de ops). - Configure o NODE_ENV para "produção" - Executar o seu aplicativo (e Node) diretamente com o sistema @@ -36,7 +37,7 @@ para melhorar o desempenho dos aplicativos: - Use a compactação gzip - Não use funções síncronas - Faça o registro de logs corretamente -- [Handle exceptions properly](#handle-exceptions-properly) +- [Tratar exceções corretamente](#handle-exceptions-properly) ### Use a compactação gzip @@ -63,16 +64,18 @@ aplicativo. Evite o uso delas na produção. Apesar de o Node e muitos módulos fornecerem versões síncronas e assíncronas de suas funções, sempre use as versões assíncronas na produção. O único momento em que o uso de uma função síncrona pode ser justificado é na primeira inicialização. -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. Obviamente, não seria desejado usar isto na produção, mas sim antes, para garantir que seu código está pronto para produção. Consulte a Atualização +Se estiver usando o Node.js + ou o .+, é possível usar a sinalização `--trace-sync-io` da linha de comandos para imprimir um aviso e um rastreio de pilha sempre que o seu aplicativo usar uma API síncrona. Obviamente, não seria desejado usar isto na produção, mas sim antes, para garantir que seu código está pronto para produção. Consulte a Atualização semanal para o io.js 2.1.0 para obter mais informações. ### Lide com exceções adequadamente Em geral, existem duas razões para registrar logs em seu aplicativo: Para depuração e para registro de logs de atividade do aplicativo (essencialmente, todo o resto). Usar o `console.log()` ou o `console.err()` para imprimir mensagens de log no -terminal é uma prática comum em desenvolvimento. 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. +terminal é uma prática comum em desenvolvimento. Mas essas +funções são síncronas quando o destino é um terminal ou um arquivo, portanto elas não são adequadas para produção, a não ser que +a saída seja canalizada para outro programa. -#### For debugging +#### Para depuração Se estiver registrando logs com o propósito de depuração, então ao invés de usar o `console.log()`, use um módulo especial para depuração como o [debug](https://www.npmjs.com/package/debug). Este @@ -82,7 +85,10 @@ módulo permite que seja usada a variável de ambiente DEBUG para controlar quai #### Para atividade do aplicativo -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. +Se estiver registrando logs de atividade do aplicativo (por +exemplo, rastreamento de tráfico ou chamadas de API), ao invés de +usar o `console.log()`, use uma biblioteca de +registro de logs como [Winston](https://www.npmjs.com/package/pino) ou Bunyan. ### Lide com exceções adequadamente @@ -110,7 +116,7 @@ Para obter mais informações sobre os fundamentos de manipulação de erros, co - [Manipulação de Erros no Node.js](https://www.tritondatacenter.com/node-js/production/design/errors) -#### Use try-catch +#### Usar try-catch Try-catch é uma construção da linguagem JavaScript que pode ser usada para capturar exceções em um código síncrono. Use try-catch, por exemplo, para tratar erros de análise sintática de JSON como mostrado abaixo. @@ -139,7 +145,7 @@ exceções. #### Use promessas -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)` +Quando um erro é lançado em uma função `async` ou uma promessa rejeitada é aguardada dentro de uma função `async`, esses erros serão passados para o manipulador de erros como se chamando `next(err)` ```js app.get('/', async (req, res, next) => { @@ -153,7 +159,7 @@ app.use((err, req, res, next) => { }) ``` -Also, you can use asynchronous functions for your middleware, and the router will handle errors if the promise fails, for example: +Além disso, você pode usar funções assíncronas para o seu middleware, e o roteador irá lidar com erros se a promessa falhar, por exemplo: ```js app.use(async (req, res, next) => { @@ -163,7 +169,7 @@ app.use(async (req, res, next) => { }) ``` -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. +A melhor prática é lidar com os erros o mais próximo possível do site. Então enquanto isso é manipulado no roteador, É melhor encontrar o erro no middleware e lidar com ele sem depender de um middleware separado para manipular erros. #### O que não fazer @@ -345,7 +351,7 @@ Clustering is made possible with Node's [cluster module](https://nodejs.org/api/ spawn de processos de trabalho e distribua conexões recebidas entre os trabalhadores. -#### Using PM2 +#### Usando 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](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). diff --git a/pt-br/advanced/best-practice-security.md b/pt-br/advanced/best-practice-security.md index 4868367700..02dc6e58eb 100644 --- a/pt-br/advanced/best-practice-security.md +++ b/pt-br/advanced/best-practice-security.md @@ -3,6 +3,7 @@ layout: page title: Melhores Práticas de Segurança para o Express em Produção description: Discover crucial security best practices for Express apps in production, including using TLS, input validation, secure cookies, and preventing vulnerabilities. menu: advanced +order: 3 redirect_from: " " --- diff --git a/pt-br/advanced/developing-template-engines.md b/pt-br/advanced/developing-template-engines.md index a146c7d9ff..8d0e855b58 100644 --- a/pt-br/advanced/developing-template-engines.md +++ b/pt-br/advanced/developing-template-engines.md @@ -3,6 +3,7 @@ layout: page title: Desenvolvendo mecanismos de modelo para o 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 +order: 1 redirect_from: " " --- diff --git a/pt-br/advanced/healthcheck-graceful-shutdown.md b/pt-br/advanced/healthcheck-graceful-shutdown.md index be0604829a..be4f590a95 100644 --- a/pt-br/advanced/healthcheck-graceful-shutdown.md +++ b/pt-br/advanced/healthcheck-graceful-shutdown.md @@ -3,6 +3,7 @@ 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 +order: 5 redirect_from: " " --- diff --git a/pt-br/advanced/security-updates.md b/pt-br/advanced/security-updates.md index 3bbb7e8f3f..854a685bd2 100644 --- a/pt-br/advanced/security-updates.md +++ b/pt-br/advanced/security-updates.md @@ -3,6 +3,7 @@ layout: page title: Atualizações de segurança do Express 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 +order: 2 redirect_from: " " --- @@ -78,7 +79,7 @@ If you believe you have discovered a security vulnerability in Express, please s This series will continue to receive only security updates and bug fixes until July 2015. It is highly recommended to upgrade to Express 4.x. -If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options). +Se você não puder atualizar as últimas 3.x, por favor considere as [Opções de Suporte Comercial](/{{ page.lang }}/support#comercial-support-options). diff --git a/pt-br/api.md b/pt-br/api.md index d12a98b4f7..821025c6e0 100644 --- a/pt-br/api.md +++ b/pt-br/api.md @@ -2,7 +2,7 @@ layout: api version: 5x title: Express 5.x - Referência da API -description: Access the API reference for Express.js detailing all modules, methods, and properties for building web applications with this version. +description: Acesse a referência da API para Express.js , detalhando todos os módulos, métodos e propriedades para construir aplicações web com esta versão. menu: api redirect_from: " " --- diff --git a/pt-br/changelog/index.md b/pt-br/changelog/index.md index 2456265b18..fae626f153 100644 --- a/pt-br/changelog/index.md +++ b/pt-br/changelog/index.md @@ -10,7 +10,7 @@ redirect_from: