Casbin Forum runs on Casnode, the open-source Discourse-style forum. Try the Casnode demo →
Casbin Forum
5views
3users
1 minread

I think the DX (developer experience) of working on the frontend can be improved a lot - i recently created https://github.com/casdoor/casdoor/discussions/4486 about the timing of the frontend build but the real motivation is to make a "red carpet" for working on the frontend itself

this speaks also to increasing the quantity and quality of future frontend contributions

we are trying to use casdoor at our company and we are finding all sorts of bugs (frontend and backend) - i wont pollute this channel with the bug reports but one of the bugs we found recently was at least a frontend bug (probably also a backend bug - our backend go guy literally re-implemented the logic from a casdoor endpoint in one of our backend endpoints because using casdoor frontend you can work around the constraint) - so i cloned down casdoor and tried to see if i can get it running.... immediately had to google craco - started wondering why not vite

we use craco for a reason, dig git history if interested. maybe other ways like vite work too or even better. but there's a cost to migrate.

just need to compare the migrate cost with the gain

sure, if it is an open question i can help investigate like create a branch on my fork with some exploring migration paths

glad to see you guys use casdoor, and maybe you can start contributing to some more agreed small bugs or features

did you find any bugs, which can be fixed in the repo?

i just got as far as cloning the repo and realizing that i would like some better dx for frontend before i even begin - probably soon i will try to identify the group thing that i came to fix

1 / 15
Sep 2025