Summary

Steps to reproduce

Install the extension on Vscode and run any command (I'm using "Raycast: Start Development mode"). It'll error. My setup:

Version: 1.74.2
Commit: e8a3071ea4344d9d48ef8a4df2c097372b0c5161
Date: 2022-12-20T10:32:21.587Z (1 wk ago)
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Darwin arm64 22.2.0
Sandboxed: Yes

What is the current bug behavior?

What is the expected correct behavior?

Relevant logs and/or screenshots

Possible fixes

Summary

No way to attach the debugger

Steps to reproduce

I can't attach the debugger to the process. I start by "Start Development Mode" and than "Attach the Debugger". I created the

        {
            "name": "Attach by Process ID",
            "processId": "${command:PickProcess}",
            "request": "attach",
            "skipFiles": [
                "<node_internals>/**"
            ],
            "type": "node"
        }
    ]

launch.json however there is no process to choose from.

Problem to solve

Make it easy to see the possibility to upgrade to a higher raycast API.

Proposal

Make it easy to see the possibility to upgrade to a higher raycast API version by comparing the local (workspace) installed version with the one on npm.com. This can be shown in the treeview when there is a higher version. Clicking on the item trigger the migration command.

Further details

Links / references

npm registry API

Problem to solve

Activate React DevTools directly from VSCode.

Proposal

Add command to have a simple way to activate React DevTools directly from VSCode

Further details

Links / references

Problem to solve

Often it is required to add filenames from the assets folder in into the activate tsx file. Remember all the files is very unproductive and often it is copy paste or typing.

Proposal

Use a command to display the file from the assets folder (like in the Add Command command) to paste the content into the active selection.

Further details

Links / references

It would be cool to add some validation / completions for the @raycast directives in script commands.

Not sure how to achieve this though, since the scripts commands can be written in any language.

Problem to solve

Add a command to simply create a brand new extension in a given directoy.

Proposal

The command could also guide the user through the process via Q&A prompts.

Further details

Links / references

Problem to solve

Add command to add preferences.

Proposal

Add command to add preferences to package.json

Further details

Links / references

Summary

The docs instruct one to run this command:

$ open "vscode://tonka3000.raycast/runcommand?cmd=openInTerminal"

That does indeed launch VScode; but has no other effect as far as I can see.

I tried using the newer command-name for 'create a new terminal',

$ open "vscode://tonka3000.raycast/runcommand?cmd=workbench.action.terminal.new"

... with no further luck. (=

Problem to solve

Add a VSCode command which adds a given Raycast command and add it to package.json

Proposal

Add VSCode command which adds a given Raycast command to package.json

Further details

Maybe the command should show all existing commands in the command palette.

Links / references