chore: Update version for release (pre)

[mcansh]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to release-next, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

release-next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on release-next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@remix-run/cloudflare@1.12.0-pre.0

Minor Changes

• Rename createCloudflareKVSessionStorage to createWorkersKVSessionStorage (#2542)

Patch Changes

• Update Cloudflare Workers adapter's RequestHandler type to be in line with other adapters (#4884)
• Export JsonFunction type in @remix-run/cloudflare and @remix-run/deno (#5206)
• Updated dependencies:
  • @remix-run/server-runtime@1.12.0-pre.0

@remix-run/dev@1.12.0-pre.0

Minor Changes

• The new dev server (#5133)

  The new dev flow is to spin up the dev server alongside your normal Remix app server:

  # spin up the new dev server
  remix dev
  
  # spin up your app server in a separate tab or via `concurrently`
  nodemon ./server.js

  The dev server will build your app in dev mode and then rebuild whenever any app files change.
  It will also wait for your app server to be "ready" (more on this later) before triggering a live reload in your browser.

  Benefits

  • Navigations no longer wipe in-memory references (e.g. database connections, in-memory caches, etc...). That means no need to use global trick anymore.
  • Supports any app server, not just the Remix App Server.
  • Automatically wires up the live reload port for you (no need for you to mess with env vars for that anymore)

  App server picks up changes

  Use nodemon (or similar) so that your app server restarts and picks up changes after a rebuild finishes.

  For example, you can use wrangler --watch for Cloudflare.

  Alternatively, you can roll your own with chokidar (or similar) if you want to still use the global trick to persist in-memory stuff across rebuilds.

  Configure

  To enable the new dev server with all defaults, set the unstable_dev future flag to true:

  // remix.config.js
  
  module.exports = {
    future: {
      unstable_dev: true,
    },
  };

  You can also set specific options:

  // remix.config.js
  
  module.exports = {
    future: {
      unstable_dev: {
        // Port to use for the dev server (i.e. the live reload websocket)
        // Can be overridden by a CLI flag: `remix dev --port 3011`
        // default: finds an empty port and uses that
        port: 3010,
  
        // Port for your running Remix app server
        // Can be overridden by a CLI flag: `remix dev --app-server-port 3021`
        // default: `3000`
        appServerPort: 3020,
  
        // Path to the Remix request handler in your app server
        // Most app server will route all requests to the Remix request handler and will not need to set this option.
        // If your app server _does_ route only certain request paths to the Remix request handler, then you'll need to set this.
        // default: `""`
        remixRequestHandlerPath: "/products",
  
        // Milliseconds between "readiness" pings to your app server
        // When a Remix rebuild finishes, the dev server will ping a special endpoint (`__REMIX_ASSETS_MANIFEST`)
        // to check if your app server is serving up-to-date routes and assets.
        // You can set this option to tune how frequently the dev server polls your app server.
        // default: `50`
        rebuildPollIntervalMs: 25,
      },
    },
  };

Patch Changes

• When running the dev server (current or unstable_dev), each rebuild wrote new files to build/ and public/build/. (#5223)
  Since these files are not removed (unless the dev server crashes or is gracefully terminated),
  thousands of files could accumulate as the dev server ran.
  This causes performance issues and could be confusing.

  Now, the dev server also cleans up the build directories whenever a rebuild starts.

• Updated dependencies:

  • @remix-run/serve@1.12.0-pre.0
  • @remix-run/server-runtime@1.12.0-pre.0

@remix-run/node@1.12.0-pre.0

Minor Changes

• Add remove and getFilePath methods to NodeOnDiskFile (#4408)

Patch Changes

• Export JsonFunction as a type in @remix-run/node (#5204)
• Updated dependencies:
  • @remix-run/server-runtime@1.12.0-pre.0

@remix-run/react@1.12.0-pre.0

Minor Changes

• The new dev server (#5133)

  The new dev flow is to spin up the dev server alongside your normal Remix app server:

  # spin up the new dev server
  remix dev
  
  # spin up your app server in a separate tab or via `concurrently`
  nodemon ./server.js

  The dev server will build your app in dev mode and then rebuild whenever any app files change.
  It will also wait for your app server to be "ready" (more on this later) before triggering a live reload in your browser.

  Benefits

  • Navigations no longer wipe in-memory references (e.g. database connections, in-memory caches, etc...). That means no need to use global trick anymore.
  • Supports any app server, not just the Remix App Server.
  • Automatically wires up the live reload port for you (no need for you to mess with env vars for that anymore)

  App server picks up changes

  Use nodemon (or similar) so that your app server restarts and picks up changes after a rebuild finishes.

  For example, you can use wrangler --watch for Cloudflare.

  Alternatively, you can roll your own with chokidar (or similar) if you want to still use the global trick to persist in-memory stuff across rebuilds.

  Configure

  To enable the new dev server with all defaults, set the unstable_dev future flag to true:

  // remix.config.js
  
  module.exports = {
    future: {
      unstable_dev: true,
    },
  };

  You can also set specific options:

  // remix.config.js
  
  module.exports = {
    future: {
      unstable_dev: {
        // Port to use for the dev server (i.e. the live reload websocket)
        // Can be overridden by a CLI flag: `remix dev --port 3011`
        // default: finds an empty port and uses that
        port: 3010,
  
        // Port for your running Remix app server
        // Can be overridden by a CLI flag: `remix dev --app-server-port 3021`
        // default: `3000`
        appServerPort: 3020,
  
        // Path to the Remix request handler in your app server
        // Most app server will route all requests to the Remix request handler and will not need to set this option.
        // If your app server _does_ route only certain request paths to the Remix request handler, then you'll need to set this.
        // default: `""`
        remixRequestHandlerPath: "/products",
  
        // Milliseconds between "readiness" pings to your app server
        // When a Remix rebuild finishes, the dev server will ping a special endpoint (`__REMIX_ASSETS_MANIFEST`)
        // to check if your app server is serving up-to-date routes and assets.
        // You can set this option to tune how frequently the dev server polls your app server.
        // default: `50`
        rebuildPollIntervalMs: 25,
      },
    },
  };

Patch Changes

• Bump react router versions (#5242)
• Configure the browser-side live reload socket timeout via the new timeoutMs prop on <LiveReload /> (#4036)
• Added support for unstable_useBlocker and unstable_usePrompt from React Router (#5151)

@remix-run/serve@1.12.0-pre.0

Minor Changes

• The new dev server (#5133)

  The new dev flow is to spin up the dev server alongside your normal Remix app server:

  # spin up the new dev server
  remix dev
  
  # spin up your app server in a separate tab or via `concurrently`
  nodemon ./server.js

  The dev server will build your app in dev mode and then rebuild whenever any app files change.
  It will also wait for your app server to be "ready" (more on this later) before triggering a live reload in your browser.

  Benefits

  • Navigations no longer wipe in-memory references (e.g. database connections, in-memory caches, etc...). That means no need to use global trick anymore.
  • Supports any app server, not just the Remix App Server.
  • Automatically wires up the live reload port for you (no need for you to mess with env vars for that anymore)

  App server picks up changes

  Use nodemon (or similar) so that your app server restarts and picks up changes after a rebuild finishes.

  For example, you can use wrangler --watch for Cloudflare.

  Alternatively, you can roll your own with chokidar (or similar) if you want to still use the global trick to persist in-memory stuff across rebuilds.

  Configure

  To enable the new dev server with all defaults, set the unstable_dev future flag to true:

  // remix.config.js
  
  module.exports = {
    future: {
      unstable_dev: true,
    },
  };

  You can also set specific options:

  // remix.config.js
  
  module.exports = {
    future: {
      unstable_dev: {
        // Port to use for the dev server (i.e. the live reload websocket)
        // Can be overridden by a CLI flag: `remix dev --port 3011`
        // default: finds an empty port and uses that
        port: 3010,
  
        // Port for your running Remix app server
        // Can be overridden by a CLI flag: `remix dev --app-server-port 3021`
        // default: `3000`
        appServerPort: 3020,
  
        // Path to the Remix request handler in your app server
        // Most app server will route all requests to the Remix request handler and will not need to set this option.
        // If your app server _does_ route only certain request paths to the Remix request handler, then you'll need to set this.
        // default: `""`
        remixRequestHandlerPath: "/products",
  
        // Milliseconds between "readiness" pings to your app server
        // When a Remix rebuild finishes, the dev server will ping a special endpoint (`__REMIX_ASSETS_MANIFEST`)
        // to check if your app server is serving up-to-date routes and assets.
        // You can set this option to tune how frequently the dev server polls your app server.
        // default: `50`
        rebuildPollIntervalMs: 25,
      },
    },
  };

Patch Changes

• Updated dependencies:
  • @remix-run/express@1.12.0-pre.0

@remix-run/server-runtime@1.12.0-pre.0

Minor Changes

• The new dev server (#5133)

  The new dev flow is to spin up the dev server alongside your normal Remix app server:

  # spin up the new dev server
  remix dev
  
  # spin up your app server in a separate tab or via `concurrently`
  nodemon ./server.js

  The dev server will build your app in dev mode and then rebuild whenever any app files change.
  It will also wait for your app server to be "ready" (more on this later) before triggering a live reload in your browser.

  Benefits

  • Navigations no longer wipe in-memory references (e.g. database connections, in-memory caches, etc...). That means no need to use global trick anymore.
  • Supports any app server, not just the Remix App Server.
  • Automatically wires up the live reload port for you (no need for you to mess with env vars for that anymore)

  App server picks up changes

  Use nodemon (or similar) so that your app server restarts and picks up changes after a rebuild finishes.

  For example, you can use wrangler --watch for Cloudflare.

  Alternatively, you can roll your own with chokidar (or similar) if you want to still use the global trick to persist in-memory stuff across rebuilds.

  Configure

  To enable the new dev server with all defaults, set the unstable_dev future flag to true:

  // remix.config.js
  
  module.exports = {
    future: {
      unstable_dev: true,
    },
  };

  You can also set specific options:

  // remix.config.js
  
  module.exports = {
    future: {
      unstable_dev: {
        // Port to use for the dev server (i.e. the live reload websocket)
        // Can be overridden by a CLI flag: `remix dev --port 3011`
        // default: finds an empty port and uses that
        port: 3010,
  
        // Port for your running Remix app server
        // Can be overridden by a CLI flag: `remix dev --app-server-port 3021`
        // default: `3000`
        appServerPort: 3020,
  
        // Path to the Remix request handler in your app server
        // Most app server will route all requests to the Remix request handler and will not need to set this option.
        // If your app server _does_ route only certain request paths to the Remix request handler, then you'll need to set this.
        // default: `""`
        remixRequestHandlerPath: "/products",
  
        // Milliseconds between "readiness" pings to your app server
        // When a Remix rebuild finishes, the dev server will ping a special endpoint (`__REMIX_ASSETS_MANIFEST`)
        // to check if your app server is serving up-to-date routes and assets.
        // You can set this option to tune how frequently the dev server polls your app server.
        // default: `50`
        rebuildPollIntervalMs: 25,
      },
    },
  };

• remove react & react-dom from peerDependencies (#4801)

Patch Changes

• Bump react router versions (#5242)

create-remix@1.12.0-pre.0

Patch Changes

• Updated dependencies:
  • @remix-run/dev@1.12.0-pre.0

@remix-run/architect@1.12.0-pre.0

Patch Changes

• Updated dependencies:
  • @remix-run/node@1.12.0-pre.0

@remix-run/cloudflare-pages@1.12.0-pre.0

Patch Changes

• Updated dependencies:
  • @remix-run/cloudflare@1.12.0-pre.0

@remix-run/cloudflare-workers@1.12.0-pre.0

Patch Changes

• Update Cloudflare Workers adapter's RequestHandler type to be in line with other adapters (#4884)
• Updated dependencies:
  • @remix-run/cloudflare@1.12.0-pre.0

@remix-run/css-bundle@1.12.0-pre.0

Patch Changes

• Updated dependencies:
  • @remix-run/dev@1.12.0-pre.0

@remix-run/deno@1.12.0-pre.0

Patch Changes

• Export JsonFunction type in @remix-run/cloudflare and @remix-run/deno (#5206)
• Updated dependencies:
  • @remix-run/server-runtime@1.12.0-pre.0

@remix-run/express@1.12.0-pre.0

Patch Changes

• Updated dependencies:
  • @remix-run/node@1.12.0-pre.0

@remix-run/netlify@1.12.0-pre.0

Patch Changes

• Updated dependencies:
  • @remix-run/node@1.12.0-pre.0

@remix-run/testing@1.12.0-pre.0

Patch Changes

• Ensure all routes have IDs when using the createRemixStub testing helper (#5128)
• Bump react router versions (#5242)
• Updated dependencies:
  • @remix-run/node@1.12.0-pre.0
  • @remix-run/react@1.12.0-pre.0

@remix-run/vercel@1.12.0-pre.0

Patch Changes

• Updated dependencies:
  • @remix-run/node@1.12.0-pre.0

remix@1.12.0-pre.0

remix

See the CHANGELOG.md in individual Remix packages for all changes.

@remix-run/eslint-config@1.12.0-pre.0