-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update remix monorepo to v1.19.3 #111
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/remix-monorepo
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
May 29, 2023 15:55
42fdaeb
to
7eec476
Compare
renovate
bot
changed the title
Update remix monorepo to v1.14.3
Update remix monorepo to v1.16.1
May 29, 2023
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
June 8, 2023 23:57
7eec476
to
6fc42ab
Compare
renovate
bot
changed the title
Update remix monorepo to v1.16.1
Update remix monorepo to v1.17.0
Jun 8, 2023
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
June 17, 2023 05:26
6fc42ab
to
59ee550
Compare
renovate
bot
changed the title
Update remix monorepo to v1.17.0
Update remix monorepo to v1.17.1
Jun 17, 2023
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
June 27, 2023 02:19
59ee550
to
7abbb83
Compare
renovate
bot
changed the title
Update remix monorepo to v1.17.1
Update remix monorepo to v1.18.0
Jun 27, 2023
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
July 1, 2023 02:10
7abbb83
to
656d778
Compare
renovate
bot
changed the title
Update remix monorepo to v1.18.0
Update remix monorepo to v1.18.1
Jul 1, 2023
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
July 20, 2023 20:47
656d778
to
4be4772
Compare
renovate
bot
changed the title
Update remix monorepo to v1.18.1
Update remix monorepo to v1.19.0
Jul 20, 2023
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
July 22, 2023 05:57
4be4772
to
c45a2ab
Compare
renovate
bot
changed the title
Update remix monorepo to v1.19.0
Update remix monorepo to v1.19.1
Jul 22, 2023
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
August 4, 2023 17:31
c45a2ab
to
ac3fc0a
Compare
renovate
bot
changed the title
Update remix monorepo to v1.19.1
Update remix monorepo to v1.19.2
Aug 4, 2023
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
August 10, 2023 23:41
ac3fc0a
to
a5eeb65
Compare
renovate
bot
changed the title
Update remix monorepo to v1.19.2
Update remix monorepo to v1.19.3
Aug 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.0.6
->1.19.3
1.1.1
->1.19.3
1.0.6
->1.19.3
1.1.1
->1.19.3
1.1.1
->1.19.3
Release Notes
remix-run/remix (@remix-run/dev)
v1.19.3
Compare Source
Patch Changes
devServerBroadcastDelay
anddevServerPort
config options (#7064)@remix-run/server-runtime@1.19.3
v1.19.2
Compare Source
Patch Changes
proxy-agent
to resolve npm audit security vulnerability (#7027)@remix-run/server-runtime@1.19.2
v1.19.1
Compare Source
Patch Changes
@remix-run/server-runtime@1.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 theREMIX_DEV_ORIGIN
environment variableOutput esbuild metafiles for bundle analysis (#6772)
Written to server build directory (
build/
by default):metafile.css.json
metafile.js.json
(browser JS)metafile.server.json
(server JS)Metafiles can be uploaded to https://esbuild.github.io/analyze/ for analysis.
Add
serverNodeBuiltinsPolyfill
config option. Inremix.config.js
you can now disable polyfills of Node.js built-in modules for non-Node.js server platforms, or opt into a subset of polyfills. (#6814, #6859, #6877)Patch Changes
ignore missing react-dom/client for react 17 (#6725)
Warn if not using
v2_dev
(#6818)Also, rename
--no-restart
to--manual
to match intention and documentation.--no-restart
remains an alias for--manual
in v1 for backwards compatibility.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
clear
themselves (clear && remix dev
) ifthey want to clear.
Updated dependencies:
@remix-run/server-runtime@1.19.0
v1.18.1
Compare Source
Patch Changes
react-dom/client
for React 17 (#6725)@remix-run/server-runtime@1.18.1
v1.18.0
Compare Source
Minor Changes
remix build
andremix dev
(#6596)Patch Changes
remix dev -c
: kill all descendant processes of specified command when restarting (#6663)Architect (AWS Lambda)
->Architect
in thecreate-remix
CLI to avoid confusion for other methods of deploying to AWS (i.e., SST) (#6484)esbuild-plugins-node-modules-polyfill
to 1.0.16 to ensure that the plugin is cached (#6652)@remix-run/server-runtime@1.18.0
v1.17.1
Compare Source
Patch Changes
esbuild-plugin-polyfill-node
withesbuild-plugins-node-modules-polyfill
(#6562)@remix-run/css-bundle
is detected (#6535)@remix-run/server-runtime@1.17.1
v1.17.0
Compare 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,
scheme
defaults tohttps
v1.16.1
Compare Source
Patch Changes
loader
change detection for HDR (#6299)PATH
envvar so that it works cross-platform (e.g. Windows) (#6310).css.ts
/.css.js
files with Vanilla Extract if@vanilla-extract/css
is installed (#6345)tsconfig.json
when running usinggetConfig
(remix dev
,remix routes
,remix build
, etc) (#6156)@remix-run/server-runtime@1.16.1
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
andfuture.unstable_cssSideEffectImports
options 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
postcss
option inremix.config.js
. As a result, thefuture.unstable_postcss
option has also been deprecated. (#5960)The
postcss
option isfalse
by default, but when set totrue
will enable processing of all CSS files using PostCSS ifpostcss.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:
After you've enabled the new
postcss
option, you can delete the processed files fromapp/styles
folder and move your source files fromstyles
toapp/styles
: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 ofpostcss
since Remix handles this automatically. For example, if you had followed the original setup guide:Stabilize built-in Tailwind support via the new
tailwind
option inremix.config.js
. As a result, thefuture.unstable_tailwind
option has also been deprecated. (#5960)The
tailwind
option isfalse
by default, but when set totrue
will enable built-in support for Tailwind functions and directives in your CSS files iftailwindcss
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 toapp/tailwind.css
.Otherwise, if you don't already have an
app/tailwind.css
file, you should create one with the following contents: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 oftailwindcss
since Remix handles this automatically. For example, if you had followed the original setup guide: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
/--command
flag:The dev server will:
NODE_ENV=development
and 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
broadcastDevReady
orlogDevReady
in 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
/--command
command
remix-serve <server build path>
--http-scheme
httpScheme
http
--http-host
httpHost
localhost
--http-port
httpPort
--websocket-port
websocketPort
--no-restart
restart: false
restart: 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_dev
configuration, replaceunstable_dev: true
withunstable_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-port
flag 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-scheme
and--http-host
flag 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-restart
andrequire
cache purgingIf you want to manage server changes yourself, you can use the
--no-restart
flag to tell the dev server to refrain from restarting your app server when builds succeed:remix dev -c "node ./server.js" --no-restart
For example, you could purge the
require
cache 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 therequire
cache when changes are detected.🚨 If you use
--no-restart
, it is your responsibility to callbroadcastDevReady
when 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)devDependencies
when running remix dev (#6228)serverModuleFormat
default change (#6154)bareImports
plugin. (#6181)logDevReady
as replacement for platforms that can't initialize async I/O outside of the request response lifecycle. (#6204)@remix-run/server-runtime@1.16.0
v1.15.0
Compare Source
Minor Changes
Added deprecation warning for
v2_normalizeFormMethod
(#5863)Added a new
future.v2_normalizeFormMethod
flag to normalize the exposeduseNavigation().formMethod
as an uppercase HTTP method to align with the previoususeTransition
behavior as well as thefetch()
behavior of normalizing to uppercase HTTP methods. (#5815)future.v2_normalizeFormMethod === false
,useNavigation().formMethod
is lowercaseuseFetcher().formMethod
is uppercasefuture.v2_normalizeFormMethod === true
:useNavigation().formMethod
is uppercaseuseFetcher().formMethod
is uppercaseAdded deprecation warning for
browserBuildDirectory
inremix.config
(#5702)Added deprecation warning for
CatchBoundary
in 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.0
of@vanilla-extract/css
. (#5735)Added deprecation warning for
serverBuildDirectory
inremix.config
(#5704)Patch Changes
@remix-run/css-bundle
are picked up during HMR (#5823)path.resolve
when re-exportingentry.client
(#5707).mjs
and.cjs
extensions when detecting CSS side-effect imports (#5564)react-refresh
(#5637)future.v2_meta
(#5878)@remix-run/server-runtime@1.15.0
v1.14.3
Compare Source
Patch Changes
@remix-run/server-runtime@1.14.3
v1.14.2
Compare Source
Patch Changes
@remix-run/server-runtime@1.14.2
v1.14.1
Compare Source
Patch Changes
*.ico
files (#5430)moduleResolution: "bundler"
in tsconfig.json (#5576)serverBuildTarget
deprecation warning (#5624)@remix-run/server-runtime@1.14.1
v1.14.0
Compare Source
Minor Changes
unstable_dev
future flag to be enabledimport.meta.hot
API exposed yetentry.client
andentry.server
files 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
FutureConfig
interface between packages (#5398)Add file loader for importing
.csv
files (#3920)Updated dependencies:
@remix-run/server-runtime@1.14.0
v1.13.0
Compare Source
Minor Changes
serverBuildTarget
inremix.config
. See the release notes for v1.13.0 for more information. (#5354)future.unstable_postcss
feature flag (#5229)future.unstable_tailwind
feature flag (#5229)Patch Changes
@remix-run/server-runtime@1.13.0
v1.12.0
Compare Source
Minor Changes
unstable_dev
flag. See the release notes for a full description. (#5133)Patch Changes
v2_routeConvention
on Windows so that new and renamed files are properly included (#5266)remix watch
andremix dev
(#5228)@remix-run/server-runtime@1.12.0
v1.11.1
Compare Source
Patch Changes
v2_routeConvention
that preventedindex
modules from being recognized for route paths (195291a3d
)@remix-run/server-runtime@1.11.1
v1.11.0
Compare Source
Minor Changes
.fbx
,.glb
,.gltf
,.hdr
, and.mov
files (#5030)unstable_vanillaExtract
future flag. IMPORTANT: Features marked withunstable
are … unstable. While we're confident in the use cases they solve, the API and implementation may change without a major version bump. (#5040)unstable_cssSideEffectImports
future flag. IMPORTANT: Features marked withunstable
are … unstable. While we're confident in the use cases they solve, the API and implementation may change without a major version bump. (#4919)unstable_cssModules
future flag. IMPORTANT: Features marked withunstable
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
v2_routeConvention
future flag. (#4880)handle
in MDX frontmatter (#4865)@remix-run/server-runtime@1.11.0
v1.10.1
Compare Source
Patch Changes
@remix-run/server-runtime@1.10.1
v1.10.0
Compare Source
Patch Changes
create-remix
(#4891)@remix-run/server-runtime@1.10.0
v1.9.0
Compare Source
Minor Changes
Patch Changes
satisfies
keyword) (#4754)parentRouteId
lookup indefineConventionalRoutes
. (#4800).ts
->.js
conversion on Windows by using a relative unix-style path (#4718)@remix-run/server-runtime@1.9.0
v1.8.2
Compare Source
Patch Changes
@remix-run/server-runtime@1.8.2
@remix-run/serve@1.8.2
v1.8.1
Compare Source
Patch Changes
future
option to the@remix-run/dev/server-build
virtual module (#4771)@remix-run/serve@1.8.1
@remix-run/server-runtime@1.8.1
v1.8.0
Compare Source
Minor Changes
meta
API to handle arrays of tags instead of an object. For details, check out the RFC. (#4610)Patch Changes
remix
package is deprecated, and all 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. (#4661)@remix-run/server-runtime@1.8.0
@remix-run/serve@1.8.0
v1.7.6
Compare Source
Patch Changes
@remix-run/serve@1.7.6
@remix-run/server-runtime@1.7.6
Patch Changes
@remix-run/serve@1.7.6-pre.0
@remix-run/server-runtime@1.7.6-pre.0
v1.7.5
Compare Source
Patch Changes
@remix-run/serve@1.7.5
@remix-run/server-runtime@1.7.5
v1.7.4
Compare Source
Patch Changes
@remix-run/server-runtime@1.7.4
@remix-run/serve@1.7.4
v1.7.3
Compare Source
Patch Changes
create-remix
to use the new examples repository when using--template example/<name>
(#4208)moduleResolution
tonode
,node16
ornodenext
intsconfig.json
. (#4034)assetsBuildDirectory
(#3841)assetsBuildDirectory
. (#4130)@remix-run/serve@1.7.3
@remix-run/server-runtime@1.7.3
v1.7.2
Compare Source
Patch Changes
@remix-run/server-runtime@1.7.2
@remix-run/serve@1.7.2
v1.7.1
Compare Source
Patch Changes
@remix-run/server-runtime@1.7.1
@remix-run/serve@1.7.1
v1.7.0
Compare Source
Minor Changes
.gql
and.graphql
files as plain text (#3923).zip
and.avif
files as resource URLs (#3985)Patch Changes
@remix-run/server-runtime@1.7.0
@remix-run/serve@1.7.0
v1.6.8
Compare Source
Patch Changes
.mjs
and.cjs
file extensions forremix.config
(#3675).sql
files as text content (#3190)@remix-run/server-runtime@1.6.8
@remix-run/serve@1.6.8
v1.6.7
Compare Source
Patch Changes
@remix-run/serve@1.6.7
@remix-run/server-runtime@1.6.7
v1.6.6
Compare Source
Patch Changes
.mdx
files (#3801)@remix-run/dev/server-build
virtual module (#3743)@remix-run/serve@1.6.6
@remix-run/server-runtime@1.6.6
v1.6.5
Compare Source
Patch Changes
serverBareModulesPlugin
warning to use full import path (#3656)--port
flag increate-remix
(#3694)@remix-run/server-runtime
@remix-run/serve
v1.6.4
Compare Source
What's Changed
🐛 Bug fixes
@remix-run/serve
and@remix-run/dev
(#3602)💅 Enhancements
watchPaths
option forremix.config
. This allows you to define custom directories to watch while runningremix dev
(#3188).New Contributors
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
create-remix
CLI (#2804)💅 Enhancements
New Contributors
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
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. Runnpx @​remix-run/dev migrate
to initiate the codemod.See the release notes for v1.4.0 for more details on this change.
💅 Enhancements
@remix-run/react
(#2876)--port
flag to theremix dev
script (#3447)🐛 Bug fixes
sameSite: "lax"
to better align with browsers (#2388)imageSrcSet
/imageSizes
props forlinks
depending on the React version used (#2944)@remix-run/dev
(#3413)New Contributors
arc
call from README remix-run/remix#2332](https://redConfiguration
📅 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.
This PR was generated by Mend Renovate. View the repository job log.