JupyterLab cannot determine its build status without Node.js
Could not determine jupyterlab build status without nodejsShort answer
JupyterLab itself runs without Node.js, but source extensions need Node.js to rebuild it. If Node.js, npm or jlpm are missing from the environment JupyterLab runs in, install Node.js there, or replace source extensions with prebuilt ones, which need no rebuild.
Fix it fast
1Find out which cause you have
Check which of the three commands JupyterLab's extension tooling relies on work in the same terminal environment you start JupyterLab from.
node --version npm --version jlpm --version2Match what you see, then jump to its fix
- 1
node --version says command not foundNode.js is not installed in the environmentFix - 2
node works in another terminal or environment, but npm --version or jlpm --version fails hereNode.js exists, but npm or jlpm do not work in this environmentFix - 3
jupyter labextension list shows extensions that were installed with jupyter labextension installA source extension is installed where a prebuilt one would doFix
- 1
What does the error look like?
Could not determine jupyterlab build status without nodejs
Cause 1 of 3
Node.js is not installed in the environment
1Check
The extensions guide says source extensions require Node.js to rebuild JupyterLab, and that installing one means installing Node.js and rebuilding. Installing jupyterlab alone does not add it.
which node || echo "node missing"
jupyter labextension list2Fix
Install Node.js into the same conda environment (or from your system package manager or nodejs.org), then rebuild if you added a source extension.
conda install -c conda-forge nodejs
jupyter lab build3Verify
All three version commands print a version, and JupyterLab starts without the message.
node --version
jlpm --versionConfirmed by jupyterlab.readthedocs.io
Cause 2 of 3
Node.js exists, but npm or jlpm do not work in this environment
1Check
The installation guide says many Jupyter extensions need working npm and jlpm commands (jlpm is the alias for yarn). A Node.js installed in another conda environment, or a shell where the activate step was skipped, does not help.
jupyter --paths
which jlpm2Fix
Activate the environment that contains JupyterLab, and install Node.js into that environment.
conda activate my-env
conda install -c conda-forge nodejs3Verify
Both npm --version and jlpm --version print a version.
npm --version
jlpm --versionConfirmed by jupyterlab.readthedocs.io
Cause 3 of 3
A source extension is installed where a prebuilt one would do
1Check
Prebuilt extensions install with pip or conda and do not require rebuilding JupyterLab JavaScript files, so they need no Node.js.
jupyter labextension list2Fix
Uninstall the source extension and install the project's prebuilt package with pip or conda instead; the extension's own page shows the package name.
jupyter labextension uninstall my-extension
pip install my-extension-package3Verify
The extension is listed and works without a rebuild.
jupyter labextension listConfirmed by jupyterlab.readthedocs.io
How do I stop it coming back?
- Prefer prebuilt extensions installed with pip or conda.
- Install Node.js with conda in the same environment as JupyterLab when you need source extensions.
- Use the --no-build flag while installing several source extensions, then run jupyter lab build once.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Databases
Node.js in Docker Compose cannot find mysql2/promise
The app works on the host but fails after docker compose up
mysql2/promise is a path inside the mysql2 package.
2 causes, each with a fixDatabases
Elasticsearch rejects requests with circuit_breaking_exception: Data too large
circuit_breaking_exception with a reason that contains Data too large
A circuit_breaking_exception with 'Data too large' means Elasticsearch refused work to protect a node's JVM heap.
3 causes, each with a fixDatabases
Mongoose cannot sign in to MongoDB Atlas: bad auth, authentication failed
MongoError: bad auth Authentication failed.
Authentication failed means the server rejected the user in your connection string.
3 causes, each with a fixDatabases
MongoDB says duplicate key, but the value is null
MongoServerError: E11000 duplicate key error
A unique index in MongoDB stores a missing field as null, and only one null entry is allowed.
3 causes, each with a fixDatabases
mongodb-memory-server will not start under Jest or in Docker
NoSystemBinaryFoundError
When mongodb-memory-server fails to start, the real reason is hidden behind a generic message.
4 causes, each with a fixDatabases
updateOne() runs without an error but the document does not change
{ "acknowledged" : true, "matchedCount" : 0, "modifiedCount" : 0 }
updateOne() reports what it did in its result.
4 causes, each with a fix