Skip to content
This repository has been archived by the owner on Jul 3, 2024. It is now read-only.

Running the sample instructions not working on macOS #1

Open
arkaydeus opened this issue Jul 19, 2020 · 10 comments
Open

Running the sample instructions not working on macOS #1

arkaydeus opened this issue Jul 19, 2020 · 10 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@arkaydeus
Copy link

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
Copy link

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

@weinand weinand self-assigned this Sep 17, 2020
@weinand weinand added this to the September 2020 milestone Sep 17, 2020
@weinand weinand added the bug Issue identified by VS Code Team member as probable bug label Sep 17, 2020
@weinand
Copy link
Contributor

weinand commented Sep 17, 2020

The latest notebook should work now.

@weinand weinand closed this as completed Sep 17, 2020
@darcyalcantara
Copy link

darcyalcantara commented Jun 7, 2021

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

Captura de Tela 2021-06-07 às 00 24 56

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 weinand reopened this Jun 7, 2021
@weinand
Copy link
Contributor

weinand commented Jun 7, 2021

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

@darcyalcantara
Copy link

darcyalcantara commented Jun 7, 2021

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

@mhkeller
Copy link

mhkeller commented May 13, 2022

Getting this error:

yarn install v1.22.18
[1/5] 🔍  Validating package.json...
warning [email protected]: 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
Copy link

HlexNC commented May 8, 2024

@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 [email protected]: 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) $ 

image
image
image

@HlexNC
Copy link

HlexNC commented May 8, 2024

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

@mhkeller
Copy link

mhkeller commented May 8, 2024

@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
Copy link

HlexNC commented May 8, 2024

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 😅

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

6 participants