@jupyterlite/terminal 0.1.3 → 0.1.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -53,8 +53,8 @@ If you would like to deploy a JupyterLite site with the terminal extension, you
53
53
  As an example, this repository deploys the JupyterLite terminal to [Vercel](https://vercel.com), using the following files:
54
54
 
55
55
  - `vercel.json`: configure the COOP / COEP server headers
56
- - `requirements-deploy.txt`: dependencies for the JupyterLite deployment
57
- - `deploy.sh`: script to deploy to Vercel, using micromamba to have full control on the Python versions and isolate the build in a virtual environment
56
+ - `deploy/requirements-deploy.txt`: dependencies for the JupyterLite deployment
57
+ - `deploy/deploy.sh`: script to deploy to Vercel, using micromamba to have full control on the Python versions and isolate the build in a virtual environment
58
58
 
59
59
  For more information, have a look at the JupyterLite documentation: https://jupyterlite.readthedocs.io/
60
60
 
@@ -91,7 +91,8 @@ jupyter lab
91
91
  Then build a JupyterLite distribution with the extension installed:
92
92
 
93
93
  ```bash
94
- jupyter lite build --contents demo/contents
94
+ cd deploy
95
+ jupyter lite build --contents contents
95
96
  ```
96
97
 
97
98
  And serve it either using:
package/lib/index.js CHANGED
@@ -11,7 +11,7 @@ const terminalsPlugin = {
11
11
  autoStart: true,
12
12
  provides: ITerminals,
13
13
  activate: async (app) => {
14
- console.log('JupyterLab extension @jupyterlite/terminal:plugin is activated!');
14
+ console.log('JupyterLite extension @jupyterlite/terminal:plugin is activated!');
15
15
  const { serviceManager } = app;
16
16
  const { serverSettings, terminals } = serviceManager;
17
17
  console.log('terminals available:', terminals.isAvailable());
@@ -31,7 +31,7 @@ const terminalsRoutesPlugin = {
31
31
  autoStart: true,
32
32
  requires: [ITerminals],
33
33
  activate: (app, terminals) => {
34
- console.log('JupyterLab extension @jupyterlite/terminal:routes-plugin is activated!', terminals);
34
+ console.log('JupyterLite extension @jupyterlite/terminal:routes-plugin is activated!', terminals);
35
35
  // GET /api/terminals - List the running terminals
36
36
  app.router.get('/api/terminals', async (req) => {
37
37
  const res = await terminals.list();
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jupyterlite/terminal",
3
- "version": "0.1.3",
3
+ "version": "0.1.4",
4
4
  "description": "A terminal for JupyterLite",
5
5
  "keywords": [
6
6
  "jupyter",
@@ -61,7 +61,7 @@
61
61
  "@jupyterlab/services": "^7.2.4",
62
62
  "@jupyterlab/terminal": "^4.2.4",
63
63
  "@jupyterlab/terminal-extension": "^4.2.4",
64
- "@jupyterlite/cockle": "^0.0.10",
64
+ "@jupyterlite/cockle": "^0.0.12",
65
65
  "@jupyterlite/contents": "^0.4.0",
66
66
  "@jupyterlite/server": "^0.4.0",
67
67
  "@lumino/coreutils": "^2.2.0",
package/src/index.ts CHANGED
@@ -20,7 +20,7 @@ const terminalsPlugin: JupyterLiteServerPlugin<ITerminals> = {
20
20
  provides: ITerminals,
21
21
  activate: async (app: JupyterLiteServer) => {
22
22
  console.log(
23
- 'JupyterLab extension @jupyterlite/terminal:plugin is activated!'
23
+ 'JupyterLite extension @jupyterlite/terminal:plugin is activated!'
24
24
  );
25
25
 
26
26
  const { serviceManager } = app;
@@ -46,7 +46,7 @@ const terminalsRoutesPlugin: JupyterLiteServerPlugin<void> = {
46
46
  requires: [ITerminals],
47
47
  activate: (app: JupyterLiteServer, terminals: ITerminals) => {
48
48
  console.log(
49
- 'JupyterLab extension @jupyterlite/terminal:routes-plugin is activated!',
49
+ 'JupyterLite extension @jupyterlite/terminal:routes-plugin is activated!',
50
50
  terminals
51
51
  );
52
52