Index: node_modules/recharts/CONTRIBUTING.md
===================================================================
--- node_modules/recharts/CONTRIBUTING.md	(revision a762898ecd37a452c782821d4c2c4955c6ed2521)
+++ node_modules/recharts/CONTRIBUTING.md	(revision a762898ecd37a452c782821d4c2c4955c6ed2521)
@@ -0,0 +1,90 @@
+# Contributing to Recharts
+
+We'd love for you to contribute to our source code and to make Recharts even better than it is today!
+
+If you want to know how to develop then check out the [Development Guide](/DEVELOPING.md).
+
+Here are the guidelines we'd like you to follow:
+
+## Ongoing Initiatives
+
+We use Github Discussion to organize our discussion along new initiatives and organize ourselves. Please do check the [announcements](https://github.com/recharts/recharts/discussions/categories/announcements) section for an overview of recent initiatives.
+
+Also feel free to join us on Slack: https://recharts.slack.com/archives/C042Q5K5UDC
+
+## <a name="issues"></a>Issues and Bugs
+
+### Where to Find Known Issues
+
+We will be using [GitHub Issues](https://github.com/recharts/recharts/issues) for our bugs and feature requests. We will keep a close eye on this and try to make it clear when we have an internal fix in progress. Before filing a new task, try to make sure your problem doesn't already exist.
+
+### Reporting New Issues
+
+The best way to get your bug fixed is to provide a reduced test case. codesandbox provide a way to give live examples. You can fork our example in [recharts.github.io](https://recharts.github.io/) to show your case.
+
+## <a name="testing"></a>Testing
+
+We do cherish tests. They help us move swiftly, and release with confidence.
+In our repo, you will find three types of tests: Unit tests, rendering tests with RTL, and user interaction tests in storybook.
+Wherever possible we prefer the simplest tests - unit tests. Only where needed / useful we would use RTL or storybook tests.
+
+### Unit tests
+
+When writing new code, aim for 100% unit test code coverage.
+
+When implementing a new feature we would prefer to extract pure helper function for data processing.
+Such functions are found in a few utils files. An example is `test/util/ShallowEqual.spec.ts`.
+
+Unit testing in recharts has some specialties, please see [Recharts unit tests README](test/README.md) for more information.
+
+### React Testing Library
+
+Some behaviour must be tested upon rendering, such as interactions between components (Line, Tooltip), see `test/component/Tooltip.visibility.spec.tsx` for an example.
+
+### Storybook Test Runner
+
+Storybook also has a great interface for adding tests. By default every story in storybook is a smoke test (rendering without error logs means the test passed). Additionally, it is possible to add actual tests as play functions with an assert to a story. This will often be easier than using React Testing Library, because the natural test debugging tool is Storybook itself. See for example `storybook/stories/Examples/cartesian/ReferenceLine/ReferenceLineIfOverflow.stories.tsx`
+
+### Mutation tests
+
+We have [stryker](https://stryker-mutator.io/docs/) installed and ready to use for mutation testing.
+
+If you want to run mutation test be aware that these may take hours! A single file will take 15 minutes or more.
+
+To run, update the list of checked files in `./stryker.config.mjs` and then run with `npm run test-mutation`.
+
+You will find test output in your console, and also HTML report in the `./reports` folder.
+
+## <a name="pr"></a>Pull Requests
+
+**Working on your first Pull Request?** You can learn how from this _free_ series [How to Contribute to an Open Source Project on GitHub](https://app.egghead.io/playlists/how-to-contribute-to-an-open-source-project-on-github)
+
+_Before_ submitting a pull request, please make sure the following is done…
+
+- Search [GitHub](https://github.com/recharts/recharts/pulls) for an open or closed Pull Request that relates to your submission. You don't want to duplicate effort.
+
+- Fork the repo and create your branch from `main`.
+- If you have added functionality or changed existing functionality, be sure to add a test. Ideally a unit test for helper function, or a test that includes rendering with RTL.
+- If you've changed APIs, make sure that the stories in Storybook are working as expected.
+- Ensure the test suite passes (`npm run test`).
+- Make sure your code lints (`npm run lint`) - we've done our best to make sure these rules match our internal linting guidelines.
+
+## <a name="code"></a>Code Guide
+
+Our linter will catch most styling issues that may exist in your code.
+You can check the status of your code styling by running: `npm run lint`
+
+However, there are still some styles that the linter cannot pick up. If you are unsure about something, looking at [Airbnb's Style Guide](https://github.com/airbnb/javascript) will guide you in the right direction.
+
+## Types
+
+We use TypeScript for type safety. Some rules to follow:
+
+- Never use `any` type. Implicit or explicit.
+- Prefer `unknown` over `any`. Refine the type.
+- Type your function parameters and return values explicitly, do not rely on implicit any or inference. Exceptions are React components and trivial functions where the types are obvious.
+- Do not use `as` type assertions, ever. The only exception is `as const`.
+
+## <a name="license"></a>License
+
+By contributing to Recharts, you agree that your contributions will be licensed under its MIT license.