You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We'd always love contributions to further improve the webpack / webpack-contrib ecosystem!
3
+
We'd always love contributions to further improve the webpack / webpack-contrib ecosystem!
4
4
Here are the guidelines we'd like you to follow:
5
5
6
-
*[Questions and Problems](#question)
7
-
*[Issues and Bugs](#issue)
8
-
*[Feature Requests](#feature)
9
-
*[Pull Request Submission Guidelines](#submit-pr)
10
-
*[Commit Message Conventions](#commit)
6
+
-[Questions and Problems](#question)
7
+
-[Issues and Bugs](#issue)
8
+
-[Feature Requests](#feature)
9
+
-[Pull Request Submission Guidelines](#submit-pr)
10
+
-[Commit Message Conventions](#commit)
11
11
12
-
###<aname="question"></a> Got a Question or Problem?
12
+
## <aname="question"></a> Got a Question or Problem?
13
13
14
-
Please submit support requests and questions to StackOverflow using the tag [[webpack]](http://stackoverflow.com/tags/webpack).
15
-
StackOverflow is better suited for this kind of support though you may also inquire in [Webpack Gitter](https://gitter.im/webpack/webpack).
14
+
Please submit support requests and questions to StackOverflow using the tag [[webpack]](http://stackoverflow.com/tags/webpack).
15
+
StackOverflow is better suited for this kind of support though you may also inquire in [Webpack Gitter](https://gitter.im/webpack/webpack).
16
16
The issue tracker is for bug reports and feature discussions.
17
17
18
-
###<aname="issue"></a> Found an Issue or Bug?
18
+
## <aname="issue"></a> Found an Issue or Bug?
19
19
20
20
Before you submit an issue, please search the issue tracker, maybe an issue for your problem already exists and the discussion might inform you of workarounds readily available.
21
21
@@ -31,13 +31,13 @@ We will be insisting on a minimal reproduce scenario in order to save maintainer
31
31
32
32
Unfortunately, we are not able to investigate / fix bugs without a minimal reproduction, so if we don't hear back from you we are going to close an issue that doesn't have enough info to be reproduced.
33
33
34
-
###<aname="feature"></a> Feature Requests?
34
+
## <aname="feature"></a> Feature Requests?
35
35
36
-
You can *request* a new feature by creating an issue on Github.
36
+
You can _request_ a new feature by creating an issue on Github.
37
37
38
-
If you would like to *implement* a new feature, please submit an issue with a proposal for your work `first`, to be sure that particular makes sense for the project.
38
+
If you would like to _implement_ a new feature, please submit an issue with a proposal for your work `first`, to be sure that particular makes sense for the project.
Before you submit your Pull Request (PR) consider the following guidelines:
43
43
@@ -46,9 +46,9 @@ Before you submit your Pull Request (PR) consider the following guidelines:
46
46
- Fill out our `Pull Request Template`. Your pull request will not be considered if it is ignored.
47
47
- Please sign the `Contributor License Agreement (CLA)` when a pull request is opened. We cannot accept your pull request without this. Make sure you sign with the primary email address associated with your local / github account.
|**`cacheContext`**|`{String}`|`undefined`| Allows you to override the default cache context in order to generate the cache relatively to a path. By default it will use absolute paths |
52
-
|**`cacheKey`**|`{Function(options, request) -> {String}}`|`undefined`| Allows you to override default cache key generator |
53
-
|**`cacheDirectory`**|`{String}`|`findCacheDir({ name: 'cache-loader' }) or os.tmpdir()`| Provide a cache directory where cache items should be stored (used for default read/write implementation) |
54
-
|**`cacheIdentifier`**|`{String}`|`cache-loader:{version} {process.env.NODE_ENV}`| Provide an invalidation identifier which is used to generate the hashes. You can use it for extra dependencies of loaders (used for default read/write implementation) |
55
-
|**`write`**|`{Function(cacheKey, data, callback) -> {void}}`|`undefined`| Allows you to override default write cache data to file (e.g. Redis, memcached) |
56
-
|**`read`**|`{Function(cacheKey, callback) -> {void}}`|`undefined`| Allows you to override default read cache data from file |
57
-
|**`readOnly`**|`{Boolean}`|`false`| Allows you to override default value and make the cache read only (useful for some environments where you don't want the cache to be updated, only read from it) |
|**`cacheContext`**|`{String}`|`undefined`| Allows you to override the default cache context in order to generate the cache relatively to a path. By default it will use absolute paths |
52
+
|**`cacheKey`**|`{Function(options, request) -> {String}}`|`undefined`| Allows you to override default cache key generator |
53
+
|**`cacheDirectory`**|`{String}`|`findCacheDir({ name: 'cache-loader' }) or os.tmpdir()`| Provide a cache directory where cache items should be stored (used for default read/write implementation)|
54
+
|**`cacheIdentifier`**|`{String}`|`cache-loader:{version} {process.env.NODE_ENV}`| Provide an invalidation identifier which is used to generate the hashes. You can use it for extra dependencies of loaders (used for default read/write implementation) |
55
+
|**`write`**|`{Function(cacheKey, data, callback) -> {void}}`|`undefined`| Allows you to override default write cache data to file (e.g. Redis, memcached) |
56
+
|**`read`**|`{Function(cacheKey, callback) -> {void}}`|`undefined`| Allows you to override default read cache data from file |
57
+
|**`readOnly`**|`{Boolean}`|`false`| Allows you to override default value and make the cache read only (useful for some environments where you don't want the cache to be updated, only read from it) |
58
58
59
59
## Examples
60
60
@@ -167,8 +167,8 @@ Please take a moment to read our contributing guidelines if you haven't yet done
0 commit comments