claude-code - 💡(How to fix) Fix [BUG] Claude Code on the web session blocks registry.tiptap.dev — private npm registries fail with host_not_allowed [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#54897Fetched 2026-05-01 05:51:34
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×5commented ×1

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

In a Claude Code on the web session (https://claude.ai/code), npm install fails when a workspace depends on packages hosted on a private npm registry (in our case registry.tiptap.dev for @tiptap-pro/*). The sandbox's policy blocks the host before the request reaches the registry.

What Should Happen?

In Claude Code web session, we should be allowed to install from private npm registry. In this case, tiptap pro requires installing from private npm registry https://tiptap.dev/docs/guides/pro-extensions

Error Messages/Logs

Steps to Reproduce

Start a Claude Code on the web session in a repo whose package.json depends on @tiptap-pro/* packages. The repo's install command configures the registry and auth token: npm config set "@tiptap-pro:registry" https://registry.tiptap.dev/ npm config set "//registry.tiptap.dev/:_authToken" "$TIPTAP_REGISTRY_TOKEN" npm ci TIPTAP_REGISTRY_TOKEN is present in the env. Run npm install (or npm run build, which depends on it).

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.123

Platform

Anthropic API

Operating System

Other

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue can be resolved by configuring the Claude Code sandbox to allow requests to the private npm registry.

Guidance

  • Verify that the TIPTAP_REGISTRY_TOKEN environment variable is correctly set and passed to the npm config commands.
  • Check the Claude Code documentation for any specific configuration options or settings that may be required to allow requests to private npm registries.
  • Consider modifying the npm config commands to use a different authentication method, such as a .npmrc file, to see if that resolves the issue.
  • Test the npm install command with the --verbose flag to get more detailed output and potentially identify the exact point of failure.

Example

No code snippet is provided as the issue is more related to configuration and environment setup.

Notes

The issue may be specific to the Claude Code Opus model or the Anthropic API platform, and further investigation may be required to determine the root cause.

Recommendation

Apply workaround: Configure the Claude Code sandbox to allow requests to the private npm registry, as this is the most likely cause of the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING