-
Notifications
You must be signed in to change notification settings - Fork 134
Enable axa-fr react-oidc service worker #619
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
Open
jnfrati
wants to merge
1
commit into
main
Choose a base branch
from
feat/oidc-service-worker
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
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: netbirdio/dashboard
Length of output: 85
🏁 Script executed:
Repository: netbirdio/dashboard
Length of output: 1586
oidc-genscript has portability and reliability issues.The script has three concerns:
rmis unavailable on Windows, which breaks local dev builds for Windows contributors. Userimrafornode -einstead.-f,rmfails ifpublic/OidcTrustedDomains.jsdoesn't exist, halting the build pipeline. The file may not always be produced if upstream behavior changes.@axa-fr/oidc-clientis invoked directly from./node_modules/...but is undeclared. It's available only as a transitive dependency of@axa-fr/react-oidc. Changes to npm resolution, workspaces, or package managers could break the build. Add it explicitly todevDependenciesor invoke vianpxinstead.🛠️ Proposed fix
Add
rimraftodevDependenciesand explicitly declare@axa-fr/oidc-clientindevDependencies(pinned to the version bundled with@axa-fr/react-oidc@7.26.3).🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing the trusteddomains file should not be required.
E.g., when running locally, it would remove my local file when running the build :D
Maybe we can move the
public/local/OidcTrustedDomains.jsdirectly in public, then we can also remove thecopytrustedfrom the package.jsonThe docker build should take care of replacing the OidcTrustedDomains with the actual prod values (need to verify or adjust if not)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Length of output: 374
🏁 Script executed:
Length of output: 652
🏁 Script executed:
Length of output: 1035
🏁 Script executed:
Length of output: 98
🏁 Script executed:
Length of output: 2945
@heisbrotGreat point! I've verified thatdocker/init_react_envs.shalready handles theOidcTrustedDomains.jsreplacement at container startup viaenvsubston the.tmplfile, so Docker prod is covered ✓.Here's the full picture and the recommended approach to implement the suggestion:
How it works today:
copy-service-worker-files.mjsalways producespublic/OidcTrustedDomains.js(a generic version) — that's whyrmwas added.init_react_envs.shregeneratesOidcTrustedDomains.jsfromOidcTrustedDomains.js.tmplat runtime — no change needed there ✓.oidc-genis only called innpm run build, not innext dev— so local devs runningnext devare already unaffected by therm.Proposed implementation of heisbrot's suggestion:
public/local/OidcTrustedDomains.js→public/OidcTrustedDomains.js(committed with localhost values for local dev).&& rm public/OidcTrustedDomains.jsfromoidc-gen— Docker handles it at runtime anyway.public/OidcTrustedDomains.jsto.gitignore— this prevents git noise when someone runsnpm run buildlocally (which would overwrite it viacopy-service-worker-files.mjs) and avoids accidentally committing local dev values.copytrustedscript — no longer needed.The updated diff would look like: