-
Notifications
You must be signed in to change notification settings - Fork 250
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
UI Source Code #91
Comments
I've got a branch here that has most of the demo frontend code (I grabbed it from sources tab). It is functional-ish, but some of the configuration and styling will be different (that data isn't available so I made some guesses about the config/env files). |
thank you! Can you provide instructions to run it locally? I get error when i run gatsby build: ⠋ Building production JavaScript and CSS bundles failed Building production JavaScript and CSS bundles - 76.043s ERROR #98124 WEBPACK.BUILD-JAVASCRIPT Generating JavaScript bundles failed Can't resolve '../../../data/updates' in '/Users/amitdixit/GitHub/amdixit/llm-visualization/lida/web/react-app/src/components/views/about' If you're trying to use a package make sure that '../../../data/updates' is installed. If you're trying to use a local file make sure that the path is correct. File: src/components/views/about/index.tsx:1:252 ERROR #98124 WEBPACK.BUILD-JAVASCRIPT Generating JavaScript bundles failed Can't resolve '../../../data/updates' in '/Users/amitdixit/GitHub/amdixit/llm-visualization/lida/web/react-app/src/components/views/about' If you're trying to use a package make sure that '../../../data/updates' is installed. If you're trying to use a local file make sure that the path is correct. File: src/components/views/about/updates.tsx:1:28 |
Ah, the issue is that repo's root .gitignore is ignoring all data folders and that "updates" view is trying to access an updates.ts file within that directory. When I was pulling over from the sources tab, I had not noticed that gitignore had ignored the data directory. Here is that file's contents: export const updates = [ If you either delete the reference to that OR add that (or an empty array) to react-app/src/data/updates.ts, it should get past that specific build error. |
i went slightly ahead: I am using node 18, and encounter the below errors on gatsby build: success compile gatsby files - 1.216s ERROR UNKNOWN Truncated page data information for the failed page "/demo/": { failed Building static HTML for pages - 3.036s ERROR #95312 HTML.COMPILATION "document" is not available during server-side rendering. Enable "DEV_SSR" to debug this during "gatsby develop". See our docs page for more info on this error: https://gatsby.dev/debug-html 1 | import { render } from '../react/render';
WebpackError: ReferenceError: document is not defined
|
is there a chance anothe config file is missing from your checkin? |
I have only experimented with running it locally ( |
Hey @matt-hendrick , Can you give me a tutorial step by step to run the UI reactjs. I'm new in the react so too hard for me to run your repository without your instructions |
Sure, I just updated that branch to no longer ignore the data folder in react-web. The steps you should have to take to run that project should be:
I will caution that this branch is not something I have heavily tested or spent a lot of time on. I just was curious so I pulled down that code to experiment with. The styling is not quite right and I did not try to get the production build working properly, but it does work for testing things out locally. |
Was running into the same error as @amdixit during build. Found a fix, will post soon. Thank you @matt-hendrick for taking the time and effort to get this started. |
@BTTBoost I am faing the same issue, please share your fix, I'll be really helpful. |
Is there a plan to opensource the source code for the reactjs UI?
The text was updated successfully, but these errors were encountered: