Potential fixes for dynamic Kener base path #313
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.
Hey @rajnandan1, what about this approach for keeping
KENER_BASE_PATHdynamic on runtime? Will need you to pull this fork and help with some testing as there are many changes I made in this one. Essentially, here is the approach I tried taking...I defined
BASE_PATHinconstants.jsand passed it throughload()in.server.jsfiles. This ensures that:KENER_BASE_PATHis evaluated only on the server, preventing it from being baked into the client-side build.load(), avoiding direct exposure of environment variables.Process:
KENER_BASE_PATHenvironment variable server-side.BASE_PATHvariable (to be used by other server-side components).BASE_PATHfromconstants.jsacross various.server.jsfilesbasePathvariable viaload()functionsbasePathvariable is passed viadataprop to.sveltetemplate files