A contributor’s account traces Bazable’s startup crash to one import: vscode-languageserver/node.js. The reported repair was to remove the .js suffix and use vscode-languageserver/node. Because the import loaded as the CLI started, even bazable --version reportedly failed before the command could run.
What Bazable does
Bazable is presented in its GitHub repository as a Git-native API contract management CLI. Its README describes extracting and inspecting API contracts, mock testing, type generation, backend scaffolding, and CI workflow generation. It gives npm install -g bazable-api as the installation command.
As an Amazon Associate I earn from qualifying purchases.
This context explains why a startup problem in the CLI mattered beyond the new language-server feature: if the affected import is loaded while the command-line program boots, ordinary commands can be blocked before Bazable gets to process them.
Why the CLI reportedly crashed
In a DEV Community post, contributor Agentfield247 says the problem appeared after the bazable lsp feature was added. The language-server code imported vscode-languageserver/node.js, and startup produced this exception:
#1 Best Overall
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './node.js' is not defined by "exports"The post says the LSP import was loaded as the CLI booted. As a result, the failure was not limited to launching the language-server command: the author reports that even bazable --version failed. This is the contributor’s account; the repository README establishes Bazable’s project and package context but does not independently confirm the incident.
The one-line import change
The author says the repair was to change the import specifier from vscode-languageserver/node.js to vscode-languageserver/node. In the post’s words: “The fix was to change the import from vscode-languageserver/node.js to vscode-languageserver/node.” The author reports that this restored CLI operation and allowed the language server to start.
| Import specifier | Reported outcome |
|---|---|
vscode-languageserver/node.js |
The contributor says this triggered the package-subpath export error during CLI startup. |
vscode-languageserver/node |
The contributor says removing .js fixed the startup failure. |
This account supports the specific correction for this incident; it does not establish a general rule for every package or import path. When diagnosing a similar exception, inspect the exact subpath named in the error and the package’s supported exports rather than assuming that adding or removing a file extension is always correct.
Running the language server manually
The contributor also reports adding --stdio so the LSP command could be run manually when an editor did not provide connection arguments. This is separate from the import correction: the reported import change addressed the CLI startup crash, while the flag addressed how the language server could be invoked in that circumstance.
What is known about the release
The DEV post attributes the changes to Bazable v1.2.0. The inspected repository README confirms the package installation command and project features, but does not independently verify that release-specific claim. Treat the version attribution as the author’s report rather than a separately confirmed release record.
Quick Recap
Best Value
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.
