Alessandro

I hope the dev upgrade it because this project is useful (at least in my activities) and it will be bad if this project become "not maintained". We will see...

Sin! It's a nice project...but to continue with the fix as you mentioned it's kinda only the merge...so quite easy I guess...hoping that will be done, just to have React...

> npm ERR! Could not resolve dependency: npm ERR! peer react@"^17.0.0 || ^16.3.0 || ^15.5.4" from [email protected] > > I'm getting this error in a React (v18) project. Is there...

Come on guys, please do this simple merge :) Im joking but it's important for all the people that kinda continue to use this nice repo and fixes the deps...

> npm solution is to add to your package.json: > > ```json > "overrides": { > "react-json-view": { > "react": "18.1.0", > "react-dom": "18.1.0" > } > } > ```...

Reply to myself, you can use this workaround to compile the project without issue: `"react-json-view-compare": { "react": "18.2.0", "react-dom": "18.2.0" } }`

Guys, as you know the command `--legacy-peer-deps` is not the best solution and if you want to allow compile without using that one, you can use the "overrides" object into...

Hi, idk if it is related but I've also this one about DoS vulnerability: Introduced through: [email protected] > @jimp/[email protected] > @jimp/[email protected] > [email protected] Remediation (provided by Snyk) Upgrade `file-type` to...

Hi kuhe, thanks for the update. At the first touch seems that passing through the backend with the 3.496.0 the credentials are correctly retrieved, instead using FE side, nope. Anyway...

Some as the first post. I've just updated the package with the last version released and into the console I received the same error: `Uncaught SyntaxError: The requested module '/node_modules/.vite/deps/@aws-sdk_credential-providers.js?v=4d2ccf96'...