-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Frontend dependency issues - creates a blank page #2369
Comments
.auth/me is expected to be a 404 if your app is not using user authentication The other ones, /containerpath and /config are 200 in your output Are there any JS errors in the console? Are you using auth? |
There are no js errors. We are not using user authentication. When we rebuild the frontend with updated package there are no errors or anything that shows anything, the page is just blank the only thing that is different is the lines below don't show up in the terminal. So, something is not letting the auth_setup go through maybe? We have tried lots of package scenarios, but nothing works yet. [2025-02-19 15:22:32 -0600] [551111] [INFO] 127.0.0.1:60402 GET /auth_setup 1.1 200 492 1103 |
Ah I see, you're saying that the /auth_setup route is never called at all. That's called from this JS:
So that'd imply that there's something wrong with the JS in that it's never executing that line. Could you check the compiled index JS file to see if it looks off? |
We have been trying to figure it out for awhile, tricky is an understatement :) . For the compiled js they look pretty much the same except the one with the issue has as the first entry and the one that works does not have it. Which could just be a newer version format change. I just went through and updated some of the files like authconfig to the newest version on the repo - ended up doing a handful of others with the changes hoping that would resolve it but it is still the blank page. |
This is very likely corelated with #2373 |
t is likely React: Based on the usage of createContext and the typical patterns in web app builds, it's highly probable that t is an alias (renamed variable) for the React library within the bundled code. This likely is a co accident with #2374 I already did |
I would say they are related and the same issue.. I get the same console error. I have not changed any of the frontend and mine is not t. but i know the dependency issue is with react and something in there. I have tried vite 6 and i get the same results. I know something is a little off in how they get built - our current working load the package-lock file is about 10K rows compared to the one with this issue is only 5k rows, so i know something is not loading all the way or not at all. I have not tried python 12 though since i knew it is something on the react side but maybe it is how they all work together. At this point anything is worth trying. import * as React from 'react'; const IconDirectionContextDefaultValue = {}; |
duplicate #2373 @pamelafox at least 3 independent reports for the same issue below a cleand up console out
It looks like the project might not be properly importing React, or there could be multiple versions of React causing conflicts. Since the error message points to createContext being undefined, let's go through a few debugging steps: |
Is there any possibility for any fix @pamelafox |
Browser console error: IconDirectionContext.js:2 Uncaught TypeError: Cannot read properties of undefined (reading 'createContext') import * as React from 'react'; |
I figured this problem out. I haven't resolved it all the way yet but hopefully will get it figured out. We have done lots of modifications and added approaches for our business needs on this as I am sure others have too. We originally got this from github a couple years back. We use this with databases and text to sql and other ways instead of just a doc chat. We have not updated our end with new releases very often since we have altered it so much and not wanting to redo everything to often. The issue is a fluenti version conflict. Doing a hybrid of fluenti v8 and v9 does not work( that is the issue). So to resolve this I had to rebuild the entire frontend and move ever icon , button , drop down to fluenti 9. After working through all the errors and getting all of them fixed and v8 out of the code I no longer have a blank page. Still a few other issues with login button dissappeared but hopefully once i get that back i should be up and running again. fluenti v9 looks nicer as well. Hopefully that helps others out as well. I primarily used gpt to update the code for me. the new 4.5 version was the one that helped me discover the issue and started changing things over but I found 01 was more thorough in updating all the icons and components on the first attempt. Good luck. |
We are having a few issues with the frontend dependencies. We have been trying to keep up with vulnerabilities with packages and update as needed. We are stuck on an old version right now which is limiting us. I have seen on azure about bumping the dompurify, azure/msal-browser and vite due to issues. Trying to keep up with all this.
The issue we are seeing is we can build the frontend with no issues but it is blank page. We have gone through all the packages and versions trying to find what might be causing it. Below I have the terminal output from a working version. The 8 in the second group are the ones that do not show up for the blank page. Anyone possible know what package could cause this or possible how to resolve it.
[2025-02-19 15:22:31 -0600] [551111] [INFO] 127.0.0.1:60366 GET / 1.1 200 743 2410
[2025-02-19 15:22:31 -0600] [551111] [INFO] 127.0.0.1:60366 GET / 1.1 - - 2764
[2025-02-19 15:22:31 -0600] [551111] [INFO] 127.0.0.1:60366 GET /assets/index-e5bbb2b0.js 1.1 200 359432 18989
[2025-02-19 15:22:31 -0600] [551111] [INFO] 127.0.0.1:60366 GET /assets/index-e5bbb2b0.js 1.1 - - 19320
[2025-02-19 15:22:31 -0600] [551111] [INFO] 127.0.0.1:60378 GET /assets/vendor-1c30911e.js 1.1 200 1817273 55133
[2025-02-19 15:22:31 -0600] [551111] [INFO] 127.0.0.1:60378 GET /assets/vendor-1c30911e.js 1.1 - - 55422
[2025-02-19 15:22:32 -0600] [551111] [INFO] 127.0.0.1:60382 GET /assets/fluentui-icons-24e83cba.js 1.1 200 5669 2015
[2025-02-19 15:22:32 -0600] [551111] [INFO] 127.0.0.1:60382 GET /assets/fluentui-icons-24e83cba.js 1.1 - - 2336
[2025-02-19 15:22:32 -0600] [551111] [INFO] 127.0.0.1:60398 GET /assets/index-83f5e191.css 1.1 200 16109 2104
[2025-02-19 15:22:32 -0600] [551111] [INFO] 127.0.0.1:60398 GET /assets/index-83f5e191.css 1.1 - - 2432
[2025-02-19 15:22:32 -0600] [551111] [INFO] 127.0.0.1:60402 GET /assets/fluentui-react-a4d9aecc.js 1.1 200 387279 11011
[2025-02-19 15:22:32 -0600] [551111] [INFO] 127.0.0.1:60402 GET /assets/fluentui-react-a4d9aecc.js 1.1 - - 11284
[2025-02-19 15:22:32 -0600] [551111] [INFO] 127.0.0.1:60398 GET /favicon.ico 1.1 200 4286 1716
[2025-02-19 15:22:32 -0600] [551111] [INFO] 127.0.0.1:60398 GET /favicon.ico 1.1 - - 1964
blank page is missing these
[2025-02-19 15:22:32 -0600] [551111] [INFO] 127.0.0.1:60402 GET /auth_setup 1.1 200 492 1103
[2025-02-19 15:22:32 -0600] [551111] [INFO] 127.0.0.1:60402 GET /auth_setup 1.1 - - 1393
[2025-02-19 15:22:32 -0600] [551111] [INFO] 127.0.0.1:60402 GET /.auth/me 1.1 404 207 636
[2025-02-19 15:22:32 -0600] [551111] [INFO] 127.0.0.1:60402 GET /.auth/me 1.1 - - 956
[2025-02-19 15:22:32 -0600] [551111] [INFO] 127.0.0.1:60402 GET /containerpath 1.1 200 36 830
[2025-02-19 15:22:32 -0600] [551111] [INFO] 127.0.0.1:60402 GET /containerpath 1.1 - - 1099
[2025-02-19 15:22:32 -0600] [551111] [INFO] 127.0.0.1:60402 GET /config 1.1 200 27 885
[2025-02-19 15:22:32 -0600] [551111] [INFO] 127.0.0.1:60402 GET /config 1.1 - - 1166
The text was updated successfully, but these errors were encountered: