Closed MShuttle closed 4 months ago
We think that this issue is specific to your project / project dependencies.
Are you able to provide us with a sample repo that has the same problem? Alternatively, you may start by providing us with your package.json
file. Based on the stack trace of the error, I assume you're using yarn@2+
?
@MShuttle - bumping this issue as we haven't heard back.
@smcenlly —I'm sorry I didn't get back to you sooner. I am not using yarn at the moment, but I have used it in the past.
The problem is resolved. I did this, and I think it may be helpful to you going forward.
Voila. A guess is that Quokka Init executed the artefacts even if the associated package manager was not used.
A guess is that Quokka Init executed the artefacts even if the associated package manager was not used.
Yes - if you had .pnp.cjs
, Quokka would have used it for your project. It sounds like that caused the problem if you had it in your home directory.
Thanks for getting back to us :)
Issue description or question
Is this issue related to Quokka not outputting the expected results of your code?: No
When attempting to start Quokka on any JavaScript file, Quokka does not start. The only information available is in the VSCode Quokka Extension Output panel. The total output is pasted below.
Completely removed Quokka, including all wallaby versions in the ~.vscode/extensions folder.
Reinstalling Quokka from did not resolve the issue.
Sample code
No Code
Quokka.js Console Output
Code editor version
Visual Studio Code Version: 1.86.2 (Universal) Commit: 903b1e9d8990623e3d7da1df3d33db3e42d80eda Date: 2024-02-13T19:42:13.651Z (1 wk ago) Electron: 27.2.3 ElectronBuildId: 26908389 Chromium: 118.0.5993.159 Node.js: 18.17.1 V8: 11.8.172.18-electron.0 OS: Darwin x64 22.6.0
OS name and version
OSX Ventura 13.6.4 Macbook Pro