Jugurtha/use next runtime env #1904
Merged
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
added 3 commits
November 26, 2024 15:26
…eNationale/adresse.data.gouv.fr into jugurtha/use_next_runtime_env
nkokla
approved these changes
Nov 27, 2024
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.
Amélioration de la gestion des variables d'environnement avec next-runtime-env
Actuellement, avec process.env, seules les variables définies lors du build sont accessibles. Les variables côté client, non déclarées au moment du build, ne sont jamais récupérées.
Cette PR introduit l'utilisation de next-runtime-env, qui permet de charger dynamiquement les variables d'environnement au runtime, à la fois côté serveur et client. Cela offre plus de flexibilité et résout les limitations actuelles.