Conversation
Packaging dereferences the symlinks npm creates in node_modules/.bin, so the shim body ends up in .bin/ where its own relative require resolves against node_modules/ - vtsls died with "Cannot find module '../dist/main.js'". vscode-json-language-server broke the same way. Resolve the bin entry the bundled package itself declares and run it on our node runtime instead of going through the .bin shim. This is also correct on Windows, where .bin/<command> is an sh script that cannot be spawned directly.
|
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.



Packaging dereferences the symlinks npm creates in node_modules/.bin, so the shim body ends up in .bin/ where its own relative require resolves against node_modules/ - vtsls died with "Cannot find module '../dist/main.js'". vscode-json-language-server broke the same way.
Resolve the bin entry the bundled package itself declares and run it on our node runtime instead of going through the .bin shim. This is also correct on Windows, where .bin/ is an sh script that cannot be spawned directly.