Chore: Format code

Author: Artem Sapegin

.github/ISSUE_TEMPLATE/Bug_report.md

@@ -1,28 +1,29 @@
 ---
-name: "\U0001F41B Bug report"
+name: "\U0001F41B Bug report"
 about: Something isn’t working as expected
-
 ---
 
 **Current behavior**
+
 <!-- A clear and concise description of what the bug is -->
 
 **To reproduce**
 
-<!--
-Post a link to a reproducible demo repository here.
-
-  1. Fork the example project repository: https://github.com/styleguidist/example
-     (please don’t use the main, styleguidist/react-styleguidist, repository).
-  2. Modify it to reproduce the issue.
-  3. Push to GitHub and paste the link here.
-
-Most likely you’ll find an issue yourself, while creating a demo.
-
-Make sure you’re using the latest version of React Styleguidist.
-
-💀 Issues without a demo will be closed! 💀
+<!--
+Post a link to a reproducible demo repository here.
+
+  1. Fork the example project repository: https://github.com/styleguidist/example
+     (please don’t use the main, styleguidist/react-styleguidist, repository).
+  2. Modify it to reproduce the issue.
+  3. Push to GitHub and paste the link here.
+
+Most likely you’ll find an issue yourself, while creating a demo.
+
+Make sure you’re using the latest version of React Styleguidist.
+
+💀 Issues without a demo will be closed! 💀
 -->
 
 **Expected behavior**
+
 <!-- A clear and concise description of what you expected to happen -->

.github/ISSUE_TEMPLATE/Feature_request.md

@@ -1,19 +1,22 @@
 ---
-name: "\U0001F680 Feature request"
+name: "\U0001F680 Feature request"
 about: I have a suggestion (and might want to implement myself)
-
 ---
 
 <!-- Consider opening a pull request instead: it’s a more productive way to discuss new features -->
 
 **The problem**
+
 <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
 
 **Proposed solution**
+
 <!-- A clear and concise description of what you want to happen. Add any considered drawbacks. -->
 
 **Alternative solutions**
+
 <!-- A clear and concise description of any alternative solutions or features you’ve considered. -->
 
 **Additional context**
+
 <!-- Add any other context or screenshots about the feature request here. -->

.github/ISSUE_TEMPLATE/Question.md

@@ -1,7 +1,6 @@
 ---
-name: "\U0001F914 Support question"
+name: "\U0001F914 Support question"
 about: I have a question or don’t know how to do something
-
 ---
 
 --------------^ Click “Preview”!
@@ -10,7 +9,7 @@ If you have a support question, ask it on [Stack Overflow](https://stackoverflow
 
 Before submitting a new question, make sure you:
 
-* Searched existing  [Stack Overflow questions](https://stackoverflow.com/questions/tagged/react-styleguidist).
+* Searched existing [Stack Overflow questions](https://stackoverflow.com/questions/tagged/react-styleguidist).
 * Searched opened and closed [GitHub issues](https://github.com/styleguidist/react-styleguidist/issues?utf8=%E2%9C%93&q=is%3Aissue).
 * Read [the documentation](https://react-styleguidist.js.org/docs/getting-started.html).
 * Googled your question.

.github/ISSUE_TEMPLATE/Support.md

@@ -1,7 +1,6 @@
 ---
-name: "\U0001F984 Support Styleguidist development"
+name: "\U0001F984 Support Styleguidist development"
 about: I want to support efforts in maintaining this community-driven project
-
 ---
 
 --------------^ Click “Preview”!
@@ -10,11 +9,11 @@ Developing and maintaining an open source project is a big effort. Styleguidist
 
 There are two ways you can help:
 
-1. Help develop and maintain the project:
+1.  Help develop and maintain the project:
 
-  * Answer questions in [GitHub issues](https://github.com/styleguidist/react-styleguidist/issues) and [Stack Overflow](https://stackoverflow.com/questions/tagged/react-styleguidist).
-  * Review [pull requests](https://github.com/styleguidist/react-styleguidist/pulls).
-  * Fix bugs and add new features.
-  * Write articles and talk about Styleguidist on conferences and meetups (we’re always happy to review your texts and slides).
+* Answer questions in [GitHub issues](https://github.com/styleguidist/react-styleguidist/issues) and [Stack Overflow](https://stackoverflow.com/questions/tagged/react-styleguidist).
+* Review [pull requests](https://github.com/styleguidist/react-styleguidist/pulls).
+* Fix bugs and add new features.
+* Write articles and talk about Styleguidist on conferences and meetups (we’re always happy to review your texts and slides).
 
-2. Donate via [Open Collective](https://opencollective.com/styleguidist).
+2.  Donate via [Open Collective](https://opencollective.com/styleguidist).

scripts/make-webpack-config.js

@@ -96,13 +96,14 @@ module.exports = function(config, env) {
 				compress: {
 					keep_fnames: true,
 					warnings: false,
-          			/**
-					  * We disable 'reduce_funcs' for keeping uglify from inlining Preact's VNode.
-					  * If enabled, the 'new VNode()' is replaced with a anonymous 'function(){}',
-					  * which is problematic for 'preact-compat', since it extends the VNode prototype
-					  * to accomodate React's API.
-					  * */
-					reduce_funcs: false
+					/*
+					 * Disable reduce_funcs to keep UglifyJS from inlining
+					 * Preact's VNode. If enabled, the 'new VNode()' is replaced
+					 * with a anonymous 'function(){}', which is problematic for
+					 * preact-compat, since it extends the VNode prototype to
+					 * accomodate React's API.
+					 */
+					reduce_funcs: false,
 				},
 				mangle: {
 					keep_fnames: true,