Skip to content

Feat/client js router v7 ssr sample app - #325

Open
BenjaminTruong-okta wants to merge 4 commits into
feat/client-js-opt-in-supportfrom
feat/client-js-router-v7-ssr-sample-app
Open

Feat/client js router v7 ssr sample app#325
BenjaminTruong-okta wants to merge 4 commits into
feat/client-js-opt-in-supportfrom
feat/client-js-router-v7-ssr-sample-app

Conversation

@BenjaminTruong-okta

Copy link
Copy Markdown
Contributor

PR Checklist

Please check if your PR fulfills the following requirements:

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Adding Tests
  • Build related changes
  • CI related changes
  • Documentation changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Reviewers

Demonstrates @okta/okta-react/client-js loaders in framework-mode
SSR. Requires a lazy, memoized auth singleton since @okta/spa-platform's
barrel export touches the browser-only `location` global at module
load time, which crashes if evaluated server-side; the SSR entry needs
renderToPipeableStream (not renderToString) since clientLoader.hydrate
routes render inside a Suspense boundary.
@BenjaminTruong-okta
BenjaminTruong-okta changed the base branch from master to feat/client-js-opt-in-support August 27, 2026 20:02
"type": "module" avoids Node's ESM auto-detection warning (and
outright failure on older Node versions) when running the built
server bundle. .env.development was dead - this app's env vars come
from @okta/env in vite.config.js, not Vite's .env.* convention.
…lines

The README pointed to the root README/CONTRIBUTING for the testenv
file format, but neither documents it.
@BenjaminTruong-okta
BenjaminTruong-okta marked this pull request as ready for review August 27, 2026 22:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant