Fix handling of the base url - #6943
Merged
Merged
Conversation
Contributor
|
|
Member
Author
|
@parmentelat would you be able to try this change to see if that fixes #6942? |
Contributor
|
I went into the conda environment and tried to do this pip install -U git+https://github.com/jtpio/notebook@base-urlbut I got the errors below (actually the end of the error logs because my terminal buffer was overwhelmed) how should I go about trying out this change ? pip errors
➤ YN0013: │ vega-runtime@npm:6.1.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-scale@npm:7.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-scenegraph@npm:4.10.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-schema-url-parser@npm:2.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-selections@npm:5.4.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-scale@npm:7.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-scenegraph@npm:4.10.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-schema-url-parser@npm:2.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-selections@npm:5.4.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-statistics@npm:1.9.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-scenegraph@npm:4.10.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-schema-url-parser@npm:2.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-selections@npm:5.4.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-statistics@npm:1.9.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-themes@npm:2.13.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-schema-url-parser@npm:2.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-selections@npm:5.4.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-statistics@npm:1.9.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-themes@npm:2.13.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-time@npm:2.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-selections@npm:5.4.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-statistics@npm:1.9.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-themes@npm:2.13.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-time@npm:2.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-tooltip@npm:0.32.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-statistics@npm:1.9.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-themes@npm:2.13.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-time@npm:2.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-tooltip@npm:0.32.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-transforms@npm:4.10.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-themes@npm:2.13.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-time@npm:2.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-tooltip@npm:0.32.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-transforms@npm:4.10.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-typings@npm:0.24.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-time@npm:2.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-tooltip@npm:0.32.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-transforms@npm:4.10.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-typings@npm:0.24.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-util@npm:1.17.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-tooltip@npm:0.32.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-transforms@npm:4.10.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-typings@npm:0.24.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-util@npm:1.17.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-view-transforms@npm:4.5.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-transforms@npm:4.10.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-typings@npm:0.24.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-util@npm:1.17.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-view-transforms@npm:4.5.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-view@npm:5.11.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-typings@npm:0.24.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-util@npm:1.17.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-view-transforms@npm:4.5.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-view@npm:5.11.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-voronoi@npm:4.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-util@npm:1.17.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-view-transforms@npm:4.5.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-view@npm:5.11.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-voronoi@npm:4.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-wordcloud@npm:4.1.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-view-transforms@npm:4.5.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-view@npm:5.11.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-voronoi@npm:4.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-wordcloud@npm:4.1.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega@npm:5.25.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-view@npm:5.11.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-voronoi@npm:4.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-wordcloud@npm:4.1.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega@npm:5.25.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verdaccio-audit@npm:11.0.0-6-next.34 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-voronoi@npm:4.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-wordcloud@npm:4.1.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega@npm:5.25.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verdaccio-audit@npm:11.0.0-6-next.34 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verdaccio-htpasswd@npm:11.0.0-6-next.41 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega-wordcloud@npm:4.1.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega@npm:5.25.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verdaccio-audit@npm:11.0.0-6-next.34 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verdaccio-htpasswd@npm:11.0.0-6-next.41 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verdaccio@npm:5.25.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vega@npm:5.25.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verdaccio-audit@npm:11.0.0-6-next.34 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verdaccio-htpasswd@npm:11.0.0-6-next.41 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verdaccio@npm:5.25.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verror@npm:1.10.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verdaccio-audit@npm:11.0.0-6-next.34 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verdaccio-htpasswd@npm:11.0.0-6-next.41 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verdaccio@npm:5.25.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verror@npm:1.10.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-jsonrpc@npm:6.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verdaccio-htpasswd@npm:11.0.0-6-next.41 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verdaccio@npm:5.25.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verror@npm:1.10.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-jsonrpc@npm:6.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-jsonrpc@npm:8.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verdaccio@npm:5.25.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verror@npm:1.10.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-jsonrpc@npm:6.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-jsonrpc@npm:8.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-languageserver-protocol@npm:3.17.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ verror@npm:1.10.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-jsonrpc@npm:6.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-jsonrpc@npm:8.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-languageserver-protocol@npm:3.17.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-languageserver-types@npm:3.17.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-jsonrpc@npm:6.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-jsonrpc@npm:8.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-languageserver-protocol@npm:3.17.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-languageserver-types@npm:3.17.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-ws-jsonrpc@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-jsonrpc@npm:8.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-languageserver-protocol@npm:3.17.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-languageserver-types@npm:3.17.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-ws-jsonrpc@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ w3c-keyname@npm:2.2.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-languageserver-protocol@npm:3.17.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-languageserver-types@npm:3.17.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-ws-jsonrpc@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ w3c-keyname@npm:2.2.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ w3c-xmlserializer@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-languageserver-types@npm:3.17.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-ws-jsonrpc@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ w3c-keyname@npm:2.2.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ w3c-xmlserializer@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ walk-up-path@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ vscode-ws-jsonrpc@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ w3c-keyname@npm:2.2.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ w3c-xmlserializer@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ walk-up-path@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ walker@npm:1.0.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ w3c-keyname@npm:2.2.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ w3c-xmlserializer@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ walk-up-path@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ walker@npm:1.0.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ watch@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ w3c-xmlserializer@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ walk-up-path@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ walker@npm:1.0.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ watch@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ watchpack@npm:2.4.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ walk-up-path@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ walker@npm:1.0.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ watch@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ watchpack@npm:2.4.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wcwidth@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ walker@npm:1.0.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ watch@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ watchpack@npm:2.4.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wcwidth@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webidl-conversions@npm:3.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ watch@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ watchpack@npm:2.4.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wcwidth@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webidl-conversions@npm:3.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webidl-conversions@npm:6.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ watchpack@npm:2.4.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wcwidth@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webidl-conversions@npm:3.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webidl-conversions@npm:6.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webidl-conversions@npm:7.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wcwidth@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webidl-conversions@npm:3.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webidl-conversions@npm:6.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webidl-conversions@npm:7.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-bundle-analyzer@npm:4.9.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webidl-conversions@npm:3.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webidl-conversions@npm:6.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webidl-conversions@npm:7.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-bundle-analyzer@npm:4.9.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-cli@npm:5.1.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webidl-conversions@npm:6.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webidl-conversions@npm:7.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-bundle-analyzer@npm:4.9.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-cli@npm:5.1.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-merge@npm:5.9.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webidl-conversions@npm:7.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-bundle-analyzer@npm:4.9.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-cli@npm:5.1.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-merge@npm:5.9.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-sources@npm:1.4.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-bundle-analyzer@npm:4.9.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-cli@npm:5.1.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-merge@npm:5.9.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-sources@npm:1.4.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-sources@npm:3.2.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-cli@npm:5.1.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-merge@npm:5.9.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-sources@npm:1.4.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-sources@npm:3.2.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack@npm:5.86.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-merge@npm:5.9.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-sources@npm:1.4.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-sources@npm:3.2.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack@npm:5.86.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-encoding@npm:2.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-sources@npm:1.4.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-sources@npm:3.2.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack@npm:5.86.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-encoding@npm:2.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-fetch@npm:3.6.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack-sources@npm:3.2.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack@npm:5.86.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-encoding@npm:2.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-fetch@npm:3.6.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-mimetype@npm:2.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webpack@npm:5.86.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-encoding@npm:2.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-fetch@npm:3.6.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-mimetype@npm:2.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-mimetype@npm:3.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-encoding@npm:2.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-fetch@npm:3.6.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-mimetype@npm:2.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-mimetype@npm:3.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-url@npm:11.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-fetch@npm:3.6.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-mimetype@npm:2.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-mimetype@npm:3.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-url@npm:11.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-url@npm:5.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-mimetype@npm:2.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-mimetype@npm:3.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-url@npm:11.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-url@npm:5.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-url@npm:8.7.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-mimetype@npm:3.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-url@npm:11.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-url@npm:5.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-url@npm:8.7.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which-boxed-primitive@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-url@npm:11.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-url@npm:5.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-url@npm:8.7.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which-boxed-primitive@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which-typed-array@npm:1.1.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-url@npm:5.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-url@npm:8.7.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which-boxed-primitive@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which-typed-array@npm:1.1.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which@npm:1.3.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-url@npm:8.7.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which-boxed-primitive@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which-typed-array@npm:1.1.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which@npm:1.3.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which@npm:2.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which-boxed-primitive@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which-typed-array@npm:1.1.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which@npm:1.3.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which@npm:2.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which@npm:3.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which-typed-array@npm:1.1.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which@npm:1.3.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which@npm:2.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which@npm:3.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wicked-good-xpath@npm:1.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which@npm:1.3.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which@npm:2.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which@npm:3.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wicked-good-xpath@npm:1.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wide-align@npm:1.1.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which@npm:2.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which@npm:3.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wicked-good-xpath@npm:1.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wide-align@npm:1.1.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wildcard@npm:2.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which@npm:3.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wicked-good-xpath@npm:1.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wide-align@npm:1.1.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wildcard@npm:2.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ word-wrap@npm:1.2.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wicked-good-xpath@npm:1.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wide-align@npm:1.1.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wildcard@npm:2.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ word-wrap@npm:1.2.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wordwrap@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wide-align@npm:1.1.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wildcard@npm:2.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ word-wrap@npm:1.2.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wordwrap@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ worker-loader@npm:3.0.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wildcard@npm:2.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ word-wrap@npm:1.2.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wordwrap@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ worker-loader@npm:3.0.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrap-ansi@npm:6.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ word-wrap@npm:1.2.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wordwrap@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ worker-loader@npm:3.0.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrap-ansi@npm:6.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrap-ansi@npm:7.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wordwrap@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ worker-loader@npm:3.0.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrap-ansi@npm:6.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrap-ansi@npm:7.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrap-ansi@npm:8.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ worker-loader@npm:3.0.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrap-ansi@npm:6.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrap-ansi@npm:7.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrap-ansi@npm:8.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrappy@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrap-ansi@npm:6.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrap-ansi@npm:7.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrap-ansi@npm:8.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrappy@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:2.4.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrap-ansi@npm:7.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrap-ansi@npm:8.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrappy@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:2.4.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:4.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrap-ansi@npm:8.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrappy@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:2.4.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:4.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:4.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrappy@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:2.4.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:4.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:4.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:5.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:2.4.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:4.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:4.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:5.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-json-file@npm:3.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:4.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:4.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:5.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-json-file@npm:3.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-pkg@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:4.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:5.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-json-file@npm:3.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-pkg@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ws@npm:7.5.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-file-atomic@npm:5.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-json-file@npm:3.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-pkg@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ws@npm:7.5.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ws@npm:8.13.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-json-file@npm:3.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-pkg@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ws@npm:7.5.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ws@npm:8.13.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xml-name-validator@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ write-pkg@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ws@npm:7.5.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ws@npm:8.13.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xml-name-validator@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xml@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ws@npm:7.5.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ws@npm:8.13.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xml-name-validator@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xml@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xmlchars@npm:2.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ws@npm:8.13.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xml-name-validator@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xml@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xmlchars@npm:2.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xmldom-sre@npm:0.1.31 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xml-name-validator@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xml@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xmlchars@npm:2.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xmldom-sre@npm:0.1.31 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xtend@npm:4.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xml@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xmlchars@npm:2.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xmldom-sre@npm:0.1.31 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xtend@npm:4.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-canvas@npm:0.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xmlchars@npm:2.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xmldom-sre@npm:0.1.31 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xtend@npm:4.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-canvas@npm:0.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-fit@npm:0.7.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xmldom-sre@npm:0.1.31 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xtend@npm:4.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-canvas@npm:0.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-fit@npm:0.7.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-web-links@npm:0.8.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xtend@npm:4.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-canvas@npm:0.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-fit@npm:0.7.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-web-links@npm:0.8.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-webgl@npm:0.14.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-canvas@npm:0.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-fit@npm:0.7.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-web-links@npm:0.8.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-webgl@npm:0.14.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm@npm:5.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-fit@npm:0.7.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-web-links@npm:0.8.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-webgl@npm:0.14.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm@npm:5.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ y-protocols@npm:1.0.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-web-links@npm:0.8.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-webgl@npm:0.14.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm@npm:5.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ y-protocols@npm:1.0.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ y18n@npm:5.0.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm-addon-webgl@npm:0.14.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm@npm:5.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ y-protocols@npm:1.0.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ y18n@npm:5.0.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yallist@npm:3.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xterm@npm:5.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ y-protocols@npm:1.0.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ y18n@npm:5.0.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yallist@npm:3.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yallist@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ y-protocols@npm:1.0.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ y18n@npm:5.0.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yallist@npm:3.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yallist@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yaml@npm:1.10.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ y18n@npm:5.0.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yallist@npm:3.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yallist@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yaml@npm:1.10.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs-parser@npm:20.2.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yallist@npm:3.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yallist@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yaml@npm:1.10.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs-parser@npm:20.2.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs-parser@npm:20.2.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yallist@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yaml@npm:1.10.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs-parser@npm:20.2.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs-parser@npm:20.2.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs-parser@npm:21.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yaml@npm:1.10.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs-parser@npm:20.2.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs-parser@npm:20.2.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs-parser@npm:21.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs@npm:16.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs-parser@npm:20.2.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs-parser@npm:20.2.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs-parser@npm:21.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs@npm:16.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs@npm:17.7.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs-parser@npm:20.2.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs-parser@npm:21.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs@npm:16.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs@npm:17.7.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yjs@npm:13.6.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs-parser@npm:21.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs@npm:16.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs@npm:17.7.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yjs@npm:13.6.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yocto-queue@npm:0.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs@npm:16.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs@npm:17.7.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yjs@npm:13.6.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yocto-queue@npm:0.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yup@npm:0.32.11 can't be found in the cache and will be fetched from the remote registry
➤ YN0000: └ Completed in 47s 231ms
➤ YN0000: ┌ Link step
➤ YN0007: │ @parcel/watcher@npm:2.0.4 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/fontawesome-free@npm:5.15.4 must be built because it never has been before or the last one failed
➤ YN0007: │ core-js@npm:3.30.2 must be built because it never has been before or the last one failed
➤ YN0007: │ nx@npm:15.9.4 [9d75b] must be built because it never has been before or the last one failed
➤ YN0000: └ Completed in 17s 195ms
➤ YN0000: Done with warnings in 1m 6s
INFO:hatch_jupyter_builder.utils:> /private/var/folders/9n/sxs31qhj1gnd6gk2v0ns8848000fn2/T/pip-build-env-5z_zfxub/overlay/bin/jlpm run build:prod
lerna notice cli v6.6.2
lerna info versioning independent
> Lerna (powered by Nx) Running target build:prod for 13 projects:
- @jupyter-notebook/app
- @jupyter-notebook/application-extension
- @jupyter-notebook/application
- @jupyter-notebook/console-extension
- @jupyter-notebook/docmanager-extension
- @jupyter-notebook/documentsearch-extension
- @jupyter-notebook/help-extension
- @jupyter-notebook/lab-extension
- @jupyter-notebook/notebook-extension
- @jupyter-notebook/terminal-extension
- @jupyter-notebook/tree-extension
- @jupyter-notebook/tree
- @jupyter-notebook/ui-components
> @jupyter-notebook/ui-components:"build:prod"
> @jupyter-notebook/docmanager-extension:"build:prod"
src/index.ts(15,32): error TS2307: Cannot find module '@jupyter-notebook/application' or its corresponding type declarations.
> @jupyter-notebook/application:"build:prod"
> @jupyter-notebook/terminal-extension:"build:prod"
> @jupyter-notebook/console-extension:"build:prod"
> @jupyter-notebook/help-extension:"build:prod"
> Lerna (powered by Nx) Running target build:prod for 13 projects failed
Tasks not run because their dependencies failed or --nx-bail=true:
- @jupyter-notebook/app:build:prod
- @jupyter-notebook/application-extension:build:prod
- @jupyter-notebook/documentsearch-extension:build:prod
- @jupyter-notebook/lab-extension:build:prod
- @jupyter-notebook/notebook-extension:build:prod
- @jupyter-notebook/tree-extension:build:prod
- @jupyter-notebook/tree:build:prod
Failed tasks:
- @jupyter-notebook/docmanager-extension:build:prod
Traceback (most recent call last):
File "/Users/tparment/miniconda3/envs/jlab4-nb7-text/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in
main()
File "/Users/tparment/miniconda3/envs/jlab4-nb7-text/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/tparment/miniconda3/envs/jlab4-nb7-text/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 152, in prepare_metadata_for_build_wheel
whl_basename = backend.build_wheel(metadata_directory, config_settings)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/private/var/folders/9n/sxs31qhj1gnd6gk2v0ns8848000fn2/T/pip-build-env-5z_zfxub/overlay/lib/python3.11/site-packages/hatchling/build.py", line 56, in build_wheel
return os.path.basename(next(builder.build(wheel_directory, ['standard'])))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/private/var/folders/9n/sxs31qhj1gnd6gk2v0ns8848000fn2/T/pip-build-env-5z_zfxub/overlay/lib/python3.11/site-packages/hatchling/builders/plugin/interface.py", line 150, in build
build_hook.initialize(version, build_data)
File "/private/var/folders/9n/sxs31qhj1gnd6gk2v0ns8848000fn2/T/pip-build-env-5z_zfxub/normal/lib/python3.11/site-packages/hatch_jupyter_builder/plugin.py", line 87, in initialize
raise e
File "/private/var/folders/9n/sxs31qhj1gnd6gk2v0ns8848000fn2/T/pip-build-env-5z_zfxub/normal/lib/python3.11/site-packages/hatch_jupyter_builder/plugin.py", line 82, in initialize
build_func(self.target_name, version, **build_kwargs)
File "/private/var/folders/9n/sxs31qhj1gnd6gk2v0ns8848000fn2/T/pip-build-env-5z_zfxub/normal/lib/python3.11/site-packages/hatch_jupyter_builder/utils.py", line 115, in npm_builder
run([*npm_cmd, "run", build_cmd], cwd=str(abs_path))
File "/private/var/folders/9n/sxs31qhj1gnd6gk2v0ns8848000fn2/T/pip-build-env-5z_zfxub/normal/lib/python3.11/site-packages/hatch_jupyter_builder/utils.py", line 229, in run
return subprocess.check_call(cmd, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/tparment/miniconda3/envs/jlab4-nb7-text/lib/python3.11/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/private/var/folders/9n/sxs31qhj1gnd6gk2v0ns8848000fn2/T/pip-build-env-5z_zfxub/overlay/bin/jlpm', 'run', 'build:prod']' returned non-zero exit status 1.
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
|
Member
Author
|
@parmentelat another way would be to install the wheel from the built artifacts directly: https://github.com/jupyter/notebook/actions/runs/5345232824?pr=6943 |
Contributor
|
oh yes great ! so I'm happy to report that with that change I can now open the jupytext notebook using either Open with → "Notebook" or "Jupytext Notebook" |
Member
Author
|
Nice! I suspect it still redirects to |
Contributor
|
yes, please see #6942 for details |
Contributor
|
out of curiosity, any idea when a proper rc2 can be expected ? |
Member
Author
Probably we could do it after merging this PR since it fixes a bug. |
jtpio
marked this pull request as ready for review
June 23, 2023 10:18
Member
Author
|
I think this can go in since it already fixes a bug. But there is still the question of how to handle both opening a notebook from the CLI, and opening Jupytext notebooks under This can be investigated more in #6942. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Troubleshoot #6942