Bump @remix-run/dev from 1.16.1 to 1.19.1

[dependabot]

Bumps @remix-run/dev from 1.16.1 to 1.19.1.

Release notes

Sourced from @​remix-run/dev's releases.

v1.19.1

Patch Changes

• Add a heartbeat ping to prevent the WebSocket connection from being closed due to inactivity when using a proxy like Cloudflare (#6904, #6927)
• Treeshake out HMR code from production builds (#6894)

Changes by Package 🔗

• @remix-run/dev

---

Full Changelog: 1.19.0...1.19.1

v1.19.0

New Features

Improved Networking Options

When using the new v2_dev server, the --scheme and --host options have been deprecated and replaced with the REMIX_DEV_ORIGIN environment variable. For more information, refer to the v2 dev server docs (#6724)

ESBuild metafiles

For bundle analysis, the esbuild metafiles are now written to your server build directory (build/ by default) and can be uploaded to https://esbuild.github.io/analyze/ for analysis (#6772):

• metafile.css.json
• metafile.js.json (browser JS)
• metafile.server.json (server JS)

New serverNodeBuiltinsPolyfill Config Option

When building for non-Node.js server platforms, you can now control which polyfills are included (or disbale them entirely) by setting serverNodeBuiltinsPolyfill in remix.config.js (#6814, #6859, #6877).

// Disable all polyfills
exports.serverNodeBuiltinsPolyfill = { modules: {} };
// Enable specific polyfills
exports.serverNodeBuiltinsPolyfill = {
modules: {
crypto: true, // Provide a JSPM polyfill
fs: "empty", // Provide an empty polyfill
},
};

⚠️ Note that this behavior will be changing in v2. In v1, Remix will polyfill a certain set of modules for you if you do not specify serverNodeBuiltinsPolyfill. In v2, Remix will no longer include polyfills by default. You can prepare for your eventual migration by explicitly setting this config value in your v1 app.

Other Notable Changes

... (truncated)

Changelog

Sourced from @​remix-run/dev's changelog.

1.19.1

Patch Changes

• Add a heartbeat ping to prevent the WebSocket connection from being closed due to inactivity when using a proxy like Cloudflare (#6904, #6927)
• Treeshake out HMR code from production builds (#6894)
• Updated dependencies:
  • @remix-run/server-runtime@1.19.1

1.19.0

Minor Changes

• improved networking options for v2_dev (#6724)

  deprecate the --scheme and --host options and replace them with the REMIX_DEV_ORIGIN environment variable

• Output esbuild metafiles for bundle analysis (#6772)

  Written to server build directory (build/ by default):

  • metafile.css.json
  • metafile.js.json (browser JS)
  • metafile.server.json (server JS)

  Metafiles can be uploaded to https://esbuild.github.io/analyze/ for analysis.

• Add serverNodeBuiltinsPolyfill config option. In remix.config.js you can now disable polyfills of Node.js built-in modules for non-Node.js server platforms, or opt into a subset of polyfills. (#6814, #6859, #6877)

  // Disable all polyfills
  exports.serverNodeBuiltinsPolyfill = { modules: {} };
  // Enable specific polyfills
  exports.serverNodeBuiltinsPolyfill = {
  modules: {
  crypto: true, // Provide a JSPM polyfill
  fs: "empty", // Provide an empty polyfill
  },
  };

Patch Changes

• ignore missing react-dom/client for react 17 (#6725)

• Warn if not using v2_dev (#6818)

  Also, rename --no-restart to --manual to match intention and documentation. --no-restart remains an alias for --manual in v1 for backwards compatibility.

... (truncated)

Commits

• ccb002b chore: Update version for release (#6932)
• 320ac56 chore: Update version for release (pre) (#6921)
• 316ef06 Heartbeat: implement in both live-reload servers (#6927)
• 57a6c53 liveReload: add hearbeat for keepalive
• 141b348 chore: shake out HMR code from production build (#6894)
• a68dac2 chore: Update version for release (#6882)
• ccef56a chore: Update version for release (pre) (#6880)
• 84b2304 feat(dev): remove boolean option for polyfills (#6877)
• 6c9677c chore: Update version for release (pre) (#6864)
• 472c936 feat(dev): support empty server polyfills (#6859)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #745.