FAQ#

npm install or yarn install errors#


Causes of npm install or yarn install issue can be due to various things which include:

  • Missing or inappropriate dependencies like node or some other environmental issues
  • Dependency resolved by package manager (npm/yarn) conflict with other installed dependency
  • The dependency of the package we use have an internal issue or that dependency has some issue with your environment
  • Package or dependency of the package requires some additional step or configuration to work in your environment
  • Downloaded package is broken or is tampered with

To resolve such installation issues:

  • Please re-download fresh package/zip from ThemeForest and perform installation again.
  • Please make sure you are using LTS version of node which is recommended and not one with latest features.
  • The dependency of the package we use have an internal issue or that dependency has some issue with your environment
  • run yarn cache clean or npm cache clean
  • Try using yarn if possible (Recommended)

After following above steps, if you are getting the error please raise support at our support portal with the below details:

  • Your OS information, Node version, npm/yarn version, Template/Package version
  • Mention if you are able to run fresh react project using CRA without our template
  • Attach log file of error you are getting in your console (Provide full log)
  • Mention the commands you are running
  • Mention If you have any other machine, are you able to run our template in that machine

npm/yarn installation warnings#


You might get some warnings while running npm install or yarn install like below:

info fsevents@2.3.1: The platform "win32" is incompatible with this module.
info "fsevents@2.3.1" is an optional dependency and failed compatibility check. Excluding it from installation.
info fsevents@1.2.13: The platform "win32" is incompatible with this module.
info "fsevents@1.2.13" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning " > @uppy/react@1.11.2" has unmet peer dependency "@uppy/core@^1.0.0".
warning "@uppy/react > @uppy/file-input@1.4.22" has unmet peer dependency "@uppy/core@^1.0.0".

The warnings you are receiving while installing is from library/packages we used.

We always keep our packages up to date when we make major release. However, the writer of that package may use an older dependency that is no longer maintained for backward compatibility or any other code related issue. But, that's not an issue. Those packages will work fine with our template.

If you like to try you can install these packages in fresh CRA project without our template you will still get the same warnings.

How to update logo and text#


You can update the logo and text from themeConfig.js file. Please update these properties app.appName and app.appLogoImage to update the text and logo.

Why we removed agGrid#


In our latest version we have removed agGrid. This is because agGrid was not completely free as it requires another purchase to get access to all of its features. Since reactstrap provides a decent table component and we have also added react-data-table-component (3rd party) package. it is easier to use them over agGrid and also you don't require any additional purchase.

So, we highly recommend you use reactstrap table component for your projects over any other table.

Why we removed Data List#


We have removed data list in favour of more practical table UI and UX which you can find in user list and invoice list

You can still keep using data list using old files but, as we have deprecated it we will not be able provide support for it.

Why we removed Auth0 & Firebase#


We have removed both Auth0 & Firebase in our latest update as most developers prefer JWT & it was unmaintainable because with every new update of firebase code would break and it got messy for developers who don't need all three authentication methods.

eCommerce Shop filter's not working#


We're using our own data with a fake database. Filtering on small size of data is not appropriate so we disabled filters and kept just UI.