fix(deps): update remix monorepo to v1.19.3 #26
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
559b4b3
to
330b96e
Compare
Deploying capracon-2023 with
|
| Latest commit: |
b08bfca
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://dcf783ea.capracon-2023.pages.dev |
| Branch Preview URL: | https://renovate-remix-monorepo.capracon-2023.pages.dev |
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
330b96e
to
6db8471
Compare
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
6db8471
to
188eb75
Compare
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
188eb75
to
dbe5232
Compare
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: package-lock.json |
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
dbe5232
to
b08bfca
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.11.1->1.19.31.11.1->1.19.31.11.1->1.19.31.11.1->1.19.31.11.1->1.19.3Release Notes
remix-run/remix (@remix-run/cloudflare)
v1.19.3Compare Source
Patch Changes
@remix-run/[email protected]v1.19.2Compare Source
Patch Changes
@remix-run/[email protected]v1.19.1Compare Source
Patch Changes
@remix-run/[email protected]v1.19.0Compare Source
Patch Changes
@remix-run/[email protected]v1.18.1Compare Source
Patch Changes
@remix-run/[email protected]v1.18.0Compare Source
Patch Changes
@remix-run/[email protected]v1.17.1Compare Source
Patch Changes
@remix-run/[email protected]v1.17.0Compare Source
Patch Changes
Add
HeadersArgstype to be consistent with loaders/actions/meta and allows for using afunctiondeclaration in addition to an arrow function expression (#6247)Updated dependencies:
@remix-run/[email protected]v1.16.1Compare Source
Patch Changes
@remix-run/[email protected]v1.16.0Compare Source
Patch Changes
getLoadContextin all adapters (#6170)logDevReadyas replacement for platforms that can't initialize async I/O outside of the request response lifecycle. (#6204)@remix-run/[email protected]v1.15.0Compare Source
Minor Changes
We have made a few changes to the API for route module
metafunctions when using thefuture.v2_metaflag. These changes are only breaking for users who have opted in. (#5746)V2_HtmlMetaDescriptorhas been renamed toV2_MetaDescriptormetafunction's arguments have been simplifiedparentsDatahas been removed, as each route's loader data is available on thedataproperty of its respectivematchobjectrouteproperty on route matches has been removed, as relevant match data is attached directly to the match object<script type='application/ld+json' />and meta-related<link />tags to document head via the routemetafunction when using thev2_metafuture flagPatch Changes
@remix-run/[email protected]v1.14.3Compare Source
Patch Changes
@remix-run/[email protected]v1.14.2Compare Source
Patch Changes
@remix-run/[email protected]v1.14.1Compare Source
Patch Changes
@remix-run/[email protected]v1.14.0Compare Source
Patch Changes
@remix-run/[email protected]v1.13.0Compare Source
Patch Changes
@remix-run/[email protected]v1.12.0Compare Source
Minor Changes
createCloudflareKVSessionStoragein favor ofcreateWorkersKVSessionStorage(#2542)Patch Changes
RequestHandlertype to match other adapter types (#4884)@remix-run/[email protected]remix-run/remix (@remix-run/cloudflare-pages)
v1.19.3Compare Source
Patch Changes
@remix-run/[email protected]v1.19.2Compare Source
Patch Changes
@remix-run/[email protected]v1.19.1Compare Source
Patch Changes
@remix-run/[email protected]v1.19.0Compare Source
Patch Changes
@remix-run/[email protected]v1.18.1Compare Source
Patch Changes
@remix-run/[email protected]v1.18.0Compare Source
Patch Changes
@remix-run/[email protected]v1.17.1Compare Source
Patch Changes
@remix-run/[email protected]v1.17.0Compare Source
Patch Changes
@remix-run/[email protected]v1.16.1Compare Source
Patch Changes
@remix-run/[email protected]v1.16.0Compare Source
Patch Changes
getLoadContextin all adapters (#6170)@remix-run/[email protected]v1.15.0Compare Source
Patch Changes
@remix-run/[email protected]v1.14.3Compare Source
Patch Changes
@remix-run/[email protected]v1.14.2Compare Source
Patch Changes
@remix-run/[email protected]v1.14.1Compare Source
Patch Changes
@remix-run/[email protected]v1.14.0Compare Source
Patch Changes
@remix-run/[email protected]v1.13.0Compare Source
Patch Changes
@remix-run/[email protected]v1.12.0Compare Source
Patch Changes
@remix-run/[email protected]remix-run/remix (@remix-run/dev)
v1.19.3Compare Source
Patch Changes
devServerBroadcastDelayanddevServerPortconfig options (#7064)@remix-run/[email protected]v1.19.2Compare Source
Patch Changes
proxy-agentto resolve npm audit security vulnerability (#7027)@remix-run/[email protected]v1.19.1Compare Source
Patch Changes
@remix-run/[email protected]v1.19.0Compare Source
Minor Changes
improved networking options for
v2_dev(#6724)deprecate the
--schemeand--hostoptions and replace them with theREMIX_DEV_ORIGINenvironment variableOutput esbuild metafiles for bundle analysis (#6772)
Written to server build directory (
build/by default):metafile.css.jsonmetafile.js.json(browser JS)metafile.server.json(server JS)Metafiles can be uploaded to https://esbuild.github.io/analyze/ for analysis.
Add
serverNodeBuiltinsPolyfillconfig option. Inremix.config.jsyou can now disable polyfills of Node.js built-in modules for non-Node.js server platforms, or opt into a subset of polyfills. (#6814, #6859, #6877)Patch Changes
ignore missing react-dom/client for react 17 (#6725)
Warn if not using
v2_dev(#6818)Also, rename
--no-restartto--manualto match intention and documentation.--no-restartremains an alias for--manualin v1 for backwards compatibility.ignore errors when killing already dead processes (#6773)
Always rewrite css-derived assets during builds (#6837)
fix sourcemaps for
v2_dev(#6762)Do not clear screen when dev server starts (#6719)
On some terminal emulators, "clearing" only scrolls the next line to the
top. on others, it erases the scrollback.
Instead, let users call
clearthemselves (clear && remix dev) ifthey want to clear.
Updated dependencies:
@remix-run/[email protected]v1.18.1Compare Source
Patch Changes
react-dom/clientfor React 17 (#6725)@remix-run/[email protected]v1.18.0Compare Source
Minor Changes
remix buildandremix dev(#6596)Patch Changes
remix dev -c: kill all descendant processes of specified command when restarting (#6663)Architect (AWS Lambda)->Architectin thecreate-remixCLI to avoid confusion for other methods of deploying to AWS (i.e., SST) (#6484)esbuild-plugins-node-modules-polyfillto 1.0.16 to ensure that the plugin is cached (#6652)@remix-run/[email protected]v1.17.1Compare Source
Patch Changes
esbuild-plugin-polyfill-nodewithesbuild-plugins-node-modules-polyfill(#6562)@remix-run/css-bundleis detected (#6535)@remix-run/[email protected]v1.17.0Compare Source
Minor Changes
built-in tls support (#6483)
New options:
--tls-key/tlsKey: TLS key--tls-cert/tlsCert: TLS CertificateIf both TLS options are set,
schemedefaults tohttpsv1.16.1Compare Source
Patch Changes
loaderchange detection for HDR (#6299)PATHenvvar so that it works cross-platform (e.g. Windows) (#6310).css.ts/.css.jsfiles with Vanilla Extract if@vanilla-extract/cssis installed (#6345)tsconfig.jsonwhen running usinggetConfig(remix dev,remix routes,remix build, etc) (#6156)@remix-run/[email protected]v1.16.0Compare 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_vanillaExtractandfuture.unstable_cssSideEffectImportsoptions inremix.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
postcssoption inremix.config.js. As a result, thefuture.unstable_postcssoption has also been deprecated. (#5960)The
postcssoption isfalseby default, but when set totruewill enable processing of all CSS files using PostCSS ifpostcss.config.jsis 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:
After you've enabled the new
postcssoption, you can delete the processed files fromapp/stylesfolder and move your source files fromstylestoapp/styles:You should then remove
app/stylesfrom your.gitignorefile since it now contains source files rather than processed output.You can then update your
package.jsonscripts to remove any usage ofpostcsssince 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
tailwindoption inremix.config.js. As a result, thefuture.unstable_tailwindoption has also been deprecated. (#5960)The
tailwindoption isfalseby default, but when set totruewill enable built-in support for Tailwind functions and directives in your CSS files iftailwindcssis 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.cssfile, you should move it toapp/tailwind.css.Otherwise, if you don't already have an
app/tailwind.cssfile, you should create one with the following contents:You should then remove
/app/tailwind.cssfrom your.gitignorefile since it now contains source code rather than processed output.You can then update your
package.jsonscripts to remove any usage oftailwindcsssince 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" } // ... }The Remix dev server spins up your app server as a managed subprocess. (#6133)
This keeps your development environment as close to production as possible.
It also means that the Remix dev server is compatible with any app server.
By default, the dev server will use the Remix App Server, but you opt to use your own app server by specifying the command to run it via the
-c/--commandflag:The dev server will:
NODE_ENV=developmentand warn you if it was previously set to something elseApp server coordination
In order to manage your app server, the dev server needs to be told what server build is currently being used by your app server.
This works by having the app server send a "I'm ready!" message with the Remix server build hash as the payload.
This is handled automatically in Remix App Server and is set up for you via calls to
broadcastDevReadyorlogDevReadyin the official Remix templates.If you are not using Remix App Server and your server doesn't call
broadcastDevReady, you'll need to call it in your app server after it is up and running.For example, in an Express server:
Options
Options priority order is: 1. flags, 2. config, 3. defaults.
-c/--commandcommandremix-serve <server build path>--http-schemehttpSchemehttp--http-hosthttpHostlocalhost--http-porthttpPort--websocket-portwebsocketPort--no-restartrestart: falserestart: true🚨 The
--http-*flags are only used for internal dev server <-> app server communication.Your app will run on your app server's normal URL.
To set
unstable_devconfiguration, replaceunstable_dev: truewithunstable_dev: { <options> }.For example, to set the HTTP(S) port statically:
SSL and custom hosts
You should only need to use the
--http-*flags and--websocket-portflag if you need fine-grain control of what scheme/host/port for the dev server.If you are setting up SSL or Docker networking, these are the flags you'll want to use.
🚨 Remix will not set up SSL and custom host for you.
The
--http-schemeand--http-hostflag are for you to tell Remix how you've set things up.It is your task to set up SSL certificates and host files if you want those features.
--no-restartandrequirecache purgingIf you want to manage server changes yourself, you can use the
--no-restartflag to tell the dev server to refrain from restarting your app server when builds succeed:remix dev -c "node ./server.js" --no-restartFor example, you could purge the
requirecache of your app server to keep it running while picking up server changes.If you do so, you should watch the server build path (
build/by default) for changes and only purge therequirecache when changes are detected.🚨 If you use
--no-restart, it is your responsibility to callbroadcastDevReadywhen your app server has picked up server changes.For example, with
chokidar:Patch Changes
url()rules when using CSS Modules, Vanilla Extract and CSS side-effect imports (#5788)devDependencieswhen running remix dev (#6228)serverModuleFormatdefault change (#6154)bareImportsplugin. (#6181)logDevReadyas replacement for platforms that can't initialize async I/O outside of the request response lifecycle. (#6204)@remix-run/[email protected]v1.15.0Compare Source
Minor Changes
Added deprecation warning for
v2_normalizeFormMethod(#5863)Added a new
future.v2_normalizeFormMethodflag to normalize the exposeduseNavigation().formMethodas an uppercase HTTP method to align with the previoususeTransitionbehavior as well as thefetch()behavior of normalizing to uppercase HTTP methods. (#5815)future.v2_normalizeFormMethod === false,useNavigation().formMethodis lowercaseuseFetcher().formMethodis uppercasefuture.v2_normalizeFormMethod === true:useNavigation().formMethodis uppercaseuseFetcher().formMethodis uppercaseAdded deprecation warning for
browserBuildDirectoryinremix.config(#5702)Added deprecation warning for
CatchBoundaryin favor offuture.v2_errorBoundary(#5718)Added experimental support for Vanilla Extract caching, which can be enabled by setting
future.unstable_vanillaExtract: { cache: true }inremix.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 leastv1.10.0of@vanilla-extract/css. (#5735)Added deprecation warning for
serverBuildDirectoryinremix.config(#5704)Patch Changes
@remix-run/css-bundleare picked up during HMR (#5823)path.resolvewhen re-exportingentry.client(#5707).mjsand.cjsextensions when detecting CSS side-effect imports (#5564)react-refresh(#5637)future.v2_meta(#5878)@remix-run/[email protected]v1.14.3Compare Source
Patch Changes
@remix-run/[email protected]v1.14.2Compare Source
Patch Changes
@remix-run/[email protected]v1.14.1Compare Source
Patch Changes
*.icofiles (#5430)moduleResolution: "bundler"in tsconfig.json (#5576)serverBuildTargetdeprecation warning (#5624)@remix-run/[email protected]v1.14.0Compare Source
Minor Changes
unstable_devfuture flag to be enabledimport.meta.hotAPI exposed yetentry.clientandentry.serverfiles optional (#4600)Patch Changes
Fixes flat route inconsistencies where
route.{ext}wasn't always being treated likeindex.{ext}when used in a folder (#5459)Route conflict no longer throw errors and instead display a helpful warning that we're using the first one we found.
Log errors thrown during initial build in development. (#5441)
Sync
FutureConfiginterface between packages (#5398)Add file loader for importing
.csvfiles (#3920)Updated dependencies:
@remix-run/[email protected]v1.13.0Compare Source
Minor Changes
serverBuildTargetinremix.config. See the release notes for v1.13.0 for more information. (#5354)future.unstable_postcssfeature flag (#5229)future.unstable_tailwindfeature flag (#5229)Patch Changes
@remix-run/[email protected]v1.12.0Compare Source
Minor Changes
unstable_devflag. See the release notes for a full description. (#5133)Patch Changes
v2_routeConventionon Windows so that new and renamed files are properly included (#5266)remix watchandremix dev(#5228)@remix-run/[email protected]remix-run/remix (@remix-run/eslint-config)
v1.19.3Compare 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.2Compare 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.1Compare 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.0Compare 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.0.
v1.18.1Compare 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.18.1.
v1.18.0Compare 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.18.0.
v1.17.1Compare 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.17.1.
v1.17.0Compare Source
Patch Changes
Add
HeadersArgstype to be consistent with loaders/actions/meta and allows for using afunctiondeclaration in addition to an arrow function expression (#6247)v1.16.1Compare Source
Patch Changes
v1.16.0Compare Source
Minor Changes
@remix-run/eslint-config/jestESLint config (#5697)v1.15.0Compare Source
Patch Changes
peerDependencyto allow for^5.0.0(6b6ee66a2)v1.14.3Compare 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.2Compare 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.1Compare 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.1.
v1.14.0Compare Source
No significant changes to this package were made in this release. [See the releases page on GitHub](htt
Configuration
📅 Schedule: Branch creation - "before 6am,every weekend" in timezone Europe/Oslo, 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.
This PR was generated by Mend Renovate. View the repository job log.