Merge branch 'dev' into markdalgleish/browser-node-polyfills

.changeset/beige-pugs-drive.md

@@ -0,0 +1,8 @@
+---
+"@remix-run/serve": major
+---
+
+`remix-serve` picks an open port if 3000 is taken
+
+- 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)

.changeset/get-dependencies-from-esm-without-main.md

@@ -0,0 +1,5 @@
+---
+"@remix-run/dev": patch
+---
+
+Update `getDependenciesToBundle` to handle ESM packages without main exports. Note that these packages must expose `package.json` in their `exports` field so that their path can be resolved.

.changeset/light-rivers-tell.md

@@ -0,0 +1,7 @@
+---
+"@remix-run/react": patch
+"@remix-run/server-runtime": patch
+"@remix-run/testing": patch
+---
+
+Bump router to 1.9.0/6.16.0 prereleases

.github/workflows/shared-build.yml

@@ -11,9 +11,6 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-      - name: 🛑 Cancel Previous Runs
-        uses: styfle/cancel-workflow-action@0.11.0
-
       - name: ⬇️ Checkout repo
         uses: actions/checkout@v3
 

.github/workflows/shared-test-integration.yml

@@ -34,9 +34,6 @@ jobs:
 
     runs-on: ${{ inputs.os }}
     steps:
-      - name: 🛑 Cancel Previous Runs
-        uses: styfle/cancel-workflow-action@0.11.0
-
       - name: ⬇️ Checkout repo
         uses: actions/checkout@v3
 

.github/workflows/shared-test-unit.yml

@@ -26,9 +26,6 @@ jobs:
         node: ${{ fromJSON(inputs.node_version) }}
     runs-on: ${{ inputs.os }}
     steps:
-      - name: 🛑 Cancel Previous Runs
-        uses: styfle/cancel-workflow-action@0.11.0
-
       - name: ⬇️ Checkout repo
         uses: actions/checkout@v3
 

.github/workflows/test-full.yml

@@ -1,12 +1,16 @@
 name: Branch
 
-# main/dev branches will get the full run across all OS/browsers
+# main/dev/release-* branches and nightly tags will get the full run across
+# all OS/browsers for multiple node versions
 
 on:
   push:
     branches:
       - main
       - dev
+      - release-*
+    tags:
+      - "v0.0.0-nightly-*"
     paths-ignore:
       - "docs/**"
       - "scripts/**"
@@ -25,23 +29,23 @@ jobs:
     uses: ./.github/workflows/shared-test-unit.yml
     with:
       os: "ubuntu-latest"
-      node_version: '["latest"]'
+      node_version: "[18, 20]"
 
   unit-windows:
     name: "🧪 Unit Test"
     if: github.repository == 'remix-run/remix'
     uses: ./.github/workflows/shared-test-unit.yml
     with:
       os: "windows-latest"
-      node_version: '["latest"]'
+      node_version: "[18, 20]"
 
   integration-ubuntu:
     name: "👀 Integration Test"
     if: github.repository == 'remix-run/remix'
     uses: ./.github/workflows/shared-test-integration.yml
     with:
       os: "ubuntu-latest"
-      node_version: '["latest"]'
+      node_version: "[18, 20]"
       browser: '["chromium", "firefox"]'
 
   integration-windows:
@@ -50,7 +54,7 @@ jobs:
     uses: ./.github/workflows/shared-test-integration.yml
     with:
       os: "windows-latest"
-      node_version: '["latest"]'
+      node_version: "[18, 20]"
       browser: '["msedge"]'
 
   integration-macos:
@@ -59,5 +63,5 @@ jobs:
     uses: ./.github/workflows/shared-test-integration.yml
     with:
       os: "macos-latest"
-      node_version: '["latest"]'
+      node_version: "[18, 20]"
       browser: '["webkit"]'

.github/workflows/test-pr-ubuntu.yml

@@ -10,6 +10,10 @@ on:
       - "contributors.yml"
       - "**/*.md"
 
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
 jobs:
   build:
     name: "⚙️ Build"

.github/workflows/test-pr-windows-macos.yml

@@ -9,6 +9,10 @@ on:
       - "packages/remix-dev/**"
       - "!**/*.md"
 
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
 jobs:
   unit-windows:
     name: "🧪 Unit Test"

docs/utils/sessions.md

@@ -210,6 +210,11 @@ console.log(isSession(session));
 
 Remix makes it easy to store sessions in your own database if needed. The `createSessionStorage()` API requires a `cookie` (or options for creating a cookie, see [cookies][cookies]) and a set of create, read, update, and delete (CRUD) methods for managing the session data. The cookie is used to persist the session ID.
 
+- `createData` will be called from `commitSession` on the initial session creation when no session ID exists in the cookie
+- `readData` will be called from `getSession` when a session ID exists in the cookie
+- `updateData` will be called from `commitSession` when a session ID already exists in the cookie
+- `deleteData` is called from `destorySession`
+
 The following example shows how you could do this using a generic database client:
 
 ```ts