remix-run/remix cli@0.3.0

cli v0.3.0

on GitHub

Minor Changes

• BREAKING CHANGE: Remix app scaffolding, remix doctor, and remix routes now use app/actions with controller files only. The old app/controllers directory name has been replaced by app/actions, and root route actions should no longer live in standalone files.

  When upgrading an app, move app/controllers to app/actions, then consolidate root leaf route files into app/actions/controller.tsx. For example, old files like app/controllers/home.tsx, app/controllers/about.tsx, or app/controllers/uploads.ts should become home, about, and uploads entries in the root controller's actions object. Root controller tests should follow the same shape and live in app/actions/controller.test.ts or app/actions/controller.test.tsx.

  Nested route maps should live under directories named for route-map keys, not URL path segments. For example, routes.auth is owned by app/actions/auth/controller.tsx, and routes.account.settings is owned by app/actions/account/settings/controller.tsx. Keep route-local pages, schemas, helpers, and tests beside the controller that owns them, but move shared cross-route UI to app/ui.

  This migration also changes how apps should call router.map(). A controller owns the direct leaf routes in the route map passed to router.map(): router.map(routes, rootController) maps only direct leaf routes in the root route map, so nested route-map keys such as auth, account, or admin do not belong in the root controller's actions object. Map every nested route map explicitly in app/router.ts:

  router.map(routes, rootController)
  router.map(routes.auth, authController)
  router.map(routes.account, accountController)
  router.map(routes.account.settings, accountSettingsController)

  Controller middleware applies only to the direct actions in that controller. Middleware on app/actions/controller.tsx applies only to the direct root actions in that controller; it does not protect controllers registered for nested route maps. If an app previously relied on middleware from one controller to protect another controller, copy the relevant middleware to each controller that needs it, such as app/actions/account/controller.tsx and app/actions/account/settings/controller.tsx.

  After moving files, remove nested route-map keys and unknown action keys from every controller. Each controller's actions object should contain exactly the direct leaf route keys for the route map passed to the matching router.map() call.

  The default template now starts with a single home route. Shared HTML rendering should live in middleware and be read from request context with context.render, matching the default template's app/middleware/render.tsx pattern.

• Updated the default remix new app template to serve static assets from public/, include a Remix favicon, and share the generated document shell between the starter home page and future routes.

Patch Changes

• Fixed CLI argument edge cases so -- separators still work after global options, completion help can be requested after a shell name, and remix test completions no longer duplicate --help.

• Changed the default remix new server template to use remix/node-fetch-server instead of remix/node-serve, avoiding the native uWebSockets.js transport for freshly scaffolded apps.

• Fixed remix new so scaffolded apps include the template .gitignore file from the published CLI package.

• Simplified the default app template asset server configuration so workspace installs serve package imports through node_modules without Remix monorepo-specific ../packages rules.

• Simplified the default remix new home page so it relies on the shared document title default instead of duplicating app display-name decoding in the scaffold page module.

• Removed unused frame resolver plumbing from the default remix new app template while keeping the client-entry setup used for isolated browser interactivity.

• Updated the default app template's Remix agent skill so code agents can discover the available remix/* README files shipped in node_modules/remix.

• Improved the packaging flow for the remix new app template so the template can run directly as a root workspace during development while still being included in the published CLI package.

• Bumped @remix-run/* dependencies:

  • test@0.4.0