405 comments found.
Hi,
We have a theme that we purchased from you, that we are having trouble with, can i be really honest and say from what ive read you just cont be bothered in answering any questions and i think this just isnt right, if you dont answer within a decent time scale i will be leaving you the worst possible review ! So i guess its up to you.
Cheers
I’ve to ask a refund for this theme. Typescript integration is mandatory, but here we cannot find it.
Sorry for this request.
thanks a lot
Hi The downloaded source code does not have complete documentation on how to customize the code for Laravel. Our tech team would like to know how to go about understanding and customizing the code in our Laravel application.
Please assist 3847196f-417f-4ce3-8600-06ae77b1638c is the license code
error While resolving: reactify@5.12.0
Do you have a simple version with multivendor login?
Could you please send me the best backend to connect to this app? Please?
Can you send me a simple backend that easily connects to this please?
the author is dead if u buy now you will not get support unless if you have great knowledge on how to fit it your self
Have done with setup and template working fine. Facing below issue.
Issue desc: How to deploy dist source in apache sub folder like /var/www/html/interface. If we extract dist files in /var/www/html then it’s working fine but not in subfolders. Can you let us know the required changes to do for the setup.
We need to use React source with Java Spring boot backend, is this template is flexible to do this?
Hi, I sent an email because I cannot install the script due to many errors on the dependencies. Please respond.
Hello, I have problems accessing the website https://reactify.theironnetwork.org/, please request support.
Hi,
This issue is present in react-saga-seed sample project as well
https://stackoverflow.com/questions/55341894/redux-saga-function-is-called-twice
https://spectrum.chat/react-boilerplate/general/issue-with-sagas-being-initialized-twice-maybe-related-to-async-containers~893a7eee-e23c-41cc-8cf8-d828f8ffea14
Issue description:
While calling saga action, action is triggering once but corresponding generator function is triggering twice. Due to this one extra api call is initiating
can we please check this and let us know the resolution for this
Hi,
I am unable to find any working solution till now. This issue is present in their react-saga-seed sample
https://stackoverflow.com/questions/55341894/redux-saga-function-is-called-twice https://spectrum.chat/react-boilerplate/general/issue-with-sagas-being-initialized-twice-maybe-related-to-async-containers~893a7eee-e23c-41cc-8cf8-d828f8ffea14 Issue description:While calling saga action, action is triggering once but corresponding generator function is triggering twice. Due to this one extra api call is initiating
hey, this template doesn’t compile, please help me! this run on a old version o react fuuu
I’m running the app on Node V18 and I have the following errors:
npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated flatten@1.0.3: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated @hapi/bourne@1.3.2: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/topo@3.1.6: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated sane@4.1.0: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated formidable@1.2.6: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm WARN deprecated babel-eslint@10.1.0: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated @hapi/address@2.1.4: Moved to ‘npm install @sideway/address’
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated rollup-plugin-babel@4.4.0: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-babel.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated @hapi/hoek@8.5.1: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @babel/polyfill@7.12.1: This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information.
npm WARN deprecated @hapi/joi@15.1.1: Switch to ‘npm install joi’
npm WARN deprecated svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated intl-messageformat-parser@1.4.0: We’ve written a new parser that’s 6x faster and is backwards compatible. Please use @formatjs/icu-messageformat-parser
npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
npm WARN deprecated intl-relativeformat@2.2.0: This package has been deprecated, please see migration guide at ‘https://github.com/formatjs/formatjs/tree/master/packages/intl-relativeformat#migration-guide'
npm WARN deprecated source-map-resolve@0.6.0: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated superagent@5.3.1: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>.
npm WARN deprecated core-js@2.6.12: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js@2.6.12: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js@2.6.12: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated react-toggle-switch@3.0.4: This package is no longer maintained. Please try something like react-switch instead.
npm WARN deprecated react-jvectormap@0.0.16: This package is deprecated. Please start using @react-jvectormap/core instead
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm ERR! code 1
npm ERR! path /Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/node-sass
npm ERR! command failed
npm ERR! command sh -c node scripts/build.js
npm ERR! Building: /opt/homebrew/Cellar/node/18.0.0/bin/node /Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/node-gyp/bin/node-gyp.js rebuild—verbose—libsass_ext=—libsass_cflags=—libsass_ldflags=—libsass_library=
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp verb cli [
npm ERR! gyp verb cli ’/opt/homebrew/Cellar/node/18.0.0/bin/node’,
npm ERR! gyp verb cli ’/Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/node-gyp/bin/node-gyp.js’,
npm ERR! gyp verb cli ‘rebuild’,
npm ERR! gyp verb cli ‘—verbose’,
npm ERR! gyp verb cli ‘—libsass_ext=’,
npm ERR! gyp verb cli ‘—libsass_cflags=’,
npm ERR! gyp verb cli ‘—libsass_ldflags=’,
npm ERR! gyp verb cli ‘—libsass_library=’
npm ERR! gyp verb cli ]
npm ERR! gyp info using node-gyp@3.8.0
npm ERR! gyp info using node@18.0.0 | darwin | arm64
npm ERR! gyp verb command rebuild []
npm ERR! gyp verb command clean []
npm ERR! gyp verb clean removing “build” directory
npm ERR! gyp verb command configure []
npm ERR! gyp verb check python checking for Python executable “python2” in the PATH
npm ERR! gyp verb `which` failed Error: not found: python2
npm ERR! gyp verb `which` failed at getNotFoundError (/Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/which/which.js:13:12)
npm ERR! gyp verb `which` failed at F (/Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/which/which.js:68:19)
npm ERR! gyp verb `which` failed at E (/Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/which/which.js:80:29)
npm ERR! gyp verb `which` failed at /Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/which/which.js:89:16
npm ERR! gyp verb `which` failed at /Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/isexe/index.js:42:5
npm ERR! gyp verb `which` failed at /Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/isexe/mode.js:8:5
npm ERR! gyp verb `which` failed at FSReqCallback.oncomplete (node:fs:203:21)
npm ERR! gyp verb `which` failed python2 Error: not found: python2
npm ERR! gyp verb `which` failed at getNotFoundError (/Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/which/which.js:13:12)
npm ERR! gyp verb `which` failed at F (/Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/which/which.js:68:19)
npm ERR! gyp verb `which` failed at E (/Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/which/which.js:80:29)
npm ERR! gyp verb `which` failed at /Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/which/which.js:89:16
npm ERR! gyp verb `which` failed at /Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/isexe/index.js:42:5
npm ERR! gyp verb `which` failed at /Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/isexe/mode.js:8:5
npm ERR! gyp verb `which` failed at FSReqCallback.oncomplete (node:fs:203:21) {
npm ERR! gyp verb `which` failed code: ‘ENOENT’
npm ERR! gyp verb `which` failed }
npm ERR! gyp verb check python checking for Python executable “python” in the PATH
npm ERR! gyp verb `which` failed Error: not found: python
npm ERR! gyp verb `which` failed at getNotFoundError (/Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/which/which.js:13:12)
npm ERR! gyp verb `which` failed at F (/Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/which/which.js:68:19)
npm ERR! gyp verb `which` failed at E (/Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/which/which.js:80:29)
npm ERR! gyp verb `which` failed at /Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/which/which.js:89:16
npm ERR! gyp verb `which` failed at /Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/isexe/index.js:42:5
npm ERR! gyp verb `which` failed at /Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/isexe/mode.js:8:5
npm ERR! gyp verb `which` failed at FSReqCallback.oncomplete (node:fs:203:21)
npm ERR! gyp verb `which` failed python Error: not found: python
npm ERR! gyp verb `which` failed at getNotFoundError (/Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/which/which.js:13:12)
npm ERR! gyp verb `which` failed at F (/Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/which/which.js:68:19)
npm ERR! gyp verb `which` failed at E (/Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/which/which.js:80:29)
npm ERR! gyp verb `which` failed at /Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/which/which.js:89:16
npm ERR! gyp verb `which` failed at /Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/isexe/index.js:42:5
npm ERR! gyp verb `which` failed at /Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/isexe/mode.js:8:5
npm ERR! gyp verb `which` failed at FSReqCallback.oncomplete (node:fs:203:21) {
npm ERR! gyp verb `which` failed code: ‘ENOENT’
npm ERR! gyp verb `which` failed }
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: Can’t find Python executable “python”, you can set the PYTHON env variable.
npm ERR! gyp ERR! stack at PythonFinder.failNoPython (/Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/node-gyp/lib/configure.js:484:19)
npm ERR! gyp ERR! stack at PythonFinder.<anonymous> (/Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/node-gyp/lib/configure.js:406:16)
npm ERR! gyp ERR! stack at F (/Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/which/which.js:68:16)
npm ERR! gyp ERR! stack at E (/Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/which/which.js:80:29)
npm ERR! gyp ERR! stack at /Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/which/which.js:89:16
npm ERR! gyp ERR! stack at /Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/isexe/index.js:42:5
npm ERR! gyp ERR! stack at /Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/isexe/mode.js:8:5
npm ERR! gyp ERR! stack at FSReqCallback.oncomplete (node:fs:203:21)
npm ERR! gyp ERR! System Darwin 21.4.0
npm ERR! gyp ERR! command ”/opt/homebrew/Cellar/node/18.0.0/bin/node” ”/Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/node-gyp/bin/node-gyp.js” “rebuild” “-verbose” “-libsass_ext=” “-libsass_cflags=” “-libsass_ldflags=” “—libsass_library=”
npm ERR! gyp ERR! cwd /Users/victorhernandez/Documents/dev/themes/reactify-5110/reactify-hooks/reactify-redux-thunk/node_modules/node-sass
npm ERR! gyp ERR! node -v v18.0.0
npm ERR! gyp ERR! node-gyp -v v3.8.0
npm ERR! gyp ERR! not ok
npm ERR! Build failed with error code: 1
npm ERR! A complete log of this run can be found in:
Hello, I just tried to install the template with `npm install` and it fails. How can I get it to work?
$ npm install npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: reactify@5.11.0 npm ERR! Found: react@17.0.2 npm ERR! node_modules/react npm ERR! dev react@”17.0.1” from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer react@”15.0.0 || 16.0.0” from react-credit-cards@0.8.3 npm ERR! node_modules/react-credit-cards npm ERR! react-credit-cards@”0.8.2” from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with—force, or—legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
if I try ‘npm install—legacy-peer-deps` it finished but I get warnings about many packages that are now deprecated…please advise
I’m having trouble installing this theme: Getting “Socket Timeout” Error on install of dependencies (node_modules) I was running this inside the terminal of VS Code inside the root directory i.e. inside “reactify-saga-seed” directory that contains the package.json file and the system configuration are as follows: Windows 10 version 20H2 Home Single Language running on a 64-bit OS and x64-based processor with 19042.1586 as the OS build. The command that I ran were “npm i” and I have also removed the proxy by running the command “npm config rm proxy” and “npm config rm https-proxy” and also cleaned the cache using “npm clean cache—force” but still the installation crashes. The npm version I used was 8.5.2 and the NodeJS version I used was 16.14.2
I’m still having trouble installing the theme. The original SOCKET TIMEOUT error has been fixed, and also the Node SASS dependency, but now I can only see the main page without any items. Even with the react-hooks versions of reactify-saga-seed and reactify-thunk-seed, no other items appear in the menu. Is there some obvious fix?
Hi,
Thanks for reaching out!
Please use the reactify-redux-thunk and reactify-redux-saga packages for all default data and to know more please check the documentation.
https://docs.theironnetwork.org/reactify/folder-structure/Let us know if you need anything else at support@theironnetwork.org
Thanks and have a nice day!
Hi, why it work on localhost:3000, but dont work on production. After npm run build I see only white blank and errors in console about 404 files. But if change paths to file correct, errors are empty, but page white again.
Hi,
Thanks for reaching out!
It seems that your support has expired so please renew the same.
Thanks and have a nice day!
Hi, I Buy this but it was a choosing mistake Can I ask Refund?