qwik
qwik copied to clipboard
Editor on example page is broken
Qwik Version
latest
Operating System (or Browser)
MacOS Monterey (12.3.1 [21E258])
Node Version (if applicable)
No response
Which component is affected?
Starters / CLI
Expected Behaviour
- Go to
https://qwik.builder.io/examples/reactivity/watch
(or any example) - Editor should have full height
Actual Behaviour
Editor is limited to a very small container
Additional Information
Browser: Brave Version 1.42.88 Chromium: 104.0.5112.81 (Official Build) (arm64), Safari (15.4 [17613.1.17.1.13])
Sorry, I did not know which affected component
I should pick, so I went with Starters/CLI
kind regards
Just realized that the same issue is present on all other pages that show the editor https://qwik.builder.io/tutorial/welcome/overview https://qwik.builder.io/playground
It's working for me! is this still an issue? I will close, but if it's i will be happy to reopen
@manucorporat Seems to be working again 👍
It is not working in the tutorial on Sep. 28 2022
Error: "Cannot find module '@builder.io/qwik' or its corresponding type declarations"
@roryjarrard that is a different issue. Previously it was not loading, your screenshot seems to have issues of not being able to load data from data.jsdelivr.com
.
Maybe you can observe it for a few days and check on different browsers. If it still won't load, you can open a new issue.
I'm using this issue as it's the first result when searching for "Qwik playground broken". Seems to be so again.
Error: Unable to require() path "@builder.io/qwik/build" from a browser environment. at globalThis.qwikServer.globalThis.require (eval at g (https://qwik.builder.io/repl/repl-sw.js:1:341), <anonymous>:33:11) at eval (eval at g (https://qwik.builder.io/repl/repl-sw.js:1:341), <anonymous>:164:20) at eval (eval at g (https://qwik.builder.io/repl/repl-sw.js:1:341), <anonymous>:783:26) at g (https://qwik.builder.io/repl/repl-sw.js:1:377) at async B (https://qwik.builder.io/repl/repl-sw.js:1:1357) at async F (https://qwik.builder.io/repl/repl-sw.js:12:5469)
Opened a new issue (this one is closed), there, in case you stumble upon this in 2023.