-
Notifications
You must be signed in to change notification settings - Fork 234
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
Issue with Rollup: this
has been rewritten to undefined
#461
Comments
Following here I suppressed the warning by adding into the rollup.config.js
But the core issue is that the web app doesn't load locally and is unresponsive. Here is the full print-out following
I'm running Visual Studio Code debugger with the following launch.js:
Note that the fields for Now, Visual Studio and Chrome Developer Tools Console both don't show any errors or warnings, but web app doesn't load still. Maybe there is a verbose debug mode to gather more information on why things are not loading? The loading bar is spinning in Chrome, indicating it never finishes/hangs somewhere. None of the buttons work. |
I ran into this recently too. Note the root folder is the shared sample viewer code, NOT the web app. So to launch the dev server:
Perhaps the docs could be adjusted to make this more clear. |
I'm experiencing the same behaviour on mac, and the app_web locally is non-responsive in the browser (Chrome, Firefox and Chrome Canary). Some assets remain in a Pending state while loading (damagedHelmet and libktx.js, one or two others) and I receive the "This page is not responsive, do you want to wait?" prompt. I am (and have) installed as per @emackey's suggestion, and the readme. It's not clear to me if the non-responsiveness is caused from the issue in the printed message or not. node v18.12.1 |
Is this still an issue? |
After following the instructions for running the web app from scratch, and trying to run
npm run dev
, I get the following error:My system:
Maybe this is something obvious to a more experienced web developer?
The text was updated successfully, but these errors were encountered: