Impressive Work on Live Compilation Despite Type Errors
I’m actually kind of impressed you guys were able to compile these and push them live yourself with the amount of type errors
I’m actually kind of impressed you guys were able to compile these and push them live yourself with the amount of type errors
Hey Madison, Can you share what kind of errors are you having?
Madison S. keen to understand your setup. There's a good chance a tiny change to your tsconfig would fix your issues
@slater I’m using NextJS 15, React 19, default generated tsconfig, default prettier, ESlint, default Relume components (errors present during build time without any modification) I agree it does seem like something global, considering there are errors without any customization to any config.
Madison S. If you share a screenshot with the errors you’re having we could help
I figured out the error, it was actually being caused by my cursor IDE. I’m not sure the specifics, but apparently Cursor Tab/Composer has some very finicky behavior if you are using automated scripts in the background. For me, it was running a node.js script to batch directory structure organization. Apparently Cursor’s Tab/Composer features don’t play well with other tools editing their data at the same time, I believe it is due to the was Cursor indexes projects in the cloud. Basically, you automate a script, cursor changes some code in that file at the same time, if they are close enough in execution it screws up the cloud indexing syncing with the local indexing, and causes weird global errors. Apparently no serious fix yet other than to be careful and not do that. Some people have success with clearing composer history? I did not.
Madison S. If I could piggy-back off this thread and ask how you got Relume to work with NextJS 15 and React 19 in the first place? I don't know how to get around this error (see screenshot). I think it has something to do with Relume's dependency on react-day-picker which isn't playing nice with React 19(?)
Hey Connor K., New Relume package versions are pushed, upgrade them to their latest versions and let me know if you’re still getting the same errors https://www.npmjs.com/package/@relume_io/relume-ui https://www.npmjs.com/package/@relume_io/relume-tailwind
For React upgrade errors like this there are a couple of things you can do that I’ve tried in different projects. The main issue is the change of the ‘forwardRef’ prop. You can go into node_modules manually and patch the implementations using the correct updated methods for React 19, depending on the program and how tightly integrated it is this can have varying effects. I’ve seen this error before in different projects since React 19 came out, I have personally not seen this specific error come up in my Relume projects for React however, this may be specific to you. I’ve seen it in other projects and usually fix it by patching node_modules, downgrading with legacy deps if possible, or forcing other packages to upgrade using ‘—force’ with potential breaking changes that I’m okay with. Tbh Radix is going to be a much bigger issue than React-day-picker, I still don’t understand why they haven’t updated yet lol. I’m starting to get worried that specific API will get phased out before they implement an update, causing breaking changes to their library.