Skip to content

Configurable global PATH lookup for TypeScript LSP#5

Closed
bnwa wants to merge 2 commits intochojs23:mainfrom
bnwa:feat/configure-global-path-lookup-name
Closed

Configurable global PATH lookup for TypeScript LSP#5
bnwa wants to merge 2 commits intochojs23:mainfrom
bnwa:feat/configure-global-path-lookup-name

Conversation

@bnwa
Copy link
Copy Markdown

@bnwa bnwa commented Jan 4, 2026

Addresses issue identified in #1 when node_modules not installed

Copy link
Copy Markdown
Owner

@chojs23 chojs23 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you update README for tsserver_cmd ?

@bnwa bnwa closed this Jan 10, 2026
@bnwa
Copy link
Copy Markdown
Author

bnwa commented Jan 10, 2026

@chojs23 I went ahead and closed the PR because I realized it was based on a misinterpretation of your design intent for ts-bridge. Correct me if I'm wrong, but you intend to solely interface with tsserver and not other wrappers such as ts_ls as I mentioned in the issue. If that is correct, then the case I thought I was solving for here should be resolved by simply maintaining a global TypeScript installation to lookup on the PATH.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants