Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Update version for release (pre) #5050

Closed
wants to merge 1 commit into from

Conversation

mcansh
Copy link
Collaborator

@mcansh mcansh commented Jan 10, 2023

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/[email protected]

@remix-run/architect

1.10.0

Patch Changes

1.9.0

Patch Changes

1.8.2

Patch Changes

1.8.1

Patch Changes

1.8.0

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.

Patch Changes

1.7.6

Patch Changes

1.7.5

Patch Changes

1.7.4

Patch Changes

1.7.3

Patch Changes

  • Fixed a bug that affected .wav and .webm audio file imports (#4290)
  • Updated dependencies:

1.7.2

Patch Changes

1.7.1

Patch Changes

  • Ensured that requests are properly aborted on closing of a Response instead of Request (#3626)
  • Updated dependencies:

1.7.0

Patch Changes

1.6.8

Patch Changes

1.6.7

Patch Changes

1.6.6

Patch Changes

1.6.5

Patch Changes

@remix-run/[email protected]

@remix-run/cloudflare

1.10.0

Patch Changes

  • Export V2_HtmlMetaDescriptor and V2_MetaFunction types from runtime packages (#4943)
  • Updated dependencies:

1.9.0

Patch Changes

1.8.2

Patch Changes

1.8.1

Patch Changes

1.8.0

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.

Patch Changes

1.7.6

Patch Changes

1.7.5

Patch Changes

1.7.4

Patch Changes

1.7.3

Patch Changes

1.7.2

Patch Changes

1.7.1

Patch Changes

1.7.0

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

1.6.8

Patch Changes

1.6.7

Patch Changes

1.6.6

Patch Changes

1.6.5

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
    @remix-run/cloudflare instead of typing the function directly:

    - import type { LoaderFunction } from "@remix-run/cloudflare";
    + import type { LoaderArgs } from "@remix-run/cloudflare";
    
    - 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.

  • Updated dependencies

@remix-run/[email protected]

@remix-run/deno

1.10.0

Patch Changes

  • Export V2_HtmlMetaDescriptor and V2_MetaFunction types from runtime
    packages (#4943)
  • Updated dependencies:

1.9.0

Patch Changes

1.8.2

Patch Changes

1.8.1

Patch Changes

1.8.0

Patch Changes

1.7.6

Patch Changes

Patch Changes

1.7.5

Patch Changes

1.7.4

Patch Changes

1.7.3

Patch Changes

1.7.2

Patch Changes

1.7.1

Patch Changes

1.7.0

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

1.6.8

Patch Changes

1.6.7

Patch Changes

1.6.6

Patch Changes

  • Add index.ts to main field to fix Node resolution issues when running
    remix dev or remix watch
    (#3868)
  • Updated dependencies:

1.6.5

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.
    (#1254)
  • Updated dependencies

@remix-run/[email protected]

@remix-run/dev

1.10.0

Patch Changes

  • Fixed several issues with TypeScript to JavaScript conversion when running create-remix (#4891)
  • Resolve asset entry full path to support monorepo import of styles (#4855)
  • Updated dependencies:

1.9.0

Minor Changes

  • Allow defining multiple routes for the same route module file (#3970)
  • Added support and conventions for optional route segments (#4706)

Patch Changes

  • The Remix compiler now supports new Typescript 4.9 syntax (like the satisfies keyword) (#4754)
  • Optimize parentRouteId lookup in defineConventionalRoutes. (#4800)
  • Fixed a bug in .ts -> .js conversion on Windows by using a relative unix-style path (#4718)
  • Updated dependencies:

1.8.2

Patch Changes

1.8.1

Patch Changes

  • Added a missing type definition for the Remix config future option to the @remix-run/dev/server-build virtual module (#4771)
  • Updated dependencies:

1.8.0

Minor Changes

  • 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

1.7.6

Patch Changes

Patch Changes

1.7.5

Patch Changes

1.7.4

Patch Changes

1.7.3

Patch Changes

  • Update create-remix to use the new examples repository when using --template example/<name> (#4208)
  • Add support for setting moduleResolution to node, node16 or nodenext in tsconfig.json. (#4034)
  • Add resources imported only by resource routes to assetsBuildDirectory (#3841)
  • Ensure that any assets referenced in CSS files are hashed and copied to the assetsBuildDirectory. (#4130)
  • Updated dependencies:

1.7.2

Patch Changes

1.7.1

Patch Changes

1.7.0

Minor Changes

  • Added support for importing .gql and .graphql files as plain text (#3923)
  • Added support for importing .zip and .avif files as resource URLs (#3985)

Patch Changes

1.6.8

Patch Changes

  • Added support for .mjs and .cjs file extensions for remix.config (#3675)
  • Added support for importing .sql files as text content (#3190)
  • Updated the compiler to make MDX builds deterministic (and a little faster!) (#3966)
  • Updated dependencies:

1.6.7

Patch Changes

1.6.6

Patch Changes

  • Write server build output files so that only assets imported from resource routes are written to disk (#3817)
  • Add support for exporting links in .mdx files (#3801)
  • Ensure that build hashing is deterministic (#2027)
  • Fix types for @remix-run/dev/server-build virtual module (#3743)
  • Updated dependencies:

1.6.5

Patch Changes

  • Update serverBareModulesPlugin warning to use full import path (#3656)
  • Fix broken --port flag in create-remix (#3694)
  • Updated dependencies
    • @remix-run/server-runtime
    • @remix-run/serve

@remix-run/[email protected]

@remix-run/node

1.10.0

Patch Changes

  • Export V2_HtmlMetaDescriptor and V2_MetaFunction types from runtime packages (#4943)
  • Updated dependencies:

1.9.0

Patch Changes

1.8.2

Patch Changes

1.8.1

Patch Changes

1.8.0

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.

Patch Changes

  • Update @remix-run/web-fetch. This addresses two bugs: (#4644)
    • It fixes a memory leak caused by unregistered listeners
    • It adds support for custom "credentials" values (Remix does nothing with these at the moment, but they pass through for the consumer of the request to access if needed)
  • Updated dependencies:

1.7.6

Patch Changes

1.7.5

Patch Changes

1.7.4

Patch Changes

1.7.3

Patch Changes

1.7.2

Patch Changes

  • Flush Node streams to address issues with libraries like compression that rely on chunk flushing (#4235)
  • Updated dependencies:

1.7.1

Patch Changes

1.7.0

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

  • Fixed a bug when destroying fileStorage sessions to prevent deleting entire session directories
  • Updated dependencies:

1.6.8

Patch Changes

1.6.7

Patch Changes

1.6.6

Patch Changes

1.6.5

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
    @remix-run/node instead of typing the function directly:

    - import type { LoaderFunction } from "@remix-run/node";
    + import type { LoaderArgs } from "@remix-run/node";
    
    - 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.

  • Updated dependencies

    • @remix-run/server-runtime

@remix-run/[email protected]

@remix-run/react

1.10.0

Minor Changes

1.9.0

Patch Changes

  • Update @remix-run/react to use Router from [email protected] (#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)

1.8.2

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.

1.8.1

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.

1.8.0

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)

1.7.6

Patch Changes

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

1.7.5

Patch Changes

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

1.7.4

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)

1.7.3

Patch Changes

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

1.7.2

Patch Changes

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

1.7.1

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)

1.7.0

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)

1.6.8

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)

1.6.7

Patch Changes

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

1.6.6

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)

1.6.5

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 "@remix-run/[runtime]";
    + import type { LoaderArgs } from "@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

@remix-run/[email protected]

@remix-run/serve

1.10.0

Patch Changes

1.9.0

Patch Changes

  • Fix TypedResponse so that Typescript correctly shows errors for incompatible types in loader and action functions. (#4734)
  • Updated dependencies:

1.8.2

Patch Changes

1.8.1

Patch Changes

1.8.0

Patch Changes

1.7.6

Patch Changes

1.7.5

Patch Changes

1.7.4

Patch Changes

1.7.3

Patch Changes

1.7.2

Patch Changes

1.7.1

Patch Changes

1.7.0

Minor Changes

  • We've added a new type: SerializeFrom. This is used to infer the (#4013)
    JSON-serialized return type of loaders and actions.
  • MetaFunction type can now infer data and parentsData types from route loaders (#4022)

Patch Changes

1.6.8

Patch Changes

1.6.7

Patch Changes

1.6.6

Patch Changes

1.6.5

Patch Changes

@remix-run/[email protected]

@remix-run/server-runtime

1.10.0

Minor Changes

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

Patch Changes

  • Export V2_HtmlMetaDescriptor and V2_MetaFunction types from runtime packages (#4943)
  • Fix V2_MetaFunction to return V2_HtmlMetaDescriptor[] type (#4947)

1.9.0

Patch Changes

  • Fix TypedResponse so that Typescript correctly shows errors for incompatible types in loader and action functions. (#4734)
  • Fix error boundary tracking for multiple errors bubbling to the same boundary (#4829)
  • Fixed an issue where a loader's Request object reflected method: "POST" on document submissions (a74e51830)

1.8.2

Patch Changes

  • Remove instanceof Response checks in favor of isResponse (#4782)
  • Fix performance regression with creation of @remix-run/router static handler (#4790)
  • Update dependency for @remix-run/router to v1.0.5 (bd84a9317)

1.8.1

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.

1.8.0

Minor Changes

  • We have been busy at work Layering Remix on top of React Router 6.4 and are excited to be releasing step 1 in this process that consists of performing all server-side data fetches/mutations through the new framework agnostic @remix-run/router. Server- and client-side rendering are still done the same as before, and will be updated in subsequent releases. (#4612)
  • 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

  • Properly categorize internal framework-thrown error Responses as error boundary errors (#4385)

    Previously there was some ambiguity around "thrown Responses go to the CatchBoundary".
    The CatchBoundary exists to give the user a place to handle non-happy path code flows
    such that they can throw Response instances from their own code and handle them in a
    CatchBoundary. However, there are a handful of framework-internal errors that make
    sense to have a non-500 status code, and the fact that these were being thrown as Response instances
    was causing them to go into the CatchBoundary, even though they were not user-thrown.

    With this change, anything thrown by the framework itself (Error or Response) will
    go to the ErrorBoundary, and any user-thrown Response instances will go to the
    CatchBoundary. There is one exception to this rule, which is that framework-detected
    404's will continue to go to the CatchBoundary since users should have one single
    location to handle 404 displays.

    The primary affected use cases are scenarios such as:

    • HTTP OPTIONS requests (405 Unsupported Method )
    • GET requests to routes without loaders (400 Bad Request)
    • POST requests to routes without actions (405 Method Not Allowed)
    • Missing route id in _data parameters (403 Forbidden)
    • Non-matching route id included in _data parameters (403 Forbidden)

1.7.6

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.7.6.

1.7.5

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.7.5.

1.7.4

Patch Changes

  • Ignore pathless layout routes in action matches (#4376)

1.7.3

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.7.3.

1.7.2

Patch Changes

  • Fix dependency conflicts with type-fest (87642b71b)

1.7.1

Patch Changes

  • Properly locked the dependency on react-router-dom to version 6.3.0 (#4203)

1.7.0

Minor Changes

  • We've added a new type: SerializeFrom. This is used to infer the (#4013)
    JSON-serialized return type of loaders and actions.
  • MetaFunction type can now infer data and parentsData types from route loaders (#4022)

Patch Changes

  • Improved performance for data serialization at runtime (#3889)

1.6.8

Patch Changes

  • We've added type safety for load context. AppLoadContext is now an an interface mapping string to unknown, allowing users to extend it via module augmentation: (#1876)

    declare module "@remix-run/server-runtime" {
      interface AppLoadContext {
        // add custom properties here!
      }
    }

1.6.7

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.6.7.

1.6.6

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.6.6.

1.6.5

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 "@remix-run/[runtime]";
    + import type { LoaderArgs } from "@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.

[email protected]

create-remix

1.10.0

Patch Changes

1.9.0

Patch Changes

1.8.2

Patch Changes

1.8.1

Patch Changes

1.8.0

Patch Changes

1.7.6

Patch Changes

1.7.5

Patch Changes

1.7.4

Patch Changes

1.7.3

Patch Changes

  • Update create-remix to use the new examples repository when using --template example/<name> (#4208)
  • Updated dependencies:

1.7.2

Patch Changes

1.7.1

Patch Changes

1.7.0

Patch Changes

1.6.8

Patch Changes

1.6.7

Patch Changes

1.6.6

Patch Changes

1.6.5

Patch Changes

@remix-run/[email protected]

@remix-run/cloudflare-pages

1.10.0

Patch Changes

1.9.0

Patch Changes

1.8.2

Patch Changes

1.8.1

Patch Changes

1.8.0

Patch Changes

1.7.6

Patch Changes

Patch Changes

1.7.5

Patch Changes

1.7.4

Patch Changes

1.7.3

Patch Changes

1.7.2

Patch Changes

1.7.1

Patch Changes

1.7.0

Patch Changes

1.6.8

Patch Changes

1.6.7

Patch Changes

1.6.6

Patch Changes

1.6.5

Patch Changes

@remix-run/[email protected]

@remix-run/cloudflare-workers

1.10.0

Patch Changes

1.9.0

Patch Changes

1.8.2

Patch Changes

1.8.1

Patch Changes

1.8.0

Patch Changes

1.7.6

Patch Changes

Patch Changes

1.7.5

Patch Changes

1.7.4

Patch Changes

1.7.3

Patch Changes

1.7.2

Patch Changes

1.7.1

Patch Changes

1.7.0

Patch Changes

1.6.8

Patch Changes

1.6.7

Patch Changes

1.6.6

Patch Changes

1.6.5

Patch Changes

@remix-run/[email protected]

@remix-run/eslint-config

1.10.0

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.10.0.

1.9.0

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.9.0.

1.8.2

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.

1.8.1

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.

1.8.0

Patch Changes

  • Replace references to the old migrate command with the new codemod command (#4646)

1.7.6

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.7.6.

1.7.5

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.7.5.

1.7.4

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.7.4.

1.7.3

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.7.3.

1.7.2

Patch Changes

  • Update ESLint and plugin dependencies (e4ec81c77)

1.7.1

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.7.1.

1.7.0

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.7.0.

1.6.8

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.6.8.

1.6.7

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.6.7.

1.6.6

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.6.6.

1.6.5

Patch Changes

  • Use require.resolve when importing @babel/preset-react (#3716)

@remix-run/[email protected]

@remix-run/express

1.10.0

Patch Changes

1.9.0

Patch Changes

1.8.2

Patch Changes

1.8.1

Patch Changes

1.8.0

Patch Changes

1.7.6

Patch Changes

1.7.5

Patch Changes

1.7.4

Patch Changes

1.7.3

Patch Changes

1.7.2

Patch Changes

1.7.1

Patch Changes

  • Ensured that requests are properly aborted on closing of a Response instead of Request (#3626)
  • Updated dependencies:

1.7.0

Patch Changes

1.6.8

Patch Changes

1.6.7

Patch Changes

1.6.6

Patch Changes

1.6.5

Patch Changes

@remix-run/[email protected]

@remix-run/netlify

1.10.0

Patch Changes

1.9.0

Patch Changes

1.8.2

Patch Changes

1.8.1

Patch Changes

1.8.0

Patch Changes

1.7.6

Patch Changes

1.7.5

Patch Changes

1.7.4

Patch Changes

1.7.3

Patch Changes

  • Fixed a bug that affected .wav and .webm audio file imports (#4290)
  • Updated dependencies:

1.7.2

Patch Changes

1.7.1

Patch Changes

  • Ensured that requests are properly aborted on closing of a Response instead of Request (#3626)
  • Updated dependencies:

1.7.0

Patch Changes

1.6.8

Patch Changes

  • We've added type safety for load context. AppLoadContext is now an an interface mapping string to unknown, allowing users to extend it via module augmentation: (#1876)

    declare module "@remix-run/server-runtime" {
      interface AppLoadContext {
        // add custom properties here!
      }
    }
  • Updated dependencies:

1.6.7

Patch Changes

1.6.6

Patch Changes

1.6.5

Patch Changes

@remix-run/[email protected]

@remix-run/testing

1.10.0

Patch Changes

  • Remove internal installGlobals function now that @remix-run/web-form-data includes support for passing a HTMLFormElement (#4755)
  • Use React Router data APIs directly (#4915)
  • Updated dependencies:

1.9.0

Patch Changes

@remix-run/[email protected]

@remix-run/vercel

1.10.0

Patch Changes

1.9.0

Patch Changes

1.8.2

Patch Changes

1.8.1

Patch Changes

1.8.0

Patch Changes

1.7.6

Patch Changes

1.7.5

Patch Changes

1.7.4

Patch Changes

1.7.3

Patch Changes

1.7.2

Patch Changes

1.7.1

Patch Changes

  • Ensured that requests are properly aborted on closing of a Response instead of Request (#3626)
  • Updated dependencies:

1.7.0

Patch Changes

1.6.8

Patch Changes

1.6.7

Patch Changes

1.6.6

Patch Changes

1.6.5

Patch Changes

[email protected]

remix

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants