Glide-data-grid breaks project

[SamilErd]

Hello everyone, i have a bug when using a data-editor component, it installs its associated library which is glide data grid but this one breaks the project, can't reflex run again, the first compiling runs smooth, but after that one, whatever the changes are, even with just a server stopping, it just wont run again.

the data_editor is a simple data_editor with sample values, i respect the columns and data fields type requirements, and the bug happens only when i render the data_editor since it wont install the library if i dont render it, kind of feel like its the installing of it that breaks it.

Specifics (please complete the following information):

• Python Version: 3.11
• Reflex Version: 0.3.5
• OS: Windows
• Browser (Optional): Opera GX

Additional context I use a fork of llama-index 0.9.13 to make compatible with reflex ( since reflex only supports sqlmodel 0.0.8 for now ) even if i doubt that would do anything.

[ElijahAhianyo]

from the look of this, There seem to be some dependency conflict in your project. The data editor component uses glide ^5.3.0 which depends on marked@^4.0.10. Is there a library youre using that also installs marked?

[SamilErd]

I mean as far as i know, JS Libraries are only handled by reflex itself, the only external libraries are python libraries, and don't see any trace of marked, so a conflict between 2 internal libraries of reflex ?

[ElijahAhianyo]

The possibility of dependency conflicts may arise when you wrap react components that install dependencies shared by two libraries with different requirements. Reflex in itself doesn't handle upstream dependency conflict. Out of curiosity, have you wrapped any react components in your project?

[SamilErd]

i dont use any other wrapped react components :/

[ElijahAhianyo]

i dont use any other wrapped react components :/

can you post the content of your package.json file in .web > package.json

[SamilErd]

{ "name": "reflex", "scripts": { "dev": "next dev", "export": "next build", "export-sitemap": "next build && next-sitemap", "prod": "next start" }, "dependencies": { "@chakra-ui/icons": "^2.0.19", "@chakra-ui/react": "^2.6.1", "@chakra-ui/system": "^2.5.7", "@emotion/react": "^11.11.0", "@emotion/styled": "^11.11.0", "@glideapps/glide-data-grid": "^5.3.0", "axios": "1.4.0", "focus-visible": "^5.2.0", "framer-motion": "^10.16.4", "gridjs": "^6.0.6", "gridjs-react": "^6.0.1", "json5": "2.2.3", "lodash": "^4.17.21", "marked": "^11.1.0", "next": "14.0.1", "next-sitemap": "4.1.8", "next-themes": "0.2.0", "react": "18.2.0", "react-debounce-input": "^3.3.0", "react-dom": "18.2.0", "react-dropzone": "^14.2.3", "react-responsive-carousel": "^3.2.23", "socket.io-client": "4.6.1", "tailwindcss": "^3.3.2", "universal-cookie": "4.0.4" }, "devDependencies": { "autoprefixer": "10.4.14", "postcss": "8.4.31" } }

[Evenzel]

I also have this problem after the v0.3.7 update. This didn't happen in v0.3.6.

[SamilErd]

I also have this problem after the v0.3.7 update. This didn't happen in v0.3.6.

Well, this wont help for the investigation but i'm on 0.3.5 :(

[SamilErd]

Any news regarding this issue ? still have it 0.3.8 :/

[ElijahAhianyo]

This issue should be fixed now (as of the latest reflex version v0.4.5). Closing this issue, feel free to reopen if need be