You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you follow the instructions from the website 'Quick start- Game walkthrough' and execute the following steps-
Clone from the whackamole repo
Change directory to whackamole
Run devkit install
-it seems to produce a fatal error involving the jsio module.
`$ devkit install
(node:4684) DeprecationWarning: 'GLOBAL' is deprecated, use 'global'
[install] Installing [email protected]...
Adding [email protected]
[module] set version [email protected]
[install] Copying C:\ucsd\whackthatmole\modules
[cache] installing devkit-core at C:\ucsd\whackthatmole\modules\devkit-core
[module] running install scripts...
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
[email protected] preinstall C:\ucsd\whackthatmole\modules\devkit-core
sh scripts/preinstall.sh
Synchronizing submodule url for 'modules/native-android'
Synchronizing submodule url for 'modules/native-ios'
Synchronizing submodule url for 'modules/squill'
Synchronizing submodule url for 'modules/timestep'
Synchronizing submodule url for 'node_modules/jsio'
fatal: destination path 'C:/UCSD/whackthatmole/modules/devkit-core/node_modules/jsio' already exists and is not an empty directory.
fatal: clone of 'https://github.com/gameclosure/js.io' into submodule path 'C:/UCSD/whackthatmole/modules/devkit-core/node_modules/js io' failed
Failed to clone 'node_modules/jsio'. Retry scheduled
fatal: destination path 'C:/UCSD/whackthatmole/modules/devkit-core/node_modules/jsio' already exists and is not an empty directory.
fatal: clone of 'https://github.com/gameclosure/js.io' into submodule path 'C:/UCSD/whackthatmole/modules/devkit-core/node_modules/js io' failed
Failed to clone 'node_modules/jsio' a second time, aborting
I'm on windows 10 using git bash admin privileges. After this error I simply delete the jsio module and run npm install in the directory to fix it. However I was wondering if this was intentional/unintentional behavior, or even maybe a mistake on my part.
The text was updated successfully, but these errors were encountered:
Using whackamole for reference here.
If you follow the instructions from the website 'Quick start- Game walkthrough' and execute the following steps-
-it seems to produce a fatal error involving the jsio module.
`$ devkit install
(node:4684) DeprecationWarning: 'GLOBAL' is deprecated, use 'global'
[install] Installing [email protected]...
Adding [email protected]
[module] set version [email protected]
[install] Copying C:\ucsd\whackthatmole\modules
[cache] installing devkit-core at C:\ucsd\whackthatmole\modules\devkit-core
[module] running install scripts...
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
Synchronizing submodule url for 'modules/native-android'
Synchronizing submodule url for 'modules/native-ios'
Synchronizing submodule url for 'modules/squill'
Synchronizing submodule url for 'modules/timestep'
Synchronizing submodule url for 'node_modules/jsio'
fatal: destination path 'C:/UCSD/whackthatmole/modules/devkit-core/node_modules/jsio' already exists and is not an empty directory.
fatal: clone of 'https://github.com/gameclosure/js.io' into submodule path 'C:/UCSD/whackthatmole/modules/devkit-core/node_modules/js io' failed
Failed to clone 'node_modules/jsio'. Retry scheduled
fatal: destination path 'C:/UCSD/whackthatmole/modules/devkit-core/node_modules/jsio' already exists and is not an empty directory.
fatal: clone of 'https://github.com/gameclosure/js.io' into submodule path 'C:/UCSD/whackthatmole/modules/devkit-core/node_modules/js io' failed
Failed to clone 'node_modules/jsio' a second time, aborting
[email protected] C:\ucsd\whackthatmole\modules\devkit-core
-- [email protected] extraneous
I'm on windows 10 using git bash admin privileges. After this error I simply delete the jsio module and run npm install in the directory to fix it. However I was wondering if this was intentional/unintentional behavior, or even maybe a mistake on my part.
The text was updated successfully, but these errors were encountered: