Closed rwjlewis closed 8 years ago
Please provide the following information: Windows version nodejs version ruby version python version Are you using cmd.exe or another shell? Did you install slush-marklogic-node from the npm repository or the latest from github?
Thanks!
Windows 7(6.1 Build 7601: Service Pack 1) node.js 0.10.36 ruby 2.2.3 python 3.5
cmd (as administrator and as normal) I installed both versions with no positive results
This process works with a fresh install of Windows 7 sp1 with the following potential differences from your environment:
Did the suggestions from @bluetorch help? Can we close this ticket?
Any votes for closing this?
Nothing has changed regarding the bugs as far as I know, so why move to close ?
No news sounded like good news. Did the suggestions of bluetorch help you?
We qualified bugs, but the bugs haven't been fixed via code updates.
The primary problem with @rwjlewis install is that he is using node 0.10.x with an old npm version (1.x). The reason for using node 0.10.x is for compatibility with MarkLogic Node Client API. The documentation for the Node Client API requires the latest version of npm. Unfortunately npm in this scenario is unable to update itself, so extra manual steps are required and are now outlined in the WINDOWS.mdown document.
@rwjlewis Satisfied with this resolution?
Didn't receive a reply so far, closing the ticket for now, so we can proceed with releasing 1.0.2.
Please reopen the ticket if anyone feels it wasn't solved satisfactory..
Due to the diffence in Windows commands for navigating directories. The install will fail, for example the error log contains this issue: These errors are returned – it is an automated process so there shouldn’t be a file missing, unless the there is a step not defined in the above directions to "cd" into the directory which would require a break-point in the script.
0 info it worked if it ends with ok 1 verbose cli [ 'C:\Program Files\nodejs\\node.exe', 1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js', 1 verbose cli 'install' ] 2 info using npm@1.4.28 3 info using node@v0.10.36 4 verbose node symlink C:\Program Files\nodejs\node.exe 5 error install Couldn't read dependencies 6 error package.json ENOENT, open 'C:\Users\rlewis\Downloads\package.json' 6 error package.json This is most likely not a problem with npm itself. 6 error package.json npm can't find a package.json file in your current directory. 7 error System Windows_NT 6.1.7601 8 error command "C:\Program Files\nodejs\\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" 9 error cwd C:\Users\rlewis\Downloads 10 error node -v v0.10.36 11 error npm -v 1.4.28 12 error path C:\Users\rlewis\Downloads\package.json 13 error code ENOPACKAGEJSON 14 error errno 34 15 verbose exit [ 34, true ]
The below process isolates where in the steps, the issue arises: Run the generator Go to the directory where your new project will be created (the parent). Then: slush marklogic-node
This will ask you several questions, with some intelligent defaults.
Configure your application
Go to the generated application directory:
cd {app-name}
Note the slush command is what generates the below error without any break-point to cd into the {app-name}