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
Thank you for creating this cryptocurrency generator. I am running this from a windows machine, and get tons of errors when I attempt to npm run nxt (truncated error below). I attempted to follow the troubleshooting steps as you suggest in the how-to, but I was unable to locate the win-compile.sh file after git clone & npm install.
Can you advise as you what I need to do to get this to work in windows 10?
Thank you for your consideration.
==========================================
symbol: class JSONStreamAware
location: class JSONResponses
src\java\nxt\http\JSONResponses.java:36: error: cannot find symbol
public static final JSONStreamAware INCORRECT_PUBLIC_KEY = incorrect("publicKey");
^
symbol: class JSONStreamAware
location: class JSONResponses
Note: src\java\nxt\http\APIEnum.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
100 errors
Starting default mode
Error: Could not find or load main class nxt.Nxt
←[37;40mnpm←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mcode←[0m ELIFECYCLE
←[0m←[37;40mnpm←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35merrno←[0m 1
←[0m←[37;40mnpm←[0m ←[0m←[31;40mERR!←[0m←[35m←[0m [email protected] nxt: cd nxt ; sh ./compile.sh ; sh ./run.sh
←[0m←[37;40mnpm←[0m ←[0m←[31;40mERR!←[0m←[35m←[0m Exit status 1
←[0m←[37;40mnpm←[0m ←[0m←[31;40mERR!←[0m←[35m←[0m
←[0m←[37;40mnpm←[0m ←[0m←[31;40mERR!←[0m←[35m←[0m Failed at the [email protected] nxt script.
←[0m←[37;40mnpm←[0m ←[0m←[31;40mERR!←[0m←[35m←[0m This is probably not a problem with npm. There is likely additional logging output above.
←[0m
←[37;40mnpm←[0m ←[0m←[31;40mERR!←[0m←[35m←[0m A complete log of this run can be found in:
←[0m←[37;40mnpm←[0m ←[0m←[31;40mERR!←[0m←[35m←[0m
C:\Users\j22va\AppData\Roaming\npm-cache_logs\2021-05-16T02_25_00_766Z-debug.log
←[0m
The text was updated successfully, but these errors were encountered:
Hi @sandoche,
Thank you for creating this cryptocurrency generator. I am running this from a windows machine, and get tons of errors when I attempt to npm run nxt (truncated error below). I attempted to follow the troubleshooting steps as you suggest in the how-to, but I was unable to locate the win-compile.sh file after git clone & npm install.
Can you advise as you what I need to do to get this to work in windows 10?
Thank you for your consideration.
==========================================
symbol: class JSONStreamAware
location: class JSONResponses
src\java\nxt\http\JSONResponses.java:36: error: cannot find symbol
public static final JSONStreamAware INCORRECT_PUBLIC_KEY = incorrect("publicKey");
^
symbol: class JSONStreamAware
location: class JSONResponses
Note: src\java\nxt\http\APIEnum.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
100 errors
Starting default mode
Error: Could not find or load main class nxt.Nxt
←[37;40mnpm←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mcode←[0m ELIFECYCLE
←[0m←[37;40mnpm←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35merrno←[0m 1
←[0m←[37;40mnpm←[0m ←[0m←[31;40mERR!←[0m←[35m←[0m [email protected] nxt:
cd nxt ; sh ./compile.sh ; sh ./run.sh
←[0m←[37;40mnpm←[0m ←[0m←[31;40mERR!←[0m←[35m←[0m Exit status 1
←[0m←[37;40mnpm←[0m ←[0m←[31;40mERR!←[0m←[35m←[0m
←[0m←[37;40mnpm←[0m ←[0m←[31;40mERR!←[0m←[35m←[0m Failed at the [email protected] nxt script.
←[0m←[37;40mnpm←[0m ←[0m←[31;40mERR!←[0m←[35m←[0m This is probably not a problem with npm. There is likely additional logging output above.
←[0m
←[37;40mnpm←[0m ←[0m←[31;40mERR!←[0m←[35m←[0m A complete log of this run can be found in:
←[0m←[37;40mnpm←[0m ←[0m←[31;40mERR!←[0m←[35m←[0m
C:\Users\j22va\AppData\Roaming\npm-cache_logs\2021-05-16T02_25_00_766Z-debug.log
←[0m
The text was updated successfully, but these errors were encountered: