chore(deps): update dependency @remix-run/react to v1.19.3 #45

renovate · 2022-04-27T21:39:42Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@remix-run/react (source)	`1.4.1` -> `1.19.3`

Release Notes

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

`v1.19.3`

Compare Source

No significant changes to this package were made in this release. See the releases page on GitHub for an overview of all changes in v1.19.3.

`v1.19.2`

Compare Source

No significant changes to this package were made in this release. See the releases page on GitHub for an overview of all changes in v1.19.2.

`v1.19.1`

Compare Source

No significant changes to this package were made in this release. See the releases page on GitHub for an overview of all changes in v1.19.1.

`v1.19.0`

Compare Source

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
Added some missing react-router exports to @remix-run/react (#6856)

Patch Changes

Narrowed the type of fetcher.formEncType to use FormEncType from react-router-dom instead of string (#6810)
Deferred promises that return undefined/void now surface a serialization error. (#6793)
Properly handle ?_data HTTP/Network errors that don't reach the Remix server and ensure they bubble to the ErrorBoundary (#6783)
Support proper hydration of Error subclasses such as ReferenceError/TypeError in development mode (#6675)
fix router race condition for hmr (#6767)
Avoid re-prefetching stylesheets for active routes during a revalidation (#6679)
Add generic type for useRouteLoaderData() (#5157)
Bump RR 6.14.2 (#6854)
Updated dependencies:
- react-router-dom@6.14.2
- @remix-run/router@1.7.2

`v1.18.1`

Compare Source

Patch Changes

Fix reload loops in scenarios where CDNs ignore search params (#6707)
Updated dependencies:
- react-router-dom@6.14.1
- @remix-run/router@1.7.1

`v1.18.0`

Compare Source

Minor Changes

stabilize v2 dev server (#6615)
Support application/json and text/plain submission encodings in useSubmit/fetcher.submit (#6570)
Add support for <Link prefetch="viewport"> to prefetch links when they enter the viewport via an Intersection Observer (#6433)

Patch Changes

Bump router 6.14.0-pre.1 (#6662)
Detect mismatches between the initially loaded URL and the URL at the time we hydrate and trigger a hard reload if they do not match. This is an edge-case that can happen when the network is slowish and the user clicks forward into a Remix app and then clicks forward again while the initial JS chunks are loading. (#6409)
Lock in react router 6.14.0 (#6677)
properly pass props to inline script tags for deferred data (#6389)

Minor Changes

Faster server export removal for routes when unstable_dev is enabled. (#6455)

Also, only render modulepreloads on SSR.
Do not render modulepreloads when hydrated.

Force Typescript to simplify type produced by Serialize. (#6449)

As a result, the following types and functions have simplified return types:

SerializeFrom
useLoaderData
useActionData
useFetcher

type Data = { hello: string; when: Date };

// BEFORE
type Unsimplified = SerializeFrom<Data>;
//   ^? SerializeObject<UndefinedToOptional<{ hello: string; when: Date }>>

// AFTER
type Simplified = SerializeFrom<Data>;
//   ^? { hello: string; when: string }

Reuse dev server port for WebSocket (Live Reload,HMR,HDR) (#6476)

As a result the webSocketPort/--websocket-port option has been obsoleted.
Additionally, scheme/host/port options for the dev server have been renamed.

Available options are:

Option	flag	config	default
Command	`-c` / `--command`	`command`	`remix-serve <server build path>`
Scheme	`--scheme`	`scheme`	`http`
Host	`--host`	`host`	`localhost`
Port	`--port`	`port`	Dynamically chosen open port
No restart	`--no-restart`	`restart: false`	`restart: true`

Note that scheme/host/port options are for the dev server, not your app server.
You probably don't need to use scheme/host/port option if you aren't configuring networking (e.g. for Docker or SSL).

Patch Changes

retry HDR revalidations in development mode to aid in 3rd party server race conditions (#6287)
Updated dependencies:
- react-router-dom@6.12.0
- @remix-run/router@1.6.3

`v1.16.1`

Compare Source

Patch Changes

Cross-module loader change detection for HDR (#6299)
Better opt-out of loader revalidation on UI only changes (#6278)
Add useMatch re-export from react-router-dom (#5257)
Fix data parameter typing on V2_MetaFunction to include undefined for scenarios in which the loader threw to it's own boundary. (#6231)
Updated dependencies:
- react-router-dom@6.11.2
- @remix-run/router@1.6.2

`v1.16.0`

Compare Source

Minor Changes

Enable support for CSS Modules, Vanilla Extract and CSS side-effect imports (#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 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)

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:
```
{
  "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)

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.
```
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:
```
@&#8203;tailwind base;
@&#8203;tailwind components;
@&#8203;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:
```
{
  // ...
  "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)
Revalidate loaders only when a change to one is detected. (#6135)
short circuit links and meta for routes that are not rendered due to errors (#6107)
don't warn about runtime deprecation warnings in production (#4421)
Update Remix for React Router no longer relying on useSyncExternalStore (#6121)
Fix false-positive resource route identification if a route only exports a boundary (#6125)
better type discrimination when unwrapping loader return types (#5516)
Updated dependencies:
- react-router-dom@6.11.0
- @remix-run/router@1.6.0

`v1.15.0`

Compare Source

Minor Changes

Deprecated fetcher.type and fetcher.submission for Remix v2 (#5691)
We have made a few changes to the API for route module meta functions when using the future.v2_meta flag. These changes are only breaking for users who have opted in. (#5746)
- V2_HtmlMetaDescriptor has been renamed to V2_MetaDescriptor
- The meta function's arguments have been simplified
  - parentsData has been removed, as each route's loader data is available on the data property of its respective match object
```
// before
export function meta({ parentsData }) {
  return [{ title: parentsData["routes/some-route"].title }];
}
// after
export function meta({ matches }) {
  return [
    {
      title: matches.find((match) => match.id === "routes/some-route")
        .data.title,
    },
  ];
}
```
  - The route property on route matches has been removed, as relevant match data is attached directly to the match object
```
// before
export function meta({ matches }) {
  const rootModule = matches.find((match) => match.route.id === "root");
}
// after
export function meta({ matches }) {
  const rootModule = matches.find((match) => match.id === "root");
}
```
- Added support for generating <script type='application/ld+json' /> and meta-related <link /> tags to document head via the route meta function when using the v2_meta future flag
Added deprecation warning for v2_normalizeFormMethod (#5863)
Added a new future.v2_normalizeFormMethod flag to normalize the exposed useNavigation().formMethod as an uppercase HTTP method to align with the previous useTransition behavior as well as the fetch() behavior of normalizing to uppercase HTTP methods. (#5815)
- When future.v2_normalizeFormMethod === false,
  - useNavigation().formMethod is lowercase
  - useFetcher().formMethod is uppercase
- When future.v2_normalizeFormMethod === true:
  - useNavigation().formMethod is uppercase
  - useFetcher().formMethod is uppercase
Added deprecation warning for normalizing imagesizes & imagesrcset properties returned from the route links function. Both properties should be in camelCase (imageSizes/ imageSrcSet) to align with their respective JavaScript properties. (#5706)
Added deprecation warning for CatchBoundary in favor of future.v2_errorBoundary (#5718)
Added experimental support for Vanilla Extract caching, which can be enabled by setting future.unstable_vanillaExtract: { cache: true } in remix.config. This is considered experimental due to the use of a brand new Vanilla Extract compiler under the hood. In order to use this feature, you must be using at least v1.10.0 of @vanilla-extract/css. (#5735)

Patch Changes

Bumped React Router dependencies to the latest version. See the release notes for more details. (e14699547)
Added type deprecations for types now in React Router (#5679)

`v1.14.3`

Compare Source

No significant changes to this package were made in this release. See the releases page on GitHub for an overview of all changes in v1.14.3.

`v1.14.2`

Compare Source

No significant changes to this package were made in this release. See the releases page on GitHub for an overview of all changes in v1.14.2.

`v1.14.1`

Compare Source

Patch Changes

Deprecate useTransition in favor of useNavigation (#5687)
Memoize return value of useMatches (#5603)

`v1.14.0`

Compare Source

Minor Changes

Hot Module Replacement and Hot Data Revalidation (#5259)
- Requires unstable_dev future flag to be enabled
- HMR provided through React Refresh
- Features:
  - HMR for component and style changes
  - HDR when loaders for current route change
- Known limitations for MVP:
  - Only implemented for React via React Refresh
  - No import.meta.hot API exposed yet
  - Revalidates all loaders on route when loader changes are detected
  - Loader changes do not account for imported dependencies changing

Patch Changes

Remove duplicate manifest imports (#5534)
Ensure types for fetchers always include form* submission fields (#5476)
Sync FutureConfig interface between packages (#5398)
Updated dependencies:
- @remix-run/router@1.3.3
- react-router-dom@8.6.2

`v1.13.0`

Compare Source

Minor Changes

Add built-in support for PostCSS via the future.unstable_postcss feature flag (#5229)
Add built-in support for Tailwind via the future.unstable_tailwind feature flag (#5229)

Patch Changes

Bump React Router dependencies to the latest version. See the release notes for more details. (#5389)
Improve efficiency of route manifest-to-tree transformation (#4748)
Added better detection for absolute urls in <Link> and <NavLink> components (#5390)

`v1.12.0`

Compare Source

Minor Changes

Added a new development server available in the Remix config under the unstable_dev flag. See the release notes for a full description. (#5133)
You can now configure the client-side socket timeout via the new timeoutMs prop on <LiveReload /> (#4036)

Patch Changes

<Link to> can now accept absolute URLs. When the to value is an absolute URL, the underlying anchor element will behave as normal, and its URL will not be prefetched. (#5092)
Bump React Router dependencies to the latest version. See the release notes for more details. (#5242)
Added support for unstable_useBlocker and unstable_usePrompt from React Router (#5151)

`v1.11.1`

Compare Source

No significant changes to this package were made in this release. See the releases page on GitHub for an overview of all changes in v1.11.1.

`v1.11.0`

Compare Source

Minor Changes

Added support for Vanilla Extract via the unstable_vanillaExtract future flag. IMPORTANT: Features marked with unstable are … unstable. While we're confident in the use cases they solve, the API and implementation may change without a major version bump. (#5040)
Add support for CSS side-effect imports via the unstable_cssSideEffectImports future flag. IMPORTANT: Features marked with unstable are … unstable. While we're confident in the use cases they solve, the API and implementation may change without a major version bump. (#4919)
Add support for CSS Modules via the unstable_cssModules future flag. IMPORTANT: Features marked with unstable are … unstable. While we're confident in the use cases they solve, the API and implementation may change without a major version bump. (#4852)

Patch Changes

Fix v2 meta to ensure meta is rendered from the next route in the tree if no meta export is included in a leaf route (#5041)
Ensure useFetcher is stable across re-renders in backwards-compatibility layer (#5118)

Added the v2_errorBoundary future flag to opt into the next version of Remix's ErrorBoundary behavior. This removes the separate CatchBoundary and ErrorBoundary and consolidates them into a single ErrorBoundary, following the logic used by errorElement in React Router. You can then use isRouteErrorResponse to differentiate between thrown Response/Error instances. (#4918)

// Current (Remix v1 default)
import { useCatch } from "@&#8203;remix-run/react";

export function CatchBoundary() {
  const caught = useCatch();
  return (
    <p>
      {caught.status} {caught.data}
    </p>
  );
}

export function ErrorBoundary({ error }) {
  return <p>{error.message}</p>;
}

// Using future.v2_errorBoundary
import { isRouteErrorResponse, useRouteError } from "@&#8203;remix-run/react";

export function ErrorBoundary() {
  const error = useRouteError();

  return isRouteErrorResponse(error) ? (
    <p>
      {error.status} {error.data}
    </p>
  ) : (
    <p>{error.message}</p>
  );
}

Introduces the defer() API from @remix-run/router with support for server-rendering and HTTP streaming. This utility allows you to defer values returned from loader functions by returning promises instead of resolved values. This has been refered to as "sending a promise over the wire". (#4920)

Informational Resources:
- https://gist.github.com/jacob-ebey/9bde9546c1aafaa6bc8c242054b1be26
- https://github.com/remix-run/remix/blob/main/decisions/0004-streaming-apis.md
Documentation Resources (better docs specific to Remix are in the works):

`v1.10.1`

Compare Source

Patch Changes

Fetchers should persist data through reload/resubmit (#5065)
Update babel config to transpile down to node 14 (#5047)

`v1.10.0`

Compare Source

Minor Changes

Update Remix to use new data APIs introduced in React Router v6.4 (#4900)
Added new hooks from React Router

`v1.9.0`

Compare Source

Patch Changes

Update @remix-run/react to use Router from react-router-dom@6.5.0 (#4731)
Allow pass-through props to be passed to the script rendered by ScrollRestoration (#2879)
Fixed a problem with <LiveReload> and Firefox infinitely reloading the page. (#4725)

`v1.8.2`

Compare Source

No significant changes to this package were made in this release. See the releases page on GitHub for an overview of all changes in v1.8.2.

`v1.8.1`

Compare Source

No significant changes to this package were made in this release. See the releases page on GitHub for an overview of all changes in v1.8.1.

`v1.8.0`

Compare Source

Minor Changes

Importing functions and types from the remix package is deprecated, and all (#3284)
exported modules will be removed in the next major release. For more details,
see the release notes for 1.4.0
where these changes were first announced.
Added support for a new route meta API to handle arrays of tags instead of an object. For details, check out the RFC. (#4610)

Patch Changes

Ensure route modules are loaded even in failure cases. This addresses a long standing issue where you would end up in your root catch boundary if a form transition to another route threw. This no longer occurs, and you end up in the contextual boundary you'd expect. (#4611)

`v1.7.6`

Compare Source

Patch Changes

Fixed a regression in the browser build for browsers that don't support the nullish coalescing operator (#4561)

`v1.7.5`

Compare Source

Patch Changes

Make sure namespaced Open Graph and fb:app_id meta data renders the correct attributes on <meta> tags (#4445)

`v1.7.4`

Compare Source

Patch Changes

Ignore pathless layout routes in action matches (#4376)
You can now infer the type of the .data property of useFetcher from the return type of your loader and action functions (#4392)
Fixed a bug in <Form> that prevented the correct method from being called with non-POST submissions (b52507861)

`v1.7.3`

Compare Source

Patch Changes

Ensure that <Form /> respects the formMethod attribute set on the submitter element (#4053)

`v1.7.2`

Compare Source

Patch Changes

Remove unused type-fest dependency (#4246)
Preserve ?index for fetcher get submissions to index routes (#4238)

`v1.7.1`

Compare Source

Patch Changes

Properly locked the dependency on react-router-dom to version 6.3.0 (#4203)
Fixed a bug with GET form submissions to ensure they replace the current search params, which tracks with the browser's behavior (#4046)

`v1.7.0`

Compare Source

Minor Changes

We've added a new type: SerializeFrom. This is used to infer the (#4013)
JSON-serialized return type of loaders and actions.

Patch Changes

Unblock hydration via async module scripts. (#3918)

`v1.6.8`

Compare Source

Patch Changes

Previously, if an action was omitted from <Form> or useFormAction, the action value would default to ".". This is incorrect, as "." should resolve based on the current path, but an empty action resolves relative to the current URL (including the search and hash values). We've fixed this to differentiate between the two, meaning that the resolved action will preserve the full URL. (#3697)
Enhanced some types to work more seamlessly with React 18 (#3917)
Added a subscribe method to the transition manager, which allows subscribing and unsubscribing for React 18 strict mode compliance (#3964)

`v1.6.7`

Compare Source

Patch Changes

Fix inferred types for useLoaderData and useActionData to preserve null value types (#3879)

`v1.6.6`

Compare Source

Patch Changes

Allow the ReadonlyArray type in SerializeType for action and loader data (#3774)
Support undefined unions as optional keys in types returned from useLoaderData and useActionData (#3766)

`v1.6.5`

Compare Source

Patch Changes

We enhanced the type signatures of loader/action and
useLoaderData/useActionData to make it possible to infer the data type
from return type of its related server function.

To enable this feature, you will need to use the LoaderArgs type from your
Remix runtime package instead of typing the function directly:
```
- import type { LoaderFunction } from "@&#8203;remix-run/[runtime]";
+ import type { LoaderArgs } from "@&#8203;remix-run/[runtime]";

- export const loader: LoaderFunction = async (args) => {
-   return json<LoaderData>(data);
- }
+ export async function loader(args: LoaderArgs) {
+   return json(data);
+ }
```
Then you can infer the loader data by using typeof loader as the type
variable in useLoaderData:
```
- let data = useLoaderData() as LoaderData;
+ let data = useLoaderData<typeof loader>();
```
The API above is exactly the same for your route action and useActionData
via the ActionArgs type.

With this change you no longer need to manually define a LoaderData type
(huge time and typo saver!), and we serialize all values so that
useLoaderData can't return types that are impossible over the network, such
as Date objects or functions.

See the discussions in #1254
and #3276 for more context.
Add WebSocket reconnect to LiveReload

`v1.6.4`

Compare Source

What's Changed

🐛 Bug fixes

Fixed a regression with Node v18.3 by making the detection of IPv4 addresses more durable in @remix-run/serve and @remix-run/dev (#3602)
Fix Yarn PnP resolution for empty modules (#3633)

💅 Enhancements

Add watchPaths option for remix.config. This allows you to define custom directories to watch while running remix dev (#3188).

New Contributors

@justsml made their first contribution in https://github.com/remix-run/remix/pull/3602
@christophertrudel made their first contribution in https://github.com/remix-run/remix/pull/3188
@manan30 made their first contribution in https://github.com/remix-run/remix/pull/3631
@juliaqiuxy made their first contribution in https://github.com/remix-run/remix/pull/3598
@lensbart made their first contribution in https://github.com/remix-run/remix/pull/3595
@federicoestevez made their first contribution in https://github.com/remix-run/remix/pull/3644
@shashankboosi made their first contribution in https://github.com/remix-run/remix/pull/3642
@justinsalasdev made their first contribution in https://github.com/remix-run/remix/pull/3547
@guatedude2 made their first contribution in https://github.com/remix-run/remix/pull/3637

Full Changelog: remix-run/remix@v1.6.3...v1.6.4

`v1.6.3`

Compare Source

This release fixes issues with some supported deep imports when bundling your server.

`v1.6.2`

Compare Source

What's Changed

🐛 Bug Fixes

Fixed module resolution issues when installing via Yarn 3 (#1316, #3579)
Fixed revalidation issues when following multiple redirects (#3460)
Fixed private stack validation in the create-remix CLI (#2804)

💅 Enhancements

The Remix compiler should tree-shake a bit more aggressively in dev mode, resulting in less dead code (#3588)

New Contributors

@cmd-johnson made their first contribution in https://github.com/remix-run/remix/pull/1316
@ahabhgk made their first contribution in https://github.com/remix-run/remix/pull/3526
@bgschiller made their first contribution in https://github.com/remix-run/remix/pull/2804
@binajmen made their first contribution in https://github.com/remix-run/remix/pull/3558
@jimniels made their first contribution in https://github.com/remix-run/remix/pull/3557
@alisd23 made their first contribution in https://github.com/remix-run/remix/pull/3579

Full Changelog: remix-run/remix@v1.6.1...v1.6.2-pre.0

`v1.6.1`

Compare Source

What's Changed

This release includes a few small bug fixes and DX improvements. Check out the full changelog to see what's new! ✨

New Contributors

@mush159 made their first contribution in https://github.com/remix-run/remix/pull/3485
@JeffBeltran made their first contribution in https://github.com/remix-run/remix/pull/3491
@ni554n made their first contribution in https://github.com/remix-run/remix/pull/3517
@vlindhol made their first contribution in https://github.com/remix-run/remix/pull/3511
@davecranwell-vocovo made their first contribution in https://github.com/remix-run/remix/pull/3458

Full Changelog: remix-run/remix@v1.6.0...v1.6.1

`v1.6.0`

Compare Source

What Changed?

☠️ Deprecated

Imports from the remix package are now officially deprecated. We added ESLint warnings to help you catch these (#3285). We also provide a codemod to make the necessary changes to prepare for a future breaking change. Run npx @remix-run/dev migrate to initiate the codemod.

See the release notes for v1.4.0 for more details on this change.

💅 Enhancements

We now export a few more helpful types from @remix-run/react (#2876)
Added a --port flag to the remix dev script (#3447)

🐛 Bug fixes

Fixed cookies to default to sameSite: "lax" to better align with browsers (#2388)
Normalized imageSrcSet / imageSizes props for links depending on the React version used (#2944)
Added some missing dependencies to @remix-run/dev (#3413)
Added a fix to use the correct error/catch boundary on SSR action errors (#3436)

New Contributors

@jiahao-c made their first contribution in https://github.com/remix-run/remix/pull/3216
@apeltop made their first contribution in https://github.com/remix-run/remix/pull/3242
@nvh95 made their first contribution in https://github.com/remix-run/remix/pull/3249
@realjokele made their first contribution in https://github.com/remix-run/remix/pull/3266
@JNaftali made their first contribution in https://github.com/remix-run/remix/pull/3253
@turkerdev made their first contribution in https://github.com/remix-run/remix/pull/3274
@udasitharani made their first contribution in https://github.com/remix-run/remix/pull/2332
@colinhacks made their first contribution in https://github.com/remix-run/remix/pull/3268
@johnpolacek made their first contribution in https://github.com/remix-run/remix/pull/3329
@RATIU5 made their first contribution in https://github.com/remix-run/remix/pull/3345
@penx made their first contribution in https://github.com/remix-run/remix/pull/3353
@dgurns made their first contribution in https://github.com/remix-run/remix/pull/3368
@jrubins made their first contribution in https://github.com/remix-run/remix/pull/3418
@sebz made their first contribution in https://github.com/remix-run/remix/pull/3384

Full Changelog: remix-run/remix@v1.5.1...v1.6.0

`v1.5.1`

Compare Source

What's Changed

💅 Enhancements

Added Deno to the list of options in the create-remix CLI 🦕 (#3233)

Full Changelog: remix-run/remix@v1.5.0...v1.5.1

`v1.5.0`

Compare Source

Welcome to version 1.5 of Remix. Can you believe that we are already 1.5 ~~years~~ versions old? Time flies when you're building fun web frameworks!

We've got a few things that we're excited to share with this one, so let's get started 💿 💿 💿

Official support for Deno

Your scientists were so preoccupied with whether they could that they didn't stop to think if they should.

Dr. Ian Malcolm, Jurassic Park

A short while ago we rolled out a new adapter with experimental support for building on top of Deno. At long last, the mad scientists at Remix are now ready to announce a major breakthrough:

Remix now officially supports Deno. 🦕

Apart from compiler-related changes, Deno support comes in the form of:

a brand new @remix-run/deno package
an updated Deno template (npx create-remix@latest --template deno)

We couldn't be more excited to see what Deno enables for your future Remix projects. Deno takes a very different approach than most other JS runtimes, and we learned some big lessons while implementing our adapter. For those curious, check out a some tricky Deno-related decisions we made along the way.

It was tough going at times, but as Dr. Malcolm would say: ~~life~~ the compiler finds a way 🦖

Moving closer to The Platform™

One of our driving forces with Remix is to use web standards and get to connect developers more closely to them with our APIs.

In the olden days, the only JavaScript runtime was the one implemented by browsers, but Node changed the game for everyone. In those days, many standards and APIs necessary to build a proper JS server runtime didn't exist, so the good folks working on Node had to invent them for us. Or in many cases we'd get "polyfills" for new standards from third-party libraries like node-fetch.

These were innovative times, and moving quickly allowed devs to ship more quickly. But inconsistency between runtimes also created a lot of problems. Thankfully we are getting closer than ever to consensus-driven solutions, and Remix is moving towards this new, more standardized approach.

We have removed our dependency on node-fetch and moved forward with our own implementation that gets closer to the living Fetch Standard. This opens the door to new features in your loaders and actions—you can now return ReadableStream in the body of your response, which allows you to stream data from your server and paves the way for the new streaming APIs in React 18.

This comes at an exciting time for the web, as just a few weeks ago we saw the formation of a new Web-interoperable Runtimes Community Group. We've never been more optimistic about the web, and we see this change as a necessary first step to embrace its future.

What's Changed

✨ Features

Replaced node-fetch with @remix-run/web-fetch for a more standards-based fetch implementation (#2736)
Launched official support for Deno (#3117)

💅 Enhancements

Made a few improvements in our experimental Netlify Edge adapter (#3107)

🐛 Bug fixes

Fixed support for JSX in .js route files (#3059)
Fixed issues with package manager detection (#3109)
Fixed the packageExports map (#3189)
Avoid duplicate loader calls when using prefetch-intent (#2938)

⚠️ Unstable API changes

unstable_parseMultipartFormData no longer operates on a Node.js stream, this has been changed to an AsyncIterable<Uint8Array> called data to bring this functionality to all platforms (#2736)
unstable_parseMultipartFormData no longer parses fields automatically for you; instead use unstable_composeUploadHandlers to combine multiple upload handlers (#2736)

New Contributors

@chiangs made their first contribution in [https://github.com/docs(examples/google-analytics): Change to getting GA_TRACKING_ID via .env and update README remix-run/remix#2960](https://redirect.github.com/re

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR was generated by Mend Renovate. View the repository job log.

renovate bot force-pushed the renovate/remix-run-react-1.x branch from a8c18f1 to 0779579 Compare April 28, 2022 00:15

renovate bot changed the title ~~chore(deps): update dependency @remix-run/react to v1.4.2~~ chore(deps): update dependency @remix-run/react to v1.4.3 Apr 28, 2022

renovate bot force-pushed the renovate/remix-run-react-1.x branch from 0779579 to 06241ef Compare May 18, 2022 22:43

renovate bot changed the title ~~chore(deps): update dependency @remix-run/react to v1.4.3~~ chore(deps): update dependency @remix-run/react to v1.5.0 May 18, 2022

renovate bot changed the title ~~chore(deps): update dependency @remix-run/react to v1.5.0~~ chore(deps): update dependency @remix-run/react to v1.5.1 May 19, 2022

renovate bot force-pushed the renovate/remix-run-react-1.x branch from 06241ef to 16bf05a Compare May 19, 2022 00:42

renovate bot force-pushed the renovate/remix-run-react-1.x branch from 16bf05a to f532fa2 Compare June 15, 2022 00:04

renovate bot changed the title ~~chore(deps): update dependency @remix-run/react to v1.5.1~~ chore(deps): update dependency @remix-run/react to v1.6.0 Jun 15, 2022

renovate bot force-pushed the renovate/remix-run-react-1.x branch from f532fa2 to 4ad76ee Compare June 22, 2022 15:43

renovate bot changed the title ~~chore(deps): update dependency @remix-run/react to v1.6.0~~ chore(deps): update dependency @remix-run/react to v1.6.1 Jun 22, 2022

renovate bot force-pushed the renovate/remix-run-react-1.x branch from 4ad76ee to f8916ee Compare September 25, 2022 13:10

renovate bot changed the title ~~chore(deps): update dependency @remix-run/react to v1.6.1~~ chore(deps): update dependency @remix-run/react to v1.7.2 Sep 25, 2022

renovate bot force-pushed the renovate/remix-run-react-1.x branch from f8916ee to f588193 Compare November 20, 2022 10:20

renovate bot changed the title ~~chore(deps): update dependency @remix-run/react to v1.7.2~~ chore(deps): update dependency @remix-run/react to v1.7.6 Nov 20, 2022

renovate bot force-pushed the renovate/remix-run-react-1.x branch from f588193 to 84c412a Compare March 24, 2023 19:43

renovate bot changed the title ~~chore(deps): update dependency @remix-run/react to v1.7.6~~ chore(deps): update dependency @remix-run/react to v1.14.3 Mar 24, 2023

renovate bot changed the title ~~chore(deps): update dependency @remix-run/react to v1.14.3~~ chore(deps): update dependency @remix-run/react to v1.15.0 Mar 31, 2023

renovate bot force-pushed the renovate/remix-run-react-1.x branch from 84c412a to ade813c Compare March 31, 2023 17:28

renovate bot force-pushed the renovate/remix-run-react-1.x branch from ade813c to 5e3b23c Compare May 31, 2023 04:01

renovate bot changed the title ~~chore(deps): update dependency @remix-run/react to v1.15.0~~ chore(deps): update dependency @remix-run/react to v1.16.1 May 31, 2023

renovate bot force-pushed the renovate/remix-run-react-1.x branch from 5e3b23c to 243adf9 Compare June 6, 2023 22:16

renovate bot changed the title ~~chore(deps): update dependency @remix-run/react to v1.16.1~~ chore(deps): update dependency @remix-run/react to v1.17.0 Jun 6, 2023

renovate bot force-pushed the renovate/remix-run-react-1.x branch from 243adf9 to e3a9107 Compare June 15, 2023 20:15

renovate bot changed the title ~~chore(deps): update dependency @remix-run/react to v1.17.0~~ chore(deps): update dependency @remix-run/react to v1.17.1 Jun 15, 2023

renovate bot force-pushed the renovate/remix-run-react-1.x branch from e3a9107 to a4bc9c5 Compare June 26, 2023 18:13

renovate bot changed the title ~~chore(deps): update dependency @remix-run/react to v1.17.1~~ chore(deps): update dependency @remix-run/react to v1.18.0 Jun 26, 2023

renovate bot force-pushed the renovate/remix-run-react-1.x branch from a4bc9c5 to e488a6f Compare June 30, 2023 22:46

renovate bot changed the title ~~chore(deps): update dependency @remix-run/react to v1.18.0~~ chore(deps): update dependency @remix-run/react to v1.18.1 Jun 30, 2023

renovate bot force-pushed the renovate/remix-run-react-1.x branch from e488a6f to d2923d1 Compare July 19, 2023 19:10

renovate bot changed the title ~~chore(deps): update dependency @remix-run/react to v1.18.1~~ chore(deps): update dependency @remix-run/react to v1.19.0 Jul 19, 2023

renovate bot force-pushed the renovate/remix-run-react-1.x branch from d2923d1 to 232b829 Compare July 21, 2023 21:32

renovate bot changed the title ~~chore(deps): update dependency @remix-run/react to v1.19.0~~ chore(deps): update dependency @remix-run/react to v1.19.1 Jul 21, 2023

renovate bot changed the title ~~chore(deps): update dependency @remix-run/react to v1.19.1~~ chore(deps): update dependency @remix-run/react to v1.19.2 Aug 4, 2023

renovate bot force-pushed the renovate/remix-run-react-1.x branch from 232b829 to 0f8a47e Compare August 4, 2023 13:07

chore(deps): update dependency @remix-run/react to v1.19.3

ae8d2ac

renovate bot changed the title ~~chore(deps): update dependency @remix-run/react to v1.19.2~~ chore(deps): update dependency @remix-run/react to v1.19.3 Aug 9, 2023

renovate bot force-pushed the renovate/remix-run-react-1.x branch from 0f8a47e to ae8d2ac Compare August 9, 2023 17:08

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency @remix-run/react to v1.19.3 #45

chore(deps): update dependency @remix-run/react to v1.19.3 #45

renovate bot commented Apr 27, 2022 •

edited

Loading

chore(deps): update dependency @remix-run/react to v1.19.3 #45

Are you sure you want to change the base?

chore(deps): update dependency @remix-run/react to v1.19.3 #45

Conversation

renovate bot commented Apr 27, 2022 • edited Loading

Release Notes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

What's Changed

🐛 Bug fixes

💅 Enhancements

New Contributors

What's Changed

🐛 Bug Fixes

💅 Enhancements

New Contributors

What's Changed

New Contributors

What Changed?

☠️ Deprecated

💅 Enhancements

🐛 Bug fixes

New Contributors

What's Changed

💅 Enhancements

Official support for Deno

Moving closer to The Platform™

What's Changed

✨ Features

💅 Enhancements

🐛 Bug fixes

⚠️ Unstable API changes

New Contributors

Configuration

renovate bot commented Apr 27, 2022 •

edited

Loading