Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Visual Studio Code Extension Development, inspector produces 'Window does not exist; inspector cannot be started.' #4

Open
BillHertzing opened this issue Jan 19, 2024 · 4 comments

Comments

@BillHertzing
Copy link

statelyai/inspect produces the message "Window does not exist; inspector cannot be started.'

const primaryMachineInspector = createBrowserInspector(); // This line produces the errorMessage

I am developing a Visual Studio Code Extension, xState is running in a VSC Development Host.

package.json: (// relevant entries)
"dependencies": {
"@statelyai/inspect": "^0.2.0",
"bufferutil": "^4.0.8",
"utf-8-validate": "^6.0.3",
"xstate": "^5.5.1"

Also, after installing inspect, WebPack reported two missing packages bufferutil and utf-8-validate. I installed those manually, but it did not resolve the problem.

VSC Version :
image

Windows Version:
image

Please let me know if I can supply any additional information. I'm also on the Discord Stately server as BaslimOfJubbul

@BillHertzing
Copy link
Author

Windows version info:
Windows and computer details

@BillHertzing BillHertzing changed the title Visual Studio Code Extension Development, inspecotr produces 'Window does not exist; inspector cannot be started.' Visual Studio Code Extension Development, inspector produces 'Window does not exist; inspector cannot be started.' Jan 19, 2024
@davidkpiano
Copy link
Member

bufferutil and utf-8-validate

Strange; Stately Inspect does not depend on these.

You should be able to pass in a custom window object here:

const inspector = createBrowserInspector({
  window: /* custom window object */
})

Maybe that may help? We currently assume a normal browser environment, and haven't yet tested within VS Code extensions.

@BillHertzing
Copy link
Author

BillHertzing commented Jan 19, 2024 via email

@BillHertzing
Copy link
Author

BillHertzing commented Jan 19, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants