mark-todd
mark-todd
So the thing is we've already excluded the node modules folder in tsconfig, here's the config: ```json { "compilerOptions": { "esModuleInterop": true, "jsx": "react", "module": "esnext", "moduleResolution": "node", "lib": ["es5",...
#22 - This issue is possibly related, we have strict enabled in our repo
I found from here that it can be resolved by adding "skipLibCheck" which prevents checking of d.ts files, but this is not really ideal, as this applies to all d.ts...
Interesting - thanks for checking this out! Is this because the 5xx errors are raised at the level below the Scopus API? I suppose one thing that wouldn't be out...
I would say there are a couple of good options: First is to increase versions of d3-interpolate and d3-scale - these are currently on old versions of these subpackages. Failing...
Update: After some investigation I found a simple version increase on these d3 packages would do the trick! (Please see attached PR)
Dependabot also has a PR for this it turns out #3009
Hi @G-Rath - thanks for the detailed response! Option 1 looks pretty good to me - is there any reason not to make a major release for this? If a...
@G-Rath Hmm true - based on this comment: https://github.com/d3/d3-color/issues/108#issuecomment-1275818206 ...it seems like the v2 with fix version already exists. It won't be on npm, but it could be imported to...
Yeah I agree with @gergokee on this - I know there are backwards compatibility concerns with the ESM part, but for people trying to start using recharts (and a lot...