Open
Conversation
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
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.
This pull request introduces a new Expo example app demonstrating Varlock integration, along with updates to dependencies across several example projects to use the latest Varlock and integration packages. The Expo example showcases features like sensitive value protection, Babel and Metro integration, and console log redaction. Additionally, a configuration change improves compatibility with Expo when using pnpm.
New Expo Example Integration
examples/expo, including configuration files, server routes, client demo screen, Babel and Metro integration, and documentation. The app demonstrates inlining non-sensitive env values, server-only access to sensitive values, and log redaction features. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]Dependency Updates
varlockand related integration packages (@varlock/astro-integration,@varlock/vite-integration,@varlock/nextjs-integration) to their latest versions across all example projects for improved compatibility and features. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]Configuration Improvements
.npmrcsettingnode-linker=hoistedto improve Expo compatibility with pnpm, as recommended in Expo monorepo documentation.Documentation
README.mdfor the Expo example, explaining the integration approach, features, and setup instructions.Sensitive Environment Variable Handling
.env.schemain the Expo example to markSECRET_KEYas sensitive, ensuring it is only accessible in server routes and protected from client exposure.