update some packages to avoid --legacy-peer-deps

[EnzoVezzaro]

• Fixes Fix dependency issues #63 .

Changes proposed in this PR:

• making some changes for dep updates

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
dbs-ui-lib	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 5, 2023 8:35am

[EnzoVezzaro]

Updated dependencies and some tools.

All commands work without errors:

• npm i without --legacy-peer-deps
• npm run build creates a dist folder with newest build
• npm run storybook runs storybook
• npm run build-storybook creates a static version of storybook

nevertheless when importing the build folder manually into the demo project, it doesn't seem to work properly (probably related to the new updates). This needs further investigation.

I also see that the vercel deployment is failing for some reason while in local builds correctly:

@jamiehewitt15 can you confirm that all the commands work for you too please.

@mihaisc can you please update the vercel app for these changes. The only change should be removing the --legacy-peer-deps flag from npm i and make sure all the packages are updated based on the latest package.json. Locally it builds correctly, so I'm not really sure why is failing on vercel (preview).

[mihaisc]

Fixed, we should prioritise this so we unlock the other prs

[EnzoVezzaro]

@jamiehewitt15 please for testing delete your local node_modules and start this PR from scratch before testing the commands.

[jamiehewitt15]

Tested locally and it works great. Also pulled the changes into my other branch and it works there too, fixing the vercel preview deployment