babel-plugin-transform-react-remove-prop-types | Remove unnecessary React propTypes | Plugin library

This may be a silly answer. Try checking whether the task is running or any other programs interfereing the app, like an antivirus.

Finally,found the answer, maybe this will be useful for somebody. Error reffered to CopyWebpackPlugin configuration. Instead of this:

I downgraded the sqlite3 package to v5.0.0 and it rebuilt correctly. Hope this helps anyone else with the same issue.

Source: nodejs electronjs sqlite3 - use of undeclared identifier 'napi_is_detached_arraybuffer'

By default the react template uses a webpack config which is in a different directory. Replacing the build directory app by stories fixed it.

internals\webpack\webpack.base.babel.js

If this issue happens while you're linking the local version of your library in your main project to speed up the development. It might be related to "duplicate version of React".

https://reactjs.org/warnings/invalid-hook-call-warning.html

This problem can also come up when you use npm link or an equivalent. In that case, your bundler might “see” two Reacts — one in application folder and one in your library folder. Assuming myapp and mylib are sibling folders, one possible fix is to run npm link ../myapp/node_modules/react from mylib. This should make the library use the application’s React copy.

In short:

• run npm link in /your-app/node_modules/react. This should make the React's global link.
• run npm link react in /your-ui-library. This should make the library use the application’s React copy.

Short answer: yes, PropTypes are removed by default.

React/Gatsby applications works perfectly with PropTypes. The issue described is an open debate about if in production builds, these PropTypes should be removed since the code should be coherent, robust and, valid in development environment before it's deployed or build in the production environment.

If you assume that your code in development must be valid and PropType-friendly you can infer either that you can omit the PropType validation in production environment to reduce the bandwidth and improve the build/deploy times since the validation and review is done under development.

So, by default, your PropTypes will be removed in production build.

You don't need to add any extra configuration since, by default, Gatsby uses this .babelrc structure:

If your build takes longer than 10m without output this will happen.

You can use travis_wait to print something to the console each minute, as per the docs: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received

Just travis_wait {your_command} and you should be good to go.

Be aware that your build taking longer than 10m could be a indicator of a more complicated underlying problem/freeze.

I've got what's missing.

In app/javascript/packs/application.js forgot to declare:

Issue resolved. Issue was caused by running the tests by using the "jest" command in the terminal which is different from using the npm test script which also only runs the "jest" command. The difference is the former was using a higher version of Jest which I had installed globally and ended up running into issues whereas the latter used the version of jest that corresponds with the version in the package.json.