Update remix monorepo to v2 (major) #149

renovate · 2023-09-15T19:24:46Z

This PR contains the following updates:

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

Release Notes

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

`v2.0.1`

Compare Source

Patch Changes

Fix types for MDX files when using pnpm (#7491)
Update getDependenciesToBundle to handle ESM packages without main exports (#7272)
- Note that these packages must expose package.json in their exports field so that their path can be resolved
Fix server builds where serverBuildPath extension is .cjs (#7180)
Updated dependencies:
- @remix-run/[email protected]

`v2.0.0`

Compare Source

Major Changes

The create-remix CLI has been rewritten to feature a cleaner interface, Git repo initialization and optional remix.init script execution. The interactive template prompt and official Remix stack/template shorthands have also been removed so that community/third-party templates are now on a more equal footing. (#6887)
- The code for create-remix has been moved out of the Remix CLI since it's not intended for use within an existing Remix application
- This means that the remix create command is no longer available.
Enable built-in PostCSS and Tailwind support by default. (#6909)
- These tools are now automatically used within the Remix compiler if PostCSS and/or Tailwind configuration files are present in your project.
- If you have a custom PostCSS and/or Tailwind setup outside of Remix, you can disable these features in your remix.config.js via the postcss:false and/or tailwind:false flags
Drop React 17 support (#7121)
Require Node >=18.0.0 (#6939)
Compile server build to Node 18 (#7292)
- This allows features like top-level await to be used within a Remix app
Remove default Node.js polyfills - you must now opt-into polyfills via the serverNodeBuiltinsPolyfill and browserNodeBuiltinsPolyfill configs (#7269)
Remove v2_errorBoundary flag and CatchBoundary implementation (#6906)
Remove v2_normalizeFormMethod future flag - all formMethod values will be normalized in v2 (#6875)
Remove v2_routeConvention flag - the flat route file convention is now standard (#6969)
Remove v2_headers flag - it is now the default behavior to use the deepest headers function in the route tree (#6979)
The route meta API now defaults to the new "V2 Meta" API (#6958)
- Please refer to the (docs and Preparing for V2 guide for more information.
Default to serverModuleFormat: "esm" and update remix-serve to use dynamic import to support ESM and CJS build outputs (#6949)
Remove serverBuildTarget config option (#6896)
Remove deprecated REMIX_DEV_HTTP_ORIGIN env var - use REMIX_DEV_ORIGIN instead (#6963)
Remove devServerBroadcastDelay config option (#7063)
Remove deprecated devServerPort option - use --port / dev.port instead (#7078)
Remove deprecated REMIX_DEV_SERVER_WS_PORT env var - use remix dev's '--port / port option instead (#6965)
Stop passing isTypeScript to remix.init script (#7099)
Remove replace-remix-magic-imports codemod (#6899)
Remove deprecated --no-restart/restart cli args/flags - use --manual/manual instead (#6962)
Remove deprecated --scheme/scheme and --host/host cli args/flags - use REMIX_DEV_ORIGIN instead (#6962)
Promote the future.v2_dev flag in remix.config.js to a root level dev config (#7002)
Remove browserBuildDirectory config option (#6900)
Remove serverBuildDirectory config option ([#6897](https://github.com/remix-run/remix/pull/- Remove codemod command (#6918)
6897))

Removed support for "magic exports" from the remix package. This package can be removed from your package.json and you should update all imports to use the source @remix-run/* packages: (#6895)

- import type { ActionArgs } from "remix";
- import { json, useLoaderData } from "remix";
+ import type { ActionArgs } from "@&#8203;remix-run/node";
+ import { json } from "@&#8203;remix-run/node";
+ import { useLoaderData } from "@&#8203;remix-run/react";

Minor Changes

Warn users about obsolete future flags in remix.config.js (#7048)
Detect built mode via build.mode (#6964)
- Prevents mode mismatch between built Remix server entry and user-land server
- Additionally, all runtimes (including non-Node runtimes) can use build.mode to determine if HMR should be performed
Support bun package manager (#7074)

The serverNodeBuiltinsPolyfill option (along with the newly added browserNodeBuiltinsPolyfill) now supports defining global polyfills in addition to module polyfills (#7269)

For example, to polyfill Node's Buffer global:

module.exports = {
  serverNodeBuiltinsPolyfill: {
    globals: {
      Buffer: true,
    },
    // You'll probably need to polyfill the "buffer" module
    // too since the global polyfill imports this:
    modules: {
      buffer: true,
    },
  },
};

Patch Changes

Fix importing of PNGs, SVGs, and other assets from packages in node_modules (#6813, #7182)
Decouple the @remix-run/dev package from the contents of the @remix-run/css-bundle package. (#6982)
- The contents of the @remix-run/css-bundle package are now entirely managed by the Remix compiler
- Even though it's still recommended that your Remix dependencies all share the same version, this change ensures that there are no runtime errors when upgrading @remix-run/dev without upgrading @remix-run/css-bundle
Allow non-development modes for remix watch (#7117)
Stop remix dev when esbuild is not running (#7158)

Do not interpret JSX in .ts files (#7306)

While JSX is supported in .js files for compatibility with existing apps and libraries,
.ts files should not contain JSX. By not interpreting .ts files as JSX, .ts files
can contain single-argument type generics without needing a comma to disambiguate from JSX:

// this works in .ts files
const id = <T>(x: T) => x;
//          ^ single-argument type generic

// this doesn't work in .tsx files
const id = <T,>(x: T) => x;
//          ^ is this a JSX element? or a single-argument type generic?

// this works in .tsx files
const id = <T,>(x: T) => x;
//           ^ comma: this is a generic, not a JSX element
const component = <h1>hello</h1>;
//                   ^ no comma: this is a JSX element

Enhance obsolete flag warning for future.v2_dev if it was an object, and prompt users to lift it to the root dev config (#7427)
Allow decorators in app code (#7176)
Allow JSX in .js files during HMR (#7112)
Kill app server when remix dev terminates (#7280)
Support dependencies that import polyfill packages for Node built-ins via a trailing slash (e.g. importing the buffer package with var Buffer = require('buffer/').Buffer as recommended in their README) (#7198)
- These imports were previously marked as external
- This meant that they were left as dynamic imports in the client bundle and would throw a runtime error in the browser (e.g. Dynamic require of "buffer/" is not supported)
Surface errors when PostCSS config is invalid (#7391)
Restart dev server when Remix config changes (#7269)
Remove outdated ESM import warnings (#6916)
- Most of the time these warnings were false positives.
- Instead, we now rely on built-in Node warnings for ESM imports.
Do not trigger rebuilds when .DS_Store changes (#7172)
Remove warnings for stabilized flags: (#6905)
- unstable_cssSideEffectImports
- unstable_cssModules
- unstable_vanillaExtract
Allow any mode (NODE_ENV) (#7113)
Replace the deprecated xdm package with @mdx-js/mdx (#4054)
Write a version.txt sentinel file after server build is completely written (#7299)
Updated dependencies:
- @remix-run/[email protected]

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

`v2.0.1`

Compare Source

Patch Changes

Add second generic to UIMatch for handle field (#7464)
Fix resource routes being loaded through route.lazy (#7498)
Throw a semantically correct 405 ErrorResponse instead of just an Error when submitting to a route without an action (#7423)
Updated dependencies:
- @remix-run/[email protected]

`v2.0.0`

Compare Source

Major Changes

Drop React 17 support (#7121)
Require Node >=18.0.0 (#6939)
Remove unstable_shouldReload, which has been replaced by shouldRevalidate (#6865)
The route meta API now defaults to the new "V2 Meta" API (#6958)
- Please refer to the (docs and Preparing for V2 guide for more information.
Promote the future.v2_dev flag in remix.config.js to a root level dev config (#7002)
Remove v2_errorBoundary flag and CatchBoundary implementation (#6906)
Remove back-compat layer for useFetcher/useFetchers, which includes a few small breaking changes (#6874)
- fetcher.type has been removed since it can be derived from other available information
- "Submission" fields have been flattened from fetcher.submission down onto the root fetcher object, and prefixed with form in some cases (fetcher.submission.action => fetcher.formAction)
- <fetcher.Form method="get"> is now more accurately categorized as state:"loading" instead of state:"submitting" to better align with the underlying GET request
Remove v2_normalizeFormMethod future flag - all formMethod values will be normalized in v2 (#6875)
Remove deprecated useTransition hook in favor of useNavigation - useNavigation is almost identical with a few exceptions: (#6870)
- useTransition.type has been removed since it can be derived from other available information
- "Submission" fields have been flattened from useTransition().submission down onto the root useNavigation() object
- <Form method="get"> is now more accurately categorized as state:"loading" instead of state:"submitting" to better align with the underlying GET navigation
Remove v2_routeConvention flag - the flat route file convention is now standard. (#6969)
Remove v2_headers flag - it is now the default behavior to use the deepest headers function in the route tree. (#6979)
Removed/adjusted types to prefer unknown over any and to align with underlying React Router types (#7319, #7354):
- Renamed the useMatches() return type from RouteMatch to UIMatch
- Renamed LoaderArgs/ActionArgs to LoaderFunctionArgs/ActionFunctionArgs
- AppData changed from any to unknown
- Location["state"] (useLocation.state) changed from any to unknown
- UIMatch["data"] (useMatches()[i].data) changed from any to unknown
- UIMatch["handle"] (useMatches()[i].handle) changed from { [k: string]: any } to unknown
- Fetcher["data"] (useFetcher().data) changed from any to unknown
- MetaMatch.handle (used in meta()) changed from any to unknown
- AppData/RouteHandle are no longer exported as they are just aliases for unknown
Remove imagesizes & imagesrcset properties from HtmlLinkDescriptor, LinkDescriptor & PrefetchPageDescriptor types (#6936)
Remove deprecated REMIX_DEV_SERVER_WS_PORT env var (#6965)
- use remix dev's '--port/port option instead

Removed support for "magic exports" from the remix package. This package can be removed from your package.json and you should update all imports to use the source @remix-run/* packages: (#6895)

- import type { ActionArgs } from "remix";
- import { json, useLoaderData } from "remix";
+ import type { ActionArgs } from "@&#8203;remix-run/node";
+ import { json } from "@&#8203;remix-run/node";
+ import { useLoaderData } from "@&#8203;remix-run/react";

Minor Changes

Export the Navigation type returned from useNavigation (#7136)
Update Remix to use React Router route.lazy for module loading (#7133)

Patch Changes

Add error to meta() params so you can render error titles, etc. (#7105)

export function meta({ error }) {
  return [{ title: error.message }];
}

Re-Export ShouldRevalidateFunctionArgs type from React Router (#7316)
Deduplicate prefetch link tags (#7060)
Skip preloading of stylesheets on client-side route transitions if the browser does not support <link rel=preload> (#7106)
- This prevents us from hanging on client-side navigations when we try to preload stylesheets and never receive a load/error event on the link tag
Export proper ErrorResponse type for usage alongside isRouteErrorResponse (#7244)
Use the hostname from REMIX_DEV_ORIGIN to connect to the live reload socket (#6923)
Use unique key for script:ld+json meta descriptors (#6954)
Fix live reload port when set explicitly as a prop (#7358)
Fix types for useLoaderData when using Yarn PnP (#7137)
Updated dependencies:
- @remix-run/[email protected]
- [email protected]
- @remix-run/[email protected]

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

`v2.0.1`

Compare Source

Patch Changes

Fix HMR for CJS projects using remix-serve and manual mode (remix dev --manual) (#7487)
- By explicitly busting the require cache, remix-serve now correctly re-imports new server changes in CJS
- ESM projects were already working correctly and are not affected by this.
Fix error caused by partially written server build (#7470)
- Previously, it was possible to trigger a reimport of the app server code before the new server build had completely been written. Reimporting the partially written server build caused issues related to build.assets being undefined and crashing when reading build.assets.version
Updated dependencies:
- @remix-run/[email protected]
- @remix-run/[email protected]

`v2.0.0`

Compare Source

Major Changes

remix-serve now picks an open port if 3000 is taken (#7278)
- If PORT env var is set, remix-serve will use that port
- Otherwise, remix-serve picks an open port (3000 unless that is already taken)
Integrate manual mode in remix-serve (#7231)
Remove undocumented createApp Node API (#7229)
- remix-serve is a CLI, not a library
Require Node >=18.0.0 (#6939)
Promote the future.v2_dev flag in remix.config.js to a root level dev config (#7002)
Default to serverModuleFormat: "esm" and update remix-serve to use dynamic import to support ESM and CJS build outputs (#6949)
Preserve dynamic imports in remix-serve for external bundle (#7173)
For preparation of using Node's built in fetch implementation, installing the fetch globals is now a responsibility of the app server (#7009)
- If you are using remix-serve, nothing is required
- If you are using your own app server, you will need to install the globals yourself
```
import { installGlobals } from "@&#8203;remix-run/node";

installGlobals();
```
source-map-support is now a responsibility of the app server (#7009)
- If you are using remix-serve, nothing is required
- If you are using your own app server, you will need to install source-map-support yourself.
```
npm i source-map-support
```
```
import sourceMapSupport from "source-map-support";
sourceMapSupport.install();
```

Patch Changes

Update remix-serve usage error message to support ESM projects (#7400)
Updated dependencies:
- @remix-run/[email protected]
- @remix-run/[email protected]

remix-run/remix (remix)

`v2.0.1`: v2.0.1

Compare Source

Patch Changes

Fix types for MDX files when using pnpm (#7491)
Update getDependenciesToBundle to handle ESM packages without main exports (#7272)
- Note that these packages must expose package.json in their exports field so that their path can be resolved
Fix server builds where serverBuildPath extension is .cjs (#7180)
Fix HMR for CJS projects using remix-serve and manual mode (remix dev --manual) (#7487)
- By explicitly busting the require cache, remix-serve now correctly re-imports new server changes in CJS
- ESM projects were already working correctly and are not affected by this.
Fix error caused by partially written server build (#7470)
- Previously, it was possible to trigger a reimport of the app server code before the new server build had completely been written. Reimporting the partially written server build caused issues related to build.assets being undefined and crashing when reading build.assets.version
Add second generic to UIMatch for handle field (#7464)
Fix resource routes being loaded through route.lazy (#7498)
Throw a semantically correct 405 ErrorResponse instead of just an Error when submitting to a route without an action (#7423)
Update to latest version of @remix-run/web-fetch (#7477)
Switch from crypto.randomBytes to crypto.webcrypto.getRandomValues for file session storage ID generation (#7203)
Use native Blob class instead of polyfill (#7217)

Changes by Package 🔗

Full Changelog: 2.0.0...2.0.1

`v2.0.0`: v2.0.0

Compare Source

Remix v2

We're so excited to release Remix v2 to you and we really hope this upgrade is one of the smoothest framework upgrades you've ever experienced! That was our primary goal with v2 - something we aimed to achieve through a heavy use of deprecation warnings and Future Flags in Remix v1.

If you are on the latest 1.x version and you've enabled all future flags and addressed all console warnings, then our hope is that you are 90% of the way to being upgraded for v2. There are always going to be a few things that we can't put behind a flag (like breaking type changes) or come up at the very last moment and don't have time to add as a warning or flag in 1.x.

If you're not yet on the latest 1.x version we'd recommend first upgrading to that and resolving any flag/console warnings:

> npx upgrade-remix 1.19.3

Breaking Changes

Below is a very concise list of the breaking changes in v2.

For the most thorough discussion of breaking changes, please read the Upgrading to v2 guide. This document provides a comprehensive walkthrough of the breaking changes that come along with v2 - and instructions on how to adapt your application to handle them
For additional details, you can refer to the Changes by Package section below

Upgraded Dependency Requirements

Remix v2 has upgraded it's minimum version support for React and Node and now officially requires:

React 18 (#7121)
- For information on upgrading to React 18, please see the React upgrade guide
Node 18 or later (#6939, #7292)
- For information on upgrading to Node 18, please see the Node v18 announcement
- Please refer to the Remix documentation for an overview of when we drop support for Node versions

Removed Future Flags

The following future flags were removed and their behavior is now the default - you can remove all of these from your remix.config.js file.

v2_dev - New dev server with HMR+HDR (#7002)
- If you had configurations in future.v2_dev instead of just the boolean value (i.e., future.v2_dev.port), you can lift them into a root dev object in your remix.config.js
v2_errorBoundary - Removed CatchBoundary in favor of a singular ErrorBoundary (#6906)
v2_headers - Altered the logic for headers in nested route scenarios (#6979)
v2_meta - Altered the return format of meta() (#6958)
v2_normalizeFormMethod - Normalize formMethod APIs to uppercase (#6875)
v2_routeConvention - Routes use a flat route convention by default now (#6969)

Breaking Changes/API Removals

With deprecation warnings

The following lists other breaking changes/API removals which had deprecation warnings in Remix v1. If you're on the latest 1.19.3 release without any console warnings, then you're probably good to go on all of these!

remix.config.js
- Renamed browserBuildDirectory to assetsBuildDirectory (#6900)
- Removed devServerBroadcastDelay (#7063)
- Renamed devServerPort to dev.port (000457e0)
  - Note that if you are opting into this in a 1.x release, your config flag will be future.v2_dev.port, but on a stable 2.x release it will be dev.port
- Changed the default serverModuleFormat from cjs to esm (#6949)
- Removed serverBuildTarget (#6896)
- Changed serverBuildDirectory to serverBuildPath (#6897)
- Node built-ins are no longer polyfilled on the server by default, you must opt-into polyfills via serverNodeBuiltinsPolyfill (#6911
@remix-run/react
- Removed useTransition (#6870)
- Removed fetcher.type and flattened fetcher.submission (#6874)
  - <fetcher.Form method="get"> is now more accurately categorized as state:"loading" instead of state:"submitting" to better align with the underlying GET request
- Require camelCased versions of imagesrcset/imagesizes (#6936)

Without deprecation warnings

Unfortunately, we didn't manage to get a deprecation warning on every breaking change or API removal 🙃. Here's a list of remaining changes that you may need to look into to upgrade to v2:

remix.config.js
- Node built-ins are no longer polyfilled in the browser by default, you must opt-into polyfills via browserNodeBuiltinsPolyfill (#7269)
- PostCSS/Tailwind will be enabled by default if config files exist in your app, you may disable this via the postcss and tailwind flags (#6909)
@remix-run/cloudflare
- Remove createCloudflareKVSessionStorage (#6898)
- Drop @cloudflare/workers-types v2 & v3 support (#6925)
@remix-run/dev
- Removed REMIX_DEV_HTTP_ORIGIN in favor of REMIX_DEV_ORIGIN (#6963)
- Removed REMIX_DEV_SERVER_WS_PORT in favor of dev.port or --port (#6965)
- Removed --no-restart/restart flag in favor of --manual/manual (#6962)
- Removed --scheme/scheme and --host/host in favor of REMIX_DEV_ORIGIN instead (#6962)
- Removed the codemod command (#6918)
@remix-run/eslint-config
- Remove @remix-run/eslint-config/jest config (#6903)
- Remove magic imports ESLint warnings (#6902)
@remix-run/netlify
- The @remix-run/netlify adapter has been removed in favor of the Netlify official adapters (#7058)
@remix-run/node
- fetch is no longer polyfilled by default - apps must call installGlobals() to install the polyfills (#7009)
- fetch and related APIs are no longer exported from @remix-run/node - apps should use the versions in the global namespace (#7293)
- Apps must call sourceMapSupport.install() to setup source map support
@remix-run/react
- Remove unstable_shouldReload in favor of shouldRevalidate (#6865)
@remix-run/serve
- remix-serve picks an open port if 3000 is taken and PORT is not specified (#7278)
- Integrate manual mode (#7231)
- Remove undocumented createApp Node API (#7229)
- Preserve dynamic imports in remix-serve for external bundle (#7173)
@remix-run/vercel
- The @remix-run/vercel adapter has been removed in favor of out of the box functionality provided by Vercel (#7035)
create-remix
- Stop passing isTypeScript to remix.init script (#7099)
remix
- Removed magic exports (#6895)

Breaking Type Changes

Removed V2_ prefixes from future.v2_meta types as they are now the default behavior (#6958)
- V2_MetaArgs -> MetaArgs
- V2_MetaDescriptor -> MetaDescriptor
- V2_MetaFunction -> MetaFunction
- V2_MetaMatch -> MetaMatch
- V2_MetaMatches -> MetaMatches
- V2_ServerRuntimeMetaArgs -> ServerRuntimeMetaArgs
- V2_ServerRuntimeMetaDescriptor -> ServerRuntimeMetaDescriptor
- V2_ServerRuntimeMetaFunction -> ServerRuntimeMetaFunction
- V2_ServerRuntimeMetaMatch -> ServerRuntimeMetaMatch
- V2_ServerRuntimeMetaMatches -> ServerRuntimeMetaMatches
The following types were adjusted to prefer unknown over any and to align with underlying React Router types (#7319):
- Renamed the useMatches() return type from RouteMatch to UIMatch
- Renamed LoaderArgs/ActionArgs to LoaderFunctionArgs/ActionFunctionArgs
- AppData changed from any to unknown
- Location["state"] (useLocation.state) changed from any to unknown
- UIMatch["data"] (useMatches()[i].data) changed from any to unknown
- UIMatch["handle"] (useMatches()[i].handle) changed from { [k: string]: any } to unknown
- Fetcher["data"] (useFetcher().data) changed from any to unknown
- MetaMatch.handle (used in meta()) changed from any to unknown
- AppData/RouteHandle are no longer exported as they are just aliases for unknown

New Features

New create-remix CLI (#6887)
- Most notably, this removes the dropdown to choose your template/stack in favor of the --template flag and our ever-growing list of available templates
- Adds a new --overwrite flag (#7062)
- Supports the bun package manager (#7074)
Detect built mode via build.mode (#6964)
Support polyfilling node globals via serverNodeBuiltinsPolyfill.globals/browserNodeBuiltinsPolyfill.globals (#7269)
New redirectDocument utility to redirect via a fresh document load (#7040, #6842)
Add error to meta params so you can render error titles, etc. (#7105)
unstable_createRemixStub now supports adding meta/links functions on stubbed Remix routes (#7186)
- unstable_createRemixStub no longer supports the element/errorElement properties on routes. You must use Component/ErrorBoundary to match what you would export from a Remix route module.

Other Notable Changes

Remix now uses React Router's route.lazy method internally to load route modules on navigations (#7133)
Removed the @remix-run/node atob/btoa polyfills in favor of the built-in versions (#7206)
Decouple the @remix-run/dev package from the contents of the @remix-run/css-bundle package (#6982)
- The contents of the @remix-run/css-bundle package are now entirely managed by the Remix compiler. Even though it's still recommended that your Remix dependencies all share the same version, this change ensures that there are no runtime errors when upgrading @remix-run/dev without upgrading @remix-run/css-bundle.
remix-serve now picks an open port if 3000 is taken (#7278)
- If PORT env var is set, remix-serve will use that port
- Otherwise, remix-serve picks an open port (3000 unless that is already taken)
Updated dependencies:

Changes by Package

Full Changelog: 1.19.3...2.0.0

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

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

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

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

Otherwise: ``` Error: Directory import '/srv/build' is not supported resolving ES modules imported from /srv/node_modules/@remix-run/serve/dist/cli.js Did you mean to import /srv/build/index.js? at new NodeError (node:internal/errors:406:5) at finalizeResolution (node:internal/modules/esm/resolve:227:11) at moduleResolve (node:internal/modules/esm/resolve:845:10) at defaultResolve (node:internal/modules/esm/resolve:1043:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12) at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25) at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:228:38) at ModuleLoader.import (node:internal/modules/esm/loader:315:34) at importModuleDynamically (node:internal/modules/cjs/loader:1164:37) at importModuleDynamicallyWrapper (node:internal/vm/module:431:21) ```

renovate · 2023-10-13T07:53:12Z

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

renovate bot force-pushed the renovate/major-remix-monorepo branch from d9c8b82 to b09484b Compare September 18, 2023 20:55

renovate bot force-pushed the renovate/major-remix-monorepo branch 4 times, most recently from dde71bf to 07d9a33 Compare October 6, 2023 01:26

renovate bot force-pushed the renovate/major-remix-monorepo branch 3 times, most recently from 452c2f2 to 15babb3 Compare October 10, 2023 23:12

Update remix monorepo to v2

eba44dd

renovate bot force-pushed the renovate/major-remix-monorepo branch from 15babb3 to eba44dd Compare October 12, 2023 22:13

lauraseidler added 4 commits October 13, 2023 09:44

Remove V2 feature flags

347943b

Remove obsolete package

bf8c0fa

Remove obsolete setup command run

8f85afc

Dockerfile optimizations

a70a73d

lauraseidler force-pushed the renovate/major-remix-monorepo branch from 63c9e65 to a70a73d Compare October 13, 2023 07:58

Set explicit Python version

6249d7d

lauraseidler merged commit de9933f into main Oct 13, 2023
1 check passed

lauraseidler deleted the renovate/major-remix-monorepo branch October 13, 2023 08:01

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update remix monorepo to v2 (major) #149

Update remix monorepo to v2 (major) #149

renovate bot commented Sep 15, 2023 •

edited

Loading

renovate bot commented Oct 13, 2023

Update remix monorepo to v2 (major) #149

Update remix monorepo to v2 (major) #149

Conversation

renovate bot commented Sep 15, 2023 • edited Loading

Release Notes

v2.0.1

Patch Changes

v2.0.0

Major Changes

Minor Changes

Patch Changes

v2.0.1

Patch Changes

v2.0.0

Major Changes

Minor Changes

Patch Changes

v2.0.1

Patch Changes

v2.0.0

Major Changes

Patch Changes

v2.0.1: v2.0.1

Patch Changes

Changes by Package 🔗

v2.0.0: v2.0.0

Remix v2

Breaking Changes

Upgraded Dependency Requirements

Removed Future Flags

Breaking Changes/API Removals

With deprecation warnings

Without deprecation warnings

Breaking Type Changes

New Features

Other Notable Changes

Changes by Package

Configuration

renovate bot commented Oct 13, 2023

Edited/Blocked Notification

renovate bot commented Sep 15, 2023 •

edited

Loading

`v2.0.1`

`v2.0.0`

`v2.0.1`

`v2.0.0`

`v2.0.1`

`v2.0.0`

`v2.0.1`: v2.0.1

`v2.0.0`: v2.0.0