-
Notifications
You must be signed in to change notification settings - Fork 5
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
Comments
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
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. |
I will test this tonight.
…On Thu, Jan 18, 2024 at 10:19 PM David Khourshid ***@***.***> wrote:
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.
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG2NNFGRD6ZNR6CGC2Y4STYPH64VAVCNFSM6AAAAABCBHVJMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJZG44DMNBQGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
could you please point me in the direction of where I can find a definition
of and instructions forhow to implement a /* custom window object */? I'm
unfamiliar with the term., but willing to do the research and see if I can
get it working. Hoping you can get me started in a direction more specific
than 'just google it' :-)
On Fri, Jan 19, 2024 at 11:34 AM Bill Hertzing ***@***.***>
wrote:
… I will test this tonight.
On Thu, Jan 18, 2024 at 10:19 PM David Khourshid ***@***.***>
wrote:
> 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.
>
> —
> Reply to this email directly, view it on GitHub
> <#4 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAG2NNFGRD6ZNR6CGC2Y4STYPH64VAVCNFSM6AAAAABCBHVJMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJZG44DMNBQGU>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 :
Windows Version:
Please let me know if I can supply any additional information. I'm also on the Discord Stately server as BaslimOfJubbul
The text was updated successfully, but these errors were encountered: