Running the sample instructions not working on macOS

[arkaydeus]

Procedure followed

1. Cloned repo
2. Opened VSCode in folder
3. Ran yarn (got warning The engine "vscode" appears to be invalid.)
4. Hit F5
5. New VSC instance opened

When opening sample notebook got the following errors:

"Cannot open resource with notebook editor type 'nodebook', please check if you have the right extension installed or enabled."

also

"Activating extension 'undefined_publisher.vscode-nodebook' failed: [undefined_publisher.vscode-nodebook]: Proposed API is only available when running out of dev or with the following command line switch: --enable-proposed-api undefined_publisher.vscode-nodebook."

Using VSCode 1.47.2

[sbussard]

Glad I wasn't the only one who experienced this error

[weinand]

The latest notebook should work now.

[darcyalcantara]

Hi! Same problem here, following the same procedure. Screenshot below:

Am I doing anything wrong? VSCode 1.56.2.

(Observation: when running yarn, I get: 'The engine "vscode" appears to be invalid.')

Thank you.

[weinand]

I'll have to adapt the code to the latest APIs...

[darcyalcantara]

Thank you, Weinand. This is such a great extension.

[mhkeller]

Getting this error:

yarn install v1.22.18
[1/5] 🔍  Validating package.json...
warning vscode-nodebook@1.0.0: The engine "vscode" appears to be invalid.
[2/5] 🔍  Resolving packages...
[3/5] 🚚  Fetching packages...
[4/5] 🔗  Linking dependencies...
[5/5] 🔨  Building fresh packages...
✨  Done in 9.92s.

Hitting F5 opens up a new window but the file is JSON, not a notebook.

[HlexNC]

@mhkeller, I know this is 2 years later. But have you fixed the issues? Also, are you using vscode or by any chance GitHub codespace. Because I have the exact same issue while creating a codespace here in main.

@HlexNC ➜ /workspaces/vscode-nodebook (main) $ yarn install
yarn install v1.22.19
[1/5] Validating package.json...
warning vscode-nodebook@1.0.0: The engine "vscode" appears to be invalid.
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
[5/5] Building fresh packages...

Done in 0.99s.
@HlexNC ➜ /workspaces/vscode-nodebook (main) $ 

---

[HlexNC]

@jrieken Sorry to waste your time, but would you be able to provide some assistance here?

[mhkeller]

@HlexNC I haven't tried recently. I agree that it would be great if this were working.

As an alternative, I've been working on this type of setup that brings some of the real-time feedback you get from a notebook but preserves the structure of a normal script: https://github.com/mhkeller/interactive-nodejs

It's not perfect and would benefit from changes to the VS Code debug REPL (tracking here).

[HlexNC]

As I am using GitHub Codespace, my notebook isn't even rendering. I will try running it locally, but currently I don't even have vs code installed locally 😅