15 comments found.
Hi, the ‘live preview’ option doesn’t work. Is there any url where I can see it working? thks
Thanks for sharing more details. Let us check and fix the issue very soon.
Thank you
hello , i have an learning management system and i sell my learning videos and upload videos and courses in my website by changing code. can i use this panel for uploading videos and courses and post some blog without changing code.
Hi,
This template has no any backend related functionality. You need to customize it as per your needs. Let us know if you have any questions.
Thank you
ok this mean i should write the backend of this admin panel myself .for example i should write uploading post functions,myself. is that correct? if it is correct could you tell me some admin panel that have backend related functionality and workwith nodejs.
Hi,
Yes, you are right. Sorry, I am not aware of any admin template which has this working functionality. Let me know if you have any questions.
Thank you
Thanks for the email, however I’m still not able to run the build without errors (see below):
0 info it worked if it ends with ok 1 verbose cli [ ’/usr/local/bin/node’, 1 verbose cli ’/usr/local/lib/node_modules/npm/bin/npm-cli.js’, 1 verbose cli ‘run’, 1 verbose cli ‘build’, 1 verbose cli ‘—scripts-prepend-node-path=auto’ ] 2 info using npm@6.13.4 3 info using node@v10.15.1 4 verbose run-script [ ‘prebuild’, ‘build’, ‘postbuild’ ] 5 info lifecycle Admiria@0.1.0prebuild: Admiria@0.1.0 6 info lifecycle Admiria@0.1.0build: Admiria@0.1.0 7 verbose lifecycle Admiria@0.1.0build: unsafe-perm in lifecycle true 8 verbose lifecycle Admiria@0.1.0build: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/madssidenius/Desktop/Horizontal_Code/node_modules/.bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin 9 verbose lifecycle Admiria@0.1.0build: CWD: /Users/madssidenius/Desktop/Horizontal_Code 10 silly lifecycle Admiria@0.1.0build: Args: [ ‘-c’, ‘react-scripts build’ ] 11 silly lifecycle Admiria@0.1.0build: Returned: code: 1 signal: null 12 info lifecycle Admiria@0.1.0build: Failed to exec build script 13 verbose stack Error: Admiria@0.1.0 build: `react-scripts build` 13 verbose stack Exit status 1 13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16) 13 verbose stack at EventEmitter.emit (events.js:189:13) 13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 13 verbose stack at ChildProcess.emit (events.js:189:13) 13 verbose stack at maybeClose (internal/child_process.js:970:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5) 14 verbose pkgid Admiria@0.1.0 15 verbose cwd /Users/madssidenius/Desktop/Horizontal_Code 16 verbose Darwin 18.7.0 17 verbose argv ”/usr/local/bin/node” ”/usr/local/lib/node_modules/npm/bin/npm-cli.js” “run” “build” “—scripts-prepend-node-path=auto” 18 verbose node v10.15.1 19 verbose npm v6.13.4 20 error code ELIFECYCLE 21 error errno 1 22 error Admiria@0.1.0 build: `react-scripts build` 22 error Exit status 1 23 error Failed at the Admiria@0.1.0 build script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 1, true ]
Which is odd, because test environment works?
ATTENTION: There is no authentication code
Hello,
We didn’t write anywhere in description about authentication is added. Please read description carefully.
Thank you 
You are also not writing that you are using buttons. I expect it
I think you didn’t check how authentication functionality is working on live demo. In such a case you have to register first to login. If you have any kind of issue with functionality then feel free to raise issue in support. We will happy fix them.
Hai, i am facing some issues in using this template (Reactjs). it failed to install all dependencies and shows “found 121 vulnerabilities (66 low, 37 moderate, 18 high)”.please help me the log file is pasted below.
The default interactive shell is now zsh. To update your account to use zsh, please run `chsh -s /bin/zsh`. For more details, please visit https://support.apple.com/kb/HT208050. MohamedSafarbinUbaid-MacBook-Pro:Vertical mohamedsafarbinubaid$ sudo npm i Password: npm WARN deprecated superagent@4.1.0: Please note that v5.0.1+ of superagent removes User-Agent header by default, therefore you may need to add it yourself (e.g. GitHub blocks requests without a User-Agent header). This notice will go away with v5.0.2+ once it is released. npm WARN deprecated material-ui-pickers@2.2.4: You can now upgrade to @material-ui/pickers. Documentation for v2 can be found at https://material-ui-pickers-v2.dmtr-kovalenko.now.sh/ npm WARN deprecated fsevents@1.2.4: Way too old npm WARN deprecated core-js@1.2.7: core-js@<2.6.8 is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2. npm WARN deprecated loadash@0.0.1: Package is unsupport. Please use the lodash package instead. npm WARN deprecated core-js@2.6.4: core-js@<2.6.8 is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2. npm WARN deprecated fsevents@1.2.9: One of your dependencies needs to upgrade to fsevents v2: 1) Proper nodejs v10+ support 2) No more fetching binaries from AWS, smaller package size npm WARN deprecated joi@11.4.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor. npm WARN deprecated hoek@4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated topo@2.0.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues. npm WARN deprecated kleur@2.0.2: Please upgrade to kleur@3 or migrate to ‘ansi-colors’ if you prefer the old syntax. Visit <https://github.com/lukeed/kleur/releases/tag/v3.0.0\> for migration path(s). npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues. npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()
> fsevents@1.2.9 install /Users/mohamedsafarbinubaid/Downloads/Admiria_v1.0.0/React/Vertical/node_modules/chokidar/node_modules/fsevents > node install
node-pre-gyp WARN Using request for node-pre-gyp https download [fsevents] Success: ”/Users/mohamedsafarbinubaid/Downloads/Admiria_v1.0.0/React/Vertical/node_modules/chokidar/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64/fse.node” is installed via remote
> fsevents@1.2.4 install /Users/mohamedsafarbinubaid/Downloads/Admiria_v1.0.0/React/Vertical/node_modules/fsevents > node install
node-pre-gyp WARN Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.2.4/fse-v1.2.4-node-v72-darwin-x64.tar.gz
node-pre-gyp WARN Pre-built binaries not found for fsevents@1.2.4 and node@12.13.0 (node-v72 ABI, unknown) (falling back to source compile with node-gyp)
SOLINK_MODULE(target) Release/.node
CXX Release/obj.target/fse/fsevents.o
../fsevents.cc:50:32: error: no template named ‘Handle’ in namespace ‘v8’
static void Initialize(v8::Handle<v8::Object> exports);
~~^
../fsevents.cc:63:6: warning: field ‘async_resource’ will be initialized after field ‘lockStarted’ [-Wreorder]
: async_resource(“fsevents:FSEvents”), lockStarted(false) {
^
In file included from ../fsevents.cc:82:
../src/constants.cc:89:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagNone”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagNone));
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
In file included from ../fsevents.cc:82:
../src/constants.cc:90:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagMustScanSubDirs”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagMustScan…
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
In file included from ../fsevents.cc:82:
../src/constants.cc:91:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagUserDropped”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagUserDropped));
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
In file included from ../fsevents.cc:82:
../src/constants.cc:92:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagKernelDropped”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagKernelDropped));
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
In file included from ../fsevents.cc:82:
../src/constants.cc:93:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagEventIdsWrapped”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagEventIds…
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
In file included from ../fsevents.cc:82:
../src/constants.cc:94:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagHistoryDone”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagHistoryDone));
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
In file included from ../fsevents.cc:82:
../src/constants.cc:95:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagRootChanged”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagRootChanged));
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
In file included from ../fsevents.cc:82:
../src/constants.cc:96:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagMount”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagMount));
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
In file included from ../fsevents.cc:82:
../src/constants.cc:97:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagUnmount”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagUnmount));
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
In file included from ../fsevents.cc:82:
../src/constants.cc:98:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagItemCreated”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagItemCreated));
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
In file included from ../fsevents.cc:82:
../src/constants.cc:99:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagItemRemoved”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagItemRemoved));
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
In file included from ../fsevents.cc:82:
../src/constants.cc:100:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagItemInodeMetaMod”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagItemIno…
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
In file included from ../fsevents.cc:82:
../src/constants.cc:101:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagItemRenamed”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagItemRenamed));
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
In file included from ../fsevents.cc:82:
../src/constants.cc:102:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagItemModified”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagItemModified));
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
In file included from ../fsevents.cc:82:
../src/constants.cc:103:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagItemFinderInfoMod”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagItemFi…
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
In file included from ../fsevents.cc:82:
../src/constants.cc:104:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagItemChangeOwner”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagItemChan…
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
In file included from ../fsevents.cc:82:
../src/constants.cc:105:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagItemXattrMod”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagItemXattrMod));
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
In file included from ../fsevents.cc:82:
../src/constants.cc:106:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagItemIsFile”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagItemIsFile));
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
In file included from ../fsevents.cc:82:
../src/constants.cc:107:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagItemIsDir”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagItemIsDir));
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
In file included from ../fsevents.cc:82:
../src/constants.cc:108:11: warning: ‘Set’ is deprecated: Use maybe version [-Wdeprecated-declarations]
object->Set(Nan::New<v8::String>(“kFSEventStreamEventFlagItemIsSymlink”).ToLocalChecked(), Nan::New<v8::Integer>(kFSEventStreamEventFlagItemIsSymlink));
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8.h:3402:3: note: ‘Set’ has been explicitly marked deprecated here
V8_DEPRECATED(“Use maybe version”,
^
/Users/mohamedsafarbinubaid/Library/Caches/node-gyp/12.13.0/include/node/v8config.h:311:29: note: expanded from macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
../fsevents.cc:85:16: error: variable has incomplete type ‘void’
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
^
../fsevents.cc:85:31: error: no member named ‘Handle’ in namespace ‘v8’
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
~~^
../fsevents.cc:85:48: error: expected ‘(’ for function-style cast or type construction
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
~~~~~~^
../fsevents.cc:85:50: error: use of undeclared identifier ‘exports’
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
^
../fsevents.cc:85:58: error: expected ’;’ after top level declarator
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
^
;
21 warnings and 6 errors generated.
make: * [Release/obj.target/fse/fsevents.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack at ChildProcess.emit (events.js:210:5)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Darwin 19.0.0
gyp ERR! command ”/usr/local/bin/node” ”/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js” “build” “-fallback-to-build” “-module=/Users/mohamedsafarbinubaid/Downloads/Admiria_v1.0.0/React/Vertical/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64/fse.node” “-module_name=fse” “-module_path=/Users/mohamedsafarbinubaid/Downloads/Admiria_v1.0.0/React/Vertical/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64” “-napi_version=5” “-node_abi_napi=napi”
gyp ERR! cwd /Users/mohamedsafarbinubaid/Downloads/Admiria_v1.0.0/React/Vertical/node_modules/fsevents
gyp ERR! node -v v12.13.0
gyp ERR! node-gyp -v v5.0.5
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute ’/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build—fallback-to-build—module=/Users/mohamedsafarbinubaid/Downloads/Admiria_v1.0.0/React/Vertical/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64/fse.node—module_name=fse—module_path=/Users/mohamedsafarbinubaid/Downloads/Admiria_v1.0.0/React/Vertical/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64—napi_version=5—node_abi_napi=napi’ (1)
node-pre-gyp ERR! stack at ChildProcess.<anonymous> (/Users/mohamedsafarbinubaid/Downloads/Admiria_v1.0.0/React/Vertical/node_modules/fsevents/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:210:5)
node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:1021:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
node-pre-gyp ERR! System Darwin 19.0.0
node-pre-gyp ERR! command ”/usr/local/bin/node” ”/Users/mohamedsafarbinubaid/Downloads/Admiria_v1.0.0/React/Vertical/node_modules/fsevents/node_modules/node-pre-gyp/bin/node-pre-gyp” “install” “—fallback-to-build”
node-pre-gyp ERR! cwd /Users/mohamedsafarbinubaid/Downloads/Admiria_v1.0.0/React/Vertical/node_modules/fsevents
node-pre-gyp ERR! node -v v12.13.0
node-pre-gyp ERR! node-pre-gyp -v v0.10.0
node-pre-gyp ERR! not ok
Failed to execute ’/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build—fallback-to-build—module=/Users/mohamedsafarbinubaid/Downloads/Admiria_v1.0.0/React/Vertical/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64/fse.node—module_name=fse—module_path=/Users/mohamedsafarbinubaid/Downloads/Admiria_v1.0.0/React/Vertical/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64—napi_version=5—node_abi_napi=napi’ (1)
> core-js@2.6.10 postinstall /Users/mohamedsafarbinubaid/Downloads/Admiria_v1.0.0/React/Vertical/node_modules/core-js > node postinstall || echo “ignore”
Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: > https://opencollective.com/core-js > https://www.patreon.com/zloirock
Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
> jss@9.8.7 postinstall /Users/mohamedsafarbinubaid/Downloads/Admiria_v1.0.0/React/Vertical/node_modules/jss > node -e “console.log(’\u001b[35m\u001b[1mLove JSS? You can now support us on open collective:\u001b[22m\u001b[39m\n > \u001b[34mhttps://opencollective.com/jss/donate\u001b[0m')"
Love JSS? You can now support us on open collective: > https://opencollective.com/jss/donate
> react-native-elements@1.2.7 postinstall /Users/mohamedsafarbinubaid/Downloads/Admiria_v1.0.0/React/Vertical/node_modules/react-native-elements > opencollective-postinstall || exit 0
Thank you for using react-native-elements! If you rely on this package, please consider supporting our open collective: > https://opencollective.com/react-native-elements/donate
npm notice created a lockfile as package-lock.json. You should commit this file. npm WARN react-canvas-knob@0.5.0 requires a peer of react@15.3.2 but none is installed. You must install peer dependencies yourself. npm WARN react-native-elements@1.2.7 requires a peer of react-native-vector-icons@>6.0.0 but none is installed. You must install peer dependencies yourself. npm WARN react-rangeslider@2.2.0 requires a peer of react@0.14.0 || 15.0.0 but none is installed. You must install peer dependencies yourself. npm WARN react-scrollbar-js@1.0.1 requires a peer of react@15.0.0||14.0.0 but none is installed. You must install peer dependencies yourself. npm WARN jsdom@15.2.1 requires a peer of canvas@2.5.0 but none is installed. You must install peer dependencies yourself. npm WARN The package webpack is included as both a dev and production dependency. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents): npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 install: `node install` npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
added 2620 packages from 1821 contributors and audited 53023 packages in 51.248s found 121 vulnerabilities (66 low, 37 moderate, 18 high) run `npm audit fix` to fix them, or `npm audit` for details MohamedSafarbinUbaid-MacBook-Pro:Vertical mohamedsafarbinubaid$ sudo npm audit fix npm ERR! code ELOCKVERIFY npm ERR! Errors were found in your package-lock.json, run npm install to fix them. npm ERR! Invalid: lock file’s webpack@4.19.1 does not satisfy webpack@^4.29.5
npm ERR! A complete log of this run can be found in: npm ERR! /Users/mohamedsafarbinubaid/.npm/_logs/2019-11-15T05_34_22_553Z-debug.log MohamedSafarbinUbaid-MacBook-Pro:Vertical mohamedsafarbinubaid$
Hello,
Thank you for sharing with us we will fix this issue in next upcoming update of react js. You can ask for support for this kind of issue to get is done quickly.
Thank you 
yes i would like to get support from you. please guide me what to do to fix this?
You can email us on themesbrand at gmail dot com or contact us from support tab from theme page.
Hi Pre buyer questions
1. Can we add our menu to the dashboard? 2. Can we use javascript to send forms/data entry to the template if we create own menu? 3. Does this allow API authentication? 4. Does this allow stripe/paypal gateway?
Hello,
1. Yes you can add and remove menu items. 2. Yes you can do customisation as you want. There is no any restriction to add new features. 3. No you need to implement API authentication. 4. There is no payment gateway integration is provided in this template. You can hire dev to add add those features.
Let us know if you have any questions.
Thank you 
Hello,
1. Yes you can add and remove menu items. 2. Yes you can do customisation as you want. There is no any restriction to add new features. 3. No you need to implement API authentication. 4. There is no payment gateway integration is provided in this template. You can hire dev to add add those features.
Let us know if you have any questions.
Thank you 
Congratulations! Nice Work, GLWS. & I am looking for buy this one for my own project. but i have question 1. it have all function as you mention like node js. php. and docomention because i want to edit and make my own working project thanks
Hello, We have converted html template to node.js and PHP version but not with backend functionalities. Also have documentation with folder structure and setup guidance.
Hi, Does your PHP version have code and database?
Hello,
Sorry we have not done any database related code in PHP Version.
Hello, What is the bdd (backend) used with react please ?
Hello, We have not implemented backend functionality in this template.
Hello, the theme looks great. Is the authentication logic (user login) and other backend php logic included, or just the front end code? Thanks
It’s just frontend code. We are planning to provide authentication functionality in next upcoming update.
Great work…best of luck with sales
Thank you 
Congratulations!!! Nice Work, Good Luck With Sale 
Thank you 
Congratulations! Nice Work, Good Luck With Sale 
Thank you 
Great Work, Congratulations GLWS 
Thank you 
Nice Work, GLWS 
Thank you 