Consider removing debounce dependency / working on node 16 #1441
mansimransingh
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I understand node 16 is past EOL - but the only reason we haven’t been able to update to latest version of flowbite-react in our next.js app is because debounce package wants node 18.
We can maybe try supporting older versions of node since this project doesn’t have a hard dependency on any particular version. (And also because sometimes it’s painfully slow to get old architecture updated but I want the new components).
To achieve this, we should consider removing debounce dependency, since it really shouldn’t have a hard requirement for node 18 (it’s like 40 lines of code).
If anybody is interested, I got around this by forking debounce, removing the node 18 requirement and defining a resolver for debounce in package.json of my app.
https://github.com/mansimransingh/debounce
Beta Was this translation helpful? Give feedback.
All reactions