Repository navigation
Conversation
Only a Vite dev server fell back to the dev Tangent or accepted a local Tangent address. A production build served from localhost, such as a locally run Docker image, refused both, so it could never open a project against a local Tangent. A loopback page isn't prompted for local network access, so it now behaves like the dev server. Deployed origins are unchanged. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
🎩 PreviewA preview build has been created at: |
Collaborator
Author
|
I found a better solution |
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.
Description
A production build served from
localhostor127.0.0.1now uses a local Tangent the way the Vite dev server does:http://localhost:5173, instead of showing "Tangent isn't configured".Both used to depend on
import.meta.env.DEV, so only the dev server got them. A production build running locally, such as a Docker image, couldn't open any project against a local Tangent. That build is the only way to test with config a deployment injects intoindex.html, such as team impersonation.Deployed origins are unchanged. The guard is there because Chrome prompts for local network access when a page reaches a more private address than its own. Nothing is more private than loopback, so a page served from loopback isn't prompted. A build served from a private IP or a
.localname still rejects local addresses, because Chrome would prompt there.Related Issue and Pull requests
masteron its own.Type of Change
Line Breakdown
Checklist
Screenshots (if applicable)
None. No UI changes.
Test Instructions
With a Tangent running on
localhost:5173, serve a production build fromlocalhost:http://localhost:5173. The project still opens.On any other host, both still show the same errors as before.
🤖 Generated with Claude Code