It'd be nice to provide some examples that demonstrates the way of testing custom React hooks. It can also be documented as part of #33.

The project doesn't allow using dynamic imports. It's a huge issue whenever someone is about to use lazy loading.

To resolve the issue:

• install babel-dynamic-import plugin,
• also add babel-eslint so that get rid of the parsing error,
• create an example inside Examples to ensure that it works as expected.

Looked at the generic parts of the boilerplate (e.g. vscode, eslint, prettier configs) and noticed it differs from what we use elsewhere: https://github.com/c-hive/js-boilerplate

Unless this is on purpose it would be nice to align these. AFAICT the result would actually be the same, but I did some cleanup since the version you're currently using.

Let's use the fancy badges in the README. Required ones:

• build passes/fails,
• test coverage.

Unfortunately, CircleCI doesn't support displaying the coverage badge by default. As a result, it might be reasonable to move to another provider - TravisCI is the preferable one along with Coveralls as the setup is quite straightforward.

https://github.com/testing-library/react-testing-library

What is the advantage of putting babel presets in a .babelrc.

{
    "presets": ["@babel/preset-env", "@babel/preset-react"],

or including them in webpack config in the modules section?

{
            test: /\.js$/i,
            use: [
                { 
                    loader: 'babel-loader',
                    options: { presets: ['@babel/env', '@babel/react'] }
                }
            ],

Create a useFetch hook that comprises the following elements:

• provides an abstract interface that handles the data fetching and parsing,
• uses the built-in JS fetch(it might be different based on the users' preferences),
• sets an isLoading property to false/true based on the process.

Example gist.

Let's adapt a comprehensive documentation to the project that contains:

• installation / setup,
• configurations,
• frameworks.

TODOs:

• investigate docz and mdx,
• setup auto-deployment on a specific branch(?).

Extracted from #27.

Referring to the specified issue above, create a free plan on TravisCI and also setup the same building blocks as before:

• test coverage,
• lint.

If I'm reading the readme right (https://github.com/yannickcr/eslint-plugin-react), using

    "plugins": [
        "react",
    ],

means you'd have to specify rules individually. Instead, it is recommended to use

  extends: [
    "plugin:react/recommended",
  ],

From my testing, it looks like the rules are in effect when using extends without using plugins.

The React team has just released the official hooks plugin. It seemingly in the stable version, thus adapt it to the boilerplate.

The script property of package.json might be extended with other useful ones:

• test:watchAll to run all the tests and "keep an eye" on them,
• test:coverage to display the result of the coverage measurement along with the amount of passed/not passed tests,
• test:only to run all the tests without any specific impact.

Proposals are welcome.