{
  "id": 3034483,
  "title": "Meteor 3.5: accounts-express Brings Meteor Accounts to Express",
  "url": "https://urgent.news/2026/08/24/meteor-3-5-accounts-express-brings-meteor-accounts-to-express",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-24T14:06:12.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/meteor/meteor-35-accounts-express-brings-meteor-accounts-to-express-lni"
  },
  "original_language": "en",
  "account": "Meteor 3.5 introduces accounts-express, a package that integrates Meteor Accounts with Express routes, allowing developers to bring authenticated Meteor users into Express without building a separate session system. This integration preserves the Meteor authentication, data, and developer experience, making it easier to work with Express endpoints in Meteor applications.\n\nTo use accounts-express, install the package and add it to an Express route using createAuthMiddleware. This middleware reads a Meteor login token and attaches the resolved user ID to req.userId, allowing the application's existing login state to carry through to the HTTP layer. This means that account summaries, webhook follow-ups, and private API routes can reuse the signed-in user's identity without separate credentials, sessions, and user lookups.\n\nFor client code, use the package's authenticated fetch to make authenticated requests to Express routes. With the package's authentication enabled, signed-in clients will automatically include their Meteor login token in requests. This also makes the security boundary clear, as browser address bar visits do not automatically include the Meteor login token.\n\naccounts-express simplifies integrating Meteor authentication with Express, making it easier to protect routes and maintain a consistent authentication experience across both layers. This integration is part of Meteor's ongoing modernization efforts and addresses long-standing integration gaps, allowing developers to focus on building their applications rather than building additional infrastructure.",
  "summary": "Bring authenticated Meteor users into Express routes without building a second session system. Meteor 3 is modernizing the framework in two complementary ways: adopting proven tools from the wider JavaScript ecosystem and completing them with the Meteor-specific capabilities that make an application coherent. Adding a library is only the start; a strong integration should preserve the Accounts,…",
  "key_points": [
    "accounts-express package integrates Meteor Accounts with Express routes.",
    "Middleware reads Meteor login token, attaches user ID to req.userId.",
    "Enables authenticated requests to Express routes using authenticated fetch."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}