- #Jupyterlab debug install#
- #Jupyterlab debug windows 10#
- #Jupyterlab debug code#
- #Jupyterlab debug windows#
#Jupyterlab debug install#
I have written a read me to help me install plotly on jupyterlab. + 453 packages from 166 contributors and audited 454 packages in 30.7sīut another round of jupyter labextension install fails with the debug log saying again that it can’t find plotly.js (same as above). Npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\tj\package.json' npm WARN saveError ENOENT: no such file or directory, open 'C:\Users\tj\package.json' So it looks like it couldn’t find plotly.js. Info Visit for documentation about this command.Įrror: Couldn't find package required by on the "npm" registry.Īt C:\Users\tj\Anaconda3\share\jupyter\lab\staging\yarn.js:38113:17Īt step (C:\Users\tj\Anaconda3\share\jupyter\lab\staging\yarn.js:310:30)Īt C:\Users\tj\Anaconda3\share\jupyter\lab\staging\yarn.js:323:13Īt process._tickCallback (internal/process/next_tick.js:68:7) > node C:\Users\tj\Anaconda3\lib\site-packages\jupyterlab\staging\yarn.js install -non-interactiveĮrror Couldn't find package required by on the "npm" registry. It at least found the npm package but when trying to install it we had another issue: Node v10.13.0īuilding jupyterlab assets (build:prod:minimize) Looking at it’s debug log things made some progress. Then I ran jupyter labextension install again failed. From my Anaconda prompt I issued a npm config set registry Ĭommand. Has anyone successfully followed these steps and gotten plotly to work properly in a Jupyter Lab environment? It’s not clear to me where I’ve gone wrong. To select an environment, use the Python: Select Interpreter command from the Command Palette ( Ctrl+Shift+P ). If I go to the NPM site I can find the package jupyterlab-plotly which indicates it’s version 4.9.0. Debug a Jupyter Notebook Setting up your environment To work with Python in Jupyter Notebooks, you must activate an Anaconda environment in VS Code, or another Python environment in which you've installed the Jupyter package. So all indications to me are that it thinks it can’t find the nodejs package called jupyterlab-plotly. Npm ERR! A complete log of this run can be found in: Npm ERR! notarget a package version that doesn't exist. Npm ERR! notarget No matching version found for ERR! notarget In most cases you or one of your dependencies are requesting Npm WARN registry Using stale package data from due to a request error during revalidation. > C:\Users\tj\Anaconda3\npm.CMD pack WARN registry Unexpected warning for : Miscellaneous Warning SELF_SIGNED_CERT_IN_CHAIN: request to failed, reason: self signed certificate in certificate chain
#Jupyterlab debug windows#
The log file says the following: Node v10.13.0 Set the breakpoints in the selected cell and press Alt + Shift + Enter for Windows or for macOS. See the log file for details: C:\Users\tj\AppData\Local\Temp\jupyterlab-debug-cm_yk8nr.log I also installed nodejs using: conda install nodejsīut when it comes time to do the Jupyter Lab specific stuff then this fails jupyter labextension install error occured. The following install commands all worked correctly conda install -c plotly plotly=4.9.0Ĭonda install "notebook>=5.3" "ipywidgets>=7.2"Ĭonda install jupyterlab "ipywidgets=7.5"
#Jupyterlab debug windows 10#
I’m installing on top of a fresh Anaconda 64-bit install on a Windows 10 OS. I’m trying to install Plotly for use within a Jupyter Lab environment using the instructions from Plotly’s web site Instructions. I pretty much only use jupyter for fast prototyping and plotting.This is a copy of an issue I posted on Stack Overflow, but now that I’ve found these forums I’ll repost here. I write modules with functions, writing unit tests as I go, then write scripts that call those functions.
#Jupyterlab debug code#
Writing tests has substantially reduced the amount of time I spend actually stepping through code in a debugger. I find that writing tests forces me to write modular, easy-to-understand code. The community wanted all the tools for all the workflows.Īnyways, to get back to the topic at hand: I use both the interactive debugger and write lots of tests. TLDR The creators of Julia thought that interactive debuggers were unnecessary and possibly even harmful. This thread is great for those who want to break out the popcorn and see some nerds go at it: Prior to that, you debugged your code by writing tests.
The lack of a debugger in Julia is a long-standing controversy that was recently resolved with the creation of
0 kommentar(er)
