iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A contributor reports that Bazable’s CLI crashed on startup after its language-server feature imported vscode-languageserver/node.js. Because the import was loaded as the CLI booted, even bazable --version failed. The contributor says changing the specifier to vscode-languageserver/node fixed the startup failure.
What Bazable does—and what failed
Bazable is presented in its repository README as a Git-native API contract management CLI. Its listed functions include extracting and inspecting API contracts, mock testing, type generation, backend scaffolding, and CI workflow generation. The README gives npm install -g bazable-api as the installation command.
The reported incident followed the addition of bazable lsp, a command for the Language Server Protocol feature. According to the contributor’s account of the bug, the language-server import was loaded during CLI startup, not only when users invoked the LSP command. That made the failure affect ordinary CLI commands too.
Why the CLI crashed at startup
The contributor reports this exception:
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './node.js' is not defined by "exports"
#1 Best Overall
The error indicates that the requested package subpath, ./node.js, was not available through the package’s declared exports. In this incident, the import named vscode-languageserver/node.js. Since that import was evaluated while the CLI booted, the reported impact was broader than a failed language-server session: even bazable --version could not run.
This explanation is specific to the contributor’s report; the repository README provides project and package context but does not independently document the crash or verify its cause.
The reported one-line fix
The author says the import was changed from vscode-languageserver/node.js to vscode-languageserver/node. In the author’s account, removing the .js suffix resolved the startup failure and allowed the language server to start.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems| Import specifier | Reported outcome |
|---|---|
vscode-languageserver/node.js |
Startup error: package subpath ./node.js was not defined by exports. |
vscode-languageserver/node |
The contributor says this corrected the failure. |
This is the fix reported for this particular dependency and incident, not a general rule for every package import. The source does not provide a broader comparison of package export behavior.
What changed for the LSP command
The contributor also reports adding --stdio so the LSP command could be run manually when an editor did not supply connection arguments. That change addresses how the language server can be launched; it is distinct from the import correction that reportedly restored CLI startup.
Release attribution and verification
The contributor says the changes were published in Bazable v1.2.0. The inspected repository README confirms the project description and the bazable-api installation command, but it does not expose a release listing or changelog entry confirming that version claim. Treat v1.2.0 as the author’s attribution rather than an independently verified release detail.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →
