react-dropzone 14.2.9 → 14.2.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -0
- package/package.json +9 -4
- package/CONTRIBUTING.md +0 -135
package/README.md
CHANGED
|
@@ -424,5 +424,8 @@ Become a sponsor and get your logo on our README on Github with a link to your s
|
|
|
424
424
|
### Hosting
|
|
425
425
|
[react-dropzone.js.org](https://react-dropzone.js.org/) hosting provided by [netlify](https://www.netlify.com/).
|
|
426
426
|
|
|
427
|
+
## Contribute
|
|
428
|
+
Checkout the organization [CONTRIBUTING.md](https://github.com/react-dropzone/.github/blob/main/CONTRIBUTING.md).
|
|
429
|
+
|
|
427
430
|
## License
|
|
428
431
|
MIT
|
package/package.json
CHANGED
|
@@ -5,9 +5,14 @@
|
|
|
5
5
|
"module": "dist/es/index.js",
|
|
6
6
|
"exports": {
|
|
7
7
|
".": {
|
|
8
|
-
"import":
|
|
9
|
-
|
|
10
|
-
|
|
8
|
+
"import": {
|
|
9
|
+
"types": "./typings/react-dropzone.d.ts",
|
|
10
|
+
"default": "./dist/es/index.js"
|
|
11
|
+
},
|
|
12
|
+
"require": {
|
|
13
|
+
"types": "./typings/react-dropzone.d.ts",
|
|
14
|
+
"default": "./dist/index.js"
|
|
15
|
+
}
|
|
11
16
|
}
|
|
12
17
|
},
|
|
13
18
|
"typesVersions": {
|
|
@@ -185,7 +190,7 @@
|
|
|
185
190
|
"webpack-blocks": "^2.1.0"
|
|
186
191
|
},
|
|
187
192
|
"typings": "typings/react-dropzone.d.ts",
|
|
188
|
-
"version": "14.2.
|
|
193
|
+
"version": "14.2.10",
|
|
189
194
|
"engines": {
|
|
190
195
|
"node": ">= 10.13"
|
|
191
196
|
},
|
package/CONTRIBUTING.md
DELETED
|
@@ -1,135 +0,0 @@
|
|
|
1
|
-
# Contributing
|
|
2
|
-
|
|
3
|
-
First off, thanks for taking the time to contribute!
|
|
4
|
-
|
|
5
|
-
All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions.
|
|
6
|
-
|
|
7
|
-
And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
|
|
8
|
-
* Star the project
|
|
9
|
-
* Refer this project in your project's readme
|
|
10
|
-
* Mention the project at local meetups and tell your friends/colleagues
|
|
11
|
-
* Become a sponsor
|
|
12
|
-
|
|
13
|
-
## Table of Contents
|
|
14
|
-
|
|
15
|
-
* [Code of Conduct](#code-of-conduct)
|
|
16
|
-
* [I Have a Question](#i-have-a-question)
|
|
17
|
-
* [I Want To Contribute](#i-want-to-contribute)
|
|
18
|
-
* [Reporting Bugs](#reporting-bugs)
|
|
19
|
-
* [Suggesting Enhancements](#suggesting-enhancements)
|
|
20
|
-
* [Your First Code Contribution](#your-first-code-contribution)
|
|
21
|
-
* [Styleguides](#styleguides)
|
|
22
|
-
* [Join The Project Team](#join-the-project-team)
|
|
23
|
-
|
|
24
|
-
## Code of Conduct
|
|
25
|
-
|
|
26
|
-
This project and everyone participating in it is governed by the
|
|
27
|
-
[Code of Conduct](https://github.com/react-dropzone/react-dropzone?tab=coc-ov-file#readme).
|
|
28
|
-
By participating, you are expected to uphold this code. Please report unacceptable behavior
|
|
29
|
-
to rolandjitsu@gmail.com.
|
|
30
|
-
|
|
31
|
-
## I Have a Question
|
|
32
|
-
|
|
33
|
-
If you want to ask a question, we assume that you have read the available [Documentation](https://react-dropzone.js.org/).
|
|
34
|
-
|
|
35
|
-
Before you ask a question, it is best to search for existing [Issues](/issues) or [Discussions](/discussions) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
|
|
36
|
-
|
|
37
|
-
If you then still feel the need to ask a question and need clarification, we recommend the following:
|
|
38
|
-
|
|
39
|
-
* Open an [Issue](/issues/new).
|
|
40
|
-
* Provide as much context as you can about what you're running into.
|
|
41
|
-
* Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
|
|
42
|
-
|
|
43
|
-
We will then take care of the issue as soon as possible.
|
|
44
|
-
|
|
45
|
-
## I Want To Contribute
|
|
46
|
-
|
|
47
|
-
### Reporting Bugs
|
|
48
|
-
|
|
49
|
-
#### Before Submitting a Bug Report
|
|
50
|
-
|
|
51
|
-
A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
|
|
52
|
-
|
|
53
|
-
* Make sure that you are using the latest version.
|
|
54
|
-
* Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://react-dropzone.js.org/). If you are looking for support, you might want to check [this section](#i-have-a-question)).
|
|
55
|
-
* To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](issues?q=label%3Abug).
|
|
56
|
-
* Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
|
|
57
|
-
* Collect information about the bug:
|
|
58
|
-
* Stack trace (Traceback)
|
|
59
|
-
* OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
|
|
60
|
-
* Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant.
|
|
61
|
-
* Possibly your input and the output
|
|
62
|
-
* Can you reliably reproduce the issue? And can you also reproduce it with older versions?
|
|
63
|
-
|
|
64
|
-
#### How Do I Submit a Good Bug Report?
|
|
65
|
-
|
|
66
|
-
We use GitHub issues to track bugs and errors. If you run into an issue with the project, open an [Issue](/issues/new), select the `Bug Report` and fill in all the details.
|
|
67
|
-
|
|
68
|
-
Once it's filed:
|
|
69
|
-
|
|
70
|
-
* The project team will label the issue accordingly.
|
|
71
|
-
* A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as `needs example`. Bugs with the `needs example` tag will not be addressed until they are reproduced.
|
|
72
|
-
* If the team is able to reproduce the issue, it will be marked `needs investigation`, as well as possibly other tags (such as `in progress`), and the issue will be left to be [implemented by someone](#your-first-code-contribution).
|
|
73
|
-
|
|
74
|
-
### Suggesting Enhancements
|
|
75
|
-
|
|
76
|
-
This section guides you through submitting an enhancement suggestion for this project, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
|
|
77
|
-
|
|
78
|
-
#### Before Submitting an Enhancement
|
|
79
|
-
|
|
80
|
-
* Make sure that you are using the latest version.
|
|
81
|
-
* Read the [documentation](https://react-dropzone.js.org/) carefully and find out if the functionality is already covered, maybe by an individual configuration.
|
|
82
|
-
* Perform a [search](/issues) to see if the enhancement has already been suggested (filter by the `enhancement` label). If it has, add a comment to the existing issue instead of opening a new one.
|
|
83
|
-
* Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
|
|
84
|
-
|
|
85
|
-
#### How Do I Submit a Good Enhancement Suggestion?
|
|
86
|
-
|
|
87
|
-
Enhancement suggestions are tracked as [GitHub issues](/issues). If you have a suggestion, open an [Issue](/issues/new), select the `Feature Request` and fill in all the details.
|
|
88
|
-
|
|
89
|
-
### Your First Code Contribution
|
|
90
|
-
|
|
91
|
-
Make sure your node version is at least 18, then:
|
|
92
|
-
|
|
93
|
-
1. Fork this repo
|
|
94
|
-
2. Clone your fork:
|
|
95
|
-
```bash
|
|
96
|
-
git clone https://github.com/myusername/react-dropzone.git
|
|
97
|
-
```
|
|
98
|
-
3. Install system dependencies (needed for local development):
|
|
99
|
-
```bash
|
|
100
|
-
# macOS
|
|
101
|
-
brew install libpng libimagequant
|
|
102
|
-
# Linux
|
|
103
|
-
sudo apt-get install -y libpng-dev libimagequant-dev
|
|
104
|
-
```
|
|
105
|
-
4. Install project dependencies:
|
|
106
|
-
```bash
|
|
107
|
-
yarn install
|
|
108
|
-
```
|
|
109
|
-
5. Create a new branch:
|
|
110
|
-
```bash
|
|
111
|
-
git checkout -b fix/fix-some-bug
|
|
112
|
-
```
|
|
113
|
-
6. Start hacking
|
|
114
|
-
7. Commit and push your code
|
|
115
|
-
8. Make a PR
|
|
116
|
-
|
|
117
|
-
**NOTE** If you're using Apple silicon, you'll need to install Rosetta 2 (see [imagemin/pngquant-bin#121](https://github.com/imagemin/pngquant-bin/issues/121) and [SO](https://stackoverflow.com/a/66662497/1092007)):
|
|
118
|
-
```bash
|
|
119
|
-
/usr/sbin/softwareupdate --install-rosetta
|
|
120
|
-
```
|
|
121
|
-
|
|
122
|
-
## Styleguides
|
|
123
|
-
|
|
124
|
-
When you commit we'll make sure everything is formatted according to our styleguide, so don't worry to much about it.
|
|
125
|
-
|
|
126
|
-
### Commit Messages
|
|
127
|
-
|
|
128
|
-
Please follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) spec.
|
|
129
|
-
|
|
130
|
-
## Join The Project Team
|
|
131
|
-
|
|
132
|
-
Send an email to rolandjitsu@gmail.com and see how you can become a project member.
|
|
133
|
-
|
|
134
|
-
## Attribution
|
|
135
|
-
This guide is based on the **contributing.md**. [Make your own](https://contributing.md/)!
|