chore(deps): update all non-major dependencies

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@babel/core (source)	`^7.21.4` -> `^7.21.5`
@remix-run/dev (source)	`^1.15.0` -> `^1.16.0`
@remix-run/eslint-config	`^1.15.0` -> `^1.16.0`
@remix-run/express	`^1.15.0` -> `^1.16.0`
@remix-run/node	`^1.15.0` -> `^1.16.0`
@remix-run/react	`^1.15.0` -> `^1.16.0`
@remix-run/serve	`^1.15.0` -> `^1.16.0`
@remix-run/server-runtime	`^1.15.0` -> `^1.16.0`
@types/node (source)	`^18.16.2` -> `^18.16.3`
@typescript-eslint/eslint-plugin	`^5.59.1` -> `^5.59.2`
@typescript-eslint/parser	`^5.59.1` -> `^5.59.2`
framer-motion	`^10.12.4` -> `^10.12.6`
pnpm (source)	`8.3.1` -> `8.4.0`
react-remove-scroll	`^2.5.5` -> `^2.5.6`
rollup (source)	`^3.21.0` -> `^3.21.3`
tsx	`^3.12.6` -> `^3.12.7`
vitepress (source)	`^1.0.0-alpha.74` -> `^1.0.0-alpha.75`

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

Release Notes

babel/babel

### [`v7.21.5`](https://togithub.com/babel/babel/blob/HEAD/CHANGELOG.md#v7215-2023-04-28) [Compare Source](https://togithub.com/babel/babel/compare/v7.21.4...v7.21.5) ##### :eyeglasses: Spec Compliance - `babel-generator`, `babel-parser`, `babel-types` - [#15539](https://togithub.com/babel/babel/pull/15539) fix: Remove `mixins` and `implements` for `DeclareInterface` and `InterfaceDeclaration` ([@liuxingbaoyu](https://togithub.com/liuxingbaoyu)) ##### :bug: Bug Fix - `babel-core`, `babel-generator`, `babel-plugin-transform-modules-commonjs`, `babel-plugin-transform-react-jsx` - [#15515](https://togithub.com/babel/babel/pull/15515) fix: `)` position with `createParenthesizedExpressions` ([@liuxingbaoyu](https://togithub.com/liuxingbaoyu)) - `babel-preset-env` - [#15580](https://togithub.com/babel/babel/pull/15580) Add syntax import meta to preset env ([@JLHwung](https://togithub.com/JLHwung)) ##### :nail_care: Polish - `babel-types` - [#15546](https://togithub.com/babel/babel/pull/15546) Improve the layout of generated validators ([@liuxingbaoyu](https://togithub.com/liuxingbaoyu)) - `babel-core` - [#15535](https://togithub.com/babel/babel/pull/15535) Use `lt` instead of `lte` to check TS version for .cts config ([@nicolo-ribaudo](https://togithub.com/nicolo-ribaudo)) ##### :house: Internal - `babel-core` - [#15575](https://togithub.com/babel/babel/pull/15575) Use synchronous `import.meta.resolve` ([@nicolo-ribaudo](https://togithub.com/nicolo-ribaudo)) - `babel-helper-fixtures`, `babel-preset-typescript` - [#15568](https://togithub.com/babel/babel/pull/15568) Handle `.overrides` and `.env` when resolving plugins/presets from fixture options ([@JLHwung](https://togithub.com/JLHwung)) - `babel-helper-create-class-features-plugin`, `babel-helper-create-regexp-features-plugin` - [#15548](https://togithub.com/babel/babel/pull/15548) Use `semver` package to compare versions ([@nicolo-ribaudo](https://togithub.com/nicolo-ribaudo))

remix-run/remix (@remix-run/dev)

### [`v1.16.0`](https://togithub.com/remix-run/remix/blob/HEAD/packages/remix-dev/CHANGELOG.md#1160) [Compare Source](https://togithub.com/remix-run/remix/compare/@remix-run/dev@1.15.0...@remix-run/dev@1.16.0) ##### Minor Changes - Enable support for [CSS Modules](https://togithub.com/css-modules/css-modules), [Vanilla Extract](http://vanilla-extract.style) and CSS side-effect imports ([#6046](https://togithub.com/remix-run/remix/pull/6046)) These CSS bundling features were previously only available via `future.unstable_cssModules`, `future.unstable_vanillaExtract` and `future.unstable_cssSideEffectImports` options in `remix.config.js`, but they have now been stabilized. In order to use these features, check out our guide to [CSS bundling](https://remix.run/docs/en/1.16.0/guides/styling#css-bundling) in your project. - Stabilize built-in PostCSS support via the new `postcss` option in `remix.config.js`. As a result, the `future.unstable_postcss` option has also been deprecated. ([#5960](https://togithub.com/remix-run/remix/pull/5960)) The `postcss` option is `false` by default, but when set to `true` will enable processing of all CSS files using PostCSS if `postcss.config.js` is present. If you followed the original PostCSS setup guide for Remix, you may have a folder structure that looks like this, separating your source files from its processed output: . ├── app │ └── styles (processed files) │ ├── app.css │ └── routes │ └── index.css └── styles (source files) ├── app.css └── routes └── index.css After you've enabled the new `postcss` option, you can delete the processed files from `app/styles` folder and move your source files from `styles` to `app/styles`: . ├── app │ └── styles (source files) │ ├── app.css │ └── routes │ └── index.css You should then remove `app/styles` from your `.gitignore` file since it now contains source files rather than processed output. You can then update your `package.json` scripts to remove any usage of `postcss` since Remix handles this automatically. For example, if you had followed the original setup guide: ```diff { "scripts": { - "dev:css": "postcss styles --base styles --dir app/styles -w", - "build:css": "postcss styles --base styles --dir app/styles --env production", - "dev": "concurrently \"npm run dev:css\" \"remix dev\"" + "dev": "remix dev" } } ``` - Stabilize built-in Tailwind support via the new `tailwind` option in `remix.config.js`. As a result, the `future.unstable_tailwind` option has also been deprecated. ([#5960](https://togithub.com/remix-run/remix/pull/5960)) The `tailwind` option is `false` by default, but when set to `true` will enable built-in support for Tailwind functions and directives in your CSS files if `tailwindcss` is installed. If you followed the original Tailwind setup guide for Remix and want to make use of this feature, you should first delete the generated `app/tailwind.css`. Then, if you have a `styles/tailwind.css` file, you should move it to `app/tailwind.css`. ```sh rm app/tailwind.css mv styles/tailwind.css app/tailwind.css ``` Otherwise, if you don't already have an `app/tailwind.css` file, you should create one with the following contents: ```css @tailwind base; @tailwind components; @tailwind utilities; ``` You should then remove `/app/tailwind.css` from your `.gitignore` file since it now contains source code rather than processed output. You can then update your `package.json` scripts to remove any usage of `tailwindcss` since Remix handles this automatically. For example, if you had followed the original setup guide: ```diff { // ... "scripts": { - "build": "run-s \"build:*\"", + "build": "remix build", - "build:css": "npm run generate:css -- --minify", - "build:remix": "remix build", - "dev": "run-p \"dev:*\"", + "dev": "remix dev", - "dev:css": "npm run generate:css -- --watch", - "dev:remix": "remix dev", - "generate:css": "npx tailwindcss -o ./app/tailwind.css", "start": "remix-serve build" } // ... } ``` - The Remix dev server spins up your app server as a managed subprocess. ([#6133](https://togithub.com/remix-run/remix/pull/6133)) This keeps your development environment as close to production as possible. It also means that the Remix dev server is compatible with *any* app server. By default, the dev server will use the Remix App Server, but you opt to use your own app server by specifying the command to run it via the `-c`/`--command` flag: ```sh remix dev # uses `remix-serve ` as the app server remix dev -c "node ./server.js" # uses your custom app server at `./server.js` ``` The dev server will: - force `NODE_ENV=development` and warn you if it was previously set to something else - rebuild your app whenever your Remix app code changes - restart your app server whenever rebuilds succeed - handle live reload and HMR + Hot Data Revalidation ##### App server coordination In order to manage your app server, the dev server needs to be told what server build is currently being used by your app server. This works by having the app server send a "I'm ready!" message with the Remix server build hash as the payload. This is handled automatically in Remix App Server and is set up for you via calls to `broadcastDevReady` or `logDevReady` in the official Remix templates. If you are not using Remix App Server and your server doesn't call `broadcastDevReady`, you'll need to call it in your app server *after* it is up and running. For example, in an Express server: ```js // server.js // import { broadcastDevReady } from "@remix-run/node"; // Path to Remix's server build directory ('build/' by default) const BUILD_DIR = path.join(process.cwd(), "build"); //



app.listen(3000, () => {
  const build = require(BUILD_DIR);
  console.log("Ready: http://localhost:" + port);

  // in development, call `broadcastDevReady` _after_ your server is up and running
  if (process.env.NODE_ENV === "development") {
    broadcastDevReady(build);
  }
});
```

##### Options

Options priority order is: 1. flags, 2. config, 3. defaults.

| Option         | flag               | config           | default                           |
| -------------- | ------------------ | ---------------- | --------------------------------- |
| Command        | `-c` / `--command` | `command`        | `remix-serve ` |
| HTTP(S) scheme | `--http-scheme`    | `httpScheme`     | `http`                            |
| HTTP(S) host   | `--http-host`      | `httpHost`       | `localhost`                       |
| HTTP(S) port   | `--http-port`      | `httpPort`       | Dynamically chosen open port      |
| Websocket port | `--websocket-port` | `websocketPort`  | Dynamically chosen open port      |
| No restart     | `--no-restart`     | `restart: false` | `restart: true`                   |

🚨 The `--http-*` flags are only used for internal dev server <-> app server communication.
Your app will run on your app server's normal URL.

To set `unstable_dev` configuration, replace `unstable_dev: true` with `unstable_dev: {  }`.
For example, to set the HTTP(S) port statically:

```js
// remix.config.js
module.exports = {
  future: {
    unstable_dev: {
      httpPort: 8001,
    },
  },
};
```

##### SSL and custom hosts

You should only need to use the `--http-*` flags and `--websocket-port` flag if you need fine-grain control of what scheme/host/port for the dev server.
If you are setting up SSL or Docker networking, these are the flags you'll want to use.

🚨 Remix **will not** set up SSL and custom host for you.
The `--http-scheme` and `--http-host` flag are for you to tell Remix how you've set things up.
It is your task to set up SSL certificates and host files if you want those features.

##### `--no-restart` and `require` cache purging

If you want to manage server changes yourself, you can use the `--no-restart` flag to tell the dev server to refrain from restarting your app server when builds succeed:

```sh
remix dev -c "node ./server.js" --no-restart
```

For example, you could purge the `require` cache of your app server to keep it running while picking up server changes.
If you do so, you should watch the server build path (`build/` by default) for changes and only purge the `require` cache when changes are detected.

🚨 If you use `--no-restart`, it is your responsibility to call `broadcastDevReady` when your app server has picked up server changes.
For example, with `chokidar`:

```js
// server.dev.js
const BUILD_PATH = path.resolve(__dirname, "build");

const watcher = chokidar.watch(BUILD_PATH);

watcher.on("change", () => {
  // 1. purge require cache
  purgeRequireCache();
  // 2. load updated server build
  const build = require(BUILD_PATH);
  // 3. tell dev server that this app server is now ready
  broadcastDevReady(build);
});
```

##### Patch Changes

-   Fix absolute paths in CSS `url()` rules when using CSS Modules, Vanilla Extract and CSS side-effect imports ([#5788](https://togithub.com/remix-run/remix/pull/5788))
-   look for [@remix-run/serve](https://togithub.com/remix-run/serve) in `devDependencies` when running remix dev ([#6228](https://togithub.com/remix-run/remix/pull/6228))
-   add warning for v2 "cjs"->"esm" `serverModuleFormat` default change ([#6154](https://togithub.com/remix-run/remix/pull/6154))
-   write mjs server output files ([#6225](https://togithub.com/remix-run/remix/pull/6225))
-   fix(react,dev): dev chunking and refresh race condition ([#6201](https://togithub.com/remix-run/remix/pull/6201))
-   Use correct require context in `bareImports` plugin. ([#6181](https://togithub.com/remix-run/remix/pull/6181))
-   use minimatch for regex instead of glob-to-regexp ([#6017](https://togithub.com/remix-run/remix/pull/6017))
-   add `logDevReady` as replacement for platforms that can't initialize async I/O outside of the request response lifecycle. ([#6204](https://togithub.com/remix-run/remix/pull/6204))
-   Use the "automatic" JSX runtime when processing MDX files. ([#6098](https://togithub.com/remix-run/remix/pull/6098))
-   forcibly kill app server during dev ([#6197](https://togithub.com/remix-run/remix/pull/6197))
-   show first compilation error instead of cancelation errors ([#6202](https://togithub.com/remix-run/remix/pull/6202))
-   Resolve imports from route modules across the graph back to the virtual module created by the v2 routes plugin. This fixes issues where we would duplicate portions of route modules that were imported. ([#6098](https://togithub.com/remix-run/remix/pull/6098))
-   Updated dependencies:
    -   `@remix-run/server-runtime@1.16.0`



remix-run/remix (@remix-run/eslint-config)

### [`v1.16.0`](https://togithub.com/remix-run/remix/blob/HEAD/packages/remix-eslint-config/CHANGELOG.md#1160)

[Compare Source](https://togithub.com/remix-run/remix/compare/@remix-run/eslint-config@1.15.0...@remix-run/eslint-config@1.16.0)

##### Minor Changes

-   add deprecation warning to `@remix-run/eslint-config/jest` ESLint config ([#5697](https://togithub.com/remix-run/remix/pull/5697))



remix-run/remix (@remix-run/express)

### [`v1.16.0`](https://togithub.com/remix-run/remix/blob/HEAD/packages/remix-express/CHANGELOG.md#1160)

[Compare Source](https://togithub.com/remix-run/remix/compare/@remix-run/express@1.15.0...@remix-run/express@1.16.0)

##### Patch Changes

-   feat: support async `getLoadContext` in all adapters ([#6170](https://togithub.com/remix-run/remix/pull/6170))
-   Updated dependencies:
    -   `@remix-run/node@1.16.0`



remix-run/remix (@remix-run/node)

### [`v1.16.0`](https://togithub.com/remix-run/remix/blob/HEAD/packages/remix-node/CHANGELOG.md#1160)

[Compare Source](https://togithub.com/remix-run/remix/compare/@remix-run/node@1.15.0...@remix-run/node@1.16.0)

##### Patch Changes

-   add `@remix-run/node/install` side-effect to allow `node --require @remix-run/node/install` ([#6132](https://togithub.com/remix-run/remix/pull/6132))
-   add `logDevReady` as replacement for platforms that can't initialize async I/O outside of the request response lifecycle. ([#6204](https://togithub.com/remix-run/remix/pull/6204))
-   add missing files to published package ([#6179](https://togithub.com/remix-run/remix/pull/6179))
-   Updated dependencies:
    -   `@remix-run/server-runtime@1.16.0`



remix-run/remix (@remix-run/react)

### [`v1.16.0`](https://togithub.com/remix-run/remix/blob/HEAD/packages/remix-react/CHANGELOG.md#1160)

[Compare Source](https://togithub.com/remix-run/remix/compare/@remix-run/react@1.15.0...@remix-run/react@1.16.0)

##### Minor Changes

-   Enable support for [CSS Modules](https://togithub.com/css-modules/css-modules), [Vanilla Extract](http://vanilla-extract.style) and CSS side-effect imports ([#6046](https://togithub.com/remix-run/remix/pull/6046))

    These CSS bundling features were previously only available via `future.unstable_cssModules`, `future.unstable_vanillaExtract` and `future.unstable_cssSideEffectImports` options in `remix.config.js`, but they have now been stabilized.

    In order to use these features, check out our guide to [CSS bundling](https://remix.run/docs/en/1.16.0/guides/styling#css-bundling) in your project.

-   Stabilize built-in PostCSS support via the new `postcss` option in `remix.config.js`. As a result, the `future.unstable_postcss` option has also been deprecated. ([#5960](https://togithub.com/remix-run/remix/pull/5960))

    The `postcss` option is `false` by default, but when set to `true` will enable processing of all CSS files using PostCSS if `postcss.config.js` is present.

    If you followed the original PostCSS setup guide for Remix, you may have a folder structure that looks like this, separating your source files from its processed output:

        .
        ├── app
        │   └── styles (processed files)
        │       ├── app.css
        │       └── routes
        │           └── index.css
        └── styles (source files)
            ├── app.css
            └── routes
                └── index.css

    After you've enabled the new `postcss` option, you can delete the processed files from `app/styles` folder and move your source files from `styles` to `app/styles`:

        .
        ├── app
        │   └── styles (source files)
        │       ├── app.css
        │       └── routes
        │           └── index.css

    You should then remove `app/styles` from your `.gitignore` file since it now contains source files rather than processed output.

    You can then update your `package.json` scripts to remove any usage of `postcss` since Remix handles this automatically. For example, if you had followed the original setup guide:

    ```diff
    {
      "scripts": {
    -    "dev:css": "postcss styles --base styles --dir app/styles -w",
    -    "build:css": "postcss styles --base styles --dir app/styles --env production",
    -    "dev": "concurrently \"npm run dev:css\" \"remix dev\""
    +    "dev": "remix dev"
      }
    }
    ```

-   Stabilize built-in Tailwind support via the new `tailwind` option in `remix.config.js`. As a result, the `future.unstable_tailwind` option has also been deprecated. ([#5960](https://togithub.com/remix-run/remix/pull/5960))

    The `tailwind` option is `false` by default, but when set to `true` will enable built-in support for Tailwind functions and directives in your CSS files if `tailwindcss` is installed.

    If you followed the original Tailwind setup guide for Remix and want to make use of this feature, you should first delete the generated `app/tailwind.css`.

    Then, if you have a `styles/tailwind.css` file, you should move it to `app/tailwind.css`.

    ```sh
    rm app/tailwind.css
    mv styles/tailwind.css app/tailwind.css
    ```

    Otherwise, if you don't already have an `app/tailwind.css` file, you should create one with the following contents:

    ```css
    @tailwind base;
    @tailwind components;
    @tailwind utilities;
    ```

    You should then remove `/app/tailwind.css` from your `.gitignore` file since it now contains source code rather than processed output.

    You can then update your `package.json` scripts to remove any usage of `tailwindcss` since Remix handles this automatically. For example, if you had followed the original setup guide:

    ```diff
    {
      // ...
      "scripts": {
    -    "build": "run-s \"build:*\"",
    +    "build": "remix build",
    -    "build:css": "npm run generate:css -- --minify",
    -    "build:remix": "remix build",
    -    "dev": "run-p \"dev:*\"",
    +    "dev": "remix dev",
    -    "dev:css": "npm run generate:css -- --watch",
    -    "dev:remix": "remix dev",
    -    "generate:css": "npx tailwindcss -o ./app/tailwind.css",
        "start": "remix-serve build"
      }
      // ...
    }
    ```

##### Patch Changes

-   fix(react,dev): dev chunking and refresh race condition ([#6201](https://togithub.com/remix-run/remix/pull/6201))
-   Revalidate loaders only when a change to one is detected. ([#6135](https://togithub.com/remix-run/remix/pull/6135))
-   short circuit links and meta for routes that are not rendered due to errors ([#6107](https://togithub.com/remix-run/remix/pull/6107))
-   don't warn about runtime deprecation warnings in production ([#4421](https://togithub.com/remix-run/remix/pull/4421))
-   Update Remix for React Router no longer relying on `useSyncExternalStore` ([#6121](https://togithub.com/remix-run/remix/pull/6121))
-   Fix false-positive resource route identification if a route only exports a boundary ([#6125](https://togithub.com/remix-run/remix/pull/6125))
-   better type discrimination when unwrapping loader return types ([#5516](https://togithub.com/remix-run/remix/pull/5516))
-   Updated dependencies:
    -   [`react-router-dom@6.11.0`](https://togithub.com/remix-run/react-router/releases/tag/react-router%406.11.0)
    -   [`@remix-run/router@1.6.0`](https://togithub.com/remix-run/react-router/blob/main/packages/router/CHANGELOG.md#160)



remix-run/remix (@remix-run/serve)

### [`v1.16.0`](https://togithub.com/remix-run/remix/blob/HEAD/packages/remix-serve/CHANGELOG.md#1160)

[Compare Source](https://togithub.com/remix-run/remix/compare/@remix-run/serve@1.15.0...@remix-run/serve@1.16.0)

##### Patch Changes

-   add `@remix-run/node/install` side-effect to allow `node --require @remix-run/node/install` ([#6132](https://togithub.com/remix-run/remix/pull/6132))
-   Updated dependencies:
    -   `@remix-run/express@1.16.0`
    -   `@remix-run/node@1.16.0`



remix-run/remix (@remix-run/server-runtime)

### [`v1.16.0`](https://togithub.com/remix-run/remix/blob/HEAD/packages/remix-server-runtime/CHANGELOG.md#1160)

[Compare Source](https://togithub.com/remix-run/remix/compare/@remix-run/server-runtime@1.15.0...@remix-run/server-runtime@1.16.0)

##### Minor Changes

-   Enable support for [CSS Modules](https://togithub.com/css-modules/css-modules), [Vanilla Extract](http://vanilla-extract.style) and CSS side-effect imports ([#6046](https://togithub.com/remix-run/remix/pull/6046))

    These CSS bundling features were previously only available via `future.unstable_cssModules`, `future.unstable_vanillaExtract` and `future.unstable_cssSideEffectImports` options in `remix.config.js`, but they have now been stabilized.

    In order to use these features, check out our guide to [CSS bundling](https://remix.run/docs/en/1.16.0/guides/styling#css-bundling) in your project.

-   Stabilize built-in PostCSS support via the new `postcss` option in `remix.config.js`. As a result, the `future.unstable_postcss` option has also been deprecated. ([#5960](https://togithub.com/remix-run/remix/pull/5960))

    The `postcss` option is `false` by default, but when set to `true` will enable processing of all CSS files using PostCSS if `postcss.config.js` is present.

    If you followed the original PostCSS setup guide for Remix, you may have a folder structure that looks like this, separating your source files from its processed output:

        .
        ├── app
        │   └── styles (processed files)
        │       ├── app.css
        │       └── routes
        │           └── index.css
        └── styles (source files)
            ├── app.css
            └── routes
                └── index.css

    After you've enabled the new `postcss` option, you can delete the processed files from `app/styles` folder and move your source files from `styles` to `app/styles`:

        .
        ├── app
        │   └── styles (source files)
        │       ├── app.css
        │       └── routes
        │           └── index.css

    You should then remove `app/styles` from your `.gitignore` file since it now contains source files rather than processed output.

    You can then update your `package.json` scripts to remove any usage of `postcss` since Remix handles this automatically. For example, if you had followed the original setup guide:

    ```diff
    {
      "scripts": {
    -    "dev:css": "postcss styles --base styles --dir app/styles -w",
    -    "build:css": "postcss styles --base styles --dir app/styles --env production",
    -    "dev": "concurrently \"npm run dev:css\" \"remix dev\""
    +    "dev": "remix dev"
      }
    }
    ```

-   Stabilize built-in Tailwind support via the new `tailwind` option in `remix.config.js`. As a result, the `future.unstable_tailwind` option has also been deprecated. ([#5960](https://togithub.com/remix-run/remix/pull/5960))

    The `tailwind` option is `false` by default, but when set to `true` will enable built-in support for Tailwind functions and directives in your CSS files if `tailwindcss` is installed.

    If you followed the original Tailwind setup guide for Remix and want to make use of this feature, you should first delete the generated `app/tailwind.css`.

    Then, if you have a `styles/tailwind.css` file, you should move it to `app/tailwind.css`.

    ```sh
    rm app/tailwind.css
    mv styles/tailwind.css app/tailwind.css
    ```

    Otherwise, if you don't already have an `app/tailwind.css` file, you should create one with the following contents:

    ```css
    @tailwind base;
    @tailwind components;
    @tailwind utilities;
    ```

    You should then remove `/app/tailwind.css` from your `.gitignore` file since it now contains source code rather than processed output.

    You can then update your `package.json` scripts to remove any usage of `tailwindcss` since Remix handles this automatically. For example, if you had followed the original setup guide:

    ```diff
    {
      // ...
      "scripts": {
    -    "build": "run-s \"build:*\"",
    +    "build": "remix build",
    -    "build:css": "npm run generate:css -- --minify",
    -    "build:remix": "remix build",
    -    "dev": "run-p \"dev:*\"",
    +    "dev": "remix dev",
    -    "dev:css": "npm run generate:css -- --watch",
    -    "dev:remix": "remix dev",
    -    "generate:css": "npx tailwindcss -o ./app/tailwind.css",
        "start": "remix-serve build"
      }
      // ...
    }
    ```

-   The Remix dev server spins up your app server as a managed subprocess. ([#6133](https://togithub.com/remix-run/remix/pull/6133))
    This keeps your development environment as close to production as possible.
    It also means that the Remix dev server is compatible with *any* app server.

    By default, the dev server will use the Remix App Server, but you opt to use your own app server by specifying the command to run it via the `-c`/`--command` flag:

    ```sh
    remix dev # uses `remix-serve ` as the app server
    remix dev -c "node ./server.js" # uses your custom app server at `./server.js`
    ```

    The dev server will:

    -   force `NODE_ENV=development` and warn you if it was previously set to something else
    -   rebuild your app whenever your Remix app code changes
    -   restart your app server whenever rebuilds succeed
    -   handle live reload and HMR + Hot Data Revalidation

##### App server coordination

In order to manage your app server, the dev server needs to be told what server build is currently being used by your app server.
This works by having the app server send a "I'm ready!" message with the Remix server build hash as the payload.

This is handled automatically in Remix App Server and is set up for you via calls to `broadcastDevReady` or `logDevReady` in the official Remix templates.

If you are not using Remix App Server and your server doesn't call `broadcastDevReady`, you'll need to call it in your app server *after* it is up and running.
For example, in an Express server:

```js
// server.js
// 
import { broadcastDevReady } from "@remix-run/node";

// Path to Remix's server build directory ('build/' by default)
const BUILD_DIR = path.join(process.cwd(), "build");

// 

app.listen(3000, () => {
  const build = require(BUILD_DIR);
  console.log("Ready: http://localhost:" + port);

  // in development, call `broadcastDevReady` _after_ your server is up and running
  if (process.env.NODE_ENV === "development") {
    broadcastDevReady(build);
  }
});
```

##### Options

Options priority order is: 1. flags, 2. config, 3. defaults.

| Option         | flag               | config           | default                           |
| -------------- | ------------------ | ---------------- | --------------------------------- |
| Command        | `-c` / `--command` | `command`        | `remix-serve ` |
| HTTP(S) scheme | `--http-scheme`    | `httpScheme`     | `http`                            |
| HTTP(S) host   | `--http-host`      | `httpHost`       | `localhost`                       |
| HTTP(S) port   | `--http-port`      | `httpPort`       | Dynamically chosen open port      |
| Websocket port | `--websocket-port` | `websocketPort`  | Dynamically chosen open port      |
| No restart     | `--no-restart`     | `restart: false` | `restart: true`                   |

🚨 The `--http-*` flags are only used for internal dev server <-> app server communication.
Your app will run on your app server's normal URL.

To set `unstable_dev` configuration, replace `unstable_dev: true` with `unstable_dev: {  }`.
For example, to set the HTTP(S) port statically:

```js
// remix.config.js
module.exports = {
  future: {
    unstable_dev: {
      httpPort: 8001,
    },
  },
};
```

##### SSL and custom hosts

You should only need to use the `--http-*` flags and `--websocket-port` flag if you need fine-grain control of what scheme/host/port for the dev server.
If you are setting up SSL or Docker networking, these are the flags you'll want to use.

🚨 Remix **will not** set up SSL and custom host for you.
The `--http-scheme` and `--http-host` flag are for you to tell Remix how you've set things up.
It is your task to set up SSL certificates and host files if you want those features.

##### `--no-restart` and `require` cache purging

If you want to manage server changes yourself, you can use the `--no-restart` flag to tell the dev server to refrain from restarting your app server when builds succeed:

```sh
remix dev -c "node ./server.js" --no-restart
```

For example, you could purge the `require` cache of your app server to keep it running while picking up server changes.
If you do so, you should watch the server build path (`build/` by default) for changes and only purge the `require` cache when changes are detected.

🚨 If you use `--no-restart`, it is your responsibility to call `broadcastDevReady` when your app server has picked up server changes.
For example, with `chokidar`:

```js
// server.dev.js
// eslint-disable-next-line no-restricted-globals
const BUILD_PATH = path.resolve(__dirname, "build");

const watcher = chokidar.watch(BUILD_PATH);

watcher.on("change", () => {
  // 1. purge require cache
  purgeRequireCache();
  // 2. load updated server build
  const build = require(BUILD_PATH);
  // 3. tell dev server that this app server is now ready
  broadcastDevReady(build);
});
```

##### Patch Changes

-   add `logDevReady` as replacement for platforms that can't initialize async I/O outside of the request response lifecycle. ([#6204](https://togithub.com/remix-run/remix/pull/6204))
-   better type discrimination when unwrapping loader return types ([#5516](https://togithub.com/remix-run/remix/pull/5516))
-   pass `AppLoadContext` to `handleRequest` ([#5836](https://togithub.com/remix-run/remix/pull/5836))
-   Updated dependencies:
    -   [`react-router-dom@6.11.0`](https://togithub.com/remix-run/react-router/releases/tag/react-router%406.11.0)
    -   [`@remix-run/router@1.6.0`](https://togithub.com/remix-run/react-router/blob/main/packages/router/CHANGELOG.md#160)



typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)

### [`v5.59.2`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5592-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5591v5592-2023-05-01)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.1...v5.59.2)

**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)



typescript-eslint/typescript-eslint (@typescript-eslint/parser)

### [`v5.59.2`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5592-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5591v5592-2023-05-01)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.1...v5.59.2)

**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)



framer/motion

### [`v10.12.6`](https://togithub.com/framer/motion/blob/HEAD/CHANGELOG.md#10126-2023-05-02)

[Compare Source](https://togithub.com/framer/motion/compare/v10.12.5...v10.12.6)

##### Fixed

-   Fixing relative layout animations when mixing `type: false` and `type: "tween", duration: 0`.

### [`v10.12.5`](https://togithub.com/framer/motion/blob/HEAD/CHANGELOG.md#10125-2023-05-01)

[Compare Source](https://togithub.com/framer/motion/compare/v10.12.4...v10.12.5)

##### Changed

-   Exporting `visualElementStore` for internal use.



pnpm/pnpm

### [`v8.4.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.4.0)

[Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.3.1...v8.4.0)

#### Minor Changes

-   `pnpm publish` supports the `--provenance` CLI option [#6435](https://togithub.com/pnpm/pnpm/issues/6435).

#### Patch Changes

-   Link the bin files of local workspace dependencies, when `node-linker` is set to `hoisted` [6486](https://togithub.com/pnpm/pnpm/issues/6486).
-   Ask the user to confirm the removal of `node_modules` directory unless the `--force` option is passed.
-   Do not create a `node_modules` folder with a `.modules.yaml` file if there are no dependencies inside `node_modules`.

#### Our Gold Sponsors


  
    
      
        
      
      
        
          
            
            
            
          
        
      
    
    
      
        
          
            
            
            
          
        
      
      
        
      
    
  


#### Our Silver Sponsors


  
    
      
        
          
        
      
      
        
          
            
            
            
          
        
      
    
    
      
        
          
            
            
            
          
        
      
      
        
          
            
            
            
          
        
      
    
    
      
        
          
            
            
            
          
        
      
      
        
          
            
            
            
          
        
      
    
  




theKashey/react-remove-scroll

### [`v2.5.6`](https://togithub.com/theKashey/react-remove-scroll/compare/v2.5.5...v2.5.6)

[Compare Source](https://togithub.com/theKashey/react-remove-scroll/compare/v2.5.5...v2.5.6)



rollup/rollup

### [`v3.21.3`](https://togithub.com/rollup/rollup/blob/HEAD/CHANGELOG.md#3213)

[Compare Source](https://togithub.com/rollup/rollup/compare/v3.21.2...v3.21.3)

*2023-05-02*

##### Bug Fixes

-   Run `process.exit()` when Rollup CLI finishes successfully to solve issues on some systems ([#4969](https://togithub.com/rollup/rollup/issues/4969))

##### Pull Requests

-   [#4954](https://togithub.com/rollup/rollup/pull/4954): test: enable typecheck for \_config files ([@antfu](https://togithub.com/antfu))
-   [#4969](https://togithub.com/rollup/rollup/pull/4969): Automatically force close Rollup when done ([@lukastaegert](https://togithub.com/lukastaegert))

### [`v3.21.2`](https://togithub.com/rollup/rollup/blob/HEAD/CHANGELOG.md#3212)

[Compare Source](https://togithub.com/rollup/rollup/compare/v3.21.1...v3.21.2)

*2023-04-30*

##### Bug Fixes

-   Mark global functions that trigger iterators as impure for now ([#4955](https://togithub.com/rollup/rollup/issues/4955))

##### Pull Requests

-   [#4955](https://togithub.com/rollup/rollup/pull/4955): fix: mark some known globals or their functions as impure ([@TrickyPi](https://togithub.com/TrickyPi))

### [`v3.21.1`](https://togithub.com/rollup/rollup/blob/HEAD/CHANGELOG.md#3211)

[Compare Source](https://togithub.com/rollup/rollup/compare/v3.21.0...v3.21.1)

*2023-04-29*

##### Bug Fixes

-   Make sure call arguments are properly deoptimized when a function uses the `arguments` variable ([#4965](https://togithub.com/rollup/rollup/issues/4965))

##### Pull Requests

-   [#4957](https://togithub.com/rollup/rollup/pull/4957): Update dependencies ([@lukastaegert](https://togithub.com/lukastaegert))
-   [#4964](https://togithub.com/rollup/rollup/pull/4964): Fix REPL in dev ([@lukastaegert](https://togithub.com/lukastaegert))
-   [#4965](https://togithub.com/rollup/rollup/pull/4965): Ensure arguments are deoptimized when arguments variable is used ([@lukastaegert](https://togithub.com/lukastaegert))
-   [#4967](https://togithub.com/rollup/rollup/pull/4967): Log REPL output to console ([@lukastaegert](https://togithub.com/lukastaegert))



esbuild-kit/tsx

### [`v3.12.7`](https://togithub.com/esbuild-kit/tsx/releases/tag/v3.12.7)

[Compare Source](https://togithub.com/esbuild-kit/tsx/compare/v3.12.6...v3.12.7)

##### Bug Fixes

-   **watch:** check child message data to be an object ([#224](https://togithub.com/esbuild-kit/tsx/issues/224)) ([64ece39](https://togithub.com/esbuild-kit/tsx/commit/64ece39ea4ecda6b103901b0fbb39799d217dce3))



vuejs/vitepress

### [`v1.0.0-alpha.75`](https://togithub.com/vuejs/vitepress/blob/HEAD/CHANGELOG.md#100-alpha75-httpsgithubcomvuejsvitepresscomparev100-alpha74v100-alpha75-2023-04-30)

[Compare Source](https://togithub.com/vuejs/vitepress/compare/v1.0.0-alpha.74...v1.0.0-alpha.75)

##### Bug Fixes

-   **build:** reset regex lastIndex before testing ([188893c](https://togithub.com/vuejs/vitepress/commit/188893c2c1569e332e8776581cfa40b4c5f1168e))
-   **cli/init:** remove trailing slash from npm scripts ([64ecedc](https://togithub.com/vuejs/vitepress/commit/64ecedc73f3e7010de85381d946af1c95404820e))
-   **theme:** hide local nav on home page ([f07587a](https://togithub.com/vuejs/vitepress/commit/f07587af8a51f92a5ec491e5789dd088e28067b5)), closes [#2312](https://togithub.com/vuejs/vitepress/issues/2312)
-   **theme:** local search get 404 on build when use route rewrites in windows ([#2301](https://togithub.com/vuejs/vitepress/issues/2301)) ([494c634](https://togithub.com/vuejs/vitepress/commit/494c634eb1d77963e555a736fa057dcb23700989))
-   **theme:** vitepress data not properly injected in app when use localSearch ([#2299](https://togithub.com/vuejs/vitepress/issues/2299)) ([69c7646](https://togithub.com/vuejs/vitepress/commit/69c7646dafe7a774e0717e032f697b008d9cf7aa))

##### Features

-   add `filePath` to `PageData` ([#2140](https://togithub.com/vuejs/vitepress/issues/2140)) ([b24acc6](https://togithub.com/vuejs/vitepress/commit/b24acc6991570aa054a99b8d3977b8b4d0255418))
-   **build:** allow using `@` prefix with `@include` ([#2292](https://togithub.com/vuejs/vitepress/issues/2292)) ([a3b38d1](https://togithub.com/vuejs/vitepress/commit/a3b38d18824343fd5b571a7a9a5d2c4ccf29e8e1))
-   preserve user log level ([#2310](https://togithub.com/vuejs/vitepress/issues/2310)) ([a647cd3](https://togithub.com/vuejs/vitepress/commit/a647cd384320101f6df31e03960dd2c40808c49c))
-   **theme:** support light shiki themes ([#2319](https://togithub.com/vuejs/vitepress/issues/2319)) ([d0f0012](https://togithub.com/vuejs/vitepress/commit/d0f0012aea4cc71fb28f60f2dd649c23aae146b8))

##### BREAKING CHANGES

-   **theme:** Styling for code blocks might break, especially if you were earlier overriding it for light theme. Those workarounds are no longer required. VitePress will now show code blocks and groups in light mode too if a light shiki theme is specified.



Configuration
📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


[ ] If you want to rebase/retry this PR, check this box


This PR has been generated by Mend Renovate. View repository job log here.

kineticio / runnable

chore(deps): update all non-major dependencies #32

⚠ Dependency Lookup Warnings ⚠

Release Notes

Configuration