-
-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Attempting to set up. #5
Comments
if "npm update" fails, then there is a problem with your node installation |
I fixed the NPM update problem. Now when I run npm start it get the following result. `C:\Downloads\apps-1.0.61\apps-1.0.61 (gridspace-apps@1.0.61) C:\Downloads\apps-1.0.61\apps-1.0.61 (gridspace-apps@1.0.61)
{ update_cache: 'js/ext-n3d.js' } undefined:1555 npm ERR! Windows_NT 10.0.14393 npm ERR! Please include the following file with any support request: C:\Downloads\apps-1.0.61\apps-1.0.61 (gridspace-apps@1.0.61) |
this may be a windows-specific issue. i just cloned the repo and followed the readme and it's working on mac and linux. |
What version of node are you using? |
any version above 8.1 |
Ok. I got it working on linux. Is there a build script to make a static build that dose not require node to be hosting it. By the way thanks so mush for open sourcing this thing. I found it to be very quick and my current slicing set up take place on the web server side at the cost of resources. This pushes all of that nativity to the local client witch is great. |
And where is your donate button. |
lower right link on the wiki: https://github.com/GridSpace/apps/wiki |
That's awesome. Is there a build script to make a static copy of the app to be uploaded to a regular web server? |
it's not my use case, so I have not invested time to do it. thanks for the donation! |
I would be very interested in such a feature if you find the time or desire to implement. |
Hey Stewart! I'm having the same issue on a Windows machine. I think it has to do with windows slashes in filePath on line 86 on web-server.js. |
slashes should be converted on windows. are there spaces in your path?
… On Sep 10, 2017, at 5:58 PM, John Scimone ***@***.***> wrote:
Hey Stewart! I'm having the same issue on a Windows machine. I think it has to do with windows slashes in filePath on line 86.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I've replicated this and it looks like a problem with windows not supporting sym-links. Looking into a workaround. |
Simple solution, when cloning the repo on windows, you need to enable symlinks like so: git clone -c core.symlinks=true [repo-url] |
i receive the following error when using the latest node.js on windows.
`C:\laragon\www\kirt modo\apps (master) (gridspace-apps@1.0.61)
λ npm update
openssl config failed: error:02001003:system library:fopen:No such process
openssl config failed: error:02001003:system library:fopen:No such process
C:\laragon\www\kirt modo\apps (master) (gridspace-apps@1.0.61)
λ npm start
openssl config failed: error:02001003:system library:fopen:No such process
openssl config failed: error:02001003:system library:fopen:No such process
openssl config failed: error:02001003:system library:fopen:No such process
{ update_cache: 'js/ext-n3d.js' }
undefined:1625
throw new JS_Parse_Error(message, filename, line, col, pos);
^
SyntaxError: Unexpected token: punc (.)
at JS_Parse_Error.get (eval at (C:\laragon\www\kirt modo\apps\node_modules\uglify-js\tools\node.js:27:1), :86:23)
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\laragon\bin\nodejs\node.exe" "C:\laragon\bin\nodejs\node_modules\npm\bin\npm-cli.js" "start"
npm ERR! node v6.11.3
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! gridspace-apps@1.0.61 start:
node js/web-server debug
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the gridspace-apps@1.0.61 start script 'node js/web-server debug'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the gridspace-apps package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node js/web-server debug
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs gridspace-apps
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls gridspace-apps
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! C:\laragon\www\kirt modo\apps\npm-debug.log
`
The text was updated successfully, but these errors were encountered: