How do you run the demo? #45
Comments
|
|
From a fresh clone doing only that (starting inside c:\code\origami, and cd origami is to go into c:\code\origami\origami), on the npm run build I get this: |
|
Otherwise, assuming the first cd was to get into the main package and not the sub-package, I get this error: |
|
Yes, I'm sorry. I had assumed you already ran You should be in the root folder of the project (where |
|
I'd tried doing npm install initially, but the npm install seems to spit out a multitude of errors, which is why I assumed I was just missing a step or doing the wrong thing. cd origami/ Latest version of stable node and npm, running npm install gives an error npm-debug.log 11,000 lines long, the last few lines being: Where the previous 10,000 lines before the start of this were the same "no script for install, continuing" loop that you see at the top of this log for a few hundred more modules. |
|
This might be a problem with Windows and the I don't know if If that doesn't work, you can go into the As a last step, you can also ignore the build and go directly into the |
|
That was cmd.exe, but did also try in powershell. Running the npm install in powershell, it starts talking about Python path being missing first, which is weird: And running npm run build gives an error at that point, but after replacing the "&&"s with ";"s it seems to finish building (? no errors but no dist file created though). Bower install seems to work fine, but then running npm install in demo... (sigh): I assume you meant npm install and not npm run install because that gives: EDIT: Forgot to add this bit EDIT 2: Next, it seems that in your app.module.ts you're trying to import @codebakery/origami/collections when the real location is @codebakery/origami/lib/collections Then... It works :D |
|
It's saying the I noticed you're running an older version of npm. If you want to bypass the build and just use the latest version on npm, you'll need to add |
|
Sorry, already made edits to previous comment. Please re-read. |
|
As for npm, I updated node today and that updated my npm version from 3.9 to 3.10.10, so assumed that was latest. Seems that the node stable install goes back that far. I'm on 5.2.0 now, cheers. |
|
If I read correctly, you were able to install origami from npm and the demo is working after changing the collections import path? For the build issues, I'm guessing replacing ^ hopefully that sheds light on why I use excessive You could also try |
|
Yes, after changing the && to ; the build gave no errors but didn't create a dist, tried in Powershell and cmd.exe, on the latest version (5.2.0) of npm. Then by using which gave errors, as that isn't where collections is, to followed by Were you trying to use && to mean Possibly (?) relevant docs here: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/ntcmds_shelloverview.mspx?mfr=true And this thread of people arguing seems helpful: |
|
Sounds good! I'm going to close this since you've got the demo running. The collection import change is something that hasn't been published yet, which is why you had to modify when running from npm's version. Yea, I develop in a Unix bash environment. It's always a challenge getting builds to work cross platform. |
How do we run the demo contained within this project?
The text was updated successfully, but these errors were encountered: