Bump default dependencies
Hi. I want to know if a user of refine is restricted to using the default dependencies added after project initialization with npm or will it cause dependency mismatch?
3 Replies
Hi @princemuel. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Refine is a flexible framework and it's not restricted to the default dependencies added after project initialization. You can add or update dependencies as per your project requirements. However, it's important to ensure that the added or updated dependencies are compatible with refine to avoid any potential issues.
For instance, if you want to add the
@refinedev/cli to your existing project, you can do so by adding it to your project's dependencies using npm or yarn. After that, you need to add the refine command to your scripts in your package.json file. Here's how you can do it:
or
Then, in your package.json file:
(Source: refine.dev/docs (https://refine.dev/docs/packages/documentation/cli))
Also, refine has recently migrated to a new NPM organization and is using @refinedev as the new NPM organization. As a result of this migration, all of their package names have been updated accordingly. With complete codemod support, updating package names will be effortless when migrating your refine project to v4 (Source: refine.dev/blog (https://refine.dev/blog/refine-v4-announcement)).
Remember to always check the compatibility of the dependencies you're adding or updating with refine to avoid any potential issues.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------<@738221142229385297> kapa.ai is still learning and improving, please let us how it did by reacting below
unwilling-turquoise•13mo ago
ofc you can use any version of default dependencies. but we tested on installed versions